Hi all, Lucas Nussbaum on June 04, 2008 - 00:53 wrote:
> It's strange that you describe it as a gem. I've always thought of it as
a library.Umm... It is a Ruby Gem, hence the xmpp4r.gemspec file and the fact that it is installed using RubyGems. No?
~/ > gem list | grep xmpp4r xmpp4r (0.3.2)> We are very open to giving commit access to contributors, if they want >to integrate their patches and improve xmpp4r. I really don't think that
>moving to github would be a step in the right direction, because it >would make it even easier for people to hack on xmpp4r in their corner >without making the effort to contribute patches back.If I may counter that argument. If you have used Git and GitHub for any period of time it becomes clear that the velocity of contributions increases. Sometimes dramatically. The reason for this is because of the relative ease in creating a code change and asking the project owner to pull that change into the master. It does require a little different way of thinking but it clearly works (note the movement of Ruby on Rails, Merb, Scriptaculous, Prototype, and hundreds of other ruby projects to GitHub in the last several months). In fact the scenario that you mention is actually unlikely due to the nature of distributed SCM's and GitHub in particular. For example, if I 'fork' a copy of the primary xmpp4r repository I can easily track the progress of the upstream repo and merge its changes into my copy on an ongoing basis. Conversely, the 'parent' repo can see the changes that I push to child forks. In fact they can then pull those changes back to the master at any time they desire. The parent can also cherry pick specific commits instead of taking all changes. This process is so easy that the velocity of patches really increases. I have personally made a fork of a project, commited a change, pushed it back to github, issued a pull request through the web UI to the owner, and seen my changes commited to the master in less than 30 min. To come back to your comment. There is NO effort (except for issuing a pull request which involves clicking one button) to contribute a patch back to the master project. No creating diff/patches. No email traffic. No stale patches that can't be applied anymore.
Here is a good blog post on the topic. http://skwpspace.com/2008/06/03/github-is-leading-us-to-an-opensource-renaissance/ Sorry if I am enthusiastic. But I love it. :-) Cheers, Glenn
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Xmpp4r-devel mailing list [email protected] https://mail.gna.org/listinfo/xmpp4r-devel
