Hi Florian, :-) All the active members of the docs team have accounts on the Alfresco site I'm hosting right now. There is a general consensus/willingness to use it, and people have already started trying it out for actual work.
Putting it under a TDF sub-domain will only further strengthen people's commitment to uptake. We're ready to start a pilot work project, using the workflow that has been developed. We have a system set up with: - a custom-designed workflow for the docs team, developed by a professional Alfresco developer and a member of the docs team, - full git-like versioning, - rollback, - discussion around documents, - full built-in support for ODF/OOo/LibreOffice file formats, - simple usage (publication/updating) for users via the use of an existing plugin for OOo/LibO that lets you collaborate right from within the LibO applications, - sophisticated searching capability, that can extend right into hosted documents. Basically, we have all the sophisticated functionality we need for properly-managed, automation-assisted documentation development and prepping for publication, with the potential ability to interface with a variety of outside systems, such as directly with the LibreOffice code repository... It would be a great tool for producing developer documentation in the future, in addition to the user documentation the docs team is now working on. It could also be used for easy management of HTML content on TDF servers (documentfoundation.org, for instance), and for a variety of other purposes. Using Alfresco, we will be able to develop all our documentation and many other kinds of content in-house, and we will acquire expertise and autonomy within the LibreOffice project and docs team. The advantages of hosting it on my server would be as follows: 1) It's quite a complicated package to set-up and configure. It is quite memory-hungry. On my server, it is already fully operational. No workload or worry for you. Version upgrades will be done whenever I want, without putting workload and responsibility on you. 2) On my server, it is running within an environment that is simple to manage. No problems of conflicts with the many other software products that TDF runs. You get none of the complications that would inevitably exist with integrating Alfresco into a TDF server. 3) I have access to 24/7 professional technical support, with in-house Alfresco expertise. Any problems can be troubleshot within minutes, at any time of day or night, with no problems of people on vacation, sick, etc. 4) On my server, I have full root access and full control over all the other software running on the server. I can't have that on a TDF server. 5) On my server, I can peacefully reboot the system at any time and, generally, do anything I want, without having to worry about other users, running software, etc. And one does need to anticipate occasional *total* system outages during the running-in period. 6) On my server, I can do memory and disk space upgrades 24/7 within minutes. That kind of turnaround will not be available on a TDF server. 7) The server is hosted in a secure data center in the UK, and automated backups are taken at regular intervals, under my control. 8) You and Christian already have admin access to the Alfresco back end. You can also both have permanent SSH user accounts to inspect the server, suggest security improvements, etc. But you will find pretty much the same security arrangements as I found on documentfoundation.org. 9) I undertake to provide TDF with the best-possible service, and to work on building a strong docs team and documentation base for LibreOffice. I will also make a major effort in the future to expand the number of active docs contributors within the LibreOffice project. If you agree, the sub-domain name I would suggest would be alfresco.libreoffice.org. What do you think? ;-) David Nelson -- Unsubscribe instructions: E-mail to steering-discuss+h...@documentfoundation.org List archive: http://listarchives.documentfoundation.org/www/steering-discuss/ *** All posts to this list are publicly archived for eternity ***
