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

Le 2010-11-11 10:29, Charles Marcus a écrit :
On 2010-11-11 9:47 AM, Rainer Bielefeld wrote:
the current bug tracking system is sufficien for expert communication,
but if masses of users will file their problems, we will loose overview,
soon. There are too less sort criterias for subcomponents, OS-Versions,
LibO version and and and, afaik we don't have an useful permissions
management ... . I'm afraid we will run into problems. Is there any
discussion concerning solutions for these problems?
'Masses of users' will not know how to properly report bugs.

As I have advocated in the past (on this and the OOo list), I would
suggest a two-tiered system - a simple bug reporting page for end users..

Agreed. I do not consider myself totally stupid; I am a decent programmer and quite good with macros. Yet, I do not understand the "issue" system used by OpenOffice and Mozilla. Well, I could *learn* to work my way through it, but it defies all logic. We need a more user-friendly system that will help a lot more people understand the situation and even work on the project. What would we need?

First, we need to get rid of the non-meaningful term "issue" and distinguish between bugs and requests for improvements. Those should be in two different tables, with two very different follow-up processes. What's the difference ? – LibreOffice claims that it exports Writer documents in PDF format. Let's say that it crashes during the process (it doesn't) or that it doesn't output the file properly with some fonts or character stretching values. That's a bug. The developers could either correct the program or even remove the function so LibreOffice would not export a document anymore. Then the bug is resolved. Another example of a less serious bug is the inconsistencies between the original files (odt) vs the .doc imports and exports. – On the other hand, LibreOffice does not export colours in CMYK pdfs, nor it integrates animation styles in Impress styles. Those would be improvements and those do not belong into a list of bugs. Likewise for suggested improvements to the interface.

Bugs could be declared via a forum. I suggest basic questions are asked, maybe through pop ups (LO version, system, module...). Then, they need to be sorted by hand, with a human-understandable description and classified by topics. For instance : under "Tables", a bug could be described as "[Writer] Cells defined as headers are not reprinted properly on each page".

As for Improvements, there are two issues to discuss:
– their feasibility: whether or not it is technically possible – or technically wise – to implement them;
– their effect on the user interface: especially for front-end changes.

Again, a table that would say, in user-friendly terms, what has been suggested so far would help avoid duplicate issues.


Michel Gagnon
Montréal (Québec, Canada) --

Unsubscribe instructions: Email to
Posting guidelines:
*** All posts to this list are publicly archived ***


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.