UC: That said I personally would prefer the following:
  • Have no working platform distribution
  • Distribute an empty XE (with just the extension manager)
  • When XE starts the first time, propose different "flavors" (public documentation web site, intranet, empty, etc) and install automatically all required extensions
With this vision there's no need for a minimal distribution version in platform and platform can remain a repo of libraries/resources.
UC: The user will get shown flavors to pick (a flavor is simply a predefined set of extensions), which the ability to not choose a flavor and instead hand-pick the list of extensions to install.
UC: What is a distribution? From what I understand our idea is to not have any distribution by default in the future and instead to start up with a minimal runtime having only the Extension Manager (and what it needs to work) and then ask the user to pick a "Flavor" (preset of extensions) or start with an empty "Flavor" (or hand pick the extensions he'd like to see used).Thus for me there's only 1 "distribution" in the future, it's the EM one. And XE becomes a "Flavor".
UC: An idea we have discussed at length is to have no extension installed initially and ask the user to pick a flavor (i.e a preset selection of extensions) or manually check extensions to be installed.
UC: Note that flavors should be defined as extensions (they are simple extensions having dependencies on other extensions) and as such the community will be able to publish flavors on extensions.xwiki.org and these flavors would get available when starting xwiki for the first time.
UC: Bring everything as extensions of XE and have them installed by the Extension Manager and introduce flavors to even more quickly set them up.
UC: We've restructured are code base so that everything is platform. Platform contains modules which are "features" (a.k.a extensions). Right now we still have enterprise/ but it's only a packaging and it could possibly even be removed in some future and replaced by a flavor.
UC: We need to finish the Flavor idea by allowing the DM to list flavors.
UC: strong ecosystem of extensions
UC:
UC:
UC:
UC: