On Sep 3, 2013, at 2:54 PM, Vincent Massol <[email protected]> wrote:
> > On Sep 2, 2013, at 12:02 PM, Vincent Massol <[email protected]> wrote: > >> Hi devs, >> >> We've recently discussed about renaming the notion of (sub)wiki from "wiki" >> to "subwiki". We've discussed this in the context of integrating creation of >> (sub)wikis by default in the platform and in XE. So the latest discussion >> seemed to agree about: >> * Calling the whole system a "Wiki" >> * Calling each (sub)wikis a "SubWiki" >> >> Now, I was working on updating the new model branch I have created to align >> to this and to rename my Server class to a Wiki class and my existing Wiki >> class to a SubWiki class… >> >> I've realized that aligning our API on this is a huge task since we have >> tons of APIs using the word "wiki". Just to cite 3: >> * WikiReference (reference) >> * WikiComponentScope.WIKI (wiki component) >> * WikiDeletedEvent (bridge) >> >> It's a bit everywhere and changing that seems too big a task IMO. >> >> Thus we have 2 real choices IMO: >> * Agree that the UI has a different wording than the API: SubWiki for the UI >> and Wiki for the API >> * Don't use subwiki in the UI and keep using Wiki in the UI and find another >> word to represent the whole system (System/Portal/Wiki System/WMS = Wiki >> Management System/Home/etc). > > 3rd choice: > * Use SubWiki whenever we create new APIs > * Keep existing APIs unchanged > * This means that progressively our API will move from "Wiki" to "SubWiki". > > This is maybe the more realistic solution, even if not perfect, WDYT? Personally I'm fine to keep the "Wiki" terminology and thus have Add > Wiki. Thanks -Vincent > Thanks > -Vincent > >> WDYT? >> >> Thanks >> -Vincent >> > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
