Re: [libreoffice-marketing] Re: Community building

On 09/05/2012 06:40 PM, leif wrote:

> Speaking of language: many and users from non-English areas has a
 problem writing perfect English. Its not a problem when thy do. The
 problem is to make them do it. Writing English is the first obstacle.

For bug reports, I think something between the current users list and
BugZilla is needed. A place for non-techies, and non-developers to post
the issues they come across in their _native_ language. Screenshots
showing the bug must be included with the report.

Ideally, the report should state:
* What the individual was doing, or attempting to do;
* What happened;
* What they expected to happen;
* What the difference between what happened, and what their expectation is;
* OS they are using. This must include version, localization and chip data;
* Chip type & byte size. (EG: 32 bit Intel, 64 bit AMD, 32 bit ARM.);
* Amount of RAM in their system;
* Device / Device type: (EG: Motorola Xoom, HP Touchscreen Desktop, Dell
Laptop);
* Bug report synopsis in English. All other data relating to the bug
report can be in the individual's native language.  (A statement in
English that states the language used to write the rest of the report
would probably be useful.)

> But we need a group of people to build the bridge. I think it's
 unrealistic to ask end users to report bugs directly.

Agreed.

However, I don't think I've seen any flow process for bug reporting that
is both understandable to Joe Sixpack, and can scale to a hundred bug
reports per hour. (That might be a slight exaggeration, but for some
software I've used, I've seen between two and three hundred messages
posted to support people asking "Is it me, or the upgrade?", when
something hasn't worked as expected.)

In an ideal world, there would be something like Bugzilla, that the
techies can directly interact with, alongside the preferred forum or
list, where actual or alleged bug reports can be submitted.

> When we publish the list of new features and bug fices we always credit
 the developer. How about also give credit to the original (first)
 reporter of the bug?

+1

When bug report proxies are used, then the credit should not go to the
proxy, but the original individual.

jonathon

  * Unknown - detected
  * English

  * English

 <javascript:void(0);>

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