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

Il 13/03/2013 20:45, Immanuel Giulea ha scritto:

The description page ( is
rather vague for requirements in each category.

This is an area where we must improve, although the process is quite clear for developers where certification is based on a peer review (which means that you are certified by your peers, based on your contributions).

If we want to grow our community, there should be training done. A training
session happened last month. Was the trainer certified? I have no idea, but
probably not.

We do not have certified trainers yet, although we have many trainers in many countries. They will be able to apply for certification, which will be probably based on a peer review (we are still discussing this subject, but peer review is probably the best way for TDF).

Companies are not necessarily using certified migration professional.
The same logic applies for L1 and L2 support.

Same as above, we do not have certified migration and certified support professionals yet. The project is quite young (just over two years) and this is the first certification program coming from an independent not for profit foundation.

Any help in this area is welcome.

Italo Vignoli -
mob +39.348.5653829 - VoIP
skype italovignoli - gtalk

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.