On Tue, Nov 25, 2014 at 9:45 PM, James Forrester <jforrester(a)wikimedia.org>
wrote:
I can't find documentation anywhere for what's valid in callsigns besides
"uppercase", but seeing feature requests for stuff like "Allow digits in
callsigns" and "allow hyphens in callsigns" I'm suspecting the
character
set is literally [A-Z]. Which means a lot of the callsigns you have on that
page aren't even valid.
Is the "repo name" column there supposed to be meaning "rename
'mediawiki/extensions/AbuseFilter' to just 'AbuseFilter'"? If
that's the
case, then IMO the proposed naming is simply awful. We have so many
repositories that namespacing them is essential to make any sense out of
things without already knowing what is what. For example, what's "Donate"?
An extension for donations would be my guess. It's much clearer when it's
called "mediawiki/skins/Donate", then you know it's actually a skin. And
your own naming conventions page says that "Example" is a bad name, and yet
you're proposing renaming "mediawiki/skins/Example" to "Example"
and
"mediawiki/extensions/Examples" to "Examples"!
elsewhere in this thread, it looks like this whole idea of
"callsigns" is a
response to someone having a problem with resolving svn revision numbers on
the level of single-digit numbers of repositories. It doesn't seem to me
that it will scale AT ALL to the hundreds of repositories that we have, and
we're extremely likely to be running into problems that are far more
serious than the claimed problems from calling a repository "/core".
If we can't -2 the whole idea of required callsigns, it seems to me we'd be
better served by just treating them as random base-26 integers with no
inherent meaning.
--
Brad Jorsch (Anomie)
Software Engineer
Wikimedia Foundation