Good morning xmpp4r team, It's Git Time!
http://github.com/ln/xmpp4r/tree/masterAs you may have noticed we have been having a discussion regarding the merits of moving the main source code repository for XMPP4R from Gna's SVN repository over to using the Git SCM and GitHub. Lucas agreed to try it out and we're going to run a grand experiment for a month to see how this transition goes. If, at the end of that month, all is well we will continue development using only Git/Github.
Here are the discussion threads if you are just joining: https://mail.gna.org/public/xmpp4r-devel/2008-06/threads.html Here are some key things to note: For One Month (Until July 7, 2008):- DO NOT COMMIT ANYTHING TO SVN! We want to try to keep the merging a one way process.
- Did I mention? DO NOT COMMIT ANYTHING TO SVN!- All commits to the Git repository will also be pushed back to the SVN mirror (Hence, DO NOT COMMIT ANYTHING TO SVN!) - I will make the periodic commits to SVN which mirror the commits we have applied to Git - If Git is working well at the end of the month we'll use Git exclusively going forward and commits will no longer be pushed to SVN for core xmpp4r code. - Please continue to use the same bug tracking, and please continue to share and discuss your changes on the devel mailing list.
Why are we doing this?- Git, being a distributed SCM allows for a much more agile process and the velocity of patches applied should increase. - GitHub provides much more visibility to developers who might be interested in using or patching the code. - The work involved for maintainers to review and apply patches is greatly reduced and accuracy increased. - Git allows every person to have their own 'clone' of the ENTIRE repository history and commi t freely, even when off-line. Patches can be later submitted when online. This also obviates the need for backups since we'll now have as many clones of the full repo as there are developers. - Git provides vastly superior branching and merging to SVN, is incredibly fast, and very space efficient (the entire XMPP4R repos is less than 3MB on disk! That's every commit from rev 1). - It becomes almost trivial now to submit little patches that clean up docs, spelling errors, whitespace, etc. Keep the code tidy.
OK, I understand using Git. Why GitHub?- GitHub is a great way to collaborate on source code, and has been especially well adopted by the Ruby community. - GitHub allows us to easily visualize changes on the repository, as well as changes that contributing developers want commited to the master. - Comments can be provided on specific files/commits which the owner will see. - GitHub will allow us to have an automated build of the RubyGem version of XMPP4R that tracks the master branch of the repo. - GitHub allows trivially easy 'forking' of a repository which retains linkage to its parent. So 'fork' away!
I have started an XMPP4R development using Git wiki FAQ page here which should help you get started. Please tell me if you have any problems with the FAQ or want to add to it.
http://github.com/ln/xmpp4r/wikis/developer-faq Cheers, Now go make some patches or I'll have to pay Lucas 10 Euros! Glenn
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Xmpp4r-devel mailing list [email protected] https://mail.gna.org/listinfo/xmpp4r-devel
