On 27/11/12 19:26, Arthur Richards wrote: > After thinking about this some more, I realized that my reaction to the > proposal in part came from feeling apprehensive about external forces > defining bug priorities/resolution timelines, and thereby defining how a > team must respond to issues in bugzilla. Who would be (is?) responsible for > setting bug priorities? Given that teams rely on bugzilla in different > ways, organize their work in different ways, and likely have differing > criteria for defining what priority a bug/task/etc should have, it seems it > ought to be fully up to the team responsible for dealing with issues in > bugzilla to prioritize them (rather than directly from some external > actor). Of course this prioritization should be informed by people/things > beyond the team, but at the end of the day prioritization should be managed > by the team/maintainer responsible for the issue.
Well, I don't think you would need to ban people not in your group from touching those fields. You only need to take into account who said that as well as what they said. Even when having a shared meaning, it doesn't hold the same meaning the priority set by the reporter (how he thinks it should be treated), other developers/bugzilla gnomes (a more accurate view) or your boss (this is how you must consider it). _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
