It would be great if you coud host the SPTK on Github. It's easy to fork, easy to contribute (using pull requests), easy to review changes, and probably easy to find (I guess that Github is one of the most popular code hosting and sharing service lately). Furthermore, there are free continuous integration (CI) services available for Github; Travis (https://travis-ci.org/) for Linux and OSX, AppVeyor (http://www.appveyor.com/) on Windows to name a few. I wonder there is any reason not to migrate?
I agree with Ryuichi for the most part.
This is cvs versus git :)
https://gist.github.com/btilford/716213
http://biz30.timedoctor.com/git-mecurial-and-cvs-comparison-of-svn-software/
http://stackoverflow.com/questions/802573/difference-between-git-and-cvs
Moreover, the developers should consider the below:
in the case of receiving any source codes or patches through pull-request from anonymous user on github, they should decide whether requiring submission of the copyright assignment or Contributor License Agreement (CLA) for the user beforehand.
I also second this idea. It would be much easier to contribute to the project by using git and having a public repository. If needed I will be happy to help with the migration.
Dear SPTK developers, thanks for having developed SPTK and making it available to the open source community.
I also believe that releasing the public repository on Gibhub could encourage other people to contribute.
Hi,
Thank you for using SPTK.
I am the one of the developer assistants of SPTK.
We are considering including the transition to Github in the next major update. (SPTK4.0)
Motoki Shikano
Migrated.