Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Christoph, Riemer, *,

thanks for bringing this up..

Christoph Noack schrieb:
Am Dienstag, den 19.04.2011, 16:13 +0200 schrieb Riemer Thalen:

[.. get reason for dropping (LibO|OOo) by survey ..]

Ah, another thought - we do also have trainers on our lists who can
provide rather neutral feedback what is important to users they know.
Although there is no statistical evidence, it might work ... but
sometimes its much easier to deal with answers backed up by numbers.

+ 17

This in my opinion is the first step to go regarding the purpose in
question. Why: 

- Trainers can provide information collected "digestible" for the
  project organism - thus providing the abreviation to get the desired
  knowledge.

- Trainers should be more deeply integrated in (bug|feature request)
  rating. They know the really hurting things through feeling the pain
  day by day. This is one more abreviation to get rid of *out there*
  most annoying bugs. This also might lower dropping rate of LibO *now*.

[..]


Gruß/regards
-- 
Friedrich
Libreoffice-Box http://libreofficebox.org/
LibreOffice and more on CD/DVD images


-- 
Unsubscribe instructions: E-mail to marketing+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/marketing/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.