DarcsTeam

Like many free and open source projects, darcs is running on spare time and pure enthusiasm. We need your help! Here are the roles which we are currently filling and that we would like to fill.

Review team

We hope to grow the review team over time. Members of the team will be asked to review patches on a regular basis and to push them into mainline Darcs as they see fit.

Interested in joining? It's the best way to get to know the Darcs code. Subscribe to darcs-users and start reviewing some patches today. We'll be sure to notice!

Managers

Release manager

Issue manager

Patch manager

  • Jobs

    • Ensure that patches are reviewed in a timely manner
    • Chase up on people as amendments are requested.

  • filled by: nobody, help wanted!

Documentation manager

  • Jobs

    • FAQ maintainance
    • wiki gardening
    • tutorials and docs

  • filled by: Trent Buck

Communications team

Marketing team

Making sure people understand what darcs does that other distributed RCSes do not

Events manager

The events manager makes sure that we can have regular hacking sprints, twice a year. Part of this job includes fundraising.

  • Jobs

    • find venues for Sprints
    • prepare sprints, organise beginner tasks, get people up to speed
    • co-ordinate with Haskell Hackathon and other hacking projects
    • obtain sponsorship or funding if needed

  • filled by: EricKow (help wanted!)

Platform czars and liaisons

Packagers produce official darcs.net binaries in conjunction with the source tarball releases:

Platform czars are our go-to people for issues specific to a popular platform. They also steer Darcs development so that our support for these platforms is as strong as possible.

Platform liaisons help us to translate from one community culture to another.

Infrastructure