Hi Saul,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 02/18/2013 06:20 PM, Saúl Ibarra Corretgé wrote:
What things need to be sorted out when moving to GIT:
First question: would it be a self-hosted Git repository or the GitHub service?
1) for backward compatibility, I would suggest having a Read-Only SVN, so
people will be able to update their current SVN checkouts.
Does any of you have experience in mirroring (GIT to SVN only) data ?
If GitHub is chosen it already provides this, so there is nothing to be done:
https://github.com/blog/1178-collaborating-on-github-with-subversion
2) about the hooks in GIT - we have now the scripts for sending email on each
SVN commits - some help in this matter will be highly appreciated.
I don't know myself, but shouldn't be too hard to do.
3) we are heavily using the SVN keywords (%id%, etc) - is there a way to keep
something similar in GIT ?
Ditto. Also, we should keep the svn authors mapped to git authors where
possible.
I will appreciate any help from any GIT "expert" around here, just to be sure
we get the things in the right way from the beginning :).
Not a git super expert, but I have maintained a unofficial OpenSIPS repo for a
while: https://github.com/saghul/OpenSIPS
Since I'm here, let me elaborate on why I think moving to GitHub is a good idea:
- Pull requests.
That's it. Pull requests are the perfect way to collaborate with the project.
Only people who actively contribute need commit rights, the rest can send a
pull request with their changes just fine. Inline commenting is awesome, it's a
very good way to iterate on a bugfix without sending diffs left and right,
making code reviews very simple.
GitHub also has an issue tracker, so existing issues can be migrated there.
This would also help remove all sorts of old issues that have piled up over
time ;-)
When comes to SF versus GITHUB - the main problem from my perspective is
that SF overs a unified (one account) for tracker, forums, downloads,
code repo.....If we move code repo to GITHUB, we will force the
developer to use 2 accounts (on SF for tracker, forum , etc, and one on
GITHUB for GIT only)..
For manageability reasons I would prefer to have a place hosting everything.
What options I see:
1) move everything (tracker + GIT and the rest ?) on GITHUB
2) keep SF as primary GIT repo and GITHUB can be a secondary. Developers
can use the SF accounts for everything and use GITHUB as an interface to
the community (changes, pull requests, etc)..
If I'm talking BS, please correct me :D.
Regards,
Bogdan
_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel