Hi devs,
Now that we have a SOLR search, I think we should close all Lucene-related JIRA issues as won't fix, remove the Lucene search by default in XWiki 5.3 and move it to xwiki-contrib.
I don't think we want to maintain 2 implementation especially since the SOLR one is better.
Here's my +1.
Thanks
-Vincent
Hello devs,
XWiki 5.2 M2's release has been postponed until this Wednesday. I'll test
the latest features, validate the bugs fixed for this version and also do a
full manual test in the following days. Is there anything else you want me
to test ?
Thank you,
Manuel
Hi devs,
As discussed with some of you on IRC I'm proposing to postpone the 5.2M2 release till Wednesday (Marius is RM BTW).
This should allow us to commit stuff that's on the roadmap for M2 and then tune them/improve them for the RC1 release.
Thanks
-Vincent
For the Workspace integration in XE, I need to modify the default XARs. It
makes me able to provide template XARs for the creation of subwikis, which
will be different from the XAR of the main wiki (for example: we don't need
the WorkspaceManager UI in every subwikis).
What I propose to do:
1/ Create a subproject *xwiki-enterprise-workspace-ui*, which defines what
a workspace should be.
1bis/ Create a *xwiki-enterprise-workspace-ui-all* too, in *
xwiki-enterprise-distribution*
2/ Create a subproject *xwiki-enterprise-wiki-ui*, which defines what a
subwiki should be.
2bis/ Create a *xwiki-enterprise-wiki-ui-all* too, in *
xwiki-enterprise-distribution*
3/ Add *xwiki-enterprise-wiki-ui* as a dependency of *xwiki-enterprise-ui*.
This will be a temporary solution, because we will have flavours in the
future.
WDYT?
Louis-Marie
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).
WDYT?
Thanks
-Vincent
Hi devs,
I'm working on the Active Installs module and I need to add a unique instance id in the database.
I'm proposing to put that code in a new module called xwiki-platform-instance. Right now it would only contain the unique id but int he future it could contain code related specifically to the xwiki instance.
I'd like to do this quickly. Let me know what you think.
Thanks
-Vincent
Hi devs,
Could all of you who added some UIX please make sure they are documented on http://extensions.xwiki.org/xwiki/bin/view/Extension/UIExtension+Module#HAv…
For example I can see that the "org.xwiki.platform.search" UIX is not documented…
It's very important since UI are like public APIs (probably even more important since they impact the visual appearance).
Thanks!
-Vincent