- Either the article has the wrong title or the title has unrelated content :-)
I meant it to give a very quick over view of what to do to get commit rights, and then how to use them once you get them. It was something I couldn't find anywhere else :-)
- Steps 1 - 3 are related to commit rights. There seems to be some overlap with Contributing_Patches.
IMO, the difference between submitting patches and commit rights is that submitting patches is the first step on the path to gaining commit rights, and the difference between someone who is a one off contributor, and a regular contributor.
I note that Kendy has just written such an article, which is much better than my brief instructions.
I think a brief tour is required, where someone can get a good overview of what's expected, what processes exist, and how to follow them, and also links to further information on each stage. IMO, the steps are:
- Decide to get involved in OOo.
- Find bugs, file issues for them.
- Decide to fix some of these bugs yourself.
- Get Source.
- Build it.
- Submit patches for these bugs.
- Be granted CVS commit access to increase turn around time on getting code integrated into the code base.
- Create CWSs, have them integrated upstream.
We need an article similar to this one: http://www.mozilla.org/hacking/getting-cvs-write-access.html
Ie, we need to define casual contributors, who are people who only submit patches, and the more involved contributers who require CVS rights. Also we need to clearly define the path from 'not involved at all' to 'issue filer' to 'bug fixer' to 'patch supplier' to 'committer'. For each definition of user, we need a quick over view of how they should do, whatever it is that they need to do.
Basically, the document I wrote was the document I would have wanted to read when I started working on OOo again, and would have saved me from having to send a few emails to MH :-)
- --stx12 16:15, 30 November 2005 (CET)
Mtg 13:06, 1 December 2005 (CET)