Creating a PyPI account for workflow tools
I'm thinking we should create an account to own things like cherry_picker and blurb for when they get put on PyPI. I'm not sure if it should be specific to core-workflow or generic to python-dev, though? Anyone have an opinion on the scope of the account?
On 10 June 2017 at 09:36, Brett Cannon <brett@python.org> wrote:
Principle of least privilege suggests a `core-workflow` account would make sense. It may also be worth talking to Jannis Leidel (founder of the Jazzband package maintenance collective), since he has some nice automation set up whereby GitHub tag -> PyPI release without any manual intervention (that's how I publish contextlib2 releases these days). Things like the docs theme could then also happily live under core-workflow from a release automation perspective. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On 10 June 2017 at 09:36, Brett Cannon <brett@python.org> wrote:
Principle of least privilege suggests a `core-workflow` account would make sense. It may also be worth talking to Jannis Leidel (founder of the Jazzband package maintenance collective), since he has some nice automation set up whereby GitHub tag -> PyPI release without any manual intervention (that's how I publish contextlib2 releases these days). Things like the docs theme could then also happily live under core-workflow from a release automation perspective. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (2)
-
Brett Cannon -
Nick Coghlan