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

Thanks for your feedback and your support Marco.

Thanks also for your support and the edits on the wiki page which is
making it a lot easier for other people to start working on their own

I see that it is getting constantly improved and if it can be automated
with Ansible then anyone with basic skills can build his/her own LOOL.

I read that unfortunately you received an answer that is surely
unacceptable. Collabora has been one of the major contributors to the
project and they employ quite a few of the developers, it seems like one
of them forgot that he is contributing to an Open Source project on
which the company has/is investing but from which is also benefiting to
pay his wage. I'm sure the answer has been due to a moment of
distraction and that the person in question realised his mistake.

I believe Friday's discussion has been a very important milestone for LOOL.
It has brought together several contributors which are working hard to
complete the documentation needed to make LOOL available also to the
less experienced part of the community and I'm sure that many other will
join in now that several complex items have been clarified and simplified.

As from my summarised proposal lots more needs to be done and thanks to
the feedback coming from you and the rest of the community we are
working now to refine the details of the project.

Let's keep the conversation going as I'd like to see LibreOffice On-Line
becoming the obvious choice for on-line collaboration for both the
community and the enterprise market.



On 22/05/2020 20:39, Marco Marinello - Mailing lists wrote:
Hi all,

in September 2019, to get another project up and running (in which the
main component is NextCloud), I found myself working on LibreOffice Online.

This was totally a pain. The lack of any consistent documentation (until
May 5 in the INSTALL file there was just written "Left as an exercise to
the reader") was one of the biggest problems. The only way was to rely
on old blog posts found on the internet.

Another totally undocumented topic (obviously I refer to the official
documentation on was the configuration of a
reverse proxy to work with LOOL, essential since configuring LOOL to use
a non-self signed certificate is even harder.

I experienced how the community was once helpful (e.g. addressing me to
the l10n-docker-nightly and explaining the branches) and once, let's
say, less helpful (quote from the IRC "and why do you think we
(Collabora) would want to help you in creating a competing product?").
Needless to say, this has left me stunned: certainly if I write to the
community I don't expect someone to judge if I'm able to declare a
variable in Javascript or not.

Since then, however, much has been done: Online now has at least a
decent documentation which covers the build of a stable version of the
docker container. Many information are though still missing, a reliable
evaluation of the resources needed to have a stable instance and how
many users it could serve, for example. Clustering LOOL even seems to be
an untouched topic for now (to the public, at least).

Therefore, I totally endorse Paolo's proposal. TDF should, in my
opinion, definitely release working stable binaries of online. Many many
associations out there don't have the money or simply don't need a
professional support just the same way it happens for the client version.

I even agree with Simon: deploying online is horribly hard. I've been
working on some Ansible playbook since a while and I think they could be
soon released. The aim is to provide sysadmins (even myself) an easy way
to deploy LOOL. If we have on the Docker HUB an arm64/amrhf image,
having it working on a RaspberryPi would be just a side effect.

All the best,


Paolo Vecchi - Deputy Member of the Board of Directors
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details:

Attachment: signature.asc
Description: OpenPGP digital signature


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.