Opened 13 years ago

Last modified 13 years ago

#15 closed defect (FIXED)

flesh out contributing howto

Reported by: Will Kahn-Greene Owned by:
Priority: minor Milestone: 0.0.1
Component: Keywords:
Cc: Parent Tickets:


The documentation will have a howto on contributing. This is in
addition to the hacking howto. We decided last week that it was a
good idea to have two separate chapters so that we can more easily
focus on getting non-code contributors into the project.

For April 30th, the contributing howto should have the following

1. filing bugs
2. translating
3. hacking -- which refers to the hacking howto
4. theming -- which refers to the theming howto (which will be a
   stub for April 30th)
5. where to go when you get stuck

We should have a section for each kind of work we need help with.
What other sections should it have?

Adding everyone to the watch list on this one because it needs more

Change History (5)

comment:1 by Will Kahn-Greene, 13 years ago

Milestone: 0.0.1
Putting this in the 0.0.1 target.

comment:2 by Will Kahn-Greene, 13 years ago

We did a contributor howto sprint party and it was moderately
successful. I think the document is good enough, though it'd do a
lot better if:

1. Deb did a pass on it
2. Matt did a pass on it
3. Rob did a pass on it

Can you three do a pass on the document in the next few days?

The current version is here:
` <>`_

comment:3 by Will Kahn-Greene, 13 years ago

Status: NewResolved
I got Asheesh to do a pass on it and I'm really happy with the
results. I'm going to close this one out.

comment:4 by Will Kahn-Greene, 13 years ago

Status: ResolvedClosed

comment:4 by Will Kahn-Greene, 12 years ago

The original url for this bug was .

Note: See TracTickets for help on using tickets.