[Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

[Barry Warsaw]

On Jul 01, 2010, at 03:26 PM, Brett Cannon wrote:

>On Thu, Jul 1, 2010 at 15:07, Barry Warsaw <barry at python.org> wrote:

>> Other than that, while I sometimes review patches in email, I do not
>> think patches in a tracker are the best way to manage these.  A
>> dvcs's biggest strength is in branches, so we should use those as
>> much as possible.
>
>As I said, quick-and-dirty. It will take discussion to decide what we
>want to ask non-committers to do, weighing cost of complexity of the
>approach for people new to DVCS in general and Hg in particular,
>resource access such as a publicly accessible place to push repos,
>what data format we prefer, etc. I just wanted to give David something
>to go to PyOhio with that I know will be simple to explain and will
>always work.

That's cool.  I've had pretty good luck asking contributors on other project
to create branches and merge proposals (a Launchpad feature that triggers code
reviews), even when they first posted patches to a tracker or mailing list.
I'm confident most of our non-committers will find it pretty easy, especially
if we can provide a guide for the basics.

-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100701/18db4e91/attachment.pgp>