<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=""><div class=""><div class="">Hello fellow committers!</div><div class="">I'm organizing another core sprint this year to make Python 3.7 the best release possible.</div><div class=""><br class=""></div><div class=""><div class=""><b class="">WHY</b>:</div><div class="">1. <span class="" style="background-color: rgb(255, 255, 255);"><i class="">Community</i>. The sprints at the end of PyCon are great but they mostly get the same people in the room year after year. Many of the most active contributors never attend conferences. My goal with this sprint is to bring together many core devs who rarely if ever meet!</span></div><div class="">2. <span class="" style="background-color: rgb(255, 255, 255);"><i class="">Focus</i>. When we have sprints at the end of a conference, many of us are pretty tired and less productive than we could have been without the late dinners, endless hallway sessions, and so on. Some of the sprinters are preoccupied with tutoring newcomers. This sprint won't be after a major conference, and it's only for seasoned CPython core devs--so get to work!</span></div><div class="">3. <span class="" style="background-color: rgb(255, 255, 255);"><i class="">Communication</i>. There are tremendous benefits to getting everyone together in one big room. Conversations that drag on on python-dev can be solved quickly in person. Even contentious debates become faster, easier, and more civil. And meeting face-to-face helps us all feel more connected to our community.</span></div><div class=""><br class=""></div><div class=""><span class="" style="background-color: rgb(255, 255, 255);"><b class="">WHY THE BAY AREA</b>: We have a large population of core contributors here. Also, I can arrange for Facebook to provide us a "war room" for the whole week, with full access to the campus during the sprints. That includes free food for breakfast, lunch, dinner, and snacks, compatible with almost any dietary restrictions.</span><br class="" style="background-color: rgb(255, 255, 255);"><br class=""></div><div class=""><span class="" style="background-color: rgb(255, 255, 255);"><b class="">WHY EARLY SEPTEMBER</b>: It's almost impossible to find a time that doesn't overlap with a PyCon. This week worked well last year so we're redoing it that way. Monday September 4 is Labor Day in the US, which may make it easier for employees of US companies to attend, as they'd only be taking off four days instead of five.</span><br class="" style="background-color: rgb(255, 255, 255);"></div><div class=""><br class=""></div><div class=""><b class="">HOW LONG</b>: A full week Monday, Sep 4 to Friday, Sep 8 evening. You can check into your hotel the day before the sprint (Sunday, Sep 3) and check out the day after (Saturday, Sep 9).<br class=""><br class=""></div><div class=""><b class="">HOW BIG</b>: <span class="" style="background-color: rgb(255, 255, 255);">No fewer than 10, no more than 20. More than 20 people would be great but it'd be hard for me to organize a sprint that big.</span></div><div class=""><br class=""></div><div class=""><b class="">WHO PAYS</b>: The venue, hotels, and food are provided by Facebook. I'm working on getting flight reimbursements. Last year they were provided by the Python Software Foundation. Anybody is free to waive their reimbursement.</div><div class=""><br class=""></div><div class=""><b class="">PLEASE REPLY</b>: If you're interested in attending and have the commit bit on GitHub's python/cpython, fill out this Google Form: </div><div class=""><a href="https://goo.gl/forms/MzrNtRe0NAmzvGwF2" class="">https://goo.gl/forms/MzrNtRe0NAmzvGwF2</a></div><div class=""><br class=""></div><div class=""><b class="">DISCLAIMER</b>: I'd like to be able to host everybody. However, if I receive more than 20 applications, this is not going to be possible. In this case, the following will happen:</div><div class=""><br class=""></div><div class="">1. I will look at your current level of involvement in CPython development. This includes metrics like commits / PRs, activity on the bug tracker and python-dev, special role (release manager, infrastructure dev, etc.).</div><div class="">2. I will look at your sprint plan and ability to participate in the entire sprint (per answers to the questions above).</div></div><div class="">3. I will gather all this data and leave the final decision to our Benevolent Dictator (who is also attending the sprint). This is one of those occasions where having a dictator is useful.</div><div class=""><div class=""><br class=""></div><div class=""><b class="">DON'T WAIT</b>: September is closer than you think! Please let me know as soon as possible so we can start setting up the event. I'm going to close the sign-up form on June 23rd.</div></div></div><div class=""><br class=""></div><div class=""><div class="">Organizational-ly yours,</div><div class="">Ł</div><div class="">Vice-Minister of Silly Sprints</div></div></body></html>