There has been some (followup) discussion in T268 //specifically// about the "Needs Volunteer" priority field value in Phabricator. As T268 is/was generally about the Priority field values and as all the other values are not debated, let's focus on "Needs Volunteer" here.
I've copied the CC list from T268. Feel free to unsubscribe if you are not interested.
Several comments pointed out that using a name heterogenous to all the other priority levels, in lowest rank, and containing the "volunteer" word, is
* degrading/not nice/anti-engaging for volunteers: T268#787946, T268#840749, T268#847537, T417#4432
* logically weak ("1, 2, 3, 4, APPLE". APPLE > 1? APPLE < 1?): T268#785698, T268#847537, T417
* unable to convey meaning: T268#785759, T268#843635, T417#4432, T78617#853809
* actively disruptive of volunteer developers' workflow: T268#835928
* overlapping with the aim of keywords: T417#4432
There seem to be four options:
* Keep the status quo by keeping the current name "Needs Volunteer"
** See above for disadvantages.
* Rename "Needs Volunteer" to "Wishlist" to potentially avoid the confusion created by the word "volunteer" brought up.
** Same logical issues as "Needs volunteer", see above.
** It was called "Lowest" in Bugzilla but that's potentially derogatory for reporters.
* Remove "Needs Volunteer" entirely by merging "Needs Volunteer" into "Low", if developers in practice do not see a need to differentiate between "Low" and one level lower
** No known disadvantages.
** Optionally create a keyword to signify the maintainers are actively looking for a volunteer.
** Optionally convey the same meaning in another way like "Stalled, Needs Triage", to signify the report has not yet been prioritised/fully assessed.
* Rename "Lowest" to "None". T78617#852409
** No known disadvantages.
Tasks with //Open/Stalled// status and //Needs Volunteer// priority: 1331
Tasks with //Open/Stalled// status and //Low// priority: 5909