[Python-Dev] contributing to multiprocessing
Hi all -- I am interested in making some serious ongoing contributions around multiprocessing. My inspiration, first and foremost, comes from the current documentation for multiprocessing. There is great material there but I believe it is being presented in a way that hinders adoption and understanding. I've taken some initial baby-steps to propose specific changes: http://bugs.python.org/issue22952 http://bugs.python.org/issue23100 The first, issue22952, can reasonably be tackled with a patch like I've submitted. Continuing with patches for issue23100 can also be made to work. I realize that reviewing such patches takes non-trivial time from volunteers yet I'm interested in submitting a series of patches to hopefully make the documentation for multiprocessing much more consistent with other module docs and much more accessible to end users. I don't want to simply create more work for other volunteers -- I'd like to volunteer to reduce / share some of their work as well. Beyond the documentation, there is currently a backlog of 186 issues mentioning multiprocessing, some with patches on offer, some without. I'd like to volunteer my time reviewing and triaging these issues. Hopefully you can already get a sense of my voice on issues from what I wrote in those two issues above. Rather than me simply walking through that backlog, offering comments or encouragement here and there on issues, it makes more sense for me to ask: what is the right way for me to proceed? What is the next step towards me helping triage issues? Is there a bridge-keeper with at least three, no more than five questions for me? Thanks, Davin ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] contributing to multiprocessing
On Thu, 08 Jan 2015 17:08:07 -0800, Ethan Furman et...@stoneleaf.us wrote: On 01/08/2015 03:21 PM, Davin Potts wrote: I am interested in making some serious ongoing contributions around multiprocessing. Great! Rather than me simply walking through that backlog, offering comments or encouragement here and there on issues, it makes more sense for me to ask: what is the right way for me to proceed? What is the next step towards me helping triage issues? Is there a bridge-keeper with at least three, no more than five questions for me? I would suggest having at least one, if not two or three, current core-devs ready and willing to quickly review your work (I believe Raymond Hettinger may be one); then, go ahead and triage, improve and/or submit patches, and make comments. Once you've got a few of these under your belt, with favorable reviews and your patches committed, you may get stuck with commit privileges of your own. ;) Indeed, the best way to proceed, regardless of any other issues, is in fact to review, triage, comment on, and improve the issues you are interested in. Get the patches commit ready, and then get a current core dev to do a commit review. Oddly, the doc issues may be more problematic than the code issues. Fixing bugs in docs isn't difficult to get done, but restructuring documentation sometimes gets bogged down in differing opinions. (I haven't myself looked at your proposals since I don't use multiprocessing, so I don't know how radical the proposed changes are). --David ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] contributing to multiprocessing
Thanks! That sounds like a nice, clear path forward. Regarding the doc issues being a bit more problematic to work through, I thoroughly understand. Davin On Jan 8, 2015, at 21:19, R. David Murray rdmur...@bitdance.com wrote: On Thu, 08 Jan 2015 17:08:07 -0800, Ethan Furman et...@stoneleaf.us wrote: On 01/08/2015 03:21 PM, Davin Potts wrote: I am interested in making some serious ongoing contributions around multiprocessing. Great! Rather than me simply walking through that backlog, offering comments or encouragement here and there on issues, it makes more sense for me to ask: what is the right way for me to proceed? What is the next step towards me helping triage issues? Is there a bridge-keeper with at least three, no more than five questions for me? I would suggest having at least one, if not two or three, current core-devs ready and willing to quickly review your work (I believe Raymond Hettinger may be one); then, go ahead and triage, improve and/or submit patches, and make comments. Once you've got a few of these under your belt, with favorable reviews and your patches committed, you may get stuck with commit privileges of your own. ;) Indeed, the best way to proceed, regardless of any other issues, is in fact to review, triage, comment on, and improve the issues you are interested in. Get the patches commit ready, and then get a current core dev to do a commit review. Oddly, the doc issues may be more problematic than the code issues. Fixing bugs in docs isn't difficult to get done, but restructuring documentation sometimes gets bogged down in differing opinions. (I haven't myself looked at your proposals since I don't use multiprocessing, so I don't know how radical the proposed changes are). --David ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/python%2Bpython_dev%40discontinuity.net ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] contributing to multiprocessing
On 9 January 2015 at 14:20, Davin Potts pyt...@discontinuity.net wrote: Thanks! That sounds like a nice, clear path forward. Regarding the doc issues being a bit more problematic to work through, I thoroughly understand. In the case of changes to the multiprocessing docs, accepting larger restructures would mainly be the domain of Richard Oudkerk (sbt) as the lead maintainer for the module. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] contributing to multiprocessing
On 01/08/2015 03:21 PM, Davin Potts wrote: I am interested in making some serious ongoing contributions around multiprocessing. Great! Rather than me simply walking through that backlog, offering comments or encouragement here and there on issues, it makes more sense for me to ask: what is the right way for me to proceed? What is the next step towards me helping triage issues? Is there a bridge-keeper with at least three, no more than five questions for me? I would suggest having at least one, if not two or three, current core-devs ready and willing to quickly review your work (I believe Raymond Hettinger may be one); then, go ahead and triage, improve and/or submit patches, and make comments. Once you've got a few of these under your belt, with favorable reviews and your patches committed, you may get stuck with commit privileges of your own. ;) -- ~Ethan~ signature.asc Description: OpenPGP digital signature ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
