Talk:Phabricator/Diffusion/Callsign naming conventions/Existing repositories

CX
The accepted acronym for ContentTranslation is CX. (CT could be confused with category tree.)

A lot of extension names could be abbreviated, but I am mentioning this one in particular because it has quite a lot of packages already because of its modular services-based architecture and because its configuration is less trivial than of most other extensions.

So all or most repos that have CONTENTTRANSLATION in their callsigns can be changed to CX. --Amir E. Aharoni (talk) 17:26, 13 November 2014 (UTC)


 * These sound like good changes to me-- edit away! ^demon[omg plz] 18:29, 13 November 2014 (UTC)

INTEGRATION -> CI
INTEGRATION is long and shows up in a lot of repo names. CI is a common industry abbreviation for "continuous integration" and it's short! --BDavis (WMF) (talk) 23:38, 13 November 2014 (UTC)


 * ✅ Works for me. Jdforrester (WMF) (talk) 11:49, 14 November 2014 (UTC)

OPERATIONS -> OPS
Just makes sense to me. --BDavis (WMF) (talk) 23:42, 13 November 2014 (UTC)


 * ✅ Works for me. Jdforrester (WMF) (talk) 11:49, 14 November 2014 (UTC)

OPSPUPPET vs. other OPS-Repos
Why OPSPUPPET, when every other operations-thing is now prefixed with OPS-? I would be for OPS-PUPPET for consistency reasons. --se4598 (talk) 18:57, 14 November 2014 (UTC)
 * Because I didn't realize we were going to use dashes and had already done puppet. If OPS-* is the convention that's cool. ^demon[omg plz] 23:02, 14 November 2014 (UTC)
 * Well now people have already started linking to it. Too late now :( ^<b style="color:#000">demon</b><sup style="color:#c22">[omg plz] 16:26, 17 November 2014 (UTC)</i>

UNIVERSALLANGUAGESELECTOR -> ULS
Established abbreviation of a quite common extension. But on the other hand I don't know if it would be inconsistent given not many other extensions are getting shorter ones. --Nikerabbit (talk) 09:25, 17 November 2014 (UTC)