Page MenuHomePhabricator

Custom task form for #mediawiki-extension-requests
Closed, ResolvedPublic

Description

Please create a custom task submission form for MediaWiki-extension-requests.

Fields

I'd like default values adjusted for the following fields:

  • Title: Archive the <name of extension/skin>
  • Tags:
  • Assigned To: Hidden
  • Priority: Hidden
  • Space: S1
  • Visible-To: All users (locked)
  • Editable-By: All users (locked)

Description:

Reason:

  • Archive documentation on mediawiki.org ( provide the URL to the extension/skin here )
  • Remove from mediawiki/extensions / mediawiki/skins ( along with in .gitmodules)
  • Remove tests in intregation/config ( zuul/layout.yaml )
  • Remove from translatewiki ( groups/MediaWiki/mediawiki-extensions.txt / groups/MediaWiki/mediawiki-skins.txt )
  • Mark as read-only on Gerrit
  • Archive Phabricator project <#ProjectX> for associated extension/skin
  • Edit Phabricator project <#ProjectX> description for associated extension/skin with a link to this ticket

Note:

Story Points:

Please hide this field

Security:

Please hide this field

Visibility

I'd like this form to be visible to all members of MediaWiki-extension-requests via the global Create Task menu.

Preamble

Use this form for requesting an extension or skin to be archived.

  • Title: Replace <name of extension/skin> with the name of extension or skin you want to be archived.
  • Tags
  • Descripition:
    • Please provide a reason on why the the extension needs to be archived.
    • Add any other maintainers as subscribers to this ticket so they're aware of it.
    • Provide any notes here if there's anything else that others might need to know.
    • Remove any of the following actions if they're not applicable to this extension/skin.
    • If your extension/skin has a dedicated Phabricator project, replace <#ProjectX> with the project name.

Event Timeline

Thanks for creating this task! The idea is a good one, however not for the mentioned existing project, as it's scope is "Requests for new MediaWiki extensions." (emphasis by me)...
I recommend to describe the underlying problem to solve in the task summary instead of the potential solution, and check if this is all in sync with https://www.mediawiki.org/wiki/Gerrit/Inactive_projects :)

Like so mentioned in the above task description:

MediaWiki-extension-requests is currently only scoped for request of new extensions, but I think this project could potentially be changed to allow for requests of extensions/skins to be archived? Needs some discussion, potentially separate task?

I'm not sure which project this should appear for, if someone knows a better answer that'd be great :-) I was thinking Diffusion-Repository-Administrators but anyone who owns a repository and isn't a global repository admin should still be able to use such a form for archiving an extension / skin.

Meh, so much for my reading skills. Sorry :(
I'm afraid we don't have a good spot for such "janitor" work currently (I've mostly tagged it as Developer-Advocacy in the past) as it touches several fields...

@Aklapper: No worries! Maybe @mmodell might have a good idea, since I'm not sure either.

Maybe a Cleanup" umbrella project? Or milestones within some other projects

@mmodell Sorry for taking so long to respond, a Cleanup umbrella project sounds like a better idea to me since it's easier to have everything tracked in one place (and then we can separate the types of cleanup tasks with workboards). Should the creation of this project be separated into a subtask?

I'm sorry that took me so long, I've been slacking on the custom forms lately.

@mmodell No worries! Thanks for creating it. :)

MarcoAurelio subscribed.

Hi. Could we amend this form, please?

Thanks!

Once this is done I will leave MediaWiki-extension-requests and join Projects-Cleanup. I understand that I have to be in the respective group to be able to use form 33.

Moreover it will be nice if the form could be renamed from "Request for extension to be archived" to "Request to archive extension" or similar since the description is cut off in the menu at after the "...to".

mmodell triaged this task as Medium priority.