[xwiki-devs] [VOTE] Modify XEM distribution to become a Workspace distribution
Hi devs, Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution. However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users. So here's my proposal (and what you should vote on): A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualization we keep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it. Here'd my +1 Thanks -Vincent
+1 Jerome On Tue, Nov 22, 2011 at 2:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualization we keep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jérôme Velociter Winesquare http://www.winesquare.net/
+1 as well. Looking forward to it! Guillaume On Tue, Nov 22, 2011 at 5:21 PM, Jerome Velociter <[email protected]>wrote:
+1
Jerome
On Tue, Nov 22, 2011 at 2:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Jérôme Velociter Winesquare http://www.winesquare.net/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 as well. -Fabio On Tue, Nov 22, 2011 at 2:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualization we keep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Tue, Nov 22, 2011 at 14:40, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features.
Does it means that it is similar to now, except that the workspaces module is loaded and welcome you ? If you do not use it, and access the wiki manager, is there any issue, or could you administer a farm ?
B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
2011/11/22 Denis Gervalle <[email protected]>
On Tue, Nov 22, 2011 at 14:40, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application )
I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features.
Does it means that it is similar to now, except that the workspaces module is loaded and welcome you ? If you do not use it, and access the wiki manager, is there any issue, or could you administer a farm ?
The Wiki Manager would still be there but not initially visible. All the modules which allow running a farm would still be there. Ludovic
B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
On Tue, Nov 22, 2011 at 18:25, Ludovic Dubost <[email protected]> wrote:
2011/11/22 Denis Gervalle <[email protected]>
On Tue, Nov 22, 2011 at 14:40, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application
)
I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features.
Does it means that it is similar to now, except that the workspaces module is loaded and welcome you ? If you do not use it, and access the wiki manager, is there any issue, or could you administer a farm ?
The Wiki Manager would still be there but not initially visible. All the modules which allow running a farm would still be there.
+0,5 on this one then. I am just worried that using the same distribution for something different could cause some confusion for those upgrading.
Ludovic
B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwekeep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could
call
it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
+1 On Tue, Nov 22, 2011 at 2:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualization we keep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Hi Vincent, On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm
C) We create an application in xwiki-platform-core/ that contains the
current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki
The pages that are strictly related to XEM can be found at https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main... There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM and a listing of current wikis * XemManager.Install -> Install page for a wiki template. This page is supposed to have automatically the latest XE xar attached to it. This was working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations. Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage. I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application. I`m +1 for everything else. Thanks, Eduard
D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Tue, Nov 22, 2011 at 9:11 PM, Eduard Moraru <[email protected]> wrote:
Hi Vincent,
On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm
C) We create an application in xwiki-platform-core/ that contains the
current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki
The pages that are strictly related to XEM can be found at https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main...
There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM and a listing of current wikis * XemManager.Install -> Install page for a wiki template. This page is supposed to have automatically the latest XE xar attached to it. This was working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations.
Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage.
I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application.
I`m +1 for everything else.
Same comment for me, I voted a bit quickly mostly on the title. What's in XEM is only packaging and only make sense for a distribution. It's pretty much useless from platform point of view.
Thanks, Eduard
D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Nov 22, 2011, at 9:11 PM, Eduard Moraru wrote:
Hi Vincent,
On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm
C) We create an application in xwiki-platform-core/ that contains the
current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki
The pages that are strictly related to XEM can be found at https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main...
There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM and a listing of current wikis
AFAIR there was "dashboard" on the home page: wikis you view, wikis you own, wikis you administrate, recent wikis.
* XemManager.Install -> Install page for a wiki template. This page is supposed to have automatically the latest XE xar attached to it. This was working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations.
Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage.
I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application.
Good points, I agree. Makes a lot of sense. I'd then propose to include the XEM dashboard as the WebHome of WikiManager Thanks -Vincent
I`m +1 for everything else.
Thanks, Eduard
D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
On Wed, Nov 23, 2011 at 7:58 PM, Vincent Massol <[email protected]> wrote:
On Nov 22, 2011, at 9:11 PM, Eduard Moraru wrote:
Hi Vincent,
On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm
C) We create an application in xwiki-platform-core/ that contains the
current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki
The pages that are strictly related to XEM can be found at https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main...
There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM and a listing of current wikis
AFAIR there was "dashboard" on the home page: wikis you view, wikis you own, wikis you administrate, recent wikis.
The page itself just include widgets which are in wiki manager.
* XemManager.Install -> Install page for a wiki template. This page is supposed to have automatically the latest XE xar attached to it. This was working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations.
Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage.
I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application.
Good points, I agree. Makes a lot of sense.
I'd then propose to include the XEM dashboard as the WebHome of WikiManager
I don't like it very much, WikiManager home page is an admin page to manipulate wikis, this kind of dashboard would be useless for them IMO.
Thanks -Vincent
I`m +1 for everything else.
Thanks, Eduard
D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Nov 23, 2011, at 8:42 PM, Thomas Mortagne wrote:
On Wed, Nov 23, 2011 at 7:58 PM, Vincent Massol <[email protected]> wrote:
On Nov 22, 2011, at 9:11 PM, Eduard Moraru wrote:
Hi Vincent,
On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm
C) We create an application in xwiki-platform-core/ that contains the
current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki
The pages that are strictly related to XEM can be found at https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main...
There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM and a listing of current wikis
AFAIR there was "dashboard" on the home page: wikis you view, wikis you own, wikis you administrate, recent wikis.
The page itself just include widgets which are in wiki manager.
* XemManager.Install -> Install page for a wiki template. This page is supposed to have automatically the latest XE xar attached to it. This was working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations.
Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage.
I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application.
Good points, I agree. Makes a lot of sense.
I'd then propose to include the XEM dashboard as the WebHome of WikiManager
I don't like it very much, WikiManager home page is an admin page to manipulate wikis, this kind of dashboard would be useless for them IMO.
So you think we should just remove the dashboard? Or would you be ok to have the dashboard page in the wikimanager app but not on the home page? Thanks -Vincent
Thanks -Vincent
I`m +1 for everything else.
Thanks, Eduard
D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
On Wed, Nov 23, 2011 at 9:10 PM, Vincent Massol <[email protected]> wrote:
On Nov 23, 2011, at 8:42 PM, Thomas Mortagne wrote:
On Wed, Nov 23, 2011 at 7:58 PM, Vincent Massol <[email protected]> wrote:
On Nov 22, 2011, at 9:11 PM, Eduard Moraru wrote:
Hi Vincent,
On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm
C) We create an application in xwiki-platform-core/ that contains the
current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki
The pages that are strictly related to XEM can be found at https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main...
There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM and a listing of current wikis
AFAIR there was "dashboard" on the home page: wikis you view, wikis you own, wikis you administrate, recent wikis.
The page itself just include widgets which are in wiki manager.
* XemManager.Install -> Install page for a wiki template. This page is supposed to have automatically the latest XE xar attached to it. This was working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations.
Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage.
I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application.
Good points, I agree. Makes a lot of sense.
I'd then propose to include the XEM dashboard as the WebHome of WikiManager
I don't like it very much, WikiManager home page is an admin page to manipulate wikis, this kind of dashboard would be useless for them IMO.
So you think we should just remove the dashboard?
Or would you be ok to have the dashboard page in the wikimanager app but not on the home page?
This could be a WikiManager.Dashboard page provided to anyone that would want to include it somewhere like in the main wiki home page. The best would probably be to rewrite the widgets to be supported by the new dashboard system but it's really not a priority.
Thanks -Vincent
Thanks -Vincent
I`m +1 for everything else.
Thanks, Eduard
D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Thu, Nov 24, 2011 at 12:34, Thomas Mortagne <[email protected]>wrote:
On Wed, Nov 23, 2011 at 9:10 PM, Vincent Massol <[email protected]> wrote:
On Nov 23, 2011, at 8:42 PM, Thomas Mortagne wrote:
On Wed, Nov 23, 2011 at 7:58 PM, Vincent Massol <[email protected]>
wrote:
On Nov 22, 2011, at 9:11 PM, Eduard Moraru wrote:
Hi Vincent,
On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]>
wrote:
Hi devs,
Since Eduard has developed the workspaces module (see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application )
I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm
C) We create an application in xwiki-platform-core/ that contains the
current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki
The pages that are strictly related to XEM can be found at
https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main...
There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM and
a
listing of current wikis
AFAIR there was "dashboard" on the home page: wikis you view, wikis you own, wikis you administrate, recent wikis.
The page itself just include widgets which are in wiki manager.
* XemManager.Install -> Install page for a wiki template. This page is supposed to have automatically the latest XE xar attached to it. This
was
working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations.
Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage.
I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application.
Good points, I agree. Makes a lot of sense.
I'd then propose to include the XEM dashboard as the WebHome of WikiManager
I don't like it very much, WikiManager home page is an admin page to manipulate wikis, this kind of dashboard would be useless for them IMO.
So you think we should just remove the dashboard?
Or would you be ok to have the dashboard page in the wikimanager app but not on the home page?
This could be a WikiManager.Dashboard page provided to anyone that would want to include it somewhere like in the main wiki home page. The best would probably be to rewrite the widgets to be supported by the new dashboard system but it's really not a priority.
+1 for this, and maybe for a few release, we could have a link to it on the new Main.WebHome for those who could be surprised by the change. WDYT ?
Thanks -Vincent
Thanks -Vincent
I`m +1 for everything else.
Thanks, Eduard
D) Users who want to install xwiki-platform-multiwiki easily will
use the
Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
The XEM dashboard is not a good quality dashboard. It would need to be rethought. I don't know of users that actually use it. I suggest removing it in the meantime. Ludovic 2011/11/24 Thomas Mortagne <[email protected]>
On Wed, Nov 23, 2011 at 9:10 PM, Vincent Massol <[email protected]> wrote:
On Nov 23, 2011, at 8:42 PM, Thomas Mortagne wrote:
On Wed, Nov 23, 2011 at 7:58 PM, Vincent Massol <[email protected]>
wrote:
On Nov 22, 2011, at 9:11 PM, Eduard Moraru wrote:
Hi Vincent,
On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]>
wrote:
Hi devs,
Since Eduard has developed the workspaces module (see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application )
I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwe keep documenting how to transform XE into a wiki farm
C) We create an application in xwiki-platform-core/ that contains the
current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki
The pages that are strictly related to XEM can be found at
https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main...
There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM and
a
listing of current wikis
AFAIR there was "dashboard" on the home page: wikis you view, wikis you own, wikis you administrate, recent wikis.
The page itself just include widgets which are in wiki manager.
* XemManager.Install -> Install page for a wiki template. This page is supposed to have automatically the latest XE xar attached to it. This
was
working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations.
Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage.
I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application.
Good points, I agree. Makes a lot of sense.
I'd then propose to include the XEM dashboard as the WebHome of WikiManager
I don't like it very much, WikiManager home page is an admin page to manipulate wikis, this kind of dashboard would be useless for them IMO.
So you think we should just remove the dashboard?
Or would you be ok to have the dashboard page in the wikimanager app but not on the home page?
This could be a WikiManager.Dashboard page provided to anyone that would want to include it somewhere like in the main wiki home page. The best would probably be to rewrite the widgets to be supported by the new dashboard system but it's really not a priority.
Thanks -Vincent
Thanks -Vincent
I`m +1 for everything else.
Thanks, Eduard
D) Users who want to install xwiki-platform-multiwiki easily will
use the
Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
On Thu, Nov 24, 2011 at 14:43, Ludovic Dubost <[email protected]> wrote:
The XEM dashboard is not a good quality dashboard. It would need to be rethought.
Agreed, but...
I don't know of users that actually use it.
since you do not know, removing it is still risky. If some user are actually use it, they will be really annoyed not finding it anywhere. This is why I suggested for a few version to have an explanatory text on the new dashboard, with a link to the old one. Providing a smooth transition, and keeping the old dashboard available.
I suggest removing it in the meantime.
I am -1 on removing something we have had for so long without a transition period. Denis
Ludovic
2011/11/24 Thomas Mortagne <[email protected]>
On Wed, Nov 23, 2011 at 9:10 PM, Vincent Massol <[email protected]> wrote:
On Nov 23, 2011, at 8:42 PM, Thomas Mortagne wrote:
On Wed, Nov 23, 2011 at 7:58 PM, Vincent Massol <[email protected]>
wrote:
On Nov 22, 2011, at 9:11 PM, Eduard Moraru wrote:
Hi Vincent,
On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]
wrote:
> Hi devs, > > Since Eduard has developed the workspaces module (see >
http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application
)
> I'd like to push for using it in our XEM distribution. > > However there are 2 valid uses cases that exist: > 1) Using XE + workspaces, for creating workspaces (technically each > workspace being a wiki) > 2) Using XE as a wiki farm > > I think that use case 1) is the main use case for most people and this > vote is about keeping the XEM packaging/branding but repurposing so that > XEM implements use case 1). Use case 2) exists but it's less frequent and > for more technically advanced users. > > So here's my proposal (and what you should vote on): > > A) XEM = app manager module + wiki manager module + workspaces module(s). > XEM home page becomes the workspaces app home page. We update > manager.xwiki.org to align it with the fact that it now boasts the > workspaces features. > B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualizationwekeep documenting how to transform XE into a wiki farm > C) We create an application in xwiki-platform-core/ that contains the > current pages located in XEM (home page + the other pages). We could call > it xwiki-platform-multiwiki >
The pages that are strictly related to XEM can be found at
https://github.com/xwiki/xwiki-manager/tree/master/xwiki-manager-ui/src/main...
There, you have: * Main.WebHome -> main wiki home with a couple of words about XEM
and a
listing of current wikis
AFAIR there was "dashboard" on the home page: wikis you view, wikis you own, wikis you administrate, recent wikis.
The page itself just include widgets which are in wiki manager.
* XemManager.Install -> Install page for a wiki template. This page
is
supposed to have automatically the latest XE xar attached to it. This was working when it was part of the XEM product, but if we plan to put it into platform, we need to let the admin upload the XE xar (or any other xar that (s)he wishes to use for the template), just like we did for workspaces. * Panels.QuickLinks -> Override of the standard quick links panel that contains an extra link to the wiki manager if the current user is an admin * XemResources.* -> Translations page with 7 keys strictly related to the XemManager.Install page * Xapp.XWikiApplicationXem -> Application descriptor for the application manager. AFAIK, it's just a way to automatically register the above translations.
Now, knowing the above, does it make sense to name a platform package that is supposed to contain the above pages "xwiki-platform-multiwiki" ? If someone installs this package, they will not actually get multiwiki capabilities, they will just get a new homepage.
I think that the xwiki-platform-wiki-manager module (application) offers everything needed for the 2) wiki farm use case and that, from the platform's point of view (and maybe the user's as well), the proposed extra xwiki-platform-multiwiki would bring no value. The only valuable item is (maybe) the homepage, but I propose we drop all of the above and let users use the wiki manager application.
Good points, I agree. Makes a lot of sense.
I'd then propose to include the XEM dashboard as the WebHome of WikiManager
I don't like it very much, WikiManager home page is an admin page to manipulate wikis, this kind of dashboard would be useless for them IMO.
So you think we should just remove the dashboard?
Or would you be ok to have the dashboard page in the wikimanager app but not on the home page?
This could be a WikiManager.Dashboard page provided to anyone that would want to include it somewhere like in the main wiki home page. The best would probably be to rewrite the widgets to be supported by the new dashboard system but it's really not a priority.
Thanks -Vincent
Thanks -Vincent
I`m +1 for everything else.
Thanks, Eduard
> D) Users who want to install xwiki-platform-multiwiki easily will
use the
> Extension Manager UI when it's ready for general consumption > E) Users who want to install xwiki-platform-workspace easily will use the > Extension Manager UI when it's ready for general consumption. At this point > we'll decide if we want to drop the XEM distribution or keep both ways of > installing it. > > Here'd my +1 > > Thanks > -Vincent
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO
+0 Thanks, Marius On Tue, Nov 22, 2011 at 3:40 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
Since Eduard has developed the workspaces module (see http://extensions.xwiki.org/xwiki/bin/view/Extension/Workspace+Application) I'd like to push for using it in our XEM distribution.
However there are 2 valid uses cases that exist: 1) Using XE + workspaces, for creating workspaces (technically each workspace being a wiki) 2) Using XE as a wiki farm
I think that use case 1) is the main use case for most people and this vote is about keeping the XEM packaging/branding but repurposing so that XEM implements use case 1). Use case 2) exists but it's less frequent and for more technically advanced users.
So here's my proposal (and what you should vote on):
A) XEM = app manager module + wiki manager module + workspaces module(s). XEM home page becomes the workspaces app home page. We update manager.xwiki.org to align it with the fact that it now boasts the workspaces features. B) On http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualization we keep documenting how to transform XE into a wiki farm C) We create an application in xwiki-platform-core/ that contains the current pages located in XEM (home page + the other pages). We could call it xwiki-platform-multiwiki D) Users who want to install xwiki-platform-multiwiki easily will use the Extension Manager UI when it's ready for general consumption E) Users who want to install xwiki-platform-workspace easily will use the Extension Manager UI when it's ready for general consumption. At this point we'll decide if we want to drop the XEM distribution or keep both ways of installing it.
Here'd my +1
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (9)
-
Denis Gervalle -
Eduard Moraru -
Fabio Mancinelli -
Guillaume Lerouge -
Jerome Velociter -
Ludovic Dubost -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol