Le 2011-05-09 01:41, Jean Hollis Weber a écrit :
FYI... The LibreOffice Documentation Team now has a blog, here:
http://libodocs.wordpress.com/
--Jean
Thanks Jean. It is wonderful that you now have a blog. I guess it now
stands to reason that the marketing team should now have a blog as well
as other major teams of the project. We coordinate on some aspects of
the blogs "look n feel".
Firstly, I would suggest the following teams should have blogs:
* documentation
* website
* marketing (this would include the US marketing team)
* design
* dev
* discuss (what was discussed of interest for the blog readers)
* accessibility (not much being discussed on this mailing list)
-- Have I missed any other teams where a blog may prove interesting?
Secondly, as the LibreOffice and Documentation blogs are now on
Wordpress. I would suggest that all other teams follow suit and have
Wordpress blogs, determine their admins to monitor and, if need be,
moderate the blog.
Thirdly, if the Wordpress theme allows, we could all have the same theme
as the main LibreOffice blog theme, and perhaps have a different
identifying colour theme. Not sure if the theme would allow this.
Cheers
Marc
--
Unsubscribe instructions: E-mail to marketing+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/marketing/
All messages sent to this list will be publicly archived and cannot be deleted
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.