https://bugzilla.wikimedia.org/show_bug.cgi?id=57569
--- Comment #31 from MZMcBride <[email protected]> --- (In reply to comment #30) > We don't use easy keyword for shell bugs, as they're advertised not as "easy > bug to write" but as "easy bugs for new contributors to discover the code". > Shell bugs ask a knowledge of community consensus, and so they aren't > suitable for newcomers. I'm not sure this logic is sound. The "easy" keyword is associated with technical complexity. Couldn't we presume that the person adding the "easy" keyword is capable of making a full judgment of the bug, evaluating both the technical complexity and the social implications? That is, committing a change for an "easy" shell ticket still allows new users to learn and experience Git and code review without them needing to be able to divine Wikimedia wiki consensus. On bugs where consensus, technical or otherwise, is unclear, there's a strong case for not marking the bug as "easy." I don't believe that's the case here or in many other cases of "shell" bugs. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
