 software, easily installable, and it is very explicit about what those applications are going to do in terms of permissions. And Google has, I think I know a little better about that recently, but Eftroyd, I think somebody has led the way on that telling you what kind of permissions, whether it's using non-free resources. So for example, you install, say, Telegram, a build – a free software and build a Telegram from Eftroyd, but it's going to tell you it's going to use some non-free network services. So it basically is a great resource. And here you can also get like an APK or you can build it yourself. In contrast, when we started working on the LibreOffice on iOS, it was challenging. We obviously had to slim down the core code, but it was a restrictive platform. And it was really tricky to get people testing builds and so forth. Apple literally holds all the keys. Another challenge that we faced along the road towards LibreOffice Online was that every build had been platform-specific – that iOS builds, Android builds and so forth. If we didn't have a specific motivated user base or a backup for a lot of money, you weren't going to get LibreOffice on that platform. So for example, even with Solaris, which was one of the first operating systems that was being supported with openoffice.org, again, Solaris being a fun product, we now really don't have a lot of people interested in Solaris it being a shuttered project with new versions coming out. But who's going to set up and maintain a build bot for that? That's one of the key ways you can get platforms supported. An Android – we made an Android port, but it's difficult. There's a new UI. I don't know if you guys have tried to do Android testing between different operating system revisions and so forth. It's a headache. It's absolutely horrible. And say Chrome OS and a Chrome box with Ubuntu, so a side load on it, for demoing and so forth, to be able to show people something on their Chromebook, on their resource, and LibreOffice just doesn't run. Same computer, consumer devices right now have accessing anything to be written in HTML, CSS, and JavaScript that can manage office documents. But a lot of you still want to maintain control over your data and be able to have control in who's accessing those resources. So the easy answer right now is code. So this is the easiest way for you guys to access LibreOffice. What is LibreOffice online, essentially? So I can sort of break this down a little bit. Calabra is a consultancy in the U.K. and they do a lot of LibreOffice that they're working on, sort of additions and improvements that we're going for LibreOffice. OWNCloud – are you guys familiar with what OWNCloud is, generally speaking? So immense edit done and so forth. VM – again, it's like a CD size, some kind of lights, if you go to Calabra's website there. So OWNCloud is online. Right now, Calabra is on Pollution. I don't have an exact date. I've heard things about the middle of the year, but I don't know. And the great things about what Calabra is doing is they're pushing their changes, their improvements, wanting to give them a bit of a shout-out. It's done so much hard work and they're providing that and it's great VM for people of some line. They've done amazing improvements to LibreOffice. They're a heavy developer on LibreOffice for Android and are pushing those changes very openly with the community. They have this sort of open-first guideline, which I think is a great model, is a great – then being a great role model. Because if you're looking at something that's on LibreOffice Online where historically we have desktop and mobile versions, if you guys are familiar with copy-left licenses, one of the things is that when we're moving towards an online environment, if people are making changes to LibreOffice Online, making changes to some of that code, they are not legally obligated to share that per LDPL and MPL. And so one of the things that CloudR has done and other contributors have done is been to share their changes with everybody in the community. So I think that that's something that we're going to need to consider going forward with LibreOffice Online, making sure that we are building a vibrant community where everybody is participating. So current features in development, the juicy stuff, we have support for wing points, I think, for LibreOffice in the Cloud. So if you have a system of, you have a company of 1,000 employees and you have 500 of those people who just need very simple, they can likely just use LibreOffice Online in the Bowser. They can just access those documents. Those developers I was talking about that rarely need to use an office suite, could potentially just have LibreOffice and push their documents up to it. Of course, they're geek. They're probably going to have LibreOffice Online. Anyone else in the company who needs something a little heavier who wants some more of the features currently implemented on the desktop could use LibreOffice there as well. And because of the consistent code base, you're going to see a lot more higher fidelity of rendering between the Online version and the desktop version. Now unfortunately, I ran into a couple of issues on the wireless network here. But I do have some quick screenshots to show you of just what the interface is looking like and some of the documents. So this is just a DocX file with an image and some layout heading and so forth. And the rendering based on the LibreOffice Engine is quite good. For example, an Impress presentation, I was hoping to give my presentation in LibreOffice Online maybe next time. You can see it renders the presentations. Charts, for example, in terms of linking of data and so forth, I think that there's a great opportunity for people who are interested in development to take some of the LibreOffice Online tools and extend them far beyond what other tools have done in terms of, say, Google Docs and so forth. Someone was asking me, you know, how is the LibreOffice Online going to distinguish itself by providing better linking of data, better ways of using the interface, at least for me. I much prefer working with my hands on a keyboard than just mousing around a lot. So I thought that especially for people who felt that that was a much more way to be more productive, get less of this strain, that maybe LibreOffice Online could take the force to use these online applications. So I'll jump ahead here. So building the code. So building the code is really easy. The amusing thing, when I was talking to a couple of developers recently, and they said, the new code, you should just grab the VM, and I thought that was kind of a silly thing at first, but when I was starting to work on computers and tweaking things, and I was talking to a lot of people recently, one of the best ways to get people engaged is to lower the barrier to changing code or making improvements to zero. And it's true, if you have a live VM and you can go in and tweak the JavaScript directly, if you can go in and tweak any aspect of the application without having to download and install on and build all these pieces, then that's going to be essentially almost a, you know, a thin line barrier to getting started and making improvements. So again, if you feel super lazy, just grab the VM and test it out. Otherwise, you can grab the LibreOffice Online code from our Git repo on free desktop.org. And the own cloud pieces are on GitHub. And if you are interested in making contributions, you can send your contributions, probably the easiest way to LibreOffice is to hop on the development mail for some help. But if you're familiar with Garrett, you can start using Garrett directly pushing patches up and pushing patches to own cloud via GitHub. So testing QA is near and dear to my heart being a QA engineer for a while. And so testing in this environment is a little bit interesting and tricky. You know, obviously high quality feedback is really greatly appreciated. And I'm really interested in hearing how you guys are interested in using LibreOffice Online and what kind of environments, what kind of devices you're going to be testing it out on. I felt slightly compelled to mention that if people, again, I really would like to hear from you being technical audience because I hear from a lot of people who often have a very robust amount of content to say and not much actual content because they whine a lot. So this is sort of like an appeal to you to have your feedback concise to the point because we get a lot of feedback that is Black Substance and I think that you would be a great audience and everyone at scale would be a great audience to give us precise feedback about, you know, the problem and the code. If you're interested in doing QA we have a bugzola for all the LibreOffice, LibreOffice Online and LibreOffice for Android bugs. Please take a look at all the open bugs. I think it's a very short list right now. I want to say it's 50 or so. So please take a quick look and please give us some feedback. Filing new bugs is very much appreciated to help promote and move the developer LibreOffice online forward fast. So what needs testing? I really would like to hear from people who are having a number of things like templates or other consistent documents, time sheets and so forth across your institution. I'd love to work with you to help you, again, have your company try out LibreOffice online. I think it's going to be a low barrier for companies to try out LibreOffice who otherwise wouldn't use the desktop version of LibreOffice. And if you see any differences between rendering LibreOffice online and the desktop, again, fonts and things might be a slight issue but if you just see some major issues I'd love to hear about that. And for speakers, I remember speakers here who are speaking at scale. Anybody? Yes. So I'd love for you guys to try it out with your presentations and give feedback to see if it's working for you or for any features because I would love to see, perhaps in the next scale, have people presenting directly from LibreOffice online as little dog suiting exercise. So I'd love to get that feedback from you. So in terms of getting your company or your organization to try out LibreOffice online, I think our number of control are important. So if we're talking about situations that are required to treat patient data under HIPAA rules, confidentiality rules, or if you operate law firm or otherwise work with legal data, you're going to have to have some strict compliance to data security rules or face huge fines. I was actually just talking to someone who works with healthcare data. And LibreOffice online, I think, in terms of deployment, you have a lot of choices. It could obviously be deployed in a cloud hosted by a third party, or you could host it locally on a server that's even air-gapped if necessary. And because of the license and because of your flexibility and how you source your technical support from whom, you can have someone audit the code if necessary and so forth to make sure that you have a tool that is purposeful for business for productivity documents, but, again, can be as secure as it needs to be for you. So, I think that's the end of my talk. But I'd love to hear from you guys if you have any questions or if you have any suggestions about how we can improve LibreOffice online or getting started with it. So, in the end, yeah. Yeah. Sure, sure. So, I do work at a hospital. Yeah. Right, right, sorry. I'll repeat the question. Integration of security and so forth. So, right now, you break it, you got to keep both pieces down. It's being connected as sort of a plug-in with that in cloud. And so, things like access and control and so forth are all three. So, I'm not sure how people are deploying on cloud right now, some plug-ins and so forth for authentication. You can use with it. But my suggestion, especially in a hospital, would be to, I mean, you probably would keep stuff behind a VPN or a firewall VPN for people to access from outside and so forth. I don't know. Again, yeah. Oh, okay. Yeah, I mean, that's a good point. You know, LibreOffice on the desktop, partially because of the nature of its history and so forth, from the ability to encrypt individual files, doesn't have any security baked into it. And so, as far as I know right now, LibreOffice online doesn't have any extra security added onto it. It stays online. Yeah, right now it does. Yeah, so that's the integration with the familiar home cloud. Oh, sorry. So, for those who don't know, the music should play me off. For those who don't know, home cloud is a cloud-based document storage and editing. Okay, we good? Breaking my microphone. So, right, we're up with that coupled with LibreOffice online, as much as you'd like. I mean, of course, for security, you know, for security data, I'm sure there are questions about browser cache and so forth, you know, that you need to address. But at least in, you know, security of data, I can imagine that if you say, disable the ability to save locally within a couple other, you know, pieces about clearing cache, I feel like you could create a pretty secure setup so that people couldn't, generally speaking, you know, accidentally, you know, leak data. So, as far as I know, around the time of, for those who don't know, Etherpad is a protected editor online. So, it's a very simplified version of this. And LibreOffice uses Etherpad extensively for our meetings. So, and, you know, so we're probably dog food. We're almost online for that use in the future. Yeah, in the back there. Right, so it would just be like an autoplay presentation kind of thing, is what you're asking. Yeah, I mean, I think that's a great question. So, that's basically exactly the kind of question or suggestion that I'd like to hear from people because I'm continuously looking to the future for LibreOffice. So, as I mentioned earlier, LibreOffice has this, you know, decades-long history and that can be good and that can be challenging. And so, for example, LibreOffice is a German company. It's just a historic panel. We have a German non-profit. And we have tons of German in common. I think Assumptong Line is continuously working on improving pieces. And I think that for LibreOffice to not only exist, I guess, but things like implementing new features, again, like sort of self-contained presentation that someone can view. Now, the thing from my perspective is that I'd love for people who, as you said, it's an embedded presentation online it'd be great for people to then be able to take that content and edit it and manipulate it and work on it in the future. I think that one of the things about a lot of applications online, a lot of tools online is that other companies also that are not of association and such are locked down. And so, as much as I encourage people to use LibreOffice as much as I ask people to take data that's in LibreOffice online I really want to make sure they're not locked into the drug because we're good, not because they can't do something else. So with the presentations, I think it would be great and again, they can right now if they're viewing a presentation online for them to be able to then again export that to HTML. I think there might still be a flash exporter and so forth so that they can take that content that's embedded in a blog, as you said. And we're not just linking them to something static, we're linking them to something that they have more ability to manipulate. So, yep. So the question is, is there any goal of running email contacts and calendaring? Either there's interest or I think one of the challenges sort of going back to having people be able to take their data out of the system and use other pieces is that it would be more complicated obviously to have additional components for email and for calendaring and so forth. I remember when we had Thunderbird and Lightning and all these other components, I know that there were some issues getting all those pieces to work together and I think there were like resource questions about how much energy was being put into each one of them and some interaction with that. But even if we were to implement something ourselves, again be hopeful that we made it extremely easy for people to plug in other tools as well because community manifesto and so forth is making sure that people can access their data and edit it and manipulate it and share it in their own language. So that's partially why we put so much emphasis on translations and so forth but also on making sure that data is accessible here and in the back. So you're asking how easy is it to connect PostgreSQL? I'm forgetting this right now. If I'm not correctly, there's connectivity bases. But if there's a specific concern you have a question then I can talk to you in person afterwards. Okay, yeah, yeah. So one of the actually interesting things is that if anyone here speaks German or any other language I'll talk to you, but especially German in Germany and in fact our documentation is in German. So in contrast to most of our documentation starting in English and then being translated to other languages the base documentation starts in German and gets translated to English. So if anyone here would like to volunteer and help us speed up that translation that would be great and that might help you, again, correct Postgres to base more quickly. You have a question in the back there? Yeah. You can embed a number of different types of documents within an open document format file. The document physically or just in like a directory, is what you're saying? Yeah. So you could probably link to that and put anything on a directory by directory basis and embed that PDF in there if necessary. Yeah, well, so you can tweak them, change the content on XML file and so forth by hand which is fun and exciting but don't do it the day before your presentation. No, this one's okay. But in fact, oh, XML file. So my sort of competitor to open up a format would say it's a zip file with XML inside it. So that's one way, you know, again, you can take a little bit of what's in there in terms of thumbnails and so forth. But yeah, I mean, you could have a lot of paths or not. But yeah, here. Yeah, so what we have right now in terms of the viewer, so you can view content and I believe, I make a look back at the bug reports, I believe that right now you should be able to open up, you know, presentations. Yes, so you can read all the content and make minor edits to, with the view you can make minor edits to those files still correctly from a new file. I would believe so. Again, the same guts are being used in that League of Office for Android code as we're using in the League of Office desktop version. But the difference is we haven't implemented everything that the desktop version of League of Office does. We haven't implemented all of the feature sets. Like if you try to do, again, there's a button to do it, but if you try to call out, the code prize isn't even there to say do a mail order on Android, although I would challenge you to try your contacts. But the thing is that, again, like a presentation, so if I took my presentation, and so if I took my presentation on my phone, right, and then went in and changed some text in it, I believe that it would then have those saved edits, like I take it back to my desktop, and that would be a fully correct and valid ODP file. So, I mean, does that answer your question? Is that? Yeah. So, yeah, I mean, again, my personal preference, my thought, I generally don't edit a little device. The screen is tiny, and the interface is horrible. I miss my phone with physical buttons because I get text and make changes in the dark and without really looking. I mean, I'm such a typist, right, so I really appreciate that interface, and I feel like I make so many more mistakes with a non-taptile sort of feedback device. But for those people who do feel like they want to use a mobile interface, you know, I think that there probably is a market for that, and I would love to see the lead office for the Android viewer, and again, with the little beta editing tools and right now for that to expand. But I think that we're really going to have to think about how to correctly create a useful interface because unless our devices get larger than this or a finger shrink, we're going to be in trouble. So, a question in the back. That's a great question. I mean, in terms of version content, I've actually used flat OVT for that previously. So, if you guys use open document files and you have a version control system for storing progressive changes to them, you can save in the one of the flat, the corresponding flat versions of open document. So, like, .FOVT is flat, .OVTX.FODS is flat, open document spreadsheet. And then you can save it and diff it to a certain extent in that fashion. So, I have heard some changes using that. It's tricky, and again, for things like binaries, I mean, it's complicated. But, I mean, I guess I just sort of have to know what kinds of changes you're merging and so forth. You know, there are, again, a sort of competing sphere to version controls using, like, track changes and so forth. So, there's a disk stack in the file. I was talking with Bradley Kuhn probably a year or two ago, and he asked if you could get, if there's a tool to convert open document change tracking, so a list of changes with information to a stack of commits, like big commits. And I thought that would be really cool. I haven't had time to implement that yet. So, if any of you guys would like a little project and you want to make Bradley happy, I mean, who doesn't want to make Bradley Kuhn happy? He's an awesome guy and works on a whole bunch of really important projects at the Software Freedom Conservancy among other places. And then, again, please chat with me, because I think, again, this is another, I think, aspect. The more that we can make it easy for people to hack on open document files, then the more expressive people can be and the better control people can have over the data, you know, from merging and so forth. So, yes, that's, yeah, there is some, I think, work there and perhaps we're going to see some improvements to merging, you know, when that lands, because the goal is for that to land, you know, not just in the online version, but in the desktop as well, because same code base, yes. Any other questions? People, I think we're nearing the end of the time. I think all of you have been a great audience. If you have any other questions, if you want to volunteer specifically if you are deploying Libraffis in the United States right now, I'd love to hear about your success stories. If you're an educator, I'd love to put you in contact with other educators who are using Libraffis in the classroom or thinking about having their classroom participate in maybe working on documentation or QAO or other projects together as part of, could I be here or back at the Libraffis booth for the next couple of hours? So go out there and do awesome things with Libraffis. Thank you.