At 2010-10-13 05:10, Trevor Parscal wrote:
On 10/12/10 8:03 PM, Chad wrote:
On Tue, Oct 12, 2010 at 10:45 PM, Trevor Parscaltpars...@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;
Trevor Parscal wrote:
On 10/12/10 10:29 PM, Ryan Lane wrote:
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
My take:
1. Vector is a terrible name for the extension, because it overloads
terminology. Now when somebody asks about Vector, we won't know if
they're talking about the skin or the extra features. The number one
thing that we engineers can do to make things simpler for users and
administrators
2010/10/13 Trevor Parscal tpars...@wikimedia.org:
That's an entirely different discussion, and the results of that
discussion have so far been that any such action is being deferred until
after 1.17.
With pretty much every participant in this thread (including myself,
for the record) saying we
On Wed, Oct 13, 2010 at 1:29 AM, Ryan Lane rlan...@gmail.com wrote:
Please, please, don't rename it again. Every time the name changes
things break. They break for us, they break for third parties using
SVN, and it breaks our ability to easily support the extensions when
people ask for help.
At 2010-10-13 09:12, Roan Kattouw wrote:
2010/10/13 Trevor Parscaltpars...@wikimedia.org:
That's an entirely different discussion, and the results of that
discussion have so far been that any such action is being deferred until
after 1.17.
With pretty much every participant in this thread
Thank you, everyone, for responding so far (not trying to stop you
here). Here's where it seems we're at.
1. Having an extension called Vector is neither descriptive or
clear, and it is anticipated to cause confusion.
2. System administrators are not enjoying things being switched
On 13 October 2010 10:54, Trevor Parscal tpars...@wikimedia.org wrote:
3. 3 out of 5 code reviewers are voting that it should be merged into
core (Brion and Tim have not weighed in yet).
Does it matter if one is one of the six persons that were lately
assigned to do code review or not?
On 2010-10-13, Trevor Parscal wrote:
Thank you, everyone, for responding so far (not trying to stop you
here). Here's where it seems we're at.
1. Having an extension called Vector is neither descriptive or
clear, and it is anticipated to cause confusion.
2. System
On Wed, Oct 13, 2010 at 9:00 PM, Robert Leverington rob...@rhl.me.uk wrote:
On 2010-10-13, Trevor Parscal wrote:
Thank you, everyone, for responding so far (not trying to stop you
here). Here's where it seems we're at.
1. Having an extension called Vector is neither descriptive or
2010/10/13 Maciej Jaros e...@wp.pl:
WikiEditor is a different thing at current stage. It breaks WYSIWYG made
from FCKeditor and don't give anything important in exchange. Vector
extension is ready to work while WikiEditor still needs a lot of work if
you ask me.
Good point. I was gonna
Offhand I hadn't even realized there were still chunks of Vector in an
extension since it got merged in as a skin! :)
More than the naming issue, it's important IMO to make sure that units that
belong together ship together and get enabled together. That definitely ties
in with the concerns about
On 10/13/10 3:00 AM, Robert Leverington wrote:
On 2010-10-13, Trevor Parscal wrote:
Thank you, everyone, for responding so far (not trying to stop you
here). Here's where it seems we're at.
1. Having an extension called Vector is neither descriptive or
clear, and it is
Conversation has been taking place on CodeReview about whether people
(developer and system administrators) will find it confusing that
there's code in both extensions/Vector and skins/vector that are
related but not the same thing.
I personally find it simple to understand and don't expect
On Tue, Oct 12, 2010 at 8:35 PM, Trevor Parscal tpars...@wikimedia.org wrote:
I personally find it simple to understand and don't expect most
developers and system administrators to feel otherwise,
People are still confused with Wikimedia/MediaWiki to this day.
You think skins/vector and
On 10/12/2010 8:35 PM, Trevor Parscal wrote:
Conversation has been taking place on CodeReview about whether people
(developer and system administrators) will find it confusing that
there's code in both extensions/Vector and skins/vector that are
related but not the same thing.
I
On 10/12/10 6:10 PM, Alex wrote:
On 10/12/2010 8:35 PM, Trevor Parscal wrote:
Conversation has been taking place on CodeReview about whether people
(developer and system administrators) will find it confusing that
there's code in both extensions/Vector and skins/vector that are
related
On 10/12/2010 9:58 PM, Trevor Parscal wrote:
On 10/12/10 6:10 PM, Alex wrote:
On 10/12/2010 8:35 PM, Trevor Parscal wrote:
Conversation has been taking place on CodeReview about whether people
(developer and system administrators) will find it confusing that
there's code in both
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]
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]
On Tue, Oct 12, 2010 at 10:45 PM, Trevor Parscal tpars...@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
On 10/12/10 8:03 PM, Chad wrote:
On Tue, Oct 12, 2010 at 10:45 PM, Trevor Parscaltpars...@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]
On Tue, Oct 12, 2010 at 11:10 PM, Trevor Parscal tpars...@wikimedia.org wrote:
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?
That would be this one:
Show me the convention for naming
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
On 10/12/10 10:29 PM, Ryan Lane wrote:
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
25 matches
Mail list logo
