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

[Ezio Melotti]

Ezio Melotti added the comment:

> Adding new keywords will make triagers' and core developers' life harder in my opinion.

I agree with Berker on this -- adding new keywords and components makes the tracker harder to use.  With more fields it is more difficult to find/select/understand all the right options while triaging and reviewing issues.  This might also lead to incomplete/incorrect classification.
When adding new keywords/components we should always evaluate if the benefits (better classification/easier search) outweigh this cost (UI cluttering/worse UX).
We have discussed in the past ways to address the UI/UX problem, such as tags or separate "triaging" (with all the fields/options) and "read-only" (with only the selected fields/options) views.  Until these are implemented I would prefer to err on the conservative side while adding new components/keywords.

----------
nosy: +ezio.melotti

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