On Mon Feb 09 2015 at 6:15:22 AM Nick Coghlan
As of earlier today, I've arranged to spend around 1 day of week of paid time on CPython infrastructure work, focusing on container based developer workflow improvements for the web services we run or are considering running.
Fantastic! And what exactly are you aiming for with "container based developer workflow improvements for the web services we run or are considering running"? If you're taking ideas then I vote for stuff like getting Buildbots up using containers so that we can download the same containers as developers and run them under, e.g. Valgrant to do local testing on the OS the container is targeting? IOW less volunteers and more structured, high uptime stuff for OS coverage? -Brett
My proposals for Kallithea based workflow changes are going to be the starting point for that work, so I've updated both PEP 462 and 474 accordingly: https://hg.python.org/peps/rev/12d44a2d7c59
As you can see, this also means I've returned to this list, as contributing to productive discussions here is now part of my job, rather than a purely volunteer activity.
Regards, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia _______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct