On Wed, Sep 29, 2010 at 3:01 AM, Ryan Lane rlan...@gmail.com wrote:
If we don't plan on doing one of two things, then we are forcing our
users into the crapshoot that is finding the correct extension
version, or possibly running insecure or buggy extensions.
Like we are doing today. So yes,
Chad wrote:
On Tue, Sep 21, 2010 at 11:34 PM, Trevor Parscal wrote:
when to move features out of core and into an extension or
out of an extension and into core.
I don't think anyone's commented on the former (everyone's been
talking about pushing in, not pulling out). IMO, the conditions
Perhaps the new installer could contain that as an option during the
inital setup.
Like a two or three-column thing with a bunch of checkboxes.
Language: English [\/]
Default theme (X) Vector (_) Monobook (_) Foobar
Common Extension: [X] ParserFunctions [X]
Op 29 sep 2010, om 01:15 heeft Platonides het volgende geschreven:
I think the point is to start shipping mediawiki with common
extensions
there.
Yeah, that sounds good !
Perhaps the new installer could contain that as an option during the
inital setup.
Like a two or three-column thing
That seems like a good idea. I would love to see this in action.
-X!
Sent from my iPod
On Sep 28, 2010, at 8:11 PM, Krinkle krinklem...@gmail.com wrote:
Perhaps the new installer could contain that as an option during the
inital setup.
Like a two or three-column thing with a bunch of
I think the point is to start shipping mediawiki with common extensions
there.
This is great if we are going to version the extensions with the
version of MediaWiki shipped, and backport changes to those extensions
to ensure they get security and bug fixes like core does.
Alternatively, we
Roan Kattouw roan.katt...@gmail.com wrote:
2010/9/22 Trevor Parscal tpars...@wikimedia.org:
Modular feature development being unique to extensions points out a
significant flaw in the design of MediaWiki core. There's no reason we
can't convert existing core features to discreet components,
On Fri, Sep 24, 2010 at 3:30 AM, Marcin Cieslak sa...@saper.info wrote:
So before asking how much to add into core, maybe we should
first clean up some, and then possibly add. Or sometimes
adding something (like a proper multi-wiki configuration
management $wgConf++) may clean up and simplify
Tim Starling wrote:
Ryan Lane wrote:
ParserFunctions is an amazing example of this. MediaWiki
simply doesn't work without ParserFunctions. You can tell me it does,
and that people can live without it, but I refuse to believe that. We
get support issues extremely frequently that end in install
On 22/09/10 05:34, Trevor Parscal wrote:
argument #2 against merging
2. Extensions encourage modularity and are easier to learn and work
on because they are smaller sets of code organized in discreet
bundles.
That is probably the most important point. It ease code review, any new
comer
On Tue, Sep 21, 2010 at 8:34 PM, Trevor Parscal tpars...@wikimedia.org wrote:
In response to recent comments in our code review tool about whether
some extensions should be merged into core MediaWiki, or not. I would
like to try and initiate a productive conversation about this topic in
hopes
Trevor Parscal wrote:
In response to recent comments in our code review tool about whether
some extensions should be merged into core MediaWiki, or not. I would
like to try and initiate a productive conversation about this topic in
hopes that we can collaboratively define a set of guidelines
It seems like there are two dimensions to this problem.
X: Should it be part of stock MediaWiki or not
Y: Is it better to write features as discreet modules or spread them out
the way core is currently done
The problem is when you move across X, you are forced to cross Y; If we
were to start
2010/9/22 Trevor Parscal tpars...@wikimedia.org:
Modular feature development being unique to extensions points out a
significant flaw in the design of MediaWiki core. There's no reason we
can't convert existing core features to discreet components, much like
how extensions are written, while
On Tue, Sep 21, 2010 at 11:34 PM, Trevor Parscal tpars...@wikimedia.org wrote:
when to move features out of core and into an extension or
out of an extension and into core.
I don't think anyone's commented on the former (everyone's been
talking about pushing in, not pulling out). IMO, the
On 22 September 2010 13:52, Chad innocentkil...@gmail.com wrote:
Quick note on the installer. It only enables extensions that already
reside in your extensions folder. Since we don't distribute any with
the default package, this might not be terribly useful. More awesome
is Jeroen's GSoC work
On Wed, Sep 22, 2010 at 6:33 PM, Trevor Parscal tpars...@wikimedia.org wrote:
Modular feature development being unique to extensions points out a
significant flaw in the design of MediaWiki core. There's no reason we
can't convert existing core features to discreet components, much like
how
On Tue, Sep 21, 2010 at 11:34 PM, Trevor Parscal tpars...@wikimedia.org wrote:
In response to recent comments in our code review tool about whether
some extensions should be merged into core MediaWiki, or not. I would
like to try and initiate a productive conversation about this topic in
On 9/22/10 9:49 AM, Aryeh Gregor wrote:
Partly this is a matter of preference. I personally write things
almost entirely for core -- I've never written an extension, so my
only extension commits are to things that other people wrote as
extensions. Other people prefer to write extensions
I suppose I have a foot in each camp here.
Ryan Lane wrote:
ParserFunctions is an amazing example of this. MediaWiki
simply doesn't work without ParserFunctions. You can tell me it does,
and that people can live without it, but I refuse to believe that. We
get support issues extremely
In response to recent comments in our code review tool about whether
some extensions should be merged into core MediaWiki, or not. I would
like to try and initiate a productive conversation about this topic in
hopes that we can collaboratively define a set of guidelines for
evaluating when
On 22 September 2010 06:34, Trevor Parscal tpars...@wikimedia.org wrote:
In response to recent comments in our code review tool about whether
some extensions should be merged into core MediaWiki, or not. I would
like to try and initiate a productive conversation about this topic in
hopes that
22 matches
Mail list logo
