Qgil added a comment. In https://phabricator.wikimedia.org/T268#840749, @Gryllida wrote:
> If we invent a way to properly indicate which of these tasks are off the Team > radar, then anybody will be able to browse such tasks and identify which of > them are higher priority. I think this is more a theoretical scenario than something likely to happen, because this situation implies that there is an official team of busine maintainers (a likely situation), an organized group of volunteers ready to start developing bugfixes and features considered low priority by the maintainers (a rare situation), and at the same time these two separate developer groups will not plan task assignments and priorities together (a very unlikely, surreal, and pretty broken situation). Your case sounds more about users having different opinions than maintainers about the priorities of tasks, and willing to reflect their opinion, and willing to influence the team priorities. In situations like this, the aspect that is frequently missed is which tasks should be deprioritized in order to prioritize these other ones, but I'm digressing... You might want to look at what we are doing in the Phabricator upstream, where we use the "Wikimedia" label to tag tasks that are relevant for us, and then place them in an "Important" or "Details" column, providing a hint to developers about how relevant certain tasks are for us: https://secure.phabricator.com/project/board/404/. This way we don't touch (even less argue) the priorities assigned by the maintainers. This solution doesn't scale; they can't have 100 users each one using their labels. Wikimedia got the label when it was clear that we would become the maintainer of one of the biggest Phabricator instances, putting developer resources as well. So we cannot have a label here for e.g. "Gryllida's-Priorities" or "Flow-Community-Lobby". But I could see the usefulness of i.e. "Tech-Ambassadors-Radar" as a way to channel and consolidate the most relevant feedback from the communities, as long as tech ambassadors would be organized and could agree on the selection and relevance of the tasks they would pick. If an organized process results in task XYZ being placed in the "Important" column of such board, I can see how that could have some real weight focusing discussions and influencing developer plans. If you are interested in this idea, in this tool, please create a task under Project-Creators, and let's discuss there. TASK DETAIL https://phabricator.wikimedia.org/T268 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Qgil Cc: Qgil, chasemp, scfc, Lydia_Pintscher, Aklapper, hoo, Awjrichards, Gryllida, Wikidata-bugs, aude, jeremyb _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
