MINC/Future/DevelopmentShift

=Where to shift development of MINC=

This book/page is an attempt to record the history of the big MINC2.0 CVS change of 2011 with perhaps a well written rationale for the choice that is to be made. For now it is nothing more than a bunch of headings that need content added in them but I hope that others will fill in more things so that we can all make a reasonably informed choice.

Add your vote by adding your name and perhaps a reason why. If you have other choices, feel free to add them.

Leave it at the BIC
The BIC uses a CVS system that requires the user to have a BIC login (and be part of the coders group) in order to commit to CVS. This is done exclusively via SSH logins. There is no strictly used bug tracking system although mantis.bic.mni.mcgill.ca was proposed and used a little. Most of the tracking is still done via the minc-users and minc-development mailing lists.

Pros
 * nothing changes
 * CVS

Cons
 * nothing changes
 * CVS

NITRC - http://www.nitrc.org/
NITRC is a NIH funded initiative that was designed to host projects such as MINC, you can make a choice of CVS or SVN and nothing else that I can see. The bug tracking and others things are done via eForge.

Pros
 * Made for the Neuroimaging community
 * Uses eForge? for issue tracking/lists/etc
 * GIT/SVN/CVS

Cons
 * not as pretty of a code interface as github/others

Votes
 * Andrew Janke

Don't care as long as it's public and DVCS
Options are:
 * Github (Git), Sourceforge (Git), Launchpad (Bazaar), Google Code (Mercurial?), NITRC (Git)

Votes
 * Jason Lerch

NITRC + DVCS wherever
NITRC : for users (mailing list, forum, MINC wiki books as a plugin ?)

Anything public and DVCS : for developpers (nice bug tracking & project management a +, not too good on NITRC).

Votes
 * Pierre Bellec

GIThub
Pros
 * DVCS
 * Awesome UI
 * Bug Tracking included
 * Large Open Source community

Cons

Votes

launchpad
Pros
 * DVCS (Bazaar)
 * makes package building for Ubuntu easier.

Cons

Votes

google code
Pros
 * DVCS

Cons

Votes