Hi. On 19 July 2012 14:53, Markus Krötzsch <[email protected]> wrote: > Jeroen did not suggest to move outside of MW git. The idea is just to > combine several closely related repos into one.
Yes, but would it be a _normal_ repo? How would the workflow be? Now you clone MW, then you get into the extensions dir and clone the extensions. Would this still work? How would you pull only some extensions of the package? Would this even be possible? If at some point an extension is deemed to be unmaintained, would it just be dropped from the HEAD version? Exported to its own repo again? I admit, I am always a bit suspicious of "package deals". I would rather decide myself, which extensions I need. But that is of course a personal preference. >> By the way, on the point of forcing developers to maintain their code: >> It might help if SMW's interface would not break all the time. Just >> saying. >> > > Suggestions are always welcome. I think the last big change to any API in > SMW was the introduction of DI classes over a year ago. Compatibility > classes and extensive emails have been provided to simplify the transition. And this was done very well, indeed. You did a great job there. The problem are not the big structural changes, but the small insignificant. One case I had lately was a function that just disappeared from the codebase (SMW_QueryPrinter.php::getValidatorParameters). Another example is a case where a function got introduced in 1.6 (I think) only to be marked as deprecated in 1.7 or 1.8. (And no, I do not remember which function that was.) Anyway, this got to much attention already. I never meant to discuss it in that much depth. Just wanted to point out that it is not always easy top keep up with the development of SMW. And I am not sure putting extensions in a common repo would improve this. Cheers, Stephan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Semediawiki-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
