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


Hi Sophie, all,

Am 25.06.22 um 01:44 schrieb sophi:
Hi Andreas, all
Le 25/06/2022 à 00:05, Andreas Mantke a écrit :
Hi all,

FYI: I wrote a short blog post about my work. And for those who like
visuals, I added two ones.

https://amantke.de/2022/06/25/work-on-revival-of-libreoffice-online/

Thanks a lot for your work on this, I really appreciate and welcome
the efforts :) Maybe what we should do is to have an online meeting
between you, Franklin, Daniel, Paolo and of course who in the
community is interested to follow-up.

The new online version is a really good news for me (thanks a lot
Franklin and Andreas for that), and I guess for a large part of the
non European community (as well as for students, SMEs and so on).
There is a clear interest in the community to have this online version.
+1

This is for me rejoining part of the Foundation roots.

But we also have to think about the ecosystem and the value they have
built upon this version and for us. I'm also concerned about this. We
should not ignore it.

I'm really happy that TDF come back in this dynamic, however I think a
serious discussion have to take place between the ecosystem and TDF,
not to stop TDF in acting like it was in the past, but to find a fair
place to live for everybody.
I'm sure this place exists if all parties are ready to make an effort
to reach a common goal.

I think such common ground could be reached, if not one side try to
dominate the other one. I don't see the necessary respect for the work
of every individual in the LibreOffice community and all talents. It
looks like if the developers think they are the only important part in
the community. And then there is the issue that the LibreOffice
(commercial) ecosystem is not divers enough. This leads to a situation
comparable with the situation in OOo community during the years before
the start of LibreOffice.

I want to state here that I have no issue with creating and selling
(commercial) derivatives from OSS projects, but I think there should be
the common ground of an upstream project, where all participants could
add their commits. And the hosting/administration of this upstream
project should be done by the LibreOffice community and TDF and not by
any vendor.

I think good citizens of a OSS community like to work together on a
common ground owned and administrated by the community.

And as far as I know the MPL and LGPL allows to make (commercial)
derivatives from this source with different flowers and for different
needs of customers (and if a customer agreed modifications on the source
code were committed back to the upstream project).


I ask, if I may, everybody taking part to the discussion to have a
deep thought to the international community we, at TDF, are committed
to represent.

+1

I hope my statement above is a starting point to get back to the root
spirit of TDF and the LibreOffice community.

Regards,
Andreas


--
## Free Software Advocate
## Plone add-on developer
## My blog: http://www.amantke.de/blog


--
To unsubscribe e-mail to: board-discuss+unsubscribe@documentfoundation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


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.