<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 2, 2014, at 2:09 PM, Brett Cannon <<a href="mailto:brett@python.org" class="">brett@python.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br class=""><br class=""><div class="gmail_quote">On Tue Dec 02 2014 at 1:59:20 PM Barry Warsaw <<a href="mailto:barry@python.org" class="">barry@python.org</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Dec 02, 2014, at 06:21 PM, Brett Cannon wrote:<br class="">
<br class="">
>Well, if I'm going to be the Great Decider on this then I can say upfront<br class="">
>I'm taking a pragmatic view of preferring open but not mandating it,<br class="">
>preferring hg over git but not ruling out a switch, preferring Python-based<br class="">
>tools but not viewing it as a negative to not use Python, etc. I would like<br class="">
>to think I have earned somewhat of a reputation of being level-headed and<br class="">
>so none of this should really be a surprise to anyone.<br class="">
<br class="">
I think it's equally important to describe what criteria you will use to make<br class="">
this decision. E.g. are you saying all these above points will be completely<br class="">
ignored, or all else being equal, they will help tip the balance?<br class=""></blockquote><div class=""><br class=""></div><div class="">Considering Guido just gave me this position I have not exactly had a ton of time to think the intricacies out, but they are all positives and can help tip the balance or break ties (I purposely worded all of that with "prefer", etc.). For instance, if a FLOSS solution came forward that looked to be good and close enough to what would be a good workflow along with support commitments from the infrastructure team and folks to maintain the code -- and this will have to people several people as experience with the issue tracker has shown -- then that can help tip over the closed-source, hosted solution which might have some perks. As for Python over something else, that comes into play in open source more from a maintenance perspective, but for closed source it would be a tie-breaker only since it doesn't exactly influence the usability of the closed-source solution like it does an open-source one.</div><div class=""><br class=""></div><div class="">Basically I'm willing to give brownie points for open source and Python stuff, but it is just that: points and not deal-breakers.</div></div></div></blockquote><br class=""></div><div>This sounds like a pretty reasonable attitude to take towards this.</div><div><br class=""></div><div>If we’re going to be experimenting/talking things over, should I withdraw my PEP?</div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">---</div><div class="">Donald Stufft</div><div class="">PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA</div></div></div>
</div>
<br class=""></body></html>