Everyone can help darcs be great, and this page is here to tell you how you can help.
You can run darcs on your projects, and let us know how it goes. In particular, we’d like to know how it works on your repositories. You probably use quite a different set of darcs’ features than we do. Let us know about:
- Bugs. Bonus points if you can produce a shell script that reproduces the bug, so we can add it to our test suite, and thus reduce the danger of the same bug reappearing later.
- Garden this wiki
- Garden the wikipedia page of Darcs and/or translate it in your language if it does not exist.
- Triage the BugTracker! If there are no new bugs to triage, look for stale bug reports or check up on people we need follow-ups from, etc.
- Commands that run unusually slowly
- Run timings (see Benchmarks).
- Bonus points for producing a shell script to demonstrate the poor behavior.
- Feature requests. When you’re using darcs (particularly hashed repositories) is there something that seems like it would make your life easier? Please, focus on features in some way related to the changes in darcs.
- Your impression: which new features do you like, what do you find confusing?
- Documentation: Read the documentation, and let us know what’s unclear. Even better, write improved documentation and send us a patch.
- Come at Sprints and work on documentation, ask questions, etc.
- You can also consider donating.
- Check the bug tracker.
http://tinyurl.com/darcs-probablyeasy2- easy bugs to solve
- Come at Sprints and hack on the code!
- Apply for a Summer of Code student project
- Help us use external libraries instead of our own implementations (see DarcsLibraries)
- See Development/Tasks for more substantial asks.