2010/6/15 Tarek Ziadé <ziade.ta...@gmail.com>: > On Tue, Jun 15, 2010 at 9:02 PM, "Martin v. Löwis" <mar...@v.loewis.de> wrote: > [..] >> Alternatively, you could start submitting patches. > > Some work Matthieu did is already integrated via the branch I worked > on for PEP 345. > And we were considering using the same workflow since I can commit. > Of course, after a while, I wanted to propose Matthieu as a PyPI commiter. > >>> Maybe it would be easier to switch to the official mercurial repository >>> (hg.python.org <http://hg.python.org>), it would allow a better >>> collaboration between everybody who would like to contribute. >> >> I'm not quite sure why that would be. You still couldn't write to the >> repository, could you? So what would be the difference?
Ooops, sent it to early. Please scratch my previous answer, here's the finished one ;) Not answering instead of Mathieu, but with a DVCS he will be able to write to the repository, and have the same privileges and changeset granularity any other commiter has, as long you or any direct commiter pull his changes (after a review you can do on your side with simple hg commands) So the difference is the same I guess, than the difference for Python itself, which switch to Mercurial. Regards Tarek _______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
