[Python-Dev] Anyone want to lead the sprints at PyCon US 2016?

[Brett Cannon]

On Fri, 6 May 2016 at 14:14 Camilla <camillamon at gmail.com> wrote:

> I was thinking about holding a Patch Review Party/Sprint, which would
> provide people unfamiliar with the Python dev process a way to contribute
> to the project and get familiar with running tests, applying patches and so
> forth. I have a list of easy-ish patches that I wanted to take a look at
> and I could expand that and use those as a starting for people who don't
> have any particular bug tracker issues in mind.
> I'm not a patch review guru by any means, though. Also not sure if this is
> a good idea or if this is just late night caffeine talking.
>

I have absolutely no problem if you want to pitch this idea to new
contributors who show up at the sprints!

-Brett


>
>
> 2016-04-28 20:07 GMT+01:00 Brett Cannon <brett at python.org>:
>
>> No one stepped forward to lead the sprints this year, so I will put
>> myself as the sprint leader and lean on everyone else who appears to help.
>> :)
>>
>>
>> On Tue, 5 Apr 2016 at 09:36 Brett Cannon <brett at python.org> wrote:
>>
>>> The call has started to go out for sprint groups to list themselves
>>> online. Anyone want to specifically lead the core sprint this year? If no
>>> one specifically does then I will sign us up and do my usual thing of
>>> pointing people at the devguide and encourage people to ask questions but
>>> not do a lot of hand-holding (I'm expecting to be busy either working on
>>> GitHub migration stuff or doing other things that I have been neglecting
>>> due to my GitHub migration work).
>>>
>>> ---------- Forwarded message ---------
>>> From: Ewa Jodlowska <ewa at python.org>
>>> Date: Mon, 4 Apr 2016 at 07:14
>>> Subject: [PSF-Community] Sprinting at PyCon US 2016
>>> To: <psf-community at python.org>
>>>
>>>
>>> Are you coming to PyCon US? Have you thought about sprinting?
>>>
>>> The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5)
>>> of coding with many Python projects and their maintainers. And if you're
>>> coming to PyCon, taking part in the Sprints is easy!
>>>
>>> You don’t need to change your registration* to join the Sprints. There’s
>>> no additional registration fee, and you even get lunch. You do need to
>>> cover the additional lodging and other meals, but that’s it. If you’ve
>>> booked a room through the PyCon registration system, you'll need to contact
>>> the registration team at pycon2016 at cteusa.com as soon as possible to
>>> request the extra nights. The sprinting itself (along with lunch every day)
>>> is free, so your only expenses are your room and other meals.
>>>
>>> If you're interested in what projects will be sprinting, just keep an
>>> eye on the sprints page on the PyCon web site at
>>> https://us.pycon.org/2016/community/sprints/ Be sure to check back, as
>>> groups are being added all the time.
>>>
>>> If you haven't sprinted before, or if you just need to brush up on
>>> sprinting tools and techniques, there will again be an 'Intro to Sprinting'
>>> session the evening of June 1, lead by Shauna Gordon-McKeon and other
>>> members of Python community. To grab a free ticket for this session, just
>>> visit
>>> https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-tickets-22435151141
>>> .
>>>
>>> *Please note that conference registration is sold out, but you do not
>>> need a conference registration to come to the Sprints.
>>>
>>> _______________________________________________
>>> PSF-Community mailing list
>>> PSF-Community at python.org
>>> https://mail.python.org/mailman/listinfo/psf-community
>>>
>>
>> _______________________________________________
>> Python-Dev mailing list
>> Python-Dev at python.org
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe:
>> https://mail.python.org/mailman/options/python-dev/camillamon%40gmail.com
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20160506/2b2f3fdf/attachment-0001.html>