Reminder: it's free to attend and participate in the PyCon development sprints (you don't need a Talks and Events PyCon registration to come to the sprints).
If you live anywhere nearish Cleveland, even if you couldn't make it to the talks days, consider joining us at least for Monday May 14th, which will probably have the most discussion.
On 05/01/2018 05:29 PM, Sumana Harihareswara wrote:
now has more info:
> * we'll have at least one Open Space/Birds of a Feather session on packaging
> * folks representing Anaconda/conda-build, bandersnatch, Pipenv, GitHub,
> the Python Packaging User Guide, & more will be at the sprints
> * more things we'll work on
> Happy to take suggestions on things to talk about and work on during the
> BoF and sprints!
> On 03/13/2018 10:04 AM, Sumana Harihareswara wrote:
is where I've started a
>> list of our upcoming planned sprints (right now, PyCon North America and
>> EuroPython), with who's attending each and what we might work on there.
>> At PyCon in Cleveland, possible work includes:
>> * User testing
>> * Updating the PyPA roadmap
>> * Packaging Problems triage
>> * PyPI API keys and two-factor auth, with Luke Sneeringer & Donald Stufft
>> * Architecture for new Warehouse API URL structure
>> On 02/13/2018 11:22 PM, Sumana Harihareswara wrote:
>>> Reminder: this Thursday, Feb. 15th, is the last day to request financial
>>> aid to attend PyCon https://us.pycon.org/2018/financial-assistance/
>>> thus the sprints. If money's a reason you're assuming you can't come
>>> join us and improve Warehouse and other Python packaging/distribution
>>> tools, I hope you'll apply for financial assistance.
>>> On 01/30/2018 01:39 PM, Sumana Harihareswara wrote:
>>>> In case you're planning your PyCon Cleveland travel: we are planning to
>>>> hold a Warehouse/packaging sprint at PyCon (the sprints are Monday, May
>>>> 14th - Thursday, May 17th 2018).
>>>> We welcome package maintainers, backend and frontend web developers,
>>>> infrastructure administrators, technical writers, and testers to help us
>>>> make the new PyPI, and the packaging ecosystem more generally, as usable
>>>> and robust as possible. I took the liberty of updating
to say so.
>>>> Once we're closer to the sprints I'll work on a more detailed list of
>>>> things we'll work on in Cleveland.