small tasks and refinements that could span any project, and require (in theory) very little work to implement. May be good for things like Google Code-in.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | Qgil | T1157 New tag request "polish" | |||
| Resolved | Qgil | T1148 Projects for outreach programs (FOSS OPW, Google Code-in...) |
Event Timeline
Comment Actions
I While the idea is good, my first thought is whether it shouldn't be implemented with something better than a new tag (we need to be careful with the proliferation and overlapping of tags).
The "very little work to implement" part is covered by the keyword "Easy" that we will get with the Bugzilla migration. "Design" and other areas will com as well, and if you need to make things even more clear in queries, we could add the "Needs Volunteer" status in the mix.
We are using queries like these to tag tasks for Google Code-in (soon with a specific GCi tag, T1148) or Annoying little bugs in general.
Tasks like T1161: Polish : rules in mobile sidebar do not extend to screen edge could be tagged with Design + Easy + GCi-2014, and set to Needs Volunteer priority, picturing them perfectly and in a discreet way. In contrast, "Polish" is a more value label with a risk of overlapping, and not easy to discover if you don't know it exists.