Do we have a naming convention?
We have AbuseFilter, CheckUser, CharInsert but MediaWiki-extensions-CentralAuth, MediaWiki-extensions-CategoryTree... Who's the responsible of creating this mess?
@MarcoAurelio: recently renamed CheckUser from "MediaWiki-extensions-CheckUser" to "CheckUser".
@Ciencia Al Poder I certainly advocated at first to keep the MediaWiki-extensions- prefix for all MediaWiki extensions. I asked about what should we do and @AKlapper (WMF) said that mantainers were free to remove the prefix from their projects. I renamed CheckUser yesterday somewhat following that advice, but I'd appreciate if we could stablish indeed some clarity, because IMHO the whole Phabricator project stuff is being slowly turned into a mess. I'd love to have a clear policy on naming and renaming projecs and that people stick to it. It'll be good for everyone, specially for newcomers, who will find more easily things if everything is standardized. Best regards.
See for example https://phabricator.wikimedia.org/project/profile/2446/ - Phabricator/Creating and renaming projects#Good practices for name and description says that multiple words should be connected with dashes in order to allow linking project names in Phabricator's markup. Plus, sprints are deprecated in favor of milestones, etc.
We do not have a naming convention when it comes to such prefixes. If "this mess" creates any problems I'd love to hear about the problems.
It would be great to have such a convention, so when assigning projects to a task about an extension you certainly know to start typing MediaWiki-Extension-Whatever instead of Whatever, although typing Whatever brings usually MediaWiki-Extension-Whatever as well. And for consistency, of course.
What I really don't understand is, if there was an initial convention to name such MediaWiki-Extension-* names (or at least they were imported with those names when coming from bugzilla), why not enforce and follow that? I couldn't believe it was left unrestricted just because "it looks nicer"...
There was no initial convention. The migration script from Bugzilla to Phabricator just used the format "$BugzillaProduct-$BugzillaComponent" to create the names of Phabricator projects.
@AKlapper (WMF) For me the mess is that I need a clear yes/no response on this question: Is it okay to rename MediaWiki-extensions-CentralAuth to CentralAuth (for example) or how new MediaWiki extensions projects should be named? MediaWiki-extensions-NEWEXTENSION or just NEWEXTENSION? I just don't want to be admonished afterwards for doing things wrong. Thanks.
Phabricator/Creating and renaming projects#Renaming projects implies that it is okay to rename.
As long as noone explains which problems "the mess" creates I have a hard time to see "a mess".
@Krenair I think I agree. On one hand, projects look "pretty" without the prefix, on the other hand, with the prefix they are more descriptive. I think we all would benefit on a clear guideline on how to name the extensions and recent extensions projects I created do carry the MediaWiki-extensions- prefixes. I think I'll stick to the MediaWiki-extensions- format still.
It's not just looking "pretty", it's a waste of users' time to put pointless information in front of them, and takes up screen space (which makes mobile Phabricating even more painful).
Ok, so try to reach consensus to remove the prefix from *all* MediaWiki-extensions-* projects?
There are a few places (like Vector-the-skin vs. Vector-the-extension) where there's a naming conflict (though that one is settled by dint of deleting the latter), but yeah, that'd help.