On 03/14/2013 02:40 AM, Italo Vignoli wrote:
We are a not for profit entity, and we cannot engage in a commercial
activity. Our objective is to develop an ecosystem of third parties
able to sell value added services.
Of course of course. What I meant was allow certified developers to
offer individual/hourly or per bug prices on the certified page IF a
user seems to want options. I fully agree and understand that our
philosophy is that we fix things for free - but with that comes time
delays and in some cases I think we can all admit that some enhancements
just will never get done (look on FDO at the # of them). If a user seems
to be hinting or directly stating "I WILL PAY FOR THIS!" or they are
just getting irritated at slow progress, I think pointing them to a
certified developer list where hourly cost is up there. Some independent
developers may sooner or later join and "mostly fix for free" but
occasionally tackle a bug that only a small amount of people want but
are willing to pay for. For these bugs that will likely be years if ever
to fix the more options the better, in general the options are:
1. Fix it yourself, code is there, just hack it
2. Make friends with a developer and beg
3. Try to convince the community that it's really important so a
developer picks it up themselves
4. /Hire a developer (certified page) -- IMO we need to add this
+Included in this is the micro funding site(s) which seem to be
In other words I just meant expanding certified developers to mean more
than corporate support.
On Thursday 14 March 2013 at 01:58, Joel Madero wrote:
This is from my phone so it will be short. I think individual support
should be considered on am hourly basis would be nice to direct high
demand users to a page where they csm get a quote for their fix of
they are unhappy with slow progress for minor bugs or enhancement
Just my thoughts.
On Mar 13, 2013 1:07 PM, "Italo Vignoli" <firstname.lastname@example.org
Il 13/03/2013 20:45, Immanuel Giulea ha scritto:
The description page
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
If we want to grow our community, there should be training done. A
session happened last month. Was the trainer certified? I have no
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 - email@example.com <mailto:firstname.lastname@example.org>
mob +39.348.5653829 <tel:%2B39.348.5653829> - VoIP
skype italovignoli - gtalk email@example.com
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-website] Page to list LibreOffice Certified Developers · Jan Holesovsky
Impressum (Legal Info)
: 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