[xwiki-devs] [Proposal] Workspace as a Flavor
Hi devs, So this is a proposal to have Workspaces as a Flavor and NOT integrated by default. IMO Workspace is a real nice use case and we should definitely promote it. This is how I envision the main homepage (Home) http://incubator.myxwiki.org/xwiki/bin/download/Improvements/WorkspaceHomepa... and this is how the homepage of a workspace would look like http://incubator.myxwiki.org/xwiki/bin/download/Improvements/WorkspaceHomepa... For more mockups please check the full proposal: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/WorkspaceHomepage The problem is that Workspace Flavor is a use case on it's own and IMO in this particular use case you will not want to have isolated wikis, and plus you will don't want to have lots of the features that are currently by default, so it's really obvious that the Workspace flavor is a specialization of XWiki and will not be anyone's cup of tee. For example, the other Flavors proposed are: - Public Website: you definitely don't need workspaces here - Documentation: same, no need - Application Development: this is intended for development, no need for workspaces See Flavors proposal http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Flavours So Workspaces Flavors is exactly the Groupware Flavor (just I proposed it with another name) http://incubator.myxwiki.org/xwiki/bin/view/Improvements/GroupwareFlavor What I think we should do in 5.2 is indeed have by default the ability to create multiple wikis (so XEM integration, bu without Workspaces). So: - Have 'Add - Wiki' only shown to admins (until we decide otherwise) http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpro... - Have main wiki homepage defined as 'Home' (using the icon and with a customizable title) - Have a consistent create step for wikis, spaces and pages (in just one step, since Members has sense only for Workspaces) http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpro... - Integrate Wiki Manager inside Administration (since it's information related to administrator and should not be public as it is now) We could improve the UI by using a livetable http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpro... All stated above is default functionality that doesn't break backwards compatibility and that is shared between all Flavors. Some base concepts related to Flavors: - Let's consider that what we currently have is a 'Default Flavor' (XE) - We could have a 'Base Flavor' in the future that will consist of 'Default Flavor' minus all the extensions that are not share between all flavors. It will contain just base features and the common denominator for all Flavors. Every time you want to create a new Flavor you could start from this Flavor. - Extra: for test purposes we could also have a 'Full Flavor' containing all the extensions supported by XWiki Development Team. This would be helpful to run the integration tests on it and see if there are possible problems when installing combinations of extensions. Also could serve as a demo flavor of what is possible in XWiki. - There will also be the 'Standard Flavors': Workspaces, Public Website, etc. (proposed and supported by XWiki Development Team) Having this is mind: - Flavors should have the ability to "remove" or alter some pages from the 'Base Flavor' (currently our 'Default Flavor'). For example the Workspace Flavor needs its custom main homepage that list the existing workspace (this doesn't make any sense to any other Flavor). Another example is removing 'Wiki Manager' from 'Default Flavor' and replace it with 'Workspaces Index' that is visible for all users. - Flavors could have their own skin (might need some changed .vm) + preferences (different layout, etc.). In the Workspace Flavor we will want to promote the creation of Workspaces and not Wikis (that is found in the Base Flavor). - Flavors need to integrate other Flavors. For example: 'Workspace Flavor' = 'Base Flavor' + extensions. Also we could have a 'Product Management Flavor' = 'Workspace Flavor' + custom applications installed like: Projects, Deliverables, Meetings, etc. So what we could also do in 5.2 (or 5.3) is: * Flavor definition (from a technical perspective), extensions collections, ability to integrate also pages in the list, etc. * Work separately on the 'Workspace Flavor' which could be our first proposed Flavor (besides the current 'Default Flavor' which is a version of Knowledge Base). This means improving the current 'Workspace Application' with the above proposed Homepages improvements. Let me know what you think, Caty
On Aug 2, 2013, at 11:30 AM, Ecaterina Moraru (Valica) <[email protected]> wrote:
Hi devs,
So this is a proposal to have Workspaces as a Flavor and NOT integrated by default.
I assume this proposal replaces everything you've said so far. It's starting to be hard to follow…
IMO Workspace is a real nice use case and we should definitely promote it.
Which is why we're proposing to have it by default in XE...
This is how I envision the main homepage (Home) http://incubator.myxwiki.org/xwiki/bin/download/Improvements/WorkspaceHomepa...
This is true for subwikis too and not just for workspaces. If I'm on a farm like myxwiki.org and I go to the main wiki dashboard, I'd like to see: * The list of (sub)wikis I can view (what you called "Workspaces" in your screenshot) * Members of the (sub)wikis I can view * Activity stream for the (sub)wikis I can view
and this is how the homepage of a workspace would look like http://incubator.myxwiki.org/xwiki/bin/download/Improvements/WorkspaceHomepa...
This depends on the flavor that the subwiki creator will choose.
For more mockups please check the full proposal: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/WorkspaceHomepage
Note: Those screenshots (the menu ones) no longer correspond to the discussion we've had on the other threads.
The problem is that Workspace Flavor is a use case on it's own and IMO in this particular use case you will not want to have isolated wikis, and plus you will don't want to have lots of the features that are currently by default, so it's really obvious that the Workspace flavor is a specialization of XWiki and will not be anyone's cup of tee.
For example, the other Flavors proposed are: - Public Website: you definitely don't need workspaces here - Documentation: same, no need - Application Development: this is intended for development, no need for workspaces See Flavors proposal http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Flavours
So Workspaces Flavors is exactly the Groupware Flavor (just I proposed it with another name) http://incubator.myxwiki.org/xwiki/bin/view/Improvements/GroupwareFlavor
So you want to rename the Groupware Flavor into the Workspaces Flavor, is that it?
What I think we should do in 5.2 is indeed have by default the ability to create multiple wikis (so XEM integration, bu without Workspaces).
Don't agree. It was the goal of 5.2 to integrate workspaces… What we did say is that we won't have the time (since GuillaumeD is on holidays) to change the home page dashboard though and that we're pushing that to 5.3. But workspaces (aka subwiki) creation should be doable in 5.2.
So: - Have 'Add - Wiki' only shown to admins (until we decide otherwise)
s/wiki/subwiki as shown on the other thread (most people prefer subwiki to wiki). Ok to ask for admin rights for now but we need to add a new subwiki right as discussed previously.
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpro... - Have main wiki homepage defined as 'Home' (using the icon and with a customizable title)
ok
- Have a consistent create step for wikis, spaces and pages (in just one step, since Members has sense only for Workspaces)
s/wiki/subwiki In the creation step, we need to checkbox to decide if local users are allowed or not (with possibly a new right for this too).
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpro... - Integrate Wiki Manager inside Administration (since it's information related to administrator and should not be public as it is now) We could improve the UI by using a livetable http://incubator.myxwiki.org/xwiki/bin/download/Improvements/CreateWikiImpro...
No, not in Admin screen. It's similar to "Documents Index", "Space Index" or "User Index" and they're NOT in the admin and if we allow users to create wikis they should be able to go there without admin rights. Again, why change what was proposed in the previous thread with the menus (i.e. the "Subwiki Index" menu entry in the "Home" menu)?
All stated above is default functionality that doesn't break backwards compatibility and that is shared between all Flavors.
Some base concepts related to Flavors: - Let's consider that what we currently have is a 'Default Flavor' (XE) - We could have a 'Base Flavor' in the future that will consist of 'Default Flavor' minus all the extensions that are not share between all flavors. It will contain just base features and the common denominator for all Flavors. Every time you want to create a new Flavor you could start from this Flavor.
I have no idea whatsoever what "base flavor" means so till it gets defined, I'm -0 on the idea.
- Extra: for test purposes we could also have a 'Full Flavor' containing all the extensions supported by XWiki Development Team. This would be helpful to run the integration tests on it and see if there are possible problems when installing combinations of extensions. Also could serve as a demo flavor of what is possible in XWiki.
-0, some extensions might be mutually exclusive. I prefer that we decide to support 2-3 flavors and we test for those.
- There will also be the 'Standard Flavors': Workspaces, Public Website, etc. (proposed and supported by XWiki Development Team)
I'm still unsure about the Workspaces/Groupware flavor vs Knowledge base. They might be the same one. The knowledge base flavor can need subwikis too.
Having this is mind: - Flavors should have the ability to "remove" or alter some pages from the 'Base Flavor' (currently our 'Default Flavor'). For example the Workspace Flavor needs its custom main homepage that list the existing workspace (this doesn't make any sense to any other Flavor). Another example is removing 'Wiki Manager' from 'Default Flavor' and replace it with 'Workspaces Index' that is visible for all users.
Don't agree, I'd like one notion only: that of subwikis. Whether the subwikis accept local users or not is just a checkbox configuration. See the other threads.
- Flavors could have their own skin (might need some changed .vm) + preferences (different layout, etc.).
Supported already if the skin is in pages. Could be possible with more UIX.
In the Workspace Flavor we will want to promote the creation of Workspaces and not Wikis (that is found in the Base Flavor).
Again I don't agree. Workspaces/wikis == subwikis.
- Flavors need to integrate other Flavors. For example: 'Workspace Flavor' = 'Base Flavor' + extensions. Also we could have a 'Product Management Flavor' = 'Workspace Flavor' + custom applications installed like: Projects, Deliverables, Meetings, etc.
So what we could also do in 5.2 (or 5.3) is: * Flavor definition (from a technical perspective), extensions collections, ability to integrate also pages in the list, etc.
No time for 5.2.
* Work separately on the 'Workspace Flavor' which could be our first proposed Flavor (besides the current 'Default Flavor' which is a version of Knowledge Base). This means improving the current 'Workspace Application' with the above proposed Homepages improvements.
The goal of 5.2 was to have the ability to create "workspaces" and "isolated wikis" by default. Since we don't have enough time to redo the dashboard we've decided to push that for later (5.3). All I want to ensure is that your "workspace flavor" doesn't include subwiki creation/visualization/management. These need to be in 5.2 (IMO in the xwiki-platform-wiki module I have started). The rest is ok. Thanks -Vincent
participants (2)
-
Ecaterina Moraru (Valica) -
Vincent Massol