On Mon, Jan 31, 2011 at 15:50, anatoly techtonik <techto...@gmail.com>wrote:
> On Mon, Jan 31, 2011 at 10:54 PM, Antoine Pitrou <solip...@pitrou.net> > wrote: > > On Mon, 31 Jan 2011 20:45:45 +0000 > > techto...@gmail.com wrote: > >> I see no reason for b.p.o bureaucracy. Mercurial-style workflow [1] is > >> more beneficial to development as it doesn't require switching from > >> console to browser for submitting changes. > > > > Ok, why don't you contribute to Mercurial instead? > > If you don't want to receive a stupid answer, why don't you read the > link and say what you don't like in this approach in a constructive > manner? > > > http://mercurial.selenic.com/wiki/ContributingChanges#The_basics:_patches_by_email > -- > anatoly t. >>> Don't send your patch to the >>> BugTracker<http://mercurial.selenic.com/wiki/BugTracker> - it can't be reviewed there, so it won't go anywhere! We do fine with reviews on the tracker, and there has been some on and off work on integrating Rietveld. For the people actually doing the work here, accepting patches on the tracker and dealing with them there has been a reasonably effective workflow, enough that we don't see a need to change it. >>> Patches go to >>> mercurial-de...@selenic.com<http://mercurial.selenic.com/wiki/MailingLists> >>> - no subscription necessary! As you were directed to in an earlier email by Georg, there is now a way to report bugs via email without requiring any subscription. *report*@*bugs*.* python*.*org is the address.* * * *>>> *Because this is a community project and our developers are very busy, patches will sometimes fall through the cracks. If you've gotten no response to your patch after a few days, feel free to resend it. This is true of any workflow on just about any open source project. Whether it's email or a bug tracker, not everything is going to be acknowledged, reviewed, fixed, or rejected immediately. We feel that the tracker allows us to, well, keep track of things. It works for us. What they do works for them, and I'm sure it works great. Could it work for python-dev? Maybe. Is it worth changing anything when no one who is doing the actual work has voiced a need for change? Absolutely not.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
