 So, thank you Dennis for the introduction, my name is Marco Maranello and today I want to give a bit of a update on the building and using the graphics line. As you can't see me, I've added one, a picture of me later on, next slide, so the agenda will be the who am I, a short story of LibreOffice online, how I met it, what I've done, about the breakup, what's building, what building online today means, and why the wiki won't trick anymore, the last one standing and why it can't be good, new versions from collaboration repository, some tips on how to build and on how to use a quick route map for the future. So who am I, I'm a freelance developer and system administrator, I was previously working in continuity which is an Italian corporate and part of work was also online, I'm a computer science student at the Free University of Bolzano, a member of the document foundation and also the president of the Linux user group of Bolzano which is celebrating the 20th anniversary this year. So the short story of online and some of you doesn't know what LibreOffice online is and dynamics behind it, so it was announced back in 2011 with the idea of bringing the LibreOffice package into a browser and have collaborative editing and so on. It was mainly developed by Collabora and it's written in C++ javascript and requires running his executable on a web server so it's not something you can just upload on a shirt hosting, you pay a couple of euros a year, it requires I would say a Linux host running his own executable which spins off a web server you can then proxy via HAProxy Apache or anything you want. It's based on the WAPI protocol which was first invented and introduced by Microsoft and it's protocol for sharing files between storage and editing environment. So C++ which as we now know was spined off as an allotropia and by the way it's an honor for me to speak next to Thorsten and the allotropia team and also one and one started developing and selling online and here you have the map of the organization contributing to the online repository at CDF's infrastructure from the Kibana dashboard. Time becomes the subject of many talks so on the wiki page of LibreOffice online you have a short list that will need to be integrated after the talks of LibreCon of this year and yeah as you can see it was quite an interesting topic was presented and talked about quite a while last time in 2019 it was the SFS and I was there since it's held in Bolzano and I live here and was basically when I was also working on LibreOffice online. Online is being integrated in many distributions for self hosting and commercial products so this is also taken from the TDF wiki and we have a list of commercial products mainly clouds let's say your next cloud instance that also offer the online editing through LibreOffice online but on the right side we also have softwares like the Cortesa community server or colab that provide an executable to run your own instance of online so you were able to have your next cloud instance or on cloud or anything else and integrated with your own online server so I said it was the 2019 when I was working on the Fusra mode access which is a web application for around the accessing files in distributed data and Samba based infrastructure when I met LibreOffice online so the integration with online editing was pretty interesting and it turned out there were almost no documentation on how to edit and the wiki page was more commercial so there was the lists we have so before regarding the providers there was a short story on how online project was started but there was no indication on how to build it and when provided Docker images came with limitation of concurrent users so the pre-built images that were published on the Docker hub or anywhere else came with a limit of concurrent user that could use that and after that limit was reached the nplus1 user would just get a message the limit it's over by a license and I had the pleasure to talk with Michael Max yesterday actually about online and he told me his imitation was removed it's kind of a really good news but back in the time there was this problem so I started working on a reliable way to build online and wrote appropriate documentation about it these Elton and Docker nightly script was already there and did almost anything we needed so starting from scratch I was going to clone down the core and online repository on the branch you want build it and then generate a Docker image it just needed to be expanded a little bit for example adding support for different host OS so back in time there was only one Docker file which is which was for Ubuntu and if you were building on Debian and then just copying the installation during size Ubuntu container this wouldn't have worked of course so one of the things we have made was provide different Docker files so that the script can autonomously decide which one to use depending on your host system a new page in the wiki targeting only how to build online and many members contributed to it so now in the tdfs wiki you can find a page which is named building online which is entirely on how to build and which flex to set and so on there are also other pages for the reverse proxy for example but that were not quite finished so yeah this one of the things done that are really done so the breakout shortly after the release of LibreOffice 7 Collabra announces they will work online and stops contributing upstream quite disappointing I know so they basically for the online repository at the point it was the time time moved it on github and simply stopped pushing their commits back on the tdf infrastructure so building online today the repo at tdf is still readable but only that it's in read only since the board of directors decides to read it and of course it's outdated so since nobody can write there the last push is almost a year ago and it misses security updates so why the wiki won't do the trick anymore yes if you watch and check the tdf wiki and try to build against the fork you will have some issues and these issues are mainly that they change the structure so as the Docker folder previously was containing the scripts to just compile down the entire stuff and now there are two different sub folders from packages and from source the first one provides an easy way to build the Docker image by just downloading the build artifacts from Collabra repository so the packages install them into the container load the license key and you go and from source it's basically what was the Docker folder before and the variables so there was this renaming as you can notice the no Docker push variable of the script has been dropped and the other have mainly been replaced from LibreOffice to Collabra yeah it has been stated in the past it's not the best practice of course this is a patch set it's available on Garrett it will be linked in the presentation changing the variables it's a practice appointing as pointed out by Samuel changing variable names break scripts and documentation so the documentation that it's a tdfs wiki it's outdated and provides a wrong name despite the Collabra branch and fork the last one standing targeting with the one that is the latest version you can build from the read only repository of the documentation which will be based on the LibreOffice 70 branch and 706 of the core but you should not do that here's why it ships with common vulnerabilities exposures that would require backporting the fixes and you can do that since the repo is frozen so some common vulnerabilities exposures where it is covered after the fork and they have of course been fixed in the Collabra repository but there is no chance to get those fixes back into LibreOffice infrastructure since the repo is frozen so the only way it would be to fork the repository on your own and back for those fixes but this won't be an improvement things will just be another fork and the same applies for the compiler so ZCC version greater of 8.3.0 requires backporting patches so trying to compile on IBM 11 will just give you a bunch of errors even if you give all the possible disabled warning flags you'll still have issues and again the only way to fix them it's to backport the patches but you can still compile versions from the Collabra fork the script is now the docker from source build.sh and will default to distrocollabra cp64 branch for the core of LibreOffice and for the master for to the master for online which up to this night doesn't compile but you can use the distrocollabra cx64 which is the stable version and you can always refer to the GitHub releases and to check out which is the latest stable if you want you can of course also download the releases from GitHub and compile from there if you want to avoid stuff with Git going on and talking about Git if you care about your time use the GitHub read-only mirror because Git at LibreOffice if you have to clone down almost four or five gigabytes of the core repository will take literally forever so at least from GitHub you can get a satisfying download speed and of course for both online and core use the cache if you don't want to compile it from zero every time and set it up properly so set cache size it is appropriate so five or ten gigabytes and keep in mind that building will require many hours in my experience more than five on a 12-core Xeon with 16 gigabytes of RAM now the most interesting part so using online how can you nowadays use online so the wiki contains a short list of non-integrations and are all marked as official as unofficial sorry since are not released by the document foundation itself and as mentioning next club is one of the strongest integration we can notice but there is also a module plugin which is quite interesting in my opinion allows you to collaboratively edit documents with the students or allow them to submit an assignment using the online editor there are also own cloud and much more integration that we know but nobody after now reported that they tested it and put it down in the wiki so as mentioned before online uses the whoopie protocol can be integrated in any application that is already integrated with office 365 or other whoopie based online editors and remember to double check the app stores for commercial names so as said many times you will find the app to integrate the graph is online into another software released as a with commercial names so for example collaborative line this also applies to moodle also the moodle plugin is named collaborative line you shouldn't be afraid of that since normal operations will hide the commercial name of the app from the end user and override them with the compile time flex so once you have opened the online editor under the health menu info you will find the stream you have specified in build time so should really not be a problem now last but not least a roadmap for the future for everyone for me for you from tdf and so on update the wiki from an historical point of view so the wiki is now stuck with this procedure on how to build online but there's nothing about the fact that the repository at tdf it's frozen and there has been a fork and so on so someone should take a final decision on the frozen repository and the documentation so if online is still a project of tdf it makes sense to me to maintain the repository and the wiki but if it's not maybe we should just drop them while waiting for wasp and this is the reason of course it was a pleasure for me to talk after allotropia use online in second time hopefully we'll be able to migrate to wasp will it yourself yeah if you have time to invest in it mainly a computer to dedicate it's of course way funnier and you can take the chance to use the customization flex which will be without name and without branding and this is also documented in the tdf wiki page be creative so life needs creativity so be creative and don't forget to contribute to the project one thing i noticed it's that tag and locker file it's broken at the moment due to the switch of bastard from stable to stable and a missing library in a bullseye so just find yourself something to do and do it thank you so much sorry i've got two minutes out of my time but if we can i'll be answering any question thank you again