ITK/Policy and Procedures for Adding Developers: Difference between revisions
| Line 28: | Line 28: | ||
= Evaluating Candidates = | = Evaluating Candidates = | ||
Once a candidate has been suggested, the developers in the | Once a candidate has been suggested, the developers in the [http://www.itk.org/Wiki/ITK_Oversight_Committee Oversight Committee] will vote in favor or against. | ||
(Majority rule ?) | (Majority rule ?) | ||
| Line 35: | Line 35: | ||
If the candidate is approved then developers will send her/him an invitation. | 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 | |||
* [http://public.kitware.com/Bug/signup_page.php Bug Tracker] | * [http://public.kitware.com/Bug/signup_page.php Bug Tracker] | ||
| Line 46: | Line 42: | ||
* [http://www.itk.org/mailman/listinfo/insight-users ITK Users Mailing List] | * [http://www.itk.org/mailman/listinfo/insight-users ITK Users Mailing List] | ||
* [http://www.itk.org/mailman/listinfo/insight-developers ITK Developers' Mailing List] | * [http://www.itk.org/mailman/listinfo/insight-developers ITK Developers' Mailing List] | ||
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. | 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. | ||
Revision as of 17:37, 1 May 2008
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
Identify Candidates
Candidates are identified on the basis of
- Regular and/or notable contributions to the users/developers mailing list
- Regular and/or notable contributions to the bug tracker
- Regular and/or notable contributions to the Insight Journal
- Participants on projects under the supervision of existing developers
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
- Competent C++ Skills
- Good communication skills
- Team building skills
- A committment to high quality software
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
Evaluating Candidates
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.
Training New Developers
New developers should be introduced to the policies and procedures of the toolkit.
In particular to the following
- How to Join the Weekly Tcon
- The Role of the Oversight Committee
- Procedure for Contributing New Classes and Algorithms
- Procedure for Contributing Bug Fixes
- Procedure for Adding a Test
- Rules for CVS Contributors
Background
Scientific Study of Debian Governance
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.
