Repository access

If you want to contribute to the task project, you can do so in a couple of ways. You can submit patches, because everyone has read-access to the code repository. Just clone the repository with:

$ git clone http://tasktools.org/task.git task.git

and off you go. Pull often, and submit patches.

The alternative is that you can get repository write access. You just need to ask, and pass the acceptance criteria.

Acceptance Criteria

  1. Understanding of task/GTD. The person has to appreciate the "simple" philosophy.
  2. Sufficient demonstrable git knowledge to not be a danger.
  3. Demonstrated ability to create quality patches.
  4. Willing to work on something that needs to be done.

Once you have write access, you'll follow the rules of conduct.

House Rules

1. Do not delete any branches, unless it is for a superceded release (like 1.7.1 and earlier). Ask Fredde.
2. If you create a branch, don't push it to the repo without a very good reason, such as a new version number. Ask Paul. By all means create your own local branches. They are incredibly useful. The branches in the repo should be:
    master
    2.0.0 (or current development effort)
    1.8.0 (or current release)
    1.8.1 (or anticipated patch)

3. Do not delete any tags, unless it is in order to move a tag to another commit, or for a very good reason. Ask Fredde.
4. By all means add tags and push them if you feel they are useful. You may be asked to remove them if they constitute "pollution".

And of course, there are disqualification criteria that could lead to having your ssh key deleted:

Disqualifiers

1. Doing something irretrievably dumb. Mistakes are normal everyday activity and are fine, but this refers to something special.
2. Attitude problem.