Brett,
>> I think this is less accurate. Patches languish because of limited time
>> *and* because newbies don't have any social capital w/in the Python
>> community. New patch contributors are volunteers too, so they understand
>> that constraint. Their big problem is their outsider status, to wh
On 8/27/06, Chad Whitacre <[EMAIL PROTECTED]> wrote:
Brett, > When you submit your patch, the tracker notifies a mailing list that > most core Python developers subscribe to of the creation of your new > patch.Isn't "of the creation of your new patch" redundant? What else would it
be notifying the
Brett,
> When you submit your patch, the tracker notifies a mailing list that
> most core Python developers subscribe to of the creation of your new
> patch.
Isn't "of the creation of your new patch" redundant? What else would it
be notifying the list of?
> Your patch may languish for week
Brett,
>> I liked the "patch angel" term in Chad's version. Stating "a Python
>> developer will take a look at your patch" smacks of a guarantee,
>> while Chad's use of "patch angel" and "get the ball rolling" better
>> conveyed the fact that this 5-for-1 rule is simply a practice of some
>>
On 8/24/06, Chad Whitacre <[EMAIL PROTECTED]> wrote:
Brett, > Below is a draft for a set of patch guidelines.Thanks for getting around to this!Welcome.
> Wait for a developer to contact you > === > > At this point you need to wait for a Python developer to come alo
Brett,
> Below is a draft for a set of patch guidelines.
Thanks for getting around to this!
> Wait for a developer to contact you
> ===
>
> At this point you need to wait for a Python developer to come along
> and look at your patch. This might be a while
On 8/24/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
On Thu, Aug 24, 2006 at 12:22:42PM -0700, Brett Cannon wrote:> Read the Developer Intro to understand the scope of your proposed change "Search through the PEPs, developer mailing lists and patches. Has a
similar patch already been proposed? H
On Thu, Aug 24, 2006 at 12:22:42PM -0700, Brett Cannon wrote:
> Read the Developer Intro to understand the scope of your proposed change
"Search through the PEPs, developer mailing lists and patches. Has a
similar patch already been proposed? Has it been accepted, postponed or
rejected? Learn t
Below is a draft for a set of patch guidelines. This is meant for that times where people ask "how do a create a patch for a change I made" or where to point people if they created a patch but it comes up short (no tests, etc.). Hopefully this will go up on
python.org/dev/ .Let me know of any er
