Caolán McNamara wrote:
On Tue, 2009-05-19 at 14:51 +0200, Joerg Skottke wrote:
Hi Caolán,
Hi there!
we have a boolean function in VCL Testtool BASIC named
hIsOOoImprovementTabVisible() which allows test writers to determine
whether the feature is available or not.
Nevertheless, presumably oooimprovement has a purpose of improving
quality of some kind, so having it in there would be a good thing when
making OOo install-sets destined for qa-ing right ? Or is it worthless
to qa unless the build being tested comes from an internal build ?
Lets put it another way, BUILD_SPECIAL is basically only set in a
Hamburg build. Is there any particular reason we *shouldn't* bundle
oooimprovement into the install-set of a cws ?
Well let´s have a look at what the feature is all about:
When the user agreed to it usage-tracking data like which actions have
been triggered by the user via menu-items, toolbar icons or akeystroke
events is being collected and send in regular intervals to a server at
Sun for storing it anonymously into a Database. Later on at some time in
the future this data is going to be analysed by a UserExperience Team at
Sun as background information for judging about ideas on how the
UserInterface of OpenOffice.org could possibly be improved.
Now, well does it make sense to activate such feature on any CWS at all?
I would say not much as the whole idea here is to get end-user usage
patterns not usage-pattern from usages of developers or testers which
might differ significantly.
Does it make sense to activate that feature on a non-sun provided
release build and send the data to Sun? I would say that depends on how
many non-mainstream patches and special features that build has and how
often those are used because for such features usage events would have
no meaning for the Sun team evaluating the usage tracking data of course.
What else can be done? Similar as with crash-reports where it doesn´t
make any sense at all to send those to Sun from a non-Sun provided build
because Sun wouldn´t have debug information for those products available
you can of course provide your own backend for the usage-tracking
reports and provide your own team analysing the data and coming up with
clever UI improvement ideas for OOo. In order to do so the
OpenOffice.org configuration must be patched and you must create your
own backend infrastructure etc.
As a side note: the Sun server used at the backend for the feature is
already receiving tons of data enough to be seen as a good statistical
basis and so adding just a few more data entries from those non-sun
builds wouldn´t really add that much more value.
C.
Kind regards,
Bernd Eilers
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
