I'm an IT professional, but not a developer. My biggest hurdle in getting my
organization to accept LO is that there is no mechanism (that I'm aware of)
for auto deployment or auto update that can be controlled by administrators.
My environment is Windows, but if I can ever move my organization to Linux
it will be an issue there as well.
I've read the wiki at
http://wiki.documentfoundation.org/Development/Enterprises_nice-to-have, but
it doesn't give a lot of info on how LO is planning to address this, or if
there is a plan yet.
I'd like to suggest that one way to handle this would be to provide an
installation option for update from a centralized location and to set where
that location is on the network. My idea is that during startup LO would
check this location to see if it the local copy is in sync with this master
repository. The repository would be populated with the latest installation
files. If the local copy is out of sync it would initiate an auto update
from the repository's files.
Since I'm not a developer, I don't want to join the dev list to suggest this
or to help with testing enterprise deployment solutions. What is the proper
channel for submitting suggestions like this?
Ernie
--
View this message in context:
http://nabble.documentfoundation.org/Enterprise-Deployment-tp2390794p2390794.html
Sent from the Users mailing list archive at Nabble.com.
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
Context
- [libreoffice-users] Enterprise Deployment · klompen
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.