[Tracker-discuss] [issue605] Python tracker needs two classes of "easy" issues -- requiring C or not

[Berker Peksag]

Berker Peksag added the comment:

Adding new keywords will make triagers' and core developers' life harder in my opinion. There are already too much fields and keywords in the issue page.

We probably have 30-35 issues (there are 300+ issues marked as "easy") that requires C knowledge and most of them shouldn't be there so adding an "easy C" keyword doesn't actually solve the problem.

If a new contributor doesn't know C, they can still help writing tests and documentation if the issue is correctly classified as "easy" (I did this when I was a contributor.) The main problem with our list is that most of them are easy for a core developer, a domain expert, or a platform expert (see the issues I collected in msg3169 -- not all of them are C issues.)

The another problem is, there is no guidance in most of the easy issues. We should clarify what is the state of the issue, what's needed for next step and which files should be updated (as an ex-Mozilla contributor I can say that Mozilla does a very good job in this area.)

I'm planning to re-triage all issues marked as "easy" in the next weeks.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue605>
_______________________________________________________