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

On Sat, Oct 16, 2010 at 8:14 PM, Andy Brown <>wrote:

On Sat Oct 16 2010 17:42:32 GMT-0700 (PDT)  Alexandro Colorado wrote:

On Sat, Oct 16, 2010 at 1:24 PM, Andy Brown <

It is a total shame that they are doing this.  What next are they going

request all that are connected to the LibreOffice community that to stop
being part of the OOo community?  Those that are working on the
Documentation project can not be connected to the LibO documentation
project?  What about the Distribution Project members?  Can't offer both?
 What about the user support from the community members, not be allowed
mailing list for both projects.

To a degree I think is the wrong issue, the who cares who lead what. The
issue is if the community is breaking apart. Are there people willing to
to TDF, and is there people that will remain in OOo no matter what. That
the big concern in my opinion. It seems more than title fighting, we
be more concern of what will be the bottom line.

Well being on both lists is not the issue, but to having duplicate
communication streams makes the rupture.  Now you want to have two sides of
a community that probably wont work as one even if to a degree are the same
people. There is the third option of exactly not having roles on either of
them, yet, provide support for both, at the end nobody would want to deal
with an Oracle representative.

Right now an even bigger call is to prohibit people (not just leads) working
at TDF to speak about OOo which seems even more crazy and nearly impossible.
Let see how that goes.

What about those, myself included, that want to work on both.  As a member
of the Documentation, Distribution and Marketing projects I feel that I can
still provide help.  The two communities are not mutually exclusive.  Work
on documentation will benefit all users.  I can mail one version just as
well as the other, based on what is requested.  If trying to convince
someone that Open Source and Open Format is the way to go then all still

Yes but the open format has their own set of communities. Again, more

 Is TDF wish to leave OOo behind? Seems so, after all, the community made
big (staroffice disappeared from many people's mind). However as for much
the TDF community now growing, we have been very slow developing the
infrastructure to receive all of the rest of the projects. So for example,
where will the documentation project go, or the distribution project go?
Still uncertain about those issues, I guess they will go with time. Then
3.3 on OOo which some people will remain until the launch of that version.

I have some concerns about the prior planning on the whole thing but will
wait and see.  The documentation project's main site is on an Oracle server,
I believe, but the actual work is done on an non-Oracle server so will not
be effected.  The distribution project I am not sure of.  The mailing list
is on Oracle server but the mirrors are all over, not sure who runs the
mirror brain.

There is a choice which involved the to get their own list,
and migrate everyone to it. This is a choice we are also discussing for
other projects. Having authorship of the servers will surely help us secure
the community.


E-mail to<>for instructions on how 
to unsubscribe
List archives are available at
All messages you send to this list will be publicly archived and cannot be

*Alexandro Colorado*
** Español

E-mail to for instructions on how to unsubscribe
List archives are available at
All messages you send 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.