Le 22/09/2012 02:14, mbp a écrit :
I really appreciate getting quite timely reviews, and getting my patches
merged to trunk fairly quickly. That's at least as important as the
mechanics and you're getting it more right than many projects do.
I do agree it's fairly hard to know how to contribute changes. For
instance, within one review thread, one person asked for patches as
attachments and someone else asked for them inline. Some documentation
says to send patches and some says to send a pull request. There are
some code reviews on logilab and maybe some on bitbucket?
There is some mention of hg mutable history, which sounds interesting,
but also sounds pretty immature and probably not something drive-by
contributors would want to have to learn. Even suggesting mq may be
too much, and if a project wants sanitized history, I think the core
maintainers are probably best placed to do that themselves.
I think the key thing is to have a consistent, simple, story for basic
contributions.
Very good tl;dr :)
I have been following the way mercurial integrates patches and I'm quite
impressed with the simplicity. We could get started with such a process
in no time.
http://mercurial.selenic.com/wiki/ContributingChanges
Regards,
Aurélien.
_______________________________________________
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects
