On Mon, Jan 31, 2011 at 7:32 PM, Charles-H. Schulz
As far as I know, the plan was to wait until David presented the work
he had compiled, then the whole website team would get involved in the
improving phase. Don't get me wrong, the work David produced is
fantastic, but I know that as a team we can create something that
really represents the quality standard of the LibreOffice software
You are absolutely welcome to work with the website team! But I don't
have the feeling they want to restart the website over and over again.
I am not sure who you are referring to by 'we', but these plans were
discussed at length on the recent conference call, and the team has
people who are willing to get on board and help out 'now'.
If I remember what was discussed it was clear that while help was
welcome on the website it wasn't for an overhaul.
I don't believe anyone is talking about an overhaul. We are talking
about working with the great work that David has produced in order to
update and upgrade the site.
As with any project it is always important to revisit your initial
plan and compare it to what you ended up with then come to a
compromise. In my experience this is the basis for any half decent
final product in any industry.
Again, nobody is talking about scrapping what we have already as you
have suggested, we just want to improve what we currently have.
Unsubscribe instructions: E-mail to firstname.lastname@example.org
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: 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