The Document foundation holds weekly ESC (Engineering Steering Committee)
calls, and today happened to be my first time on this call.
Here's what's relevant to us:
About document themes: One of the ideas for implementing theme
functionality without themes actually being included in the ODF standard is
to have templates use a standard set of styles. The user would be able to
apply styles from these templates on his document. Native theme support
would, of course, be preferrable. Neither of these is being worked on yet,
though.
About icons: To be able to include the Gnome icons Alex brought up, we need
them to be released under the MPLv2 license (or public domain/CC0).
About templates: It looks like Alex's templates will be included with
LibreOffice once we have the new template dialog, but we will need more, as
the current selection is quite bad. How about starting a call for
submissions of CC0 templates? We'd need some basic guidelines for that and
some publicity. What do you think? How should we go about it?
--
Unsubscribe instructions: E-mail to design+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/design/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-design] Notes from the ESC call · Mirek M.
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.