On Mar 25, 2011, at 9:19 AM, Thomas Mortagne wrote: > On Fri, Mar 25, 2011 at 09:09, Vincent Massol <[email protected]> wrote: >> >> On Mar 25, 2011, at 9:05 AM, Thomas Mortagne wrote: >> >>> On Fri, Mar 25, 2011 at 08:57, Vincent Massol <[email protected]> wrote: >>>> Hi Sergiu, >>>> >>>> On Mar 25, 2011, at 12:31 AM, Sergiu Dumitriu wrote: >>>> >>>>> Hi devs, >>>>> >>>>> I'd like to start moving very old plugins out of the core and into the >>>>> contrib/retired repository. >>>> >>>> I agree for plugins for which we have other ways of doing things (either >>>> it's been rewritten with a newer architecture or there's another way of >>>> doing it). >>>> >>>>> For the moment, this includes: >>>>> - PatternPlugin (regexp based text replacements when running the old >>>>> rendering engine) >>>> >>>> +1 >>>> >>>>> - TablePlugin (pre-Radeox support for wiki table syntax) >>>> >>>> +1 >>>> >>>>> - GooglePlugin (search and spelling suggestions) >>>> >>>> How is this one supposed to work? Do we want to keep its feature as a >>>> component? If yes then -0 >>>> >>>>> - GraphViz (graph drawing, unmaintained for a long time; should be >>>>> replaced with a component) >>>> >>>> This one is useful and used by several users I know. I'd be -0 to move it >>>> out. IMO it should be removed but only once we have it rewritten as >>>> components only. >>>> >>>>> - MailPlugin (unmaintained mailbox reading plugin) >>>> >>>> This feature can be useful too. >>>> >>>> -0 >>>> >>>>> - QueryPlugin (old, unused precursor of the query service) >>>> >>>> +1 >>>> >>>>> - SVG (old, unmaintained plugin; should be replaced with a component) >>>> >>>> -0 >>>> >>>>> - testPlugin (test plugin, writen as a test plugin to test the plugin >>>>> functionality :) ) >>>> >>>> +1 >>>> >>>>> - XWikiUserManagementTools (precursor for the invitation application, >>>>> unmaintained) >>>> >>>> +1 >>>> >>>>> The remaining plugins must be rewritten as components first, since they >>>>> still provide useful functionality. >>>> >>>> This I agree: >>>> >>>> - move out plugins that we don't want anymore >>>> - keep plugins for which we want to keep the features and remove them once >>>> they've been migrated to components >>> >>> We should move them from xwiki-core if it's not maintained. >> >> Yes but I don't agree that we don't want to maintain them or that we're not >> maintaining them (it's not because there haven't been changes for a long >> time that we're not maintaining them). IMO they're interesting enough to >> maintain them (I'm talking for the ones where I've put -0). Maintaining >> means having the feature available. It doesn't matter in which technology. >> Imagine if we moved in contrib all code that has technology we don't like... >> we would be left with less than 50% of the whole code... :) > > You forget the xwiki-legacy part of my answer. Ok "maintained" is not > the right word, all things in xwiki-legacy are deprecated but supposed > to work.
Indeed I missed the xwiki-legacy part of your answer :) Yes that would sound better but it would need to be reorganized as a parent module with children which can be released independently. Thanks -Vincent >> Thanks >> -Vincent >> >>> We don't >>> have to completely remove them, they can go to xwiki-legacy which is >>> here for that kind of use case. >>> >>>> >>>> Thanks >>>> -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
