Hey guys, I've noticed that with the increase of people working on the code (which is great btw) there's loads of patches flying backwards and forwards.
Perhaps it's time to think about using a peer repository (git/bzr), instead of a central repository (cvs/svn). Unless the project just doesn't have the ability at the moment to do that. I've been working on bzr projects, and since my move away from svn, I have found contributing small changes to be very easy. Obviously hats off to launchpad for allowing me to be able to publish my branches and allow the owners to see that new code is available to merge. Having merge proposals which can be peer reviewed and commented upon. The nice thing about a peer system though, is that your never stuck for commiting and your never stuck for publishing. Thoughts? Regards, Martin Owens ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
