Difference between revisions of "Talk:Commit Rights"

From Apache OpenOffice Wiki
Jump to: navigation, search
(suggestions for the article)
 
 
Line 1: Line 1:
−
Either the article has the wrong title or the title has unrelated content :-)
+
Hi Stefan,
  
−
Steps 1 - 3 are related to commit rights. There seems to be some overlap with [[Contributing_Patches]].
+
::  Either the article has the wrong title or the title has unrelated content :-)
  
−
Steps 4 - 6a could be a good start of the article [[CWS]] which is one of the [[Special:Wantedpages|most wanted topic]]s.
+
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 6b - 8 cover [[CWS_QA]] or [[CWS#QA]].
+
::Steps 1 - 3 are related to commit rights. There seems to be some overlap with [[Contributing_Patches]].
  
−
Either the very valuable content is intended as a very quick tour or it should be integrated in the [[Getting_It]], [[Building]], [[Installing]], [[Running]], [[Hacking]], [[Debugging]], [[Contributing Patches]], [[CWS]], [[QA]] documents.
+
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.  
  
−
Marty, it would be great, if you could have a look at the mentioned documents, add some of your enhancements there and start a CWS article.
+
::Steps 4 - 6a could be a good start of the article [[CWS]] which is one of the [[Special:Wantedpages|most wanted topic]]s.
  
−
--[[User:St|stx12]] 16:15, 30 November 2005 (CET)
+
I note that Kendy has just written such an article, which is much better than my brief instructions.
 +
 
 +
::Either the very valuable content is intended as a very quick tour or it should be integrated in the [[Getting_It]], [[Building]], [[Installing]], [[Running]], [[Hacking]], [[Debugging]], [[Contributing Patches]], [[CWS]], [[QA]] documents.
 +
 
 +
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 :-)
 +
 
 +
::--[[User:St|stx12]] 16:15, 30 November 2005 (CET)
 +
 
 +
[[User:Mtg|Mtg]] 13:06, 1 December 2005 (CET)

Latest revision as of 12:06, 1 December 2005

Hi Stefan,

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.

Steps 4 - 6a could be a good start of the article CWS which is one of the most wanted topics.

I note that Kendy has just written such an article, which is much better than my brief instructions.

Either the very valuable content is intended as a very quick tour or it should be integrated in the Getting_It, Building, Installing, Running, Hacking, Debugging, Contributing Patches, CWS, QA documents.

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:

  1. Decide to get involved in OOo.
  2. Find bugs, file issues for them.
  3. Decide to fix some of these bugs yourself.
  4. Get Source.
  5. Build it.
  6. Submit patches for these bugs.
  7. Be granted CVS commit access to increase turn around time on getting code integrated into the code base.
  8. 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)

Retrieved from "https://wiki.openoffice.org/w/index.php?title=Talk:Commit_Rights&oldid=2383"
Personal tools