 Okay, I will tell you something about the current stages of the LibreOffice extension and template side, the new side that I want to create to make it much easier for users to submit templates of extensions. So, a bit about me, I'm in the middle of the board. I work for LibreOffice and it's a former, what might I say, from 2010 on and currently I'm working on the step for templates and extension side. I started that for LibreOffice in 2010 on 2011 and I'm a developer in this collective part of the plan that's the community-driven projects. So, goals from this, how might I work, is first make it much easier. First, it should, this new repository should have a search function like the current one. It should have content tags, categories, so that you can search for categories. Then we need to know which version of LibreOffice you want to search, a template or extension form and we want to have lists with logo screenshots so that people can see a bit about it, description of the things, virus spreading should be there because we want not to submit extension templates that have maybe some problems inside. Then we have this configuration files for products, the label disclaimer, licensees, etc. Many things to configure and to submit to the user. Sometimes the contributor has to submit and agree to some licensees and some conditions and we will also put in front of users that download some information that we are not responsible for. Then it should have some L10N features so that we can translate it to different languages and have different language sections. There is content that is in both sides. Currently we have both two sides, one for extensions and one for templates that is not seen in the right but that are currently two sides will be in the future one side with two applications running the different stuff for extension and for extensions and for templates extensions and we have to transport the content from the older side or current outside to the new side that will be a special process because the structure will be a bit different on a show later. So that's the current status. We have this CMS Content Management System Plume. We have a bit customized Plume Software Center. That's something that Plume itself uses to submit add-ons for Plume. Then I had some plot storage because in that version of Plume Software Center it will be put into the database and lots of binaries should not be in the database because it blows the database up. So I had a special product but it's a bit not super maintained. That's also a problem. We have this virus scanning and two products for the templating of the different sides. So inside this Plume Software Center we have a Software Center project release a section that makes my head always problems because people delete this release a section and I have the problem that they get errors and I had to fix that problem because when I add a new release a section that's a problem with this product then inside this release a section you can put releases and the releases for every version you have a new release and add to this release you have to add a downloadable file that's this extension or template or you link to another direction when you have always a server or a service where the files are always delivered and you can link to that. You see it's a bit complicated. I have always to help users and so that was my start point when I want to make it more easy and comfortable for users to submit their templates and extensions. So what will we do? If you see we have this Plume. We have two different center in the future and we have virus scanning and one layout product. That's also a new method to template a site because you have rules file and then you have HTML and CSS and images and a connection between those so that the dynamic of this content management system is connected to this static files. You need only for templating one who is doing this stuff or who does the rules file and later on one developer who is able to do HTML and CSS. So what we have not have anymore is an extra block storage because the new one inside the product is putting every binary into a block storage that's started. So if you see the current status on the left side and the future status on the right side you see I have killed this release section and I have made also smaller the two battles. First I made only a release but with files that you could put inside the system but in the last weeks I made also this linked file because I know that people have always sometimes their files on different web services and want to link to that and so I provide also another object that has the possibility to link to objects that are outside of this repository but then we have not any mirror scanning for these people that may be a problem but they have to link with that. So if you see this green one is only for the side bench or the admin of the side but the contributor has only two objects to work on a project that has to be submitted and then published by review and then they could put releases with files or with linked files to this project as many as they want so should make it a bit easier would be great when it's in connection. The connection is a bit broken here. So then we have this messaging feature that we have not in the past when a new project is created the manager of the side or the management of the side will not see that although he is looking in the dashboard but that is not on your regular basis so we thought that it would be good if the manager would be informed when a new project will be created so that he or you can go to the project and review it and publish it then also for when the project owner doesn't know if the web flow status changes when he submitted for publication and the reviewer is doing the publication make it public then he don't know currently that it's public so in the future he will get an email and will be informed that this project has a workflow status change and he can look what the workflow stage is currently for this project maybe there is also some information that should do that manually so also when a new releases would be great when a new release is supported to this project because the owner knows then someone maybe said he himself has put a new release to that project and has not to look every day if there is something happening if someone is maybe contributing to this project so maybe so you see I want to show you that in the code the code system brings this messaging on some advance that's inside the features of the project and you have to have some coding to use this messaging feature in this one event the change of the status a mail will be sent to the owner of the project then the status has been changed the message is here the status of your project people on this extension project changed and your child subject that's the project name you see that's the message in hard-coded form that will go out to the user so he gets a message and can look on his project so you see that's not seen at the moment really seen but let's from the structure of the new center we have on this left side most popular extensions on the right side most recent extensions and a list to search for new extensions and templates it's the same in both parts one for extensions and one for templates that's the new project you you have here this description on the right side of the project resources for example if someone provides an external documentation and it is listed the link there so the install instructions I made it not good because I pasted a text real see it could be also linking that's a new resource for a release here you see only one is submitted one we have more than the list is longer and the compatibility and so on there's a level of mistakes can you go back? you see when someone has logged in and is able to write on this project he gets some more information one would be one he has not submitted a release and will be an information on top he should go the next step would be to submit a release if he has already one submitted then there are some links to click on it and go in the process to submit a new release they have different versions one with the person or files that are hosted on the system and the second or linked files linked release you see when someone is editing it's very easy there are fields with some descriptions that you can do this is a field where you can also put in some links it's very common on this field with some editing features as you see there is also a place for submitting a logo a screenshot and so on and some information I won't show the mail address of the owner what will you do next? the content of the current site has to be transmitted to the newer there are different methods we are thinking of making it a project for the next tunnel because we have new content types that are modern content types on the floor we have the current statuses with old content types they will be gone later with version 5 that's on the stage we have fewer content types so we have to shrink and to get the information in the right direction there are different ways to reach that maybe with a Python script because everything is running Python it depends on the numbers how much content we have to run what we want to have is also the historic of this current system the things that are in the portal are listed in the XSAT as you see then the MAM members users of the current site has to be migrated to the newer I have already a way to do that it's very easy all users have to get a new password they have to click and get a mail with the link then maybe I want to do some more exploring part of this the members I know that it's possible with Python script that I have already created that and took it up I use it for that then added some more languages the content is already enabled for multilingual support but I would first start with an English version and then later on add some more languages because everything has to be translated to the new languages that I add otherwise no one will see any content on it and that's not fine then when you get some more languages you have to move the content to language folders and that makes it that nobody will see with a different language the content when you have a German language setting in your browser then you will not see any English content so the content has to be translated many things we can do with this portal because the site itself could be and the add-ons can be translated with profiles so it's not that difficult in the normal process and the next step will be to have a new design we have to find someone who wants to make HTML and CSS files and make a new shiny design for the site because it's static HTML and CSS a skilled web designer should be able to make designs I think it's not that difficult to find one the root file is that thing that makes it dynamic to connect the dynamic CMS with this HTML so the nice thing inside the model is you can test it you can write this root file and there are also this index file that's normal HTML file and the CSS and images so you can use it to make it on the test side create a work on CSS and HTML and see already the result what's working, what's not working so it's really easy to apply a new theme so, questions what are the versions numbers the support was it really impossible to say that the support from this version and all the future versions no, but I have also made you have some fields to click on which version it's comfortable when the manager puts a new version to the list then every project owner will get a message that there is a new version of the office added to the list that you should look at his project if the releases are compatible with it that's a problem that we already have at the moment because someone puts a release outside and when there are another version of the office is out then nothing happens because nobody takes care of it so when we change over to the new side we have to look at every project, every release from the current side if it's compatible with the new and when it is there, when it is then we have to check that it's compatible we need some people, QA people who look at the projects and releases and make a list what's compatible, what's not compatible I'm not so happy to transport versions releases that are only compatible with Libre Office 3.3 for example, to the new side when they are not compatible with the current versions because we deliver 4.4 and 5.0 at the moment and 5.4.4 will not be delivered in a year or a half a year so it would be great to have only current versions transmitted from one to the other