On 22/09/10 05:34, Trevor Parscal wrote: <argument #2 against merging>
- 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 can easily understand code.
Arguments I have made/observed *for* merging things into core include:
- MediaWiki should be awesome out-of-the-box, so extensions that would be good for virtually everyone seem silly to bury deep within the poorly organized depths of the extensions folder.
What about shipping the Mediawiki release with some of the best extensions ? You do not need to actually merge them with trunk, just chip mediawiki + some extensions preconfigured. Hooks in the installer would let user tweak the configuration. I had a little script which, given a revision number would : - installed trunk and stable branch - copy my favorite extensions in the extension folders - append to local settings my extension configuration files
<snip>
If we are to develop guidelines for when to push things in/pull things out of core, ...
Would you move as extensions : squid support, math, languages, external stores, external auth, API, chinese support, Tidy, Antivirus ... They are all awesome features but not necessarily needed in core.