Page MenuHomePhabricator

Proposal: Separate Phabricator project for semi-automated edit requests in XTools
Closed, DeclinedPublic

Description

While we are working on T262631: Move AutoEdits configuration to on-wiki JSON pages, I would like to propose we create a seprate project to track the semi-automated edit requests.

Currently, when you look at the XTools board, it's very hard to separate development tasks from semi-automated requests. As such, I propose that we create a separate project (such as "XTools-SemiAutomatedRequests" though that's probably not the best name) which would collect the requests.

This would require three steps:

  1. Someone (with more stars in Phabricator than me) would need to create the new project. Optionally, we may want to map it back to the main XTools project in some way.
  2. A code change would be needed, to update the link for requesting a new project on XTools to add this new project instead.
  3. Someone would need to go through and update all semi-automated requests to this new project.

Event Timeline

Matthewrbowker created this task.
DannyS712 moved this task from Incoming to Projects to create on the Project-Admins board.
DannyS712 added subscribers: MusikAnimal, DannyS712.

I'd like to see what @MusikAnimal thinks before proceeding, but sounds like a good idea to me

That's why I didn't tag any project admins yet, I wanted to open it for wider discussion from the XTools maintainers before I went ahead and implemented.

Also, we need to find a better name...

I don't think we need a entirely separate project, personally. Maybe instead a new column on the board and move tickets accordingly. I quickly looked through the Automated Edits column, and indeed it's hard to find the development tasks -- because there are none! Every task as far as I can tell touches only the semi_automated.yml config (except for T261904 which I just moved, as it's not unique to AutoEdits).

Regardless, moving these tickets to a separate project doesn't help the actual problem, which is keeping up with the requests.

New column or maybe a subproject or milestone. IMHO it's better to try the new column first, then go for subprojects or milestones if really needed.

Aklapper subscribed.

(Sorry, I hadn't seen this task yet as it was not initially tagged with Project-Admins. )

It depends on how much you may want to differentiate (or: not receive some) notifications and how consistenyl you triage new incoming tickets tagged with XTools. If you're fine getting all and any XTools related notifications (in case that you watch the XTools project), then I'd say first try a column and find out if that works out for you.

Regarding subprojects and milestone, I highly recommend to first check the "Here are some warnings, to avoid wrong expectations" section on https://www.mediawiki.org/wiki/Phabricator/Project_management#Parent_Projects,_Subprojects_and_Milestones as there have been bad surprises in the past. :-/

Aklapper renamed this task from Proposal: Separate Phabricator project for semi-automated edit requests to Proposal: Separate Phabricator project for semi-automated edit requests in XTools.Oct 16 2020, 12:32 AM

I think this and T262631 are the only tasks in the AutoEdits column that aren't about updates to semi_automated.yml. I've no reservation against a new column (or a project), but I still don't think it would solve much. I have begun preliminary work on T262631: Move AutoEdits configuration to on-wiki JSON pages which will move the burden of updating to the community and make the new column/project redundant. That will take a good while to complete with my current workload, probably a few weeks.

DannyS712 removed a project: User-DannyS712.

In the light of T262631, I don't think this task is necessary.

MusikAnimal moved this task from Automated Edits to Complete on the XTools board.

No longer need now that T262631 has been deployed.

DannyS712 changed the task status from Invalid to Declined.Dec 13 2020, 7:18 AM