Hi dear website team,
in the current Steering Committee meeting, there has been a discussion
concerning the organization of the websites.
To make a long story short: There will be a separation between a more
"user-centered" LibO website and the TDF website run in parallel. So our
community can better meet the expectations of our users. Additionally,
we aim for a better separation of technical (developer) / non-technical
(non-developer) content. This should resolve problems we experienced in
the past.
Details (or let's say: different wording) can be found here:
http://wiki.documentfoundation.org/TDF/Steering_Committee_Meetings#Minutes_2010-10-20
Another question ... In the minutes, some other item caught my attention
- it is about the CMS. In the minutes 2010-10-14, one can find "steering
committee asks website list for a decision on which CMS to use - within
one week, otherwise we will pick." I got lost a bit in the discussion;
so is there any final result to be proposed? One of the items here?
http://wiki.documentfoundation.org/Website/Evaluation_of_CMS_Platforms
Thanks to all!
Cheers,
Christoph
--
E-mail to website+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/website/
All messages you send to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-website] Steering Committee Website Structure Decision (+ CMS Question) · Christoph Noack
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.