Hi all,
First, thanks to all who spent the time and taking the vote. The results
are quite conclusive, I would say :
http://www.opensips.org/Vote/GitResult
~80% for going for GitHub. So, let's do it :).
As a plan of attack:
1) repository
a) converting SVN repo to GIT
not a problem
b) GIT on GITHUB (master repo) to replicate all commits to SVN
on SF (to be kept as read only for the current checkouts)
help wanted here
c) installing GITHUB hooks for commits (email alerts)
to be evaluated
d) migrating all current developers from SF to GH
not a problem
2) trackers
a) create the corresponding trackers on GH
to be done
b) all new reports to be opened on GH, no new reports on SF
not a problem
c) existing long term reports from SF to be moved on GH
not a problem
3) we celebrate :)
Who ever has experience and wants to get involved in the above tasks,
please step forward - we would love to get help for free ;).
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 03/26/2013 02:08 PM, Bogdan-Andrei Iancu wrote:
Hi,
Following the discussion on migrating the OpenSISP repository from SVN
to GIT (see [1]), we are evaluating the option of migrating the
primary hosting of the project from SF to GH - GIT repository,
tracker. SF project is to be kept only for a read-only SVN (for
current checkouts), which will be synced with master GIT repo on GITHUB.
For taking a decision on this, we would like to know the opinion of
you all, via a public poll:
http://www.opensips.org/Vote/Git
Please take your time to vote - your vote is important for us ;)
[1] http://lists.opensips.org/pipermail/users/2013-February/024712.html
Regards,
_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
