ITK/Policy and Procedures for Adding Developers: Difference between revisions

From KitwarePublic
< ITK
Jump to navigationJump to search
Line 62: Line 62:
* [[ITK Procedure for Adding a Test|Procedure for Adding a Test]]
* [[ITK Procedure for Adding a Test|Procedure for Adding a Test]]
* [[ITK Rules for CVS Contributors|Rules for CVS Contributors]]
* [[ITK Rules for CVS Contributors|Rules for CVS Contributors]]
= Background =

Revision as of 16:27, 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

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.

Upon acceptance the candidate will be directed to provide its username/password for CVS write access to

https://www.kitware.com/Admin/SendPassword.cgi

The candidate (now developer) will be required to sign up for

  • Bug Tracker
  • ITK CDash
  • ITK Wiki

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 procedures of the toolkit.

In particular to the following

Background