Hi,
in last ESC meeting
(http://wiki.services.openoffice.org/wiki/ESC_meeting_minutes_20090309)
there was the item "Define Criteria when to bundle extensions" on the
agenda.
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:
Extensions should:
* be localized
* documented, online help available
* QAd, Feature must be complete and without serious bugs
* consistent with the UI of the core product and other bundled
extensions
* does not need limited UI resources, and is not considered core
functionality at the same time
* a11y compliant
There was the agreement that also the marketing and user experience team
might want to add important criteria and rules upon this so that finally
the release status meeting is able to accept proposals for bundling and
is able to decide based on these rules.
Simple rules might be something like "must have x downloads per week, at
least a rating of y stars, and z ratings at all". But I will leave it to
the experts to discuss such criteria.
From my point of view I'll add the requirement that the source code for
bundled extensions need to be in the OpenOffice.org source code
repository to get the bundling done in a automated manner so that they
will be LGPL license compliant and follow the accepted guidelines of the
project.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
