 I prepared a number of slides with a lot of pictures and I think I have to go quite quickly through it. The idea for the talk was to give you an idea, an impression of how our extension website works today and where we can move to in the future. It is one example, one option out of a couple and that's the basic idea. We have two views to the extension. One is from the people who upload an extension to the site. The other is for people who download and the first part is about the developers, the uploader of an extension and there we have also two separate kind of users. One is the average person, our persona is Eve here in this term, who uploads simple stuff. Let's say a gallery item, gallery is just images and we have more difficult stuff or more sensitive things like macros or real code. Two options here which are not so relevant for this part but you will see later that I have a particular view on it. The plan is our CMS for the extension site and it starts with this page and when you click on log in you get this dialogue which is not SSO compatible so you need a different account. After logging in you face this site and it has just a dark sidebar which is a little bit weird, how do you continue? Any idea? No, it is here. There is uploaded new extension below this section that is a list of my extension that I uploaded before I can open it via links. Our design is not optimal in this regard because we show links as green text, green font, just green font without underlining. Okay, after clicking on new extension you get a page at extension project. You get a title, probably you cannot read it, a title, a short description, a long description and below you get a number of options for what module it can work. You get also an email reference and a home page and you have to enter some more data that are more or less relevant for you to create the extension. After pressing save at the bottom you get this screen and now the site bar is filled. Is the extension online? It is not. The point here is that you create a project and not you don't upload an extension. It is a very special workflow that users likely do not expect and many people to whom I talk to do not understand the workflow including me. It took me years to understand it. Okay, what do you have to do now? You get a site bar, cannot read it myself, a couple of options that are also not self-explaining. Let's ignore the info, the blue info section here and go to the first option. This is some apparently editing feature. You get additional information to the project that you created including a delete button. It is not what we want. So the second part is edit extension project. Next one is a sub-menu where you can create a linked release. It looks not that bad but a linked release is also not what you want because it is not the release of the actual extension file that goes into an extension project and when you link it you don't upload that file to our site. So what you actually are looking for is the extension release. That's the next point on the sub-menu, on the site bar, add extension release. It gives you again a lot of options to input. It's not optional, it's a mandatory input. You have to enter the name of the extension again. You have again to enter some description. And when you scroll down you get more. You have a number of, in this part where the cursor is, a number of possible licenses. And you have to check it, what license extension is released under. Below you get all the LibreOffice releases and you have to check the releases where your extension is working because extension might not work in all older releases or are not compatible with the new one. If you scroll down you get a large disclaimer and you get more input fields and including a field where the source code is. In our page if you don't include the source code you have to add a reference to it. I think we can come later to it. And the last point is about the platform where this extension works. So you press save and here is a little bit of feedback. If you do a mistake, if you don't enter certain information you get a little bit of feedback but hard to read. It is not, again, not really self-explaning so I added everything and after that I added some file. We can only deal with OXT files. You get again an error. It says error. Cannot read it but it's a very generic error message that does not tell you what is wrong. So we would have rooms for improvement. When you have done everything, you created a project, you uploaded a file, you understood the process then you end up at this page. And again there is a green bar and it tells you remember the status of your extension is not in the proper mode. Okay, status. It is in the sidebar. There is again a menu with a lot of options. What you have to do, I cannot read through everything, what you have to do is to set it to active or to publish. It is one point here in the list and you send a message to the admin of our site to release a project including the extension and to make it public. The admin is responsible for checking it to make sure that the license is set, that the extension is containing all the files that are needed and all these stuff. What you get as a developer is exactly this message. You get it from the admin of the extension site, this status has changed. And you get it again if it is not accepted. So you do not know why things are not working in a way that you expected. What else do you have? A couple of menus more. You can change the project here again. You can change the maintainer, the rights to deal with it. And finally, you can of course also delete it. After deleting, the project is still there. So if you not understood so far that a project is not an extension file, then you realize there is some weird things are ongoing. Actually, going back, I had it on the first slide of this set. There is one button, one big red button where you can delete the project itself. So you cannot download the Ponyhof anymore. That is for sure. How does it look with open collaboration service? It is a website. It has developed for a number of years. It was before GNOME iCandy or the like. I am not perfectly sure. One website that hosts extension for different projects, mostly for KDE and GNOME, but also a large number of different sites. The project itself is called Open Collaboration Service, but the website is open desktop so you can take a look at that. From my perspective, it looks like a modern page. You have on the top some kind of login button in your back. I wanted to tell you before, it is not necessary to have one side. You can also look and feel of the open desktop side. You can also personalize the start side. Videoland Client has the add-ons on this page and has created an own start side that looks different to the main page, but it is on the same side. After logging in, you get a screen. It works with SSO and you see again the page. You get a menu where you can create a new extension. It starts similarly with the input of the name of your extension with a longer description. You have also some information about small print. Let's say the license and some categorization information. You get logos there. I uploaded the same logo here. You can finally add some social media references for your project. After saving this, you get to the next step. In this case, I missed the point to categorize the Ponyhove and you get an error message quite close to what we did. Categorization is done with the standard format. You go to, let's say, apps, office and LibreOffice, maybe. When you have done everything, then you need to upload the files and this platform has a cool feature of the Git integration, which means an extension project could have all the fancy stuff which Git offers. I didn't do it here. I stepped over and said I want to upload a file. This is how the file uploading works. You say you load the file to the platform, then you set up a version number, where it works on what system and the architecture. That's all. After that, your extension is online. This is really online, meaning the user can download it. If you have as a contributor, if you want to participate in the project, you do some design-related stuff, some small, not really hard things you still want, your stuff being shown in the project. Actually, that's what you want. You want to upload it and immediately get feedback and share these things on social media. It's working here. There are also some additional really fancy features. The company is called Plink and they give Plinks for download. I uploaded, for testing purpose, one application and one extension here to the site and it got downloaded in total by 15 times. I earned 15 Plinks, which makes it 15 Cent, who has Cent that I earned from the company. I can get my salary for the hard work only with one dollar. This is a cool thing. The yellow disclaimer tells you the company is probably stopping this survey at some point. I think when you get a million downloads, you don't earn 100,000 from the Plink company, but the idea is pretty nice to give the people a way to monetize their work. It has also a cool feature that is relevant for the user perspective. User means how do you get the extension, how do you download? Typically, you have a couple of requests. In this case, I listed a theme. Maybe you also want a new font or you want to download the help files. Today, you have to go to a certain page. You need to know where the stuff is. You need to download it. In case, when it's an extension, it is placed at the right position, but not when you do these things with help files or whatever, or when it's not possible right now, like the personalization themes. If we stick to, makes a combination with Murmed's presentation, if we stick to this Mozilla, everything remains at Mozilla, but when we consider to dump it and do our own themes, then themes would be part of the extension and would be part of the system. The user wants to download it and it is possible. Of course, it's possible on both sites. They list it. They have an opportunity to filter things. You can go through the categories, what type of application it is. You can list on this main page only the LibreOffice themes, and you can also search for it, or miss it, and you can filter all this stuff. That's possible. I think it's pretty much clear how it works. But I wonder if a user really wants to go to some weird website and load it from a website. That's actually not true. Let's say you want to use a specific font that's in a process while you edit a document. Then you see, okay, I do not want to use a serif font. I want something fancy, some monotype font. In this case, you don't want to go to exit the application, load a font, put it on the right page, start the application, load so far. No, you want to go to the... within the workflow. At the point where the object is being used. There you want to load it. And that's what is known from KDE as Get Hot New Stuff. In this case, it is some background image or the like. I don't know. But you get these filtered pieces of apps. I would call it better, not extension, but apps. It's a nice term. You get the type of additional features here listed. You click on it and you download and you can use it. We can do the same. We can provide similar dialogue. It is a very easy thing to download the extension. Let's say the font and whatever we need in the program and put it at the right place. It could be, for instance, in the properties dialogue below the font list. If you see, I'm missing a font. It could be written in... If you get a document from a Windows user and you don't have the... or Mac user, you don't have the Helvetica font, then you can just click on the Load Font button at the dialogue. You get another connection dialogue to the extension platform and you download it. Developers are concerned about security in that regards. The nice thing of this Get Hot New Staff feature is that it is known from KDE. You have the Flex access platform to put it into this workflow or to have it as a separate type of extension. I think we can do it only for... We shouldn't do it for macros. It's going back to the first slide when I said we have users who want to contribute with simple design add-ons. Those should be integrated very closely in the program, but others like macros that are safe to element, maybe privacy relevant, that could be excluded from this workflow. What type of extension could be possible? So we have, right now, we have dictionaries, we have templates, we have language tools. We could also have color schemes. That's what we have today, color schemes, gallery content, clip art, but we could add menu configuration. Why? The design team is continuously trying to improve the menus. This improvement is not an improvement for many people and we get a lot of complaints. Where is my function? And we could upload the menu from, let's say, version 5.4 and the user just loads the menu configuration with one click and gets the behavior that is known to him or her. That's true also for shortcuts. We could provide shortcuts, let's say localized shortcuts. You load a shortcut definition for English or for French or for German, Spanish, whatever that fits into your system. Makes a lot of sense to me. Icon seams, it is ridiculous that we ship four or five different icon seams. Those have to be placed in some external things. I don't go through the rest of the ideas here. The last point, the least, in my opinion, is macros. With macros we get some people who are experts in the programming but most contributors start with simple things. Of course, when I talk about macros we can also make the application even more broader, more lean and, let's say, exclude all filters from the program and provide only the basic ODT features but put everything which is a filter, let's say OXML, into one extension and you load the filters into the program. That allows to be way more faster in updating the interaction. Of course, it is a big-scale change. Why not hardcoder stuff? It is pretty clear. We clutter our system with requests. Here it is about notebook bars. We have a million requests to change the notebook bar. How should we, as a QA team or a design team, deal with a request of one user saying, why do you not include this button in your notebook bar? It might make sense. Of course, it is a good request, but in my opinion we should exclude all these requests from the core system and put it into the design of this particular look and feel layout. The same is true for what is it icon seems. We have many requests about icons. This one is about the menu bar. The point is QA should focus on the core product. We want to encourage people to contribute. That should be as easy as possible. We want to allow crazy ideas. If someone shows up and presents a notebook bar with just three buttons on it and thinks it is a good thing, I have no means to allow him to share it, or I would refuse it, of course, but why not? We have to duplicate stuff. We update, for example, fonts. The Liberation font got into a new release recently, so we have to think or to remember to update the font from one place, copy it to our place, upload to our platform, and create a hash sum and put it into our release. That is not necessary. And finally, I think keeping the code clean is also a good thing. It improves usability, of course, when you get things into the program. If you can download dictionaries and help. And let's say also localization in the same way how you deal with everything, it's easy to understand. I don't have to say anything more, so it's a funny closing slide. Thank you. Eight minutes or seven minutes are left. Five minutes on my watch, so if there's no question. It is work in progress. It is not the only option we also think in the team there are different ways to improve our extension site. It was one few how we could deal with it, one existing, and we will see how it turns out in the future. Thank you.