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

On Tue, 2011-07-12 at 20:57 +0200, Charles-H. Schulz wrote:
Hello Jomar,

With the exception of the quite good points highlighted by Drew (some
extensions might break or might not work in AOOo) , I think AOOo is free to
point to our own extensions and templates website. Do know, however, that
although we accept FOSS licences only (including Apache!) we do already have
a specific branding of the site and that the extensions are tested and
supposed to work for LibreOffice first. I would not expect too much
compatibility problems for most of the extensions, but the issues will rise
as the time will pass.

so a non-binding +1 to welcome AOOo using our extensions and templates

Just to clarify my view here:

TDF certainly made use of the OO.o extension service to date - which is
to say our users have. 

I am in favor of our communities working together, as equals.

Right now populating the new LibO extension site with those current
extensions from the OO.o site that comply with our license model helps
everyone it would seem - mostly users as they get a stable service in
likely the shortest possible time.

So - as an interim solution I would say +1.




2011/7/12 drew <>

On Tue, 2011-07-12 at 15:08 -0300, Jomar Silva wrote:

There is some discussion going on at the Apache OOo mail list
regarding the place to host extensions

It seems that the current hosting of extensions is facing some
problems, and it will be great if we find a new (and common) home for
the extensions, in a way that both Apache OOo and LibreOffice could
use as a shared extensions repository.

Hi Jomar,

hmmm - that is assuming that the two separate projects will maintain
enough common code base that shared extensions are possible - that is a
requirement that I for one would not want to see enforced. The fact that
we can share extensions today is, IMO, a remnant of a past history and
should not dictate decisions for going forward - so I would not be in
favor our hosting Apache branded extensions on a
TDF/LibreOffice service, nor would I be in favor or seeing
TDF/Libreoffice continue to point back to Apache for any
future end user services.

One related item here - Templates I think are a totally different
consideration. I can see the ability to share templates between all of
the ODF capable applications as a reasonable goal, a very desirable

It is extensions that I am concerned with here - to put it simply, I do
not consider LibreOffice a downstream product of code any
longer as with this next release if I understand correctly there will be
no merge of OO.o code, nor can I see how Apache OpenOffice can ever be a
down stream of LibreOffice.

Nor am not saying that the two separate projects must diverge for
divergence sake, only that having a shared service would add resistance
to diverging and that is something that I would strongly disagree with -
our options are open as of today and I would prefer to see them stay
that way.

I understand that many people still hope that OO.o and LibreOffice will
somehow blend back into a single project - I can only say that I am not
one of those people.

This idea that there is some finite set of resources is one I take
exception with. In my best judgment the resources assembled here under
TDF/LibreOffice are sufficient to take this project and product

I wish the folks forming up under Apache to resurrect the
project all the best of luck on the project they have decided to
undertake, but I truly believe that their actions should bear very
little weight with the people working here when it comes to
planing/building out our offerings to end users.


Drew Jensen

We could also do the same to host templates.

Any thoughts about that ?



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.