Ezio the patch was sent here: http://psf.upfronthosting.co.za/roundup/meta/issue579 Lemme know if this is what you want?
Maciej On Fri, Feb 12, 2016 at 10:10 AM, Maciej Szulik <solt...@gmail.com> wrote: > On Sun, Feb 7, 2016 at 8:24 AM, Nick Coghlan <ncogh...@gmail.com> wrote: >> On 7 February 2016 at 05:22, Brett Cannon <br...@python.org> wrote: >>> IOW if people want to help in a way that involves coding, then please help >>> Ezio with b.p.o stuff. This is also beneficial long-term for maintaining the >>> issue tracker and changes that will be needed in the future for getting >>> cpython moved over. >>> >>> As for a PSF account on dockerhub, I would ask the PSF infra team what they >>> think and have them administer it. >> >> A PSF account on DockerHub sounds like a good idea to me - that would >> likely also be useful for hosting the reference image for the >> manylinux1 build environment. >> >> Cheers, >> Nick. >> >> -- >> Nick Coghlan | ncogh...@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 > > Ezio I followed the steps you've sent me yesterday, and I was able to cleanly > setup my roundup instance. I've made slight changes, cleaned up the > structure and added > readme and makefile. My fork is under (branch dev): > https://github.com/soltysh/docker-b.p.o/tree/dev > I should start working on adding the new field later today. Will keep > you informed about the progress. > > Maciej _______________________________________________ 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
