Le 28/08/2011 15:44, Ian Lynch a écrit :
We are in the process of developing our own certification. I would
suggest that if you wish to receive a clear answer you post your
specific request to the steering-discuss@ list.
That doesn't sound too enthusiastic. If this is the general feeling, let's
just agree to go our own ways. I was simply trying to be helpful in avoiding
re-inventing the wheel, enabling better use of resources, and finding some
common ground between OOo/LibO. If you have everything covered, ok, no
problem.
No it sounds rather official. Please submit your request directly to the
SC list, that's where you'll get an official answer.
As for re-inventing the wheel there are other trainers and people who
have certification expertise so while I think we won't reinvent the
wheel, I think our approach is both a bit different and perhaps cover a
broader scope than what's discussed here. This being said this certainly
does not invalidate your proposal, I was merely trying to understand
your project a bit better.
Best,
Charles.
--
Unsubscribe instructions: E-mail to marketing+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
All messages sent 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.