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

I have just picked up this email from my huge backlog. Is this something
we are interested in discussing with the other projects Michiel is

-------- Original Message --------
Subject: Liaison between LO and Calligra project
Date: Tue, 11 Oct 2011 00:24:54 +0200
From: Michiel Leenaars <>
Organization: Stichting NLnet

Hi Italo,

I noticed that both in the Calligra and in AbiWord/Gnumeric community
there were some arguments popping up every so often how they should go
about in reporting issues where LO does not adhere to the standard.

Would it be an idea to have a liaison between the Document Foundation
and other projects such as Calligra, AbiWord/Gnumeric, with a named
standards compliance person (and a fallback) within each project, which
take care of monitoring and pushing fixes - given that breaking the
standard is a severe thing that noone wants, and fixing such things is
best done from the inside.

Is this something you can perhaps discuss with your peers in Paris?

Michiel Leenaars
Director of Strategy
NLnet Foundation

NLnet Foundation
Science Park 400 (Matrix 2)
1098 XH Amsterdam
The Netherlands
sip/xmpp: michiel [@t]

Italo Vignoli
mobile +39.348.5653829
VoIP +39.02.320621813
skype italovignoli

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.