On 10/12/10 8:03 PM, Chad wrote:
On Tue, Oct 12, 2010 at 10:45 PM, Trevor
Parscal<tparscal(a)wikimedia.org> wrote:
On 10/12/10 7:42 PM, MZMcBride wrote:
Trevor Parscal wrote:
> Apologies in advance for the sheer triviality of this matter;
> unfortunately these kinds of bike shed problems [2] tend to be
> infinitely exciting, while complex matters are more often met with
> general disinterest.
>
> [1]
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/73030#c10054
> [2]
http://en.wikipedia.org/wiki/Parkinson%27s_Law_of_Triviality
Naming and naming conventions aren't trivialities.
Show me the convention for naming extensions and I will follow it. As
long as there is none, spending time going back and forth discussing the
name of something that users will never see is indeed spending time on a
trivial matter.
There isn't one. Maybe it's because we haven't cared
until now, or
maybe because we haven't needed it. Policy or not, concerns were
raised about the naming of *this* extension. Saying "well there's
no policy so it's pointless to discuss it" is a cop-out.
I am explicitly requesting discussion about it so that I can take action
based on the desire of the community. What cop-out are you referring to?
The only response I've gotten so far is "merge into core", which is an
interesting response, but does not resolve the issue at hand, which is,
until we do so (assuming we do at some point after 1.17), what should
this extension be named?
I'm not defending the current name any more than stating it's my
preference. I'm not only open to naming it something else, but I'm
asking for input on what to name it.
Some people are being somewhat combatant or getting tangential in their
responses - fine, basically what I expect form this list - but I'm still
very interested in responses to do with my original question, "should we
rename it, and if so, what should we name it?".
IF it should be renamed then I think it has to follow two rules:
1. Should be unique (should not collide with other people ideas)
2. Should tell you a bit about the extension.
In this case "Vector" is wrong. "Vector" might be an extension for SVG
editing or something like that. To my understanding this extension is
about usability of Vector skin and so it might be called VectorUsability
or something more exact.
Having said that I also think Ryan Lane made a very valid point.
Personally I'm still using the extension as part of "Usability
Initiative" and if it is to be integrated into the core I'm not moving
anywhere from that ;-).
Regards,
Nux.