Page MenuHomePhabricator

Re-organise the #wikisource Phab board
Open, Needs TriagePublic

Description

The #all-and-every-wikisource Phabricator project is a bit confusing as it stands, as far as I can tell. It doesn't give us a good overview of what tasks are currently being worked on, nor is it a good catching place for triaging incoming tasks (because not all tasks end up here). I think we should rename it back to the general #wikisource, and:

  1. add a Herald rule that puts all 'related projects' incoming tasks into the Backlog here (where they can be looked at and then have this tag removed), and
  2. rename the columns to: Backlog, Needs discussion, Next-up, In-development, Needs code review, Needs community review.

It's not clear what tasks would be on this board and not on any of the related projects' boards; I suspect there should be none. That is, every software component relating to Wikisource already has its own Phabricator project (and if it doesn't, it probably should).

Then, the only tasks on this board would be those that are either needing to be looked at or are currently in progress.

Event Timeline

I think we should rename it back to the general #wikisource

See T196740: Rename Wikimedia project tags in Phab (#Wikisource; #Wiktionary) to clarify that they are not about language specific instances?.

It's not clear what tasks would be on this board and not on any of the related projects' boards

I'm afraid that's the problem this such generic project tags, no matter how these project tags are called. The more generic, the more it can become a dump ground for anything and nothing experienced on some Wikisource.

I'm afraid that's the problem this such generic project tags, no matter how these project tags are called. The more generic, the more it can become a dump ground for anything and nothing experienced on some Wikisource.

I guess that's my point: this generic tag should be used as a triaging place, and a "current work" place, and nothing else. Because what does belong here? Alternatively, of course, we could create a #Wikisource-developers project, and use that for current activities etc. Would that be better?

I think we do need something like a dumping ground to be able to have an overview of all the tasks related to Wikisource in one place. Currently, everything is divided among various workboards.

The dumping ground will be useful in fact, because it is a starting point to perform triage on the incoming tasks (that's the purpose of Triage Meetings).
Actually the new tasks are put in the Backlog without checking their priority, or feasibility. I agree that the label #all-and-every-wikisource is quite generic: every task with that label should have at least a second, more specific, one.

I agree that the label #all-and-every-wikisource is quite generic: every task with that label should have at least a second, more specific, one.

That's exactly the problem, no matter how that project tag is called, and beforehand it was also added to tasks happening on only one Wikisource. Thus the rename...

What we're wanting to do here is to use this project as the triaging place: so that any Wikisource-related project can be added here, but after triaging it'll be moved to the correct other projects. There's no point in having this board be only for tasks that effect every Wikisource, because those tasks already have more specific projects to which they belong.

The other thing that this project would be really useful for is to keep tasks that are actively being worked on. The Wikisource development community is not large, and it's quite possible for us all to keep track of who's working on what, in once central place. The hope is that this will result in better communication between developers and to the communities we're serving.

Certainly, there might be tasks that are only in this project, and which we struggle to find a better home for. But those discussions can take place, and we can figure out what to do.