On 14 July 2010 23:17, Laurence Rowe <[email protected]> wrote: > > > Roel Bruggink wrote: >> >> Why can we just say: if you're using the collective namespace, you *have* >> to >> use the collective svn repository? >> > > +1. While we can't enforce this on PyPI, we could enact a policy that > products listed on plone.org in the collective namespace must be in the > collective repository.
+1 again Things that are owned by the (Plone) Collective (of add-on developers) ought to be in the repository shared by those developers. Let's say you have a great product and you put in GitHub. I find a bug. I want to fix it, but you're on holiday. Now, I can clone your Git repository (if I am familiar with Git and have all the tools set up), and fix it for my purposes. I can then try to track you down and get the patches re-integrated. I may forget (you took a long holiday). Someone else comes along and finds two forks of the same add-on, wondering which one to use. Mine has a fix he needs. Yours has a fancy new feature. The poor integrator asks both of us to get together and come back to one canonical repository. This time, we're both on holiday. Stalemate. Let's say you have a great product and you put it in the Collective. I find a bug. I check out the sources in the same way I've checked out thousands of products over many years. I fix your bug. I commit the changes. Everybody wins. GitHub etc are great for personal projects. But collective.* is about community ownership. If we had some shared Git infrastructure and a collective decision to move to it, then we could all be on Git. But we don't (and there are good reasons we don't, so let's not have that discussion). We have a Subversion-centric infrastructure. It works pretty well. Instead of having packages scattered across hundreds of locations, and different types of VCS' that we have to learn and maintain a toolchain for, we can have something that's predictable and has worked for many, many years. If it ain't broke, please don't break it. Martin _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
