On Tue, 2018-10-02 at 20:43 +0100, Yuri Astrakhan wrote:
I think we are misusing the term "priority"
here. Priority for whom?
Setting something to "lowest" priority implies that users do not care about
the item.
It does not, as "users" do not prioritize what developers work on.
https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_…
I suggest we use dashboard columns for the planning
activities, while
keeping the tasks themselves fully under "requester's" control. E.g. let
the community decide what is more important
IMHO software development is not a popularity contest.
For completeness, some attempts to make communities influence
development priorities exist, such as
https://meta.wikimedia.org/wiki/2018_Community_Wishlist_Survey
Furthermore, if you are aware of a functioning system to "let the
community decide" which also covers the needs of people we want to
attract as new future members of "the community" (we have about 900
Wikimedia sites with different needs), which takes self-selection bias
into consideration: I'd love to get more info. :)
Thanks,
andre
--
Andre Klapper | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/