I think it's time to move the primary RDKit codebase from svn to a
distributed version control system.[1] This change is intended to make
it a lot easier for others to work with/contribute to the RDKit.

It seems like git is winning/has won the argument about which DVCS is
the one to use, so that part seems easy.

Since I'm pretty unhappy with the new sf.net bug tracker, I would like
to move to a new issue tracker as well.

The next question is where to host the git repository and the tracker.
There are three obvious options here: github, bitbucket, and google
code. All three offer bug trackers and wikis.

I'm looking for feedback, suggestions, opinions, rants, etc. on which
of these possibilities I should (or should not) choose.

-greg
[1] I believe it should be possible to continue to keep the svn
repository in sync with the git code base in the same way that the
current github RDKit version is kept in sync with the sf.net svn repo.

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Rdkit-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss

Reply via email to