easyproglife wrote:
1. Is this the correct way to send patches?
mailing list is not cool, things tend to stack up and get forgotten.
jira is better.
2. How can one become a committer?
http://jakarta.apache.org/site/roles.html
Overall the general rule of thumb is that you hang enough around the
project so that you're always there (at least for some time) and not
just passing by
The next one being generally is that you are seen as someone that knows
his own limits (ie: you don't suddenly decide to break all the code and
implement what you've been dreaming over night, or hack things around to
solve your own problem or add the feature you may need for your project
without thinking about others)
It is perfectly fine to have as a committer someone that only update
docs..and that sometimes may touch a bit of simple code or fix javadocs,
this is an extremely valuable contribution for a project.
All this is up to the existing committers to decide whether someone can
become one. We generally don't want to remove the privileges of someone
(though this has been done in the past, this is not a pleasant
experience to go through for all parties), so the 'knowing your limits
and up to work with others' is more important than being a 'code star'.
Generally an existing committer brings up a name, it is discussed off
list to make sure that there is consensus (to avoid someone being -1ed
in public) and the person is contacted to see if he is interested (some
people refuse because they know they won't be that available right away)
and a vote happens (which will generally always be +1 due to the
discussion before).
There's some variations, but roughly that's the idea.
3. There is no Jira for IvyDE yet so I can't document this patch. Is
it complicated to open 'ivyde' category in Jira?
Xavier will do. :)
-- stephane
