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


https://bugs.documentfoundation.org/show_bug.cgi?id=91781

--- Comment #31 from sophie <gautier.sophie@gmail.com> ---
(In reply to Cor Nouws from comment #29)
General about the process:

These UI changes must IMO maybe be handled with greater care then
incompatible API changes, since many more people are affected.

We must realize that many people working on e.g. documentation are pretty
over loaded with work, often for various projects. Therefore getting people
involved in discussions early, is difficult (see l10n).

To facilitate a good discussion, evaluation etc of a change of the whole
menu structure as easy as reasonably possible, I would consider a single
document, with rationale, explanation and discussion of every change
appropriate, eh, helpful.

And if we, as whole team, are not able to organize the (full) process
properly, then we face the question: is it such an important change to make
now, that we accept the risk of breakage that must be solved over a longer
period of time, or can it be done later, with ore preparation?

I agree with you. What is frightening me also is that some changes are made
without a full knowledge of the functionality with the risk to lose part of it
(which already happened unfortunately). That should be a pre-requisite to have
a full knowledge and overview of a function before modifying it. Sophie

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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.