Re: [xwiki-devs] [VOTE] Make the Wiki API + Script modules be core modules

+1 The model is Wiki, Space, Document, (Class), Object. It does not make much (and seems like an arbitrary decision) to consider API for Space, Document, (Class), Object as core API, but API for wikis to be treated as non-core and optional. Yes, we come from a single-wiki initial implementation, but we have long evolved from that state and should, IMO, start behaving accordingly. For instance, when we write code, it should be a given the code itself runs on a multiwiki environment and it should run the same, whether it's on the main wiki or in a subwiki and it could even interact with documents from other wikis than the current one. Ideally the wiki API code should be located in oldcore, where the rest of the API for interacting with the model is located, but since we (decided that we) can not extend it any more (in an effort to deprecate it eventually), we ended up with a separate module which looks like it's separate, but actually belongs next to the other space, document, etc. API. Also note that the wiki API also comes with extra API about users and wiki type (wiki.user) and also with extra API when creating wikis from templtes (wiki.template). I`m not sure about these API and I guess we could let extensions explicitly depend on them if they need them to be present at runtime. Finally, if we are including java and script service API, I guess we need to include the REST API as well, which features only the creation methods. This as well should ideally be present in the base REST API, but since the whole wiki module was viewed as an extension before, this was the only way to add it. If we change our point of view now, perhaps it could be merged with the base REST API, since that is outside oldcore. Even the now old "new model", that we are trying for years now to do, includes wikis as first class citizens. Thanks, Eduard On Mon, Aug 31, 2015 at 6:33 PM, vincent(a)massol.net <vincent(a)massol.net> wrote: