Hi Martin,
Based on the proposal
http://wiki.services.openoffice.org/wiki/ESC/Criteria_for_bundling_extensions
we got the following requirements from technical point of view:
thanks for bringing this to our attention (and sorry for my late reply).
The most important question to me is: Shall we bundle extensions at all?
I agree to the positive effects of extensions, like developement
independent from the main code and only adding features for the user
when needed - but this also can lead to some kind of problems.
How shall we bundle? Via a link, so the user get the most current
version from the internet, or via file bundling? In the last case,
chances are high that the extension is already outdated when we ship it,
and that the download grows and grows without an actual need for the
individual user.
For 3.0, we had lots of features announced that were available as
extension, like PDF import and presenter screen. Although they haven't
been included in the main download, I didn't hear many complaints about
the features "missing" from the main download.
I would prefer to NOT file-bundle extensions in the main download. Such
kind of bundling can easily achieved via CD/DVD distributions like our
PrOOo-Box (www.prooo-box.org). For the main download, we can link from
within the installer to our extension repository or a dedicated web site
with information on how to get more features. In terms of marketing, we
should better distinct between "features in the core" and "features via
extensions", so everyone knows what he gets.
That way, we can avoid technical problems but also keep the download
size of OOo small. Remember, we already have lots of issues with the
size of our downloads in the mirror network, so I definitely do not want
to foster them :-)
Florian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
