Le 31/07/12 18:36, Mattmann, Chris A (388J) a écrit :
My personal 2c is that if folks are doing any of the following enough:
* adding patches
* creating JIRA issues
* having thoughtful discussion on list
* writing documentation
* answering user questions
or being generally "interested" in the project, then they are a candidate, at
least for me,
for committership and PPMC membership on the project. PPMC membership and
committership is not just for code. Contributions come in many forms.
Understood. I would bring the point of view that Distributed Versionning
System, through "push" and "pull" actions, can been seen as a more
powerful way to submit patches than email.
One thing I could do is to create a Git repository synchronized on the
SIS subversion repository (I'm already doing that for GeoAPI). Using the
Git repository for creating patches would be easier for me, even if the
patch is sent by email for application on SVN, and may be an opportunity
for those who wish to get familiar with Distributed Versionning System.
My past experience with a very large and complex project on SVN
convinced me on the importance of DVS flexibility...
While I agree on the importance of welcoming new members, isn't
important to list what we think developers should know before getting
commit rights for a particular module? For example I would like a page
explaining that before committing in the "referencing" module, we pledge
the developer to become familiar with java.awt.geom.AffineTransform.
Even if the committer rarely touch directly any affine transform, the
"spirit" of affine transform is widely spread across the referencing
module and developers often take a while to become used to it. When
patches are sent by email or by a DVS system, the maintainer having
commit right can ensure that the "spirit" of affine transform is
followed. But once a developer get direct commit right, I would feel
reassured if I could be confident that AffineTransform has been well
understood by him... Of course this is our responsibility to write a
page explaining what we think the committer need to know. It would be
different for each module (e.g. AffineTransform is irrelevant to metadata).
Martin
