Poll PositionLook before you build

Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.

Darcs

The original patch-theory DVCS (2003), written in Haskell; inspired Pijul and jj's conflict model.

darcs.net/Maintenance

Last release Darcs 2.18.5 in January 2025 (darcs.net release list); no 2026 release found. (checked 2026-10-25)

In Version control beyond git

Where it stands apart

What it shares with most of the community

Nearest neighbors

Every answer

QuestionAnswerSource
Is it actively maintained?stands apart maintenance or slowingsource
2026-10-25
How is the main thing licensed?copyleft or source-available with restrictions
GPL-2.0-or-later.
source
2026-10-25
How is it mainly sustained?stands apart community, foundation, or research
Software Freedom Conservancy member project with donation link; volunteer-run.
source
2026-10-26
Can it run entirely on your own device or infrastructure, without the maker's servers?yessource
2026-10-25
Do you need an account to use it?no account
Local VCS; no central server, works offline.
source
2026-10-26
Who is it for?developerssource
2026-10-25
Which shared standard or format does it mainly build on?none of these (its own format or interface)
Own patch format; one-time git import/export only.
source
2026-10-26
How does it relate to git repositories?stands apart own storage format, one-time import or no git interop
darcs convert import/export; no live interop.
source
2026-10-25
Where does the authoritative copy of a project live?every clone is a full peer; servers are optionalsource
2026-10-25
Can you commit, branch, and read history with no network connection?yessource
2026-10-25
Is it designed with AI coding agents in mind?nosource
2026-10-25
Which layer of the stack does it mainly replace?the version control system itselfsource
2026-10-25
What is the basic unit of history? (pick the most specific that applies)stands apart patches that commutesource
2026-10-25
Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow?no
Patch dependencies are implicit; no stacked-review workflow.
source
2026-10-25
How are merge conflicts mainly handled?stands apart first-class: a conflict can be recorded and resolved later
Conflicting patches can coexist in the repository and are marked for later resolution.
source
2026-10-25
What size of project is it designed for?ordinary source repositoriessource
2026-10-25
Is code review part of the product?no review workflowsource
2026-10-25

Sources

This page was derived from:

RSS for this project

Are you a maintainer? Claiming and correcting projects is coming soon.