Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Howdy Folks,

Just an idea - as even though I just gone done saying in a different
email that we have only existed for 21 days, it has been 21 days and the
time to choose and start is, IMO, drawing nigh.

So a different perspective - Who is actually planning on doing the
install, and willing to commit to the time to see it through:

- Where is this being hosted?
- Who is going to be doing the server admin?
- Who is going to do CMS install/customization?
- Who will commit to the ongoing admin tasks for the instance of the CMS
package (not just content admin functions)?

Before you say, can't answer till you know the CMS, lets just a quick
head count and see who is actually willing to accept the responsibility
- cause I don't know, I know some of you are, as we really down the
question one over the other it's best to remember that the people
planning actually doing the work should and must have a large role in
making the final decision, even if those of us on the periphery will no
doubt have input and some influence.

Anyway, just how I would approach at this moment...shouldn't really
distract from what I'm reading about demo systems, and such.

Thanks

Drew 


-- 
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


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.