Tasks that are purely project management oriented. This may include designing work flows, reviewing team practices, periodic reviews of tasks in particular states.
Details
Tue, Oct 21
Mon, Oct 20
Change #1195663 merged by jenkins-bot:
[mediawiki/extensions/CheckUser@master] Update copy on Temporary Account Onboarding IP Reveal panel
I support the idea behind but we end up in the usual bikesheddy question how to define or detect "stale" - see T248034: Decrease issues created many years ago with no recent activity (aka stale tickets).
Change #1195710 merged by jenkins-bot:
[mediawiki/extensions/WikimediaMessages@master] Update copy on Temporary Account Onboarding IP Reveal panel
I'm not sure about this. On one hand, I absolutely agree we should care of the good first tasks to make sure they're good. On the other hand, I'm unsure if time is a good indicator. From my experience, even simplish tasks (=take me up to 30 minutes to figure out and write a patch) are often left untouched for a good while. This is because every such task eats a bit of my resources (and the reviewer's resources too) and being humans, we only have finite amount of resources.
Fri, Oct 17
Thu, Oct 16
Wed, Oct 15
Mon, Oct 13
Change #1195710 had a related patch set uploaded (by STran; author: STran):
[mediawiki/extensions/WikimediaMessages@master] Update copy on Temporary Account Onboarding IP Reveal panel
Change #1195663 had a related patch set uploaded (by STran; author: STran):
[mediawiki/extensions/CheckUser@master] Update copy on Temporary Account Onboarding IP Reveal panel
Fri, Oct 10
Change #1195198 merged by jenkins-bot:
[mediawiki/extensions/CheckUser@master] Update the order of onboarding dialog steps
Change #1195198 had a related patch set uploaded (by STran; author: STran):
[mediawiki/extensions/CheckUser@master] Update the order of onboarding dialog steps