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


On 10/30/2010 06:47 PM, Ian wrote:
http://theingots.org/community/LO_OOo_cert

I have posted a brief description of the meeting planned to support
certification at the above address. Please feel free to copy it to any
place you think it might be appropriate.

Hi Ian, I think that the certification process is a very important step because - as you say - might become an important source of revenue, but also as one of the pillars of a necessary ecosystem around TDF.

I see certification not only for teachers and users, but also for developers of templates and macros, and for enterprise support services (companies building added value around LibreOffice). In addition, there could be a specific certification for "migration" services.

I think that you have a very valuable experience, and we should work together at building the process, as soon as we have settled down and established TDF as a legal entity.

Best, Italo

--
Italo Vignoli - The Document Foundation
E-mail: italo.vignoli@documentfoundation.org
Mobile +39.348.5653829 - VoIP: +39.02.320621813
Skype: italovignoli - GTalk: italo.vignoli@gmail.com

--
E-mail to marketing+help@libreoffice.org for instructions on how to unsubscribe
List archives are available at http://www.libreoffice.org/lists/marketing/
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.