 Dobro. Vsih imaš, da bi se tudi težko težko zelo, tako sem si pričasna vzve. Pozoraj na prejizanku da je dva. Maja. Tako, tako, tako so mi tudi. So, imam Marko Marijnelo. Mi je prejizana nekaj redevčen, in sestem je izvršil. Ako vse je zelo, s pristevom svih vsevih komitecija. Imam sezvodno sezvodno sezvodnji, čo sezvoda nalivim vsezvodnja, če ne sezvodnja nekaj, ki je zbi moment vseza, vsezvodnja početno, sem tudi srednik tudi, in prezidentu linuxa ovoj boljče začali. Zelo pa se zelo v tem, da je dobro, da je djev, da je djev v DAAS, da je dobro, da je dobro, Včeš, da sem tudi tudi prav, da je klič, ki je količ, nekaj sem vse občasnjava v zelo vzelo in zelo, z vsem zelo vzelo in zelo vzelo, zelo vzelo in zelo vzelo. je, da je jaz na mene, in je prišljena na vrstani, na ko se je tudi na Microsoft Office prišljena na vrstani, da je začela, načo je začela, prišljena na vrstani na vrstani na kvali. Zvukaj, na vrstani na vrstani nekaj 30 klijaj, nekaj 300, nekaj 3 000, nekaj je vrstani, da je svetil, on a Microsoft Windows Server. And apparently, Microsoft Office licensing for Windows Server is core-based as many other softwares like the Oracle database. Yeah, it's related to the RDP server. So if you have remote desktop services installed on the server, you need a Microsoft license which is bound to the cores of the system. That's the trickering. Okay. Thank you, Emiliano for pointing that out. Yeah, and the software house responsible for the mentioned software which is not my client. So my client is a system administration company and not the developer of mentioned software. It's working on migrating the old and legacy desktop application on a browser-based software as a service based on microservices. This will make a lot of sense, I can assure you. Let me go on. So how is this software currently working and what's the user experience they have now. So this application generates some magic XML with the fields he needs Microsoft Office to fill in specific documents. The application calls directly Microsoft Office.exe which boots up, fills the fields and the user is free to manually edit the prepared documents. So he has Microsoft Office open with let's say, brief field fields. He edits the document and then usually prints it or sends the final version via email. So how we designed to migrate this. We still have the application generated fields content mapping much probably in a JSON style or a more comprehensive style, let's say. We have a library of pre-imported templates and all of that goes into the document as a service API. And then we give them as an output of this HTTP call the file in requested output format. So you're allowed to ask for starting from an ODT template and output it as an ODT template but you're also allowed to ask us to convert to a PDF. The API will have a minimalistic web guy from which you can create, upload and delete templates. Edit the templates directly in the browser thanks to free online office but hopefully will soon be WASM and check the number of requests in the last month by credits, managed token, et cetera all the kind of stuff you need to do in an API management. So some of you may already got this meme from DeskP Cable me which says in terms of money we have no money which is certainly true, don't get me wrong but I hope none of you in the amount of money we make rather in the code and in terms of code we have no code so I have presented this as an idea but has not been yet implemented or well we do have some code we have this for example you will find the link which is on your left in the published version of the slide and it's a link to the LibreOffice Kit archive and this is a part of the Pro2 software and it's responsible for generating the certificate of membership same thing just in a different way has been implemented also in Moved which is a software for to foster accessible mobility you can go check the talk by my colleague Andrei Esposito at last year's SFSCon and both this implementation relay on ODF Pi by the European Environment Agency so as you can see it's the library we actually use to edit the content of the document and then we launch the LibreOffice at less executable and ask him to convert the ODF document into a PDF this has to be still considered in an alpha stage it's certainly not adequate for large scaling lacks of any kind of cache it's missing support to FODT although it's not our fault since it's not supported upstream by the ODF Pi library and it's all filled to be created as a text so while you're creating the template in LibreOffice you need to always insert a text in the field so as you can see it's missing otherwise we might have some issue filling that since the ODT standards uses two different attributes for numeric and non-numeric values of fields so if are you interested get in touch 0.001 euro pre-invocation it feels much like this kind of mattress spots on the television I'm sorry for that it's a fake price it's just to get you into the idea of what the document as a service API could do so take a medium size the VPS load it with the document as a service API and suppose it converts 16,180 documents every month which should be one conversion every 2.5 minutes and 0.001 euro would become a reasonable price and just for a reference we are now experiencing about two seconds pre-invocation from ODT template to a field PDF of course a more advanced reliable setup would need a much more reliable infrastructure so possibly based on some kind of orchestration maybe Docker swarm or Kubernetes which can scale on demand based on the volume of requests is currently encountering boxes for load balancing multiple location replicated database et cetera so jokes aside this could be an actual project I personally can foresee a relatively wide audience of developers so colleagues that are willing to pay to externalize documents handling so they have their own application they just need to load an ODT template to our platform and then with an HTTP call being able to convert any kind of template into PDF and give them back to their user so would be let's say a zero knowledge implementation for them since it would only require an HTTP request which is quite standard stuff for a developer of course software as a service would be more and more popular so would be a useful component to have in your own infrastructure and also from a economical point of view could be a pretty solid project in this context we would have also stimulated the migration to LibreOffice so the client that uses Microsoft Office to generate and fill the templates and also the templates in Microsoft Formats and we had planned to do a one day conversion with just converting all the doc exeterer templates into ODT and import them into the new software and could be a great with LibreOffice technology product so a realistic timeline to deliver this kind of solution would be approximately a month and a half to develop the core part of API and guy and one month for bug fixes and implementation into your own software so if you're interested it's something that can be really done it's not just an idea alright, thank you for listening and it's time for questions no let's not hide behind a finger I was somehow involved with the same customer so I maybe have some more in-depth knowledge of the issue so basically in the beginning you said that the final customer need to modify the finalized document before sending it to the customer and so on have you got any idea on how to implement that on a service perspective? yeah so basically from our and also from the user and would change basically nothing so as now Microsoft Office fires up and he can edit document from the API we give them back the ODT file and they can fire up LibreOffice and edit document basically as they are doing now then that's that yeah so since the implementation we wrote up to now both for the membership certificate and for the kind of transportation sheet usually it just need to be printed without any kind of modification we decided to export directly to PDF but it's a step further in the procedure we just need to stop earlier give you back the ODT field file sorry, since I am a kind of privacy nerd the first thing that comes to mind so you're offering it as a service so it means that there are some organizations that will need to populate this field with data that could be personal information or maybe confidential information within the document how you're going to be able to ensure that actually this data being not even by the system administrator running the service and the user actually will expect that none of this information will be kind of leaked in any way and is it possible then to say I like the service for some mailers which are not risky in terms of information and then I would like to have a VM or a service span off on my private cloud so that I make sure that all this information remains within my kind of protected environment by the way, shout out to Gil Helm for this great job of microphone swapping so beginning from the end, of course it will be possible so you just need to fire up your own Linux virtual machine install the software which will be open sourced and you'll have your own instance of the API in terms of privacy and so on I can see two levels so the lower one in which you are willing to feel a document we have there will be no conservation so all the data you're transmitting to us will expire in the time of the call so once we answer the call data will be gone no another level would be on the template so I can imagine we are going quite deep but since we have time let's assume some usage by I don't know banks or medical institution etc. I can imagine they might have some kind of restricted information also in the templates themselves and not just in the data they are filling that's a bit more difficult so their own instance of the API would probably be the better solution since there is no easy way to get away if of encrypting the templates or anything like that since we would expand the aberration time since we need to decrypt the template and so on and I don't know how many real customers that need this kind of feature but are not willing to pay for their own instance there are so let's say something that we should start I believe in getting this very nice idea and say sounds brilliant now what should we do about it should this point TDF says we would like to sponsor the idea support it and so on and naturally it's nice to have a kind of clear rules so if we work together so we contribute to the project then it would be nice to say there is a commercial opportunity out there but then there is also something that the wider community is going to be able to actually use without coming up with some commercial problems in there so everybody actually benefits from what is being developed together with the rest of the community do you see any kind of limitations or problematic from the point of view no since the question so the answer is no but I personally think that the most contribution that TDF could do is more in terms of visibility of the project so not that much as of course money is always is always a benefit but the most difficult part of the project from my point of view is to find the users so the developers that are willing to use it so a customer base substantially which could also be a customer base of people who are following the product on their own but the problem I think is to gain an arbitrarious number of users that are needed to be able to tell that the solution is alive but of course free to chat with me later thank you