<br><br><div class="gmail_quote">On Wed, Jul 14, 2010 at 01:36, Eric Smith <span dir="ltr"><<a href="mailto:eric@trueblade.com">eric@trueblade.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 7/14/2010 4:21 AM, Georg Brandl wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Am 13.07.2010 22:29, schrieb Brett Cannon:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Given how high traffic python-checkins is I don't consider that a<br>
reasonable place to send follow-up and nor do I consider it the<br>
responsibility of committers to monitor it. As you said earlier this<br>
*isn't* in our standard dev procedures and nor do I think it should be.<br>
If you can't find an email address then either python-comitters or<br>
python-dev would be a better place to send feedback.<br>
<br>
<br>
Maybe reply-to on the checkin messages could be set to python-dev. Not<br>
sure if that's a mailman feature, though.<br>
<br>
I think this would be a good idea. It would be nice to have on-topic traffic<br>
here. :-)<br>
<br>
<br>
Or python-committers since this is discussing code already checked in and thus<br>
is somewhat committer-specific. This also has the perk of being easier to spot<br>
(don't know about the rest of you but my python-committers filter makes those<br>
emails much more obvious than python-dev traffic).<br>
</blockquote>
<br>
I think I've suggested this once, but it met some resistance IIRC (it supposedly<br>
made our development exclusive).<br>
</blockquote>
<br></div>
That's why I think it should go on python-dev. If the code hadn't been checked in and you were asking "what do you think of solving this by using the following code", I think you'd put it on python-dev.</blockquote>
<div><br></div><div>Actually, I probably wouldn't. =) When it gets to explicit code, a design decision has been made, so I do not need to worry about involving the general public in some low-level technical discussion that won't impact them.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> I'd want the discussion of an actual checkin to occur in that same venue.</blockquote><div><br></div>
<div>Right, which is why I want python-committers. Otherwise it's just a glorified commit lock when we are cutting releases.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm still +1 on the idea though, and +1 on python-committers.<br>
</blockquote>
<br></div>
That said, I'm +1 on the idea, but only +0 on python-dev.</blockquote><div><br></div><div>+1 on python-committers, +0 on python-dev. </div></div>