On 29/02/12 10:09, Antoine Musso wrote: > Daniel Friesen wrote: >> No, no, not a wiki. Let's fork the basic core code we use in MediaWiki >> (routing code, WebRequest, database code, etc...) and turn it into a >> framework library that can be shared with other applications. And then >> use that to write a new blogging engine. > > I would love to have some part of our code made into a framework then > rebase MediaWiki on top of that. We might benefit from it since that > would probably mean more developer will know about our code and thus be > able to submit patch and hack MediaWiki :-) > > Some years ago I have asked to factor out some of our code to submit it > in PEAR, but: > - that repo is too restrictive when it comes to coding style > - we did not want to be depending on a third party > - will have to maintains our code for other usage we have no interest > into. > So I have abandoned the PEAR idea.
It isn't a too bad idea. Although it may not be easy. I suspect there may be hidden knowledge about the deeper layers inside the front end ones. But forcing those classes to be used standalone, can help make a more robust system. _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
