Heiko,
Have noticed you are liberally deleting the UX-Advise ML recipient from BZ META issues and some
topical issues. Is there a reason?
While these issues may have had their Keyword "needUXEval" removed (or not assigned) use of the
UX-Advise ML remains an efficient way to route the BZ comments to the UX and Design team.
Every BZ issue you remove it from deletes that topic from visibility by the team. And folks have
to manually add themselves to an issue should they desire to follow along--which for most of the
META we do.
It costs nothing to keep the ML recipient in place (personally with mail rule filters I route all
the UX-Design related mail out of my inbox to a mail folder where they can be reviewed while I am
thinking about LibreOffice).
If with discussion there is some consensus to do this, I'll concede--but my personal preference is
to leave the ML in place for the META and topical issues in BZ. Folks that find the volume too high
can take the ML as digest or even remove themselves from the ML.
Stuart
Context
- [Libreoffice-ux-advise] Dropping the UX-Advise ML from META and topical BZ issues · V Stuart Foote
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.