[steering-discuss] Re: [us-marketing] Reminder: Marketing ConfCall in 5 hours
On Thu, 2011-01-20 at 12:47 +0100, Florian Effenberger wrote: I explicitly do *not* want to talk about the Drupal topic in this call, please let's focus on the 3.3 release first. I totally agree - -- 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 ***
Re: [steering-discuss] next SC call tomorrow, 1700 UTC
Hi Florian, all, On 20/01/2011 15:37, Florian Effenberger wrote: Hi David, David Nelson wrote on 2011-01-20 13.11: Wow! What inconvenient timing... We had planned the website conference call for Friday 21 January @ 5pm GMT too! I was going to catch you on the Marketing call tonight to ask you if you could give us the codes for that... ah, sh... I'm sorry, this really wasn't on purpose. I saw the mail about the website confcall, but didn't manage to react yet, and didn't notice the date and time is fixed already. Having both calls in parallel for sure isn't such a good idea... Friday evening is the only time that works, but I could move the SC call to one hour later, 1800 UTC. Would that help? Provided I'm the one in the SC where the time is the most advanced in the day, I'd say yes, will end late, but that's life ;-) Kind regards Sophie -- 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 ***
Re: [steering-discuss] next SC call tomorrow, 1700 UTC
Hi, :-) If you could have the SC call at 19.00 UTC it would be so great... This is a very special conversation we want to have tomorrow, and it's likely to be lnngg... 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 ***
Re: [steering-discuss] connecting external services to our domain
Hi David, David Nelson wrote on 2011-01-18 22.36: My request for the alfresco.libreoffice.org sub-domain still holds. I am willing to offer Christian/Florian full root access to the system, if necessary, and to comply with all feasible requirements to satisfy TDF. Would it be appropriate to request consideration of this at the next SC meeting? Or is the refusal firm and non-negotiable? no, there's no refusal in general, don't worry. :-) I'm just looking on how we can keep the infrastructure constant. We've just reached a rather stable and security state, and I would like to keep what we have achieved. For sure, we will have to look for external offers and options, I do not want to have everything in control, neither do I have the time for that. It's just that we didn't come up with policies for that yet. :-) So, don't take this as a refusal, but just a question for the ease of use: Would theoretically hosting Alfresco on one of our servers also be an option to consider, or do you see huge advantages of having it on yours? And, as a side question: Is there anyone who actually uses Alfresco? I didn't follow the documentation list closely, but I want avoid the same what tool do we need discussion we have for the website. So, have the requirements and the possible tools already been discussed or is this basically a one man show? Sorry for the direct questions, but I guess you know what I mean. I just want to avoid a group of people working on a tool they like, when there are issues with actually using it right now... Thanks for your work! Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- 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 ***
rescheduling tomorrow's SC call (was: Re: [steering-discuss] next SC call tomorrow, 1700 UTC)
Hi, David Nelson wrote on 2011-01-20 13.43: If you could have the SC call at 19.00 UTC it would be so great... This is a very special conversation we want to have tomorrow, and it's likely to be lnngg... honestly, I would have appreciated if the website folks had *first* checked the SC poll, which has been online for a few days already and thus earlier than the website poll, and *then* fixed their date and time. It's all about communcation... :-) That being said, I have no issues of rescheduling the SC call if the majority of the other SC members agree. I myself can't attend then, I'm out in the evening, but I'm not a blocker. :) So, SC folks, any objections? Florian -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- 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 ***
Re: [steering-discuss] next SC call tomorrow, 1700 UTC
Hi, Le Thu, 20 Jan 2011 20:43:39 +0800, David Nelson comme...@traduction.biz a écrit : Hi, :-) If you could have the SC call at 19.00 UTC it would be so great... This is a very special conversation we want to have tomorrow, and it's likely to be lnngg... David Nelson We could have the other call about the website at a different time, David. I don't want to sound ominous, but SC's business comes first... What do you think? -- Charles-H. Schulz Membre du Comité exécutif The Document Foundation. -- 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 ***
Re: rescheduling tomorrow's SC call (was: Re: [steering-discuss] next SC call tomorrow, 1700 UTC)
Le Thu, 20 Jan 2011 13:47:57 +0100, Florian Effenberger flo...@documentfoundation.org a écrit : Hi, David Nelson wrote on 2011-01-20 13.43: If you could have the SC call at 19.00 UTC it would be so great... This is a very special conversation we want to have tomorrow, and it's likely to be lnngg... honestly, I would have appreciated if the website folks had *first* checked the SC poll, which has been online for a few days already and thus earlier than the website poll, and *then* fixed their date and time. It's all about communcation... :-) That being said, I have no issues of rescheduling the SC call if the majority of the other SC members agree. I myself can't attend then, I'm out in the evening, but I'm not a blocker. :) So, SC folks, any objections? Yes, I do. I propose the call about the website be rescheduled. With all due respect the SC has different and very pressing issues not related to the discussions on the website, so we ought to keep our timing. 19 UTC start to be a bit too long of a week for me... Best, -- Charles-H. Schulz Membre du Comité exécutif The Document Foundation. -- 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 ***
[steering-discuss] Re: rescheduling tomorrow's SC call
Thanks a lot Michael. Really appreciated. Just added my availability to Doodle. Michael Wheatland wrote on 2011-01-20 15.00: I am in the process of doing just that. Rescheduling the website meeting. -- Florian Effenberger flo...@documentfoundation.org Steering Committee and Founding Member of The Document Foundation Tel: +49 8341 99660880 | Mobile: +49 151 14424108 Skype: floeff | Twitter/Identi.ca: @floeff -- 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 ***
Re: [steering-discuss] next SC call tomorrow, 1700 UTC
Hi Charles, :-) I understand that Mike is rescheduling the call. I'll fit in with whatever time is chosen. (It will be about 2 a.m. my time, most likely, if 19.00 UTC is chosen.) 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 ***
Re: [steering-discuss] connecting external services to our domain
From my point of view, Alfresco is great, but just for better understanding, who is sponsoring your server? What would be your benefit? And how can you warranty the uptime and performance and for how long? Cheers! On Thu, Jan 20, 2011 at 15:02, David Nelson comme...@traduction.biz wrote: 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.orgsteering-discuss%2bh...@documentfoundation.org List archive: http://listarchives.documentfoundation.org/www/steering-discuss/ *** All posts to this list are publicly archived for eternity *** -- 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 ***
Re: [steering-discuss] connecting external services to our domain
On Thu, 2011-01-20 at 13:45 +0100, Florian Effenberger wrote: So, don't take this as a refusal, but just a question for the ease of use: Would theoretically hosting Alfresco on one of our servers also be an option to consider, or do you see huge advantages of having it on yours? JFWIW - Alfresco looks like an OpenOffice.org-like, single-vendor dominated, copyright-assignment-based, pseudo-Free-Software project to me :-) As such, I'm no fan of it personally; but luckily I don't have to use it ;-) so if there is nothing else that works well for the job perhaps we have to. Do we have to run it ourselves though ? [ surely we could just give a domain-name re-direct to David's existing machine ]. ATB, Michael. -- michael.me...@novell.com , Pseudo Engineer, itinerant idiot -- 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 ***
Re: [steering-discuss] connecting external services to our domain
Come on, an Alfresco image is even offered by Amazon, you can download the Community version, which is certified only to work with OpenSource, so the only problem is that it doesn't work with proprietary SW (e.g. Windows). You can try it out yourself: http://www.alfresco.com/try/ There are other big, medium small vendors offering services and integrating Alfresco to their business. And here you find the SourceCode: http://wiki.alfresco.com/wiki/Source_Code Cheers! On Thu, Jan 20, 2011 at 15:47, Michael Meeks michael.me...@novell.comwrote: On Thu, 2011-01-20 at 13:45 +0100, Florian Effenberger wrote: So, don't take this as a refusal, but just a question for the ease of use: Would theoretically hosting Alfresco on one of our servers also be an option to consider, or do you see huge advantages of having it on yours? JFWIW - Alfresco looks like an OpenOffice.org-like, single-vendor dominated, copyright-assignment-based, pseudo-Free-Software project to me :-) As such, I'm no fan of it personally; but luckily I don't have to use it ;-) so if there is nothing else that works well for the job perhaps we have to. Do we have to run it ourselves though ? [ surely we could just give a domain-name re-direct to David's existing machine ]. ATB, Michael. -- michael.me...@novell.com , Pseudo Engineer, itinerant idiot -- Unsubscribe instructions: E-mail to steering-discuss+h...@documentfoundation.orgsteering-discuss%2bh...@documentfoundation.org List archive: http://listarchives.documentfoundation.org/www/steering-discuss/ *** All posts to this list are publicly archived for eternity *** -- 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 ***
Re: [steering-discuss] connecting external services to our domain
David, sorry if I joined discussion only late, maybe my questions have been answered already, so bear with me please. On Thursday 20 January 2011 15:02, David Nelson wrote: All the active members of the docs team have accounts on the Alfresco site I'm hosting right now. 1) Is there any integration (planned?) with odfauthors or is it just about a new and different place to produce documentation (specific for libreoffice maybe)? 2) what about the l10n people? Are they involved already or is it planned to involve them? Or is it just about to create international (i.e. English) documents (optionally serving as master for translation)? Nino -- 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 ***
Re: [steering-discuss] connecting external services to our domain
Hi, :-) On Thu, Jan 20, 2011 at 23:20, Nino Novak nn.l...@kflog.org wrote: 1) Is there any integration (planned?) with odfauthors or is it just about a new and different place to produce documentation (specific for libreoffice maybe)? IMHO, it is in the best interests of LibreOffice project for the LibreOffice documentation project to have its own workflow, expertise and policies for LibreOffice documentation. However, I proactively asked Jean Weber (odfauthors.org) to be part of the Alfresco site and the LibreOffice documentation team. I invited her to have an admin account on the Alfresco site, and actually gave her one despite her only-lukewarm interest, to encourage her close participation. But she is very taken up with odfauthors, and does not seem want any close involvement in the LibreOffice documentation team. I even suggested to her to take team leadership of the LibreOffice docs team two times in the past. But she's very much occupied with odfauthors. In any case, no matter what similarities there might be between OOo and LibO right at present, the two products are quickly going to diverge. LibreOffice might as well start developing its own documentation team and expertise now. On Thu, Jan 20, 2011 at 23:20, Nino Novak nn.l...@kflog.org wrote: 2) what about the l10n people? Are they involved already or is it planned to involve them? Or is it just about to create international (i.e. English) documents (optionally serving as master for translation)? There is every opportunity for interested l10n people to work with Alfresco, and I have been intending to throw open an invitation. But I've held back on that until a) the SC grants me a remit to operate an Alfresco server for the project and b) I've been able to consult and liaise with Sophie Gauthier beforehand. On Thu, Jan 20, 2011 at 22:35, Jaime R. Garza gar...@gmail.com wrote: who is sponsoring your server? No-one is sponsoring it. I operate it myself. On Thu, Jan 20, 2011 at 22:35, Jaime R. Garza gar...@gmail.com wrote: What would be your benefit? The pleasure, interest and kudos of working for TDF and the LibreOffice Open Source project? Worthwhile professional experience? On Thu, Jan 20, 2011 at 22:35, Jaime R. Garza gar...@gmail.com wrote: And how can you warranty the uptime and performance and for how long? The server is hosted in a high-quality, secure data center in the UK, with all the security and backup systems you find in such modern infrastructures. I can't *warranty* the server uptime and performances beyond a best-effort, good-faith commitment and the guarantees offered by the data center. But Open Source projects don't offer better, do they? For how long? Not beyond my death, in any case. Up to then, things should be OK. But, seriously, I would always cooperate in all good faith in a handover, and would always make best arrangements not to damage the LibreOffice project's interests. I *care* about the project, and I *care* about my reputation. ;-) Florian, SC, please read my post below: David Nelson On Thu, Jan 20, 2011 at 22:02, David Nelson comme...@traduction.biz wrote: 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
Re: [steering-discuss] connecting external services to our domain
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/20/2011 04:18 PM, David Nelson wrote: suggested to her to take team leadership of the LibreOffice docs teamI two times in the past. But she's very much occupied with odfauthors. Need I point out that Jean has been running OOoAuthors for the last six or seven years. Until roughly six months ago, that team wrote documentation for one program --- OOo. Within the last six months that team has been asked to assume responsibility for providing documentation for five or six different programs. (The precise number depends upon what you count as a different program.) In light of that expanded role, they changed their name to ODFAuthors. ODFAuthors has to change how they write documentation, and their entire work-flow process, if they are to adequately provide adequate documentation for each of those programs. jonathon -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNOHTnAAoJEERA7YuLpVrVdmMIALPUBbCGL3XL3HcEmFAxsWTx Cnb2/HGTOIQ95rtjOGuQH8x5saUOsHMpN/zCeNtJ1nthzPGAE/6Hx713XoEwPaLI VSVUUX/DIL9OtUkTc7woC9YnfrX5tSLxdOAPkxBm6HOLTfUdtjfHbHGjEQLDiozR Q0xvARpDZNNB7I89+ou0amfWUJRAxHRP0LU51Zwd9mbEbFuW/OMD1jA0N9aAC/8r +2uaXasd9rM3f49iBmi4q9xet6imE/TdyEVX7Mh3dn0eW0MTGc5RsQEOqX2mcHMr R7lSrHSW7UIAbTy/Gw3GtI+TI07TQuVcNjBjsu04540Up4u41XF3MCI+aamePCA= =kj45 -END PGP SIGNATURE- -- 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 ***
Re: [steering-discuss] connecting external services to our domain
Hi Andreas, :-) Thought: I think that odfauthors.org is a great resource for smaller Open Source projects that don't have the people, time or resources to properly develop their own documentation. But I think it's in the best interests of a *major* software project like LibreOffice to have an in-house documentation team that is really specialized in the product. David Nelson On Thu, Jan 20, 2011 at 22:02, David Nelson comme...@traduction.biz wrote: 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 ***
Re: [steering-discuss] connecting external services to our domain
Hi David, *, I don't know what is your purpose. You sent your submitting to the SC a third time now (if I count right). Why are you doing this. I told you in my last mail that this is not necessary. You pay no attention to the netiquette. What's the reason for your behavior? I'm very curious. Am Donnerstag, 20. Januar 2011, 21:23:01 schrieb David Nelson: Hi Andreas, :-) Thought: I think that odfauthors.org is a great resource for smaller Open Source projects that don't have the people, time or resources to properly develop their own documentation. It seemed to me as if you have no knowledge about the power of the Plone CMS (in its current version). But I think it's in the best interests of a *major* software project like LibreOffice to have an in-house documentation team that is really specialized in the product. Did you know how big the documentation team of OOo is (was). We are in the tradition of OOo here. We continue our former work under a new roof under different conditions. Regards, Andreas -- ## Developer LibreOffice ## Freie Office-Suite für Linux, Mac, Windows ## http://LibreOffice.org ## Support the Document Foundation (http://documentfoundation.org) ## Meine Seite: http://www.amantke.de -- 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 ***
Re: [steering-discuss] connecting external services to our domain
Hi Andreas, :-) IMHO, the odfauthors.org software is far from being an ideal tool for the LibreOffice docs team. A) The odfauthors.org software is a product of a past time, when leading-edge systems like Alfresco had not yet reached maturity, that does not have all the features and power of a full-blooded content development system like Alfresco: a mature version control system; powerful and sophisticated workflow management; powerful content search capability able to search within the managed content; built-in discussion system that lets you anchor a discussion on a particular content object; easy updating and uploading of content from directly within the LibreOffice applications, via the Alfresco plugin for OOo/LibO; etc. B) The odfauthors.org software is a hybrid, one-off, custom application without any community taking its development forward. The odfauthors.org system is a software dead-end, based upon a CMS that is not very widely used, for which little technical support is available except from a small group of developers. Alfresco has an entire community behind it. C) The odfauthors.org software does not have the capabilities of Alfresco to cater to the LibreOffice project's future needs for a sophisticated product that can integrate closely with the project's other development systems. Alfresco can provide a powerful platform for the production and maintenance of developer documentation: API manuals, etc. The odfauthors.org software cannot compete with it feature-wise: it is a fairly manual system that is now dated. However, Andreas, please may I respectfully ask you to understand that, in this thread, I am trying to have a conversation with the SC members, and that I very much want them to be able to read my ideas without the thread being filled with OT comments about my posting habits, etc. You are actually giving rise to more posts in the thread than are necessary, and are making my actual topic harder to follow. Could you please respect my right to communicate with the SC? Thank you for your kindness if so. ;-) If you want to continue a discussion of the relative merits of the two products, may I ask you to reply to this post in a *new and separate thread*? Thank you for your understanding if so. ;-) David Nelson On Thu, Jan 20, 2011 at 22:02, David Nelson comme...@traduction.biz wrote: 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
