I've added an "easy" keyword, with description "This is an easy task (e.g. suitable for GHOP or bug day beginners)".
Let me know if more is needed, Andrew. (I have no idea if anyone can add keywords or if I have magical powers. On the left side bar there's a section "Administration" which contains a link "Edit Keywords".) --Guido On Jan 11, 2008 1:10 PM, A.M. Kuchling <[EMAIL PROTECTED]> wrote: > On Fri, Jan 11, 2008 at 09:45:14PM +0100, Christian Heimes wrote: > > Please add two keywords, one for bug day and one for easy tasks. May > > "beginner task", "easy" or "novice level" makes a good keyword. > > I think marking easy tasks is all we need. That would certainly be > useful during ongoing non-bugday development, but marking issues as > 'bug-day' doesn't seem useful to me. What would it mean? > > > We could also mark complex/hard tasks, tasks which require C programming > > and documentation only tasks, even though I'm not sure how useful the > > additional tags would be. > > Shouldn't documentation-only bugs be marked as being for the > 'Documentation' component? The C vs. Python requirement is also > discoverable from the component field, sort of; Library is for issues > in Lib/, which is all Python, and C extensions are the 'Extension > Modules' component. > > --amk > _______________________________________________ > > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
