Adding developers to the team is a very important aspect of the process of building a healthy community.
The following are the procedures for adding developers to the toolkit
Candidates are identified on the basis of
Any current developer is welcome and encouraged to suggest candidates. Users are welcome to ask for being considered as candidates.
Characteristics that are desirable in a candidate
Candidates should be suggested to the members of the oversight committee and any additional developers that may have opinions in favor or against the particular candidate
Once a candidate has been suggested, the developers in the Oversight Committee will vote in favor or against.
(Majority rule ?) (Should we require consensus? unanimity ?)
If the candidate is approved then developers will send her/him an invitation.
Before receiving CVS write access, the candidate (now developer) must sign up for
After completing these steps, the new developer will be directed to provide its username/password for CVS write access to
https://www.kitware.com/Admin/SendPassword.cgi
In particular, the new developer should be able to receive emails when commits break the Dashboard; and it should be possible to assign bugs to the new developer.
New developers should be introduced to the policies and procedures of the toolkit.
In particular to the following
Quote:
Recent scholarship on open source communities suggests that any governance system introduced must be meritocratic in order to attract high quality contributions from voluntary members. By rewarding merit with greater status, responsibility, or opportunities to enhance their own development, production communities can satisfy a contributor’s need for recognition and reward in ways that their work lives may no.