Nemo_bis added a subscriber: Nemo_bis.
Nemo_bis added a comment.
In https://phabricator.wikimedia.org/T268#849975, @scfc wrote:
Or, to put it in another way: If priority is meant to reflect the planning of
the assignee of a task (cf.
jayvdb added a subscriber: jayvdb.
jayvdb added a comment.
I agree that 'Needs Volunteer' isnt very nice, and doesnt really fit into the
Priority scheme. 'Needs Developer' isnt always accurate, as it might not be a
development task, and it has the same problem - resourcing is typically (sadly)
He7d3r added a subscriber: He7d3r.
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:
mmodell added a subscriber: mmodell.
mmodell added a comment.
I agree with @Gryllida on this one. Having a needs volunteer priority sorta
sounds disingenuous. Might as well call a duck a duck and name it priority:
none
TASK DETAIL
https://phabricator.wikimedia.org/T268
REPLY HANDLER
Gryllida added a subscriber: Gryllida.
Gryllida added a comment.
I disagree.
Can we assign to a dummy needs volunteer or nodody account when a Team
doesn't want to work on this?
And rename needs volunteer priority to lowest.
TASK DETAIL
https://phabricator.wikimedia.org/T268
REPLY HANDLER
Qgil added a subscriber: Awjrichards.
Qgil added projects: MediaWiki-extensions-WikidataRepo, need-volunteer.
Qgil added a comment.
I kept thinking about this. There is one subtle change that we might have made
by moving to kanban-inspired Phabricator, simplifying Priority levels, getting
rid
