If you would like to actively get involved in the development of IGSTK, please read the following guidelines.
- IGSTK Wiki: Refer the Wiki for a complete documentations of current requirements, design discussion, and code reviews. The Wiki is used to coordinate our biweekly teleconference(agenda & minutes). Anyone is welcome to join the tcon discussion as well. Usually it starts around 9am ETS every other Thursday and lasts about 1~2 hours.
- IGSTK Dashboard: http://public.kitware.com/dashboard.php?name=igstk Nightly build of IGSTK. From here, you can also link to cvs repository's web interface and bugTracker.
- Committing code to CVS : Once you have access to the CVS, you need to check out the source code using your user name and password. Then you can start developing code on that developer's copy.
We have two different policies toward the main IGSTK cvs and IGSTKSandbox. IGSTKSandbox is provided for experimental code, aimed at rapid development and prototyping. The cvs control is more relaxed here. For any changes you want to make to the main IGSTK cvs, you do need to have a bug tracker # in the log message. This is to ensure the main cvs stable and keep track of code development. You can do this by creating a new bug entry in the bugTracker, or use previously entered bug entry number. The style of the log message is:
BUG: xxxx Message body [for bugs] STYLE: xxxx Message body [for style errors] ENH: xxxx Message body [for enhancement]