Qgil added a comment.
>>! In T268#835928, @Gryllida wrote:
> There are three states a task may take.
>
> A) We clearly know that if an issue is assigned, then someone (the team or a
> volunteer) took it.
> If an issue is not assigned, then either
> B) it's about to get assigned when someone from the team takes it, or
High / Normal usually denotes that the team has these tass in the pipeline,
although if a task is vacant and a volunteer has the interest and the skills to
complete it, I don't see why they could not take it.
> C) it's something the team doesn't want to work on right now (although it's
> ok if someone else does).
Low, Needs Volunteer denotes that the regular team members are not planning to
work on it any time soon.
> What we need to do is invent a way to distinguish between B and C without
> abusing the "priority" field, because volunteers should have the ability to
> invent tasks which Teams don't need, and use priorities within that set of
> tasks.
Are you talking about tasks within the same project? If external people to the
team ("volunteers") get regularly involved in tasks, then at some point they
become part of the team and can influence their priorities. In fact, as soon as
a tas is taken by someone it is appropriate to change the priority according to
the expectations. If a Needs Volunteer task is taken by someone that will work
full time on it from that very minute, setting it to High just corresponds with
the reality.
The point on which we keep insisting here is that having tasks marked as High /
Normal priority and vacant for months and years doesn't help anybody.
> By abusing this field, we leave volunteers to scribble notes on a piece of
> paper as to what they need to do first and what they need to do last.
Can you put a specific example? I would like to understand what you mean.
TASK DETAIL
https://phabricator.wikimedia.org/T268
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
<username>.
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
