Hi Dennis, all!
Weitergeleitete Nachricht
Von: Dennis E. Hamilton dennis.hamil...@acm.org
[...]
You can now subscribe (I think) and post this to
dev-...@incubator.apache.org or issues-...@incubator.apache.org.
[...]
Thanks for the hint, so here - again - some thoughts what might be
helpful for the mid- to longterm development of OOo.
Cheers,
Christoph
-Original Message-
From: Christoph Noack [mailto:christ...@dogmatux.com]
Sent: Monday, June 13, 2011 14:58
To: gene...@incubator.apache.org
Subject: Infrastructure and Data for... End-Users of OpenOffice.org
Hi Robert,
thanks for your mail ... one may notice that my reply is a bit late, so
I'm glad that I disclaimer-ed the available time in advance *g*
So, if anybody is still interested in this topic, here we go ...
Am Dienstag, den 07.06.2011, 17:03 +0100 schrieb Robert Burrell Donkin:
On Mon, Jun 6, 2011 at 9:28 PM, Christoph Noack christ...@dogmatux.com
wrote:
[...]
Sorry for talking about such stuff in such a great detail, but my aim
was to make clear that the Joe Averages we have (and we have lots of
them), don't care about licensing details, or whether the code is well
structured, or what build machinery is used. Instead, they judge whether
a product fits to their needs (in this moment).
+1
[...]
So just to name a few tools we
have/had at OOo which I still consider to be important in the mid- and
long-term:
* User survey tooling and data, including different questionnaires
with over 3 million detailed responses
* Usage data backend and data, covering millions of user actions
to create statistics for development decisions
* ...
Sounds like ensuring that all documents that need to be included
within the grant is going to be important
Okay, then please allow me to list them within the mail - it would be
great if anybody could pick those information to use them appropriately.
I'll try to add a personal judgment how important I think these
information are in the mid- to long-term.
ISSUE TRACKER CONTENT
Description: The complete content of the OOo issue tracker including all
votes, attachments and keywords.
Rationale: Many development decisions and also (partly) specifications
are documented within the issue tracker. Furthermore, there is a basic
vote system to enable community members to highlight issues to be
worked on (from their POV).
Source: http://www.openoffice.org/issues/query.cgi
Importance: Mid-High
WIKI CONTENT
Description: Selected wiki content including all linked data.
Rationale: The wiki contains development processes, ideas, and also
(partly) specifications that may be important for future use - to ensure
consistency.
Source: http://wiki.services.openoffice.org
Importance: Mid
USAGE TRACKING BACKEND AND CONTENT
Description: Also known as OpenOffice.org Improvement Program, or
OpenOffice.org User Feedback. More detailed, OpenOffice.org sends (if
the user permits) usage statistics to a server hosted by Oracle in
Hamburg. This closed-source backend both receives the data and
transforms it, so that (e.g.) the User Experience team is able to
analyze it. Important is both the backend (for analyzing changes in
OpenOffice.org) and the already available data (for development
reasons).
Rationale: Due to the complexity of OpenOffice.org, the usage data is
very important for design decisions that affect a majority of the user
base (e.g. UI changes).
Source (basic documentation, no backend source code):
http://wiki.services.openoffice.org/wiki/User_Experience/OpenOffice.org_User_Feedback_Program
Importance: High
Note:
* A plain export (numbers) is less sufficient, since it doesn't
contain dependencies between the individual recorded user
actions.
* I'm not sure who might be contacted, but maybe the Oracle guys
on this list can shed some light on that (that would be great!)
USER SURVEY STRUCTURE AND CONTENT
Description: The User Experience Team did several user surveys and
collected an incredible amount of user feedback (approx. 3 million
filled-out questionnaires). Thus, this item refers to both the user
survey structure (can be exported), and the data.
Importance: Mid-High
Source (no code):
* User Survey: http://surveys.services.openoffice.org
* Description:
http://wiki.services.openoffice.org/wiki/Renaissance:Phase_1#Who_are_our_users.3F
Note:
* The acquired data contains (helpful) text comments that may
contain personal information. So if there are any legal
concerns, the non-text data would be sufficiently helpful.
* I have been told that a plain export from withing LimeSurvey
doesn't work with the given number of data sets - so there is a
need to do an export of the underlying database.
SPECIFICATION
