Hi Kostas,
Le 2012-07-29 04:20, Kostas Mousafiris a écrit :
Hey, that was a truly great idea Marc!
I already put it in practice :-)
I wrote back to those guys, inviting them both to be a little more
precise as to the difficulties they encountered
and to also join LireOffice Discuss list, so that they can contribute
too, with their personal feedback,
to a productive and collective effort towards improving the product.
For those who were surprised by the existence of a Libo discussion group
in LinkedIn, http://tinyurl.com/c8u7z8u
Have a nice Sunday!
Στις 29/07/2012 12:30 πμ, ο/η Marc Paré έγραψε:
join the discussion here where we concentrate on improving the product.
Great! Hopefully we will get concrete feedback and some bug submissions
from it. I believe some devs are listening on the discuss list and keep
an eye out for things like this.
Cheers,
Marc
--
Marc Paré
Marc@MarcPare.com
http://www.parEntreprise.com
parEntreprise.com Supports OpenDocument Formats (ODF)
parEntreprise.com Supports http://www.LibreOffice.org
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.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.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [tdf-discuss] Re: Libo discussion group on LinkedIn · Marc Paré
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.