https://bugs.documentfoundation.org/show_bug.cgi?id=91781
--- Comment #15 from Cor Nouws <cno@nouenoff.nl> ---
for now: At the moment there are approximately 80-100 million people that will
benefit from improvements.
OTOH, in our own community, hundreds of people will have to do a _lot_ of work
in documentation. Outside the community prolly thousand will see the same task.
And above all 80-100 million people will have to learn changes. In my
experience for a major part that is hard, not to say a PITA.
So improvements for good reasons: yes.
In our past discussions, IMHO part of the changes are such good improvements.
OTOH, for part of the changes I've not been convinced for the rationale.
Different logic and considerations are used in a mix and lead to IMO not
rationale results.
I've brought into discussion in the past that a change in one go, would IMO be
preferable. For all people involved. OTOH, that is not easy to organize. But
we've already had changes in the menu before..
(Now I see a proposed change from the past, that has been reverted because it
was based on wrong understanding, is introduced again..)
So good times ahead for discussion.
The people that follow my comments know that I'm not against changes. But
indeed rather critical. For good reasons, IMO.
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 91781] Reorganization of the menu bar for Writer · bugzilla-daemon
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.