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 (mail us at firstname.lastname@example.org).
- 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).
- Feature requests. When you’re using darcs is there something that seems like it would make your life easier?
- 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.
- You can also consider donating.
- Implement or update Darcs support for GeanyVC or QCT
- Implement or update Darcs support for Meld or RabbitVCS
- 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
- Work on wome project idea for fun and/or for your studies
- Help us use external libraries instead of our own implementations (see DarcsLibraries)