Hi Martin,
Basically, from a user experience perspective an extension can be
considered as a general "feature" or "function". Therefore, to decide if
an extension can become a permanent feature in OpenOffice.org the same
rules/processes/guidelines should be used as in any other case. In
short, the process that governs if EXTENSION XYZ goes into the product
should be no different from the process that governs if FEATURE XYZ goes
into the product. This also requires that bundled extensions would not
show up in the normal view of the extension manager.
For that to happen, the following UX related questions should be considered:
1. What real user problem/user goal does the feature/extension in
question address and solve?
2. Does this user problem/user goal concern a sufficient amount of
OpenOffice.org target users?
3. Does the design/behavior of the feature /extension meet
OpenOffice.org target user's expectations?
To rephrase the questions, a candidate feature/extension should always
efficiently address a real user problem/goal that is relevant to the
majority of OpenOffice.org target users.
Furthermore updates for bundled extension should be deployed with normal
OOo/SO product updates. This would secure that all users have exactly
the same program code installed and users would not run into trouble
updating a bundled (shared) extension due to missing user rights on
their system.
Best regards,
Frank
Martin Hollmichel wrote:
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
--
Sun Microsystems GmbH Frank Loehmann
Nagelsweg 55 User Experience StarOffice
20097 Hamburg Phone: (+49 40)23646 882
Germany Fax: (+49 40)23646 550
http://www.sun.de mailto:[email protected]
OpenOffice.org User Experience Team
http://ux.openoffice.org
Sitz der Gesellschaft: Sun Microsystems GmbH,Sonnenallee 1,
D-85551 Kirchheim-Heimstetten, Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schröder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
