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

The only problem is that it wasn't actually discussed on the UX mailing
list, but only came up in the bug reference, which was copied to the UX
mailing list.

Additionally, this bug initially concerned absolute file referencing in
Calc, so would have passed under the radar of most people concerned by
Base UX issues even if there had been a discussion (which there wasn't,
at least not on the mailing list).

Sure - I'm not saying they catch everything or discuss everything, as that
would be very difficult to do. All I'm saying is that such a discussion
(even if done after the fact) can improve discussions for the future and
lead to a better product. The user mailing list typically isn't a good
place for discussing improvements (if the goal is to reach out to
contributors), nor is commenting with caps lock on as this just irritates
contributors (from my experience over the years) and adds nothing to the
fruitful and positive attitude in the project.

Just my two cents. I know all of the people on the UX team and they are all
fantastic people who are always open to bringing in new voices and
incorporating lots of ideas moving forward.


*Joel Madero*
LibreOffice QA Volunteer

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.