[Tracker-discuss] 'regression' type

anatoly techtonik techtonik at gmail.com
Thu Apr 8 09:25:21 CEST 2010

On Wed, Apr 7, 2010 at 11:06 PM, Brett Cannon <brett at python.org> wrote:
>> >
>> >> It will bring attention to delay 2.7 release.
>> >
>> > We already have a priority for that.
>> Yes. But it can not be specified/edited by reporters.
> That's on purpose. We have had issues in the past of reporters disagreeing
> with how important an issue is and flipping the state to something else
> *after* a core developer already changed the priority.

I think it is a normal workflow. How else could people state that
issue is important for them? In Google there are stars, in Bugzilla -
votes. In other projects such as Trac there are 'priority' and
'severity'. The developers may schedule issue with priority, and user
editable severity may stay the same. If a person thinks that the issue
is 'critical' or a 'blocker' - that means this person is very
interested (or even very-very interested) in fixing the issue. All you
need is to show this person that his help is required and assist in
making a proper contribution.

This means:
1. help him to localize the problem, i.e.
2. explain him which code does he need to dig the problem
3. show where is this code located
4. explain how to setup dev environment
5. explain how to get test suite running easily
6. show an entrypoint to debug/fix cycle
7. show how to create a patch for review
8. show how to submit the patch
9. show how to refresh the patch easily for review

After a few 1-9 cycles you will be able to create a Python
Contribution Manual, similar or even better than
http://subversion.apache.org/docs/community-guide/   After some more
experience some steps could be automated or streamlined.

I am adding Richard to CC. He was eager to about means of improving
community outreach. So, here are entrypoints into development from bug
tracker. Not a single entrypoint, but several for appropriate user
anatoly t.

More information about the Tracker-discuss mailing list