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

Michiel Leenaars:
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.

Hi Michiel,

hm - I wonder why we'd need this extra ceremony. From what I can
tell, the problem is not acknowledging the problem, but actually
fixing it.

I've personally addressed a bunch of interop things myself, if and
when my time permitted it (and usually made fixing those a priority
over other equally important tasks). If beyond that there are urgent
issues in LibO that you, or the other ODF-processing FLOSS projects
deem important, I think the most promising avenue to success is to
motivate hackers to come & fix those.

Or is there a recent example where not having such a role was
causing much trouble?

Of course, talking with you, Jos, Ben & others from those projects
on how to improve ODF interop should happen nevertheless - but does
take place, works nice & well, often & informally. :)


-- Thorsten

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.