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
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:
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
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
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
Brett Cannon added the comment:
Wording LGTM
--
stage: - commit review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16868
___
___
Changes by Brett Cannon br...@python.org:
--
nosy: +brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16868
___
___
Python-bugs-list
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.
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
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
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
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
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
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
Changes by Todd Rovito rovit...@gmail.com:
--
components: +Devguide -Documentation
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16868
___
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
16 matches
Mail list logo
