[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Roundup Robot added the comment: New changeset 3f2637a6fbfa by Ezio Melotti in branch 'default': #16868: mention that you can ping issues before writing to python-dev. http://hg.python.org/devguide/rev/3f2637a6fbfa -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Ezio Melotti added the comment: Fixed with a slightly different wording (thanks Chris for the suggestion). Thanks Todd for the report and the initial patch! -- assignee: docs@python - ezio.melotti resolution: - fixed stage: commit review - committed/rejected status: open - closed type: behavior - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Todd Rovito added the comment: Ok I changed the time to one month...now the patch reads: To begin with, please be patient! There are many more people submitting patches than there are people capable of reviewing your patch. Getting your patch reviewed requires a reviewer to have the spare time and motivation to look at your patch (we cannot force anyone to review patches). If your patch has not received any notice from reviewers (i.e., no comment made) after one month, first “ping” the issue on the issue tracker to remind the nosy list that the patch needs a review. After the issue has been “pinged” and if you don’t get a response after a few days then you may email python-...@python.org asking for someone to review your patch. -- Added file: http://bugs.python.org/file28611/16868PythonDeveloperGuidePingIssueBeforeEmailingPython-devV3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Changes by Todd Rovito rovit...@gmail.com: Removed file: http://bugs.python.org/file28573/16868PythonDeveloperGuidePingIssueBeforeEmailingPython-dev.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Changes by Todd Rovito rovit...@gmail.com: Removed file: http://bugs.python.org/file28603/16868PythonDeveloperGuidePingIssueBeforeEmailingPython-devV2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Brett Cannon added the comment: Wording LGTM -- stage: - commit review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Changes by Brett Cannon br...@python.org: -- nosy: +brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Todd Rovito added the comment: I agree with Meador it should be a specific amount of time. As a beginner at contributing to Python I thought substantial amount of time meant one month but it depends on interpretation. I think making it very specific makes the documentation more clear. Included in the new patch are the other suggestions made by Mr. Jerdonek. Thanks for the feedback! -- Added file: http://bugs.python.org/file28603/16868PythonDeveloperGuidePingIssueBeforeEmailingPython-devV2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Ezio Melotti added the comment: A month sounds good to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Meador Inge added the comment: This seems like a reasonable addition to me. Although, I don't like the substantial amount of time part (yes I know it was already there). That should probably be replaced with something more concrete, e.g. one week. -- nosy: +meador.inge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Chris Jerdonek added the comment: I would also take out the sentence about forgetting about the issue, because that's just one of several possible reasons and I don't think usually the main reason. -- nosy: +chris.jerdonek ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Ezio Melotti added the comment: I agree with Chris. +substantial amount of time first ping the issue on the `issue tracker`_ I would add a comma after 'time'. I don't like the substantial amount of time part (yes I know it was already there). That should probably be replaced with something more concrete, e.g. one week. That really depends on the situation. I think the point of that sentence is to make clear that some time might pass before someone can look at the issue, and I'm not sure it's necessary to quantify this. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Meador Inge added the comment: On Sat, Jan 5, 2013 at 5:55 PM, Ezio Melotti rep...@bugs.python.org wrote: That really depends on the situation. I think the point of that sentence is to make clear that some time might pass before someone can look at the issue, and I'm not sure it's necessary to quantify this. It currently says: If your patch has not received any notice from reviewers (i.e., no comment made) after a substantial amount of time then you may email python-...@python.org asking for someone to take a look at your patch. That doesn't seem very useful to me because a newcomer is going to wonder how much time is substantial. If you quantify it, then they don't really have to think about it as much which makes contributing easier. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
New submission from Todd Rovito: The Python Developer Guide in section 3.3 about the life cycle of a patch/review process makes no mention that a bug should be pinged first before posting to the python-...@python.org email list requesting a review. For more information see this thread on the Python-Dev email list: http://mail.python.org/pipermail/python-dev/2013-January/123453.html -- assignee: docs@python components: Documentation messages: 179109 nosy: Todd.Rovito, docs@python priority: normal severity: normal status: open title: Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner type: behavior versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Changes by Todd Rovito rovit...@gmail.com: -- components: +Devguide -Documentation nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16868] Python Developer Guide: Include a reminder to ping bug report if not reviewed in timely manner
Todd Rovito added the comment: Here is a suggested patch with help from R. David Murray: To begin with, please be patient! There are many more people submitting patches than there are people capable of reviewing your patch. Getting your patch reviewed requires a reviewer to have the spare time and motivation to look at your patch (we cannot force anyone to review patches). If your patch has not received any notice from reviewers (i.e., no comment made) after a substantial amount of time first “ping” the issue on the issue tracker to remind the nosy list that the patch needs a review. It is possible that the nosy committers have just forgotten about the issue. After the issue has been “pinged” and if you don’t get a response after a few days then you may email python-...@python.org asking for someone to review your patch. -- keywords: +patch Added file: http://bugs.python.org/file28573/16868PythonDeveloperGuidePingIssueBeforeEmailingPython-dev.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16868 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
