Re: [python-committers] UPDATE 1: Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California
I created https://public.etherpad-mozilla.org/p/cpython-dev-sprint-2017 etherpad to organize the sprint. Feel free to write whatever you want about the sprint there ;-) I started to list project ideas. Victor 2017-07-12 13:55 GMT+02:00 Łukasz Langa : > Update: the sprint is on! > > *Good news*: Facebook is covering the venue, food and hotel costs. This > is confirmed. I'm working on getting a PSF grant for flights like last year. > > *Please book your* *airplane tickets* as soon as possible. Like last > year, we can reimburse up to *$500* for domestic roundtrip flights and up > to *$1500* for international roundtrip flights. If that’s not enough to > get you to California and back, let me know and we’ll figure something out. > Send me the receipts my way, you should get your money back before the > event, preferably as soon as I get the grant wired. For sums smaller than > $500, provide me with a PayPal e-mail. For larger ones, I will need your > details to set up a wire transfer. I will use TransferWise for the latter > to cut down the wire costs. * I recommend flying in on Sunday and flying > out on Saturday.* > > *Please DO NOT book hotels*, Facebook is covering this, preferably in the > same hotel as close to Facebook HQ as possible. NOTE: I cannot confirm your > hotel room until I have your flight information. > > *Full list of confirmed attendance:* > zware > ned-deily > ncoghlan > warsaw > benjaminp > tiran > ericvsmith > 1st1 > larryhastings > ericsnowcurrently > Mariatta > ezio-melotti > applio > nascheme > bitdancer > gvanrossum > gpshead > zooba > haypo > rhettinger > > If for any reason you can no longer come, *please let me know immediately* > . > > - Ł > > > > On Jun 13, 2017, at 1:04 AM, Lukasz Langa wrote: > > Hello fellow committers! > I'm organizing another core sprint this year to make Python 3.7 the best > release possible. > > *WHY*: > 1. *Community*. 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! > 2. *Focus*. 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! > 3. *Communication*. 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. > > *WHY THE BAY AREA*: 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. > > *WHY EARLY SEPTEMBER*: 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. > > *HOW LONG*: 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). > > *HOW BIG*: 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. > > *WHO PAYS*: 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. > > *PLEASE REPLY*: If you're interested in attending and have the commit bit > on GitHub's python/cpython, fill out this Google Form: > https://goo.gl/forms/MzrNtRe0NAmzvGwF2 > > *DISCLAIMER*: 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: > > 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.). > 2. I will look at your sprint plan and ability to participate in the > entire sprint (per answers to the questions above). > 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 hav
Re: [python-committers] UPDATE 1: Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California
On Jul 12, 2017, at 12:00, Ezio Melotti wrote: > Both the SFO and SJC airports seem to be close to Menlo Park. Is there any > preference on the airport? Does the hotel provide any shuttle service? Personally, I prefer SJC. It works out great for me because there are reasonably timed direct flights from BWI to SJC, and SJC is a fairly easy airport to navigate. It’s closer to Menlo Park too (though when I come to the area, I go to Sunnyvale). I’m not sure about shuttle service. -Barry signature.asc Description: Message signed with OpenPGP ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] UPDATE 1: Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California
On Fri, Aug 11, 2017 at 5:22 PM, Barry Warsaw wrote: > On Jul 12, 2017, at 12:00, Ezio Melotti wrote: > > > Both the SFO and SJC airports seem to be close to Menlo Park. Is there > any preference on the airport? Does the hotel provide any shuttle service? > > Personally, I prefer SJC. It works out great for me because there are > reasonably timed direct flights from BWI to SJC, and SJC is a fairly easy > airport to navigate. It’s closer to Menlo Park too (though when I come to > the area, I go to Sunnyvale). I’m not sure about shuttle service. > > Thanks both for the replies. I ended up booking a flight to SFO, since flights to SJC were either not available or too expensive compared to SFO. I haven't heard anything yet about the hotel bookings and whether or not the hotel offers a shuttle service from/to the airport(s). If not, and if any of you lands in SFO on Sunday afternoon, we could meet up at the airport and share a cab/uber/other. Also thanks to Victor for setting up the etherpad! Best Regards, Ezio Melotti > -Barry > > > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] GitHub: remove the "needs backport to 3.5" label?
No one has said anything, so I will delete the label sometime today. On Wed, 9 Aug 2017 at 12:20 Brett Cannon wrote: > On Wed, 9 Aug 2017 at 01:55 Victor Stinner > wrote: > >> Hi, >> >> Python 3.5 entered security fix only mode. Should we now remove the >> "needs backport to 3.5" label? Other security only branches don't have >> this label neither (3.3 and 3.4). >> > > Seems reasonable to me since you will need to get Larry's attention and > approval anyway for 3.5 changes now so the label isn't that useful. If > there isn't a consensus to not do this I will remove the label probably > Friday. > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] GitHub: remove the "needs backport to 3.5" label?
Just catching up with emails. +1 to removing the label. On Aug 11, 2017 12:04 PM, "Brett Cannon" wrote: > No one has said anything, so I will delete the label sometime today. > > On Wed, 9 Aug 2017 at 12:20 Brett Cannon wrote: > >> On Wed, 9 Aug 2017 at 01:55 Victor Stinner >> wrote: >> >>> Hi, >>> >>> Python 3.5 entered security fix only mode. Should we now remove the >>> "needs backport to 3.5" label? Other security only branches don't have >>> this label neither (3.3 and 3.4). >>> >> >> Seems reasonable to me since you will need to get Larry's attention and >> approval anyway for 3.5 changes now so the label isn't that useful. If >> there isn't a consensus to not do this I will remove the label probably >> Friday. >> > > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] UPDATE 1: Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California
Thanks Łukasz for organizing the sprint, and Victor for setting up etherpad. I added my own sprint plan there. I saw that some of you are wanting to chat with me during the sprint. I'll only be at the sprint Monday-Wednesday, so let's plan accordingly and make the most out of it :) Looking forward to sprint with y'all in a few weeks. Thanks. Mariatta Wijaya ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] GitHub: remove the "needs backport to 3.5" label?
I just deleted the "backport to 3.5" label. I checked that no PRs only had that label before doing so (they all at least had a "backport to 3.6" label). On Fri, 11 Aug 2017 at 14:05 Mariatta Wijaya wrote: > Just catching up with emails. > +1 to removing the label. > > > On Aug 11, 2017 12:04 PM, "Brett Cannon" wrote: > >> No one has said anything, so I will delete the label sometime today. >> >> On Wed, 9 Aug 2017 at 12:20 Brett Cannon wrote: >> >>> On Wed, 9 Aug 2017 at 01:55 Victor Stinner >>> wrote: >>> Hi, Python 3.5 entered security fix only mode. Should we now remove the "needs backport to 3.5" label? Other security only branches don't have this label neither (3.3 and 3.4). >>> >>> Seems reasonable to me since you will need to get Larry's attention and >>> approval anyway for 3.5 changes now so the label isn't that useful. If >>> there isn't a consensus to not do this I will remove the label probably >>> Friday. >>> >> >> ___ >> python-committers mailing list >> [email protected] >> https://mail.python.org/mailman/listinfo/python-committers >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> >> ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] GitHub: remove the "needs backport to 3.5" label?
Thank you ;-) Welcome to a new world where only 2 backports are needed for bug fixes ;-) Victor Le 11 août 2017 23:49, "Brett Cannon" a écrit : > I just deleted the "backport to 3.5" label. I checked that no PRs only had > that label before doing so (they all at least had a "backport to 3.6" > label). > > On Fri, 11 Aug 2017 at 14:05 Mariatta Wijaya > wrote: > >> Just catching up with emails. >> +1 to removing the label. >> >> >> On Aug 11, 2017 12:04 PM, "Brett Cannon" wrote: >> >>> No one has said anything, so I will delete the label sometime today. >>> >>> On Wed, 9 Aug 2017 at 12:20 Brett Cannon wrote: >>> On Wed, 9 Aug 2017 at 01:55 Victor Stinner wrote: > Hi, > > Python 3.5 entered security fix only mode. Should we now remove the > "needs backport to 3.5" label? Other security only branches don't have > this label neither (3.3 and 3.4). > Seems reasonable to me since you will need to get Larry's attention and approval anyway for 3.5 changes now so the label isn't that useful. If there isn't a consensus to not do this I will remove the label probably Friday. >>> >>> ___ >>> python-committers mailing list >>> [email protected] >>> https://mail.python.org/mailman/listinfo/python-committers >>> Code of Conduct: https://www.python.org/psf/codeofconduct/ >>> >>> ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
