Re: [xwiki-devs] [Discussion] Make Invitation Application storage and configuration comparable with Invitation Manager plugin.

Hi Caleb, On Tue, May 11, 2010 at 00:34, Caleb James DeLisle <calebdelisle(a)lavabit.com +1 for this (see my reasoning below). I don't think that's a sound idea. A lot of work for little benefit. I think Ludovic's point of view is affected by the fact that he spent a lot of time working on Curriki. While I understand and sympathize a lot with it knowing where it comes from, I also think that you're making a lot of pretty valid points about why both applications should not necessarily be compatible. The different syntax, the different model (wiki application versus plugin), the different feature requirements make it a new application versus an improvement on the old one. In any case I'm not sure that even with the improvements you suggested the application would be usable in Curriki's context. The space and invitation manager have been tailored very specifically for that project, and while it's a shame that we're not able to reuse that code, we also have to acknowledge the fact that the XWiki platform has evolved a (huge) lot since those plugin were released. This means that more than their code itself, it's the way how they're architected that pauses the real issue - thus making them beyond repair. As for the migration path, as I mentioned it, besides Curriki and the retired XWiki Workspaces project that plugin is not used anywhere to my knowledge. Thus I'm not sure what the migration path would look like. In short, we need to accept that though they share the same name, we're actually talking about 2 different applications. I'm not happy that we're sending code to retirement, but it wouldn't be the first time we do it (the old rendering & WYSIWYG are a good example) and I don't think we've regretted that. My 2 cents, Guillaume -- Guillaume Lerouge Product Manager - XWiki SAS Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/