 Well, thank you guys. Good morning everybody. My name is Olivier. I am one of the first guys that also started with development foundation. And the idea here is to discuss about the hub content. And I use this Latin word, covattis, means where is going the hub content. I'm doing that because of several reasons. And I will explain why it's, for me, it's very important. Well, the history of hub content is the following. Until 2011, hub was exported to WikiHealth by a work of Kendi. The source of the hub content was still in the old help XML files, no HPE. There is constraints of some countries that cannot have good telecom service to accept WikiHealth. And also, as far as Sophie told me, there are some legal constraints that you need to have the help with the products. So this was the situation. And from 2011 to 2014, nothing absolutely happened with the hub content. I mean, it was marginally updated. Very few additions to the hub content. The feature between, the gap between features and documentation was widening. So many features absolutely no documentation. Okay, for instance, let me just give you an example. Where is the Impress Remote documented? I was supposed to use it here, but this is not documented in the hub. How do we activate this? You have probably to go to Google and find a Wiki page in the Indacment Foundation where some lines were written about that. Okay, and this is a very interesting device when you can go through your presentation with your Android telephone. Lots of new features with no hub content. For instance, personas, the personalization, the basic IDE, which was a work done by some of the Google students. The card statistics implemented by, I think it was Tomas Wangel, was not the documentation. The card XML streams, I don't even know how this works. Okay, I'm not a programmer. I'm just a very advanced user, but this is something I don't know how to make it work. The card XML filters, the card new functions, there is a lot of new function being brought to the office from Microsoft functions. The writer front pages, one thing that was implemented very early, but there is no documentation on how to set up the front pages of a writer document. The CNIS, the Palatial 12 Frisco, and other documents repositories, new format filters that are done by British. So these are examples of missing information. Okay, so if you don't document the features, user won't find the first date assistant. Oh, of course. Okay, then press F1 and you are sent to a page that doesn't say anything about your doubts. Okay, the second, they get lost. And when they get lost, they will think that they will office themselves as software. Okay, this is not good for us. There is loss of productivity and you get angry users and happy managers, CIOs and CEOs. And users can do bad things, you know, they can really screw up their files by not knowing what they are doing. Okay. And you lose, of course, if you are the manager, you lose the F1SQs because when users call you to help them say that he doesn't know how to, how a function operates. And if there is noise, no help, you can say that just press F1. Okay, there is no F1. Well, worse, an undocumented feature for me is a hidden feature. Liberal Office has hundreds of dozen features. Some of them are totally obscure. You don't know what is it. Okay. We cannot advertise your feature correctly because we can't even write a block entry on the feature because nothing is documented. You don't have assistance from the community. Your work as a developer will pass unnoticed. You will shoot yourself in the foot. Liberal Office must be more than a personal developer or person. It has to be professional. We need that, you know. If you are going to make, to give support, you need to get documentation. Okay. And worse, there is no reference for good but fixing. I mean, if you don't know what a feature is doing, it's not documented. And all of a sudden, the behavior of the feature changes. You don't know what changes, how it changes, and if the feature was really implemented correctly or not. You lose ground. Okay. So this is in a consequence of the fact that Liberal Office and other open source software has a very fast developer rotation. People come and go into development. When they go, when they leave, they don't leave information about the feature. Okay. And also the people that of the ODF author team will suffer to write the proper user guide. Okay. For instance, give examples. Document write an example. Tell us how it works. Okay. It has to be, I expressly use Latin words. It must be a situation for the Google students. The basic IDE implementation, the autocompletion of the basic IDE. I did it myself. I wrote to the students. He never answered me. What I got is one line of Miklos' presentation in Berlin. One line. And I had to write a page about that. Thank you, Miklos. It was a poorly referenced basic IDE. Okay. So what to do? At the moment, it seems that we will continue for the timing to use our old health content technology. Okay. There is an alternate technology to write the health content. It's not in place. This is a discussion that grows and comes and grows. But we don't have a documentation, a specific technology for the health. There are alternatives. Yes. And there will be some conditions to use it. Okay. Instead, I'm sorry. Instead, the health author extension is close to be fix and usable. We have a rescue from an open office. An extension that allows us to use writer to write health pages. Okay. At the beginning, it was not a good one. We had to fix it. And thanks to the work of Kendi, Yusuf Phillips, J. Phillips, and Regina Vigina, that it started to be usable. At the moment, it's much better than before. So you can use writer to input your text and get a health file. Okay. So we have many improvements in usability. And we have also corrections in the XHP filter. Yes. How do I use writer to edit it? Can I open a health file in the program and then mark it, connect the text, and make a new file on it? Or how does it work to edit with writer? In that case, as a developer, you open a health file, you edit, change, or add information, and you save it in the code, and then you compile the health. You do make health content, and it will put your changes inside the health. Okay. So it's an extension. It's a UNO extension, so you download it from our repository. You install it in your vanilla copy of library office, and then you can start using it. Okay. Well, I have opened the bug 80430, which is a meta bug for the gap between the features and the health content. Features that has no documentation, for instance, interest remotes. And the others I've already mentioned here. Okay. It also report changes in the features, menus, and dialogue. If a dialogue is changing, it's content. It has to be documented. Okay. There is a lot of options, new options coming inside library office and no documentation. I had to spend a couple of hours with Ohai because he implemented a feature on reading Excel files without having to recalculate the formats. And I had to understand what's used for, what's the purpose of that, you know? So he helped me on IRC, but it's not the right way. It has to be written somewhere what the speaker is doing. So you as a community member, or maybe even developer, you speak about independence in this and you write the health content. There is about 30 to 40 dependencies, I mean, bugs or gaps to fill in that situation. It's an easy hack for members of the community. It's not that difficult to write about a feature. I mean, it's maybe time consuming, but it's not that hard. So properly managed, we can have the community to help us. Okay. And if you find a difference, a gap between the feature and the health content, you should add a back to this list as a dependent. Okay. So we get the list of the features that are missing. I mean the documentation that are missing. And the other number to retain is this one, 9350580. It's a meta bike for the health authority extension. And all that we think that we can improve in the extension we put here. Okay. So what is the health authority extension? It's the set of liberal office model, several modules. It has two LXST filters for reading and writing XHP files. And there is one writer template with specific start for the health content. Okay. So what it will do, it will map this filter, will map writer styles into XML properties. Well, where to focus? Okay. First is to focus on reference documentation. We should have really a reference on what the feature is doing. Okay. This is the first thing. We need to describe the feature. We need to document the dialogue options. Okay. If you have options with checkboxes, radio buttons, buttons, text area, this has to be documented. Okay. We can, we should insert internal references or external. I mean if, in the case for instance, for the statistics that Thomas did, I had to go to Wikipedia and to borrow knowledge from them to write a couple of sentences. Okay. And the reference, the reference is the Wikipedia. It's better than nothing, you know. I'm not an encyclopedia of statistical functions. So add the page to the entry, page entry to the tree file. There is a file in the health content that contains all the entries of the help. And this allows you in the screen of the health on the left page, it will list your page. So to list your page there, you must put into this tree file. Okay. And then you set the ground for later bug fixing because if you describe the behavior of your feature, and later the feature does not behave correctly, then you know the reference. Okay. Wow. And the step two is to write a user guide. This is debatable. This is really debatable if we have to write, I'm sorry, this is a bug. I'm using 502. So it's debatable if you have to write a user guide. Okay. Because it takes time, it's not the best technology to write, and we have the ODF authors that writes very good books about using library objects. Okay. What is left to discuss? Should we insert media in health content? Because the health content is 99% textual. So it's the matter of if we can insert images, screenshots, or things that will help us or help the user to understand what it's going. Okay. Also, should we write the user guide? This is to debate. Can we improve the English writing? Most of us here are not English native persons. So my English is not good. I don't like to translate my English into Portuguese. Okay. I feel that I write very bad. So sometimes I think that we should have someone skip it in the linguistics of English linguistics and properly write the content. Then the translators will help us. Okay. And how can we bring the health content XML reference to library office? I mean, we have a documentation on the health content XML. There is a documentation. This documentation was written by Sun Microsystem about six to seven years ago. Okay. And this book, this paper, is, I mean, it's, it should be able, we should be able to improve it and, and, and update it. So it should, apparently it's a PDF file. Can we import the PDF file into a wiki page? Well, I'm finishing. Yes. Another issue is to use the dialogues properties for health content tips. There is a possibility that part of the health content tips can go directly to dialogue. And as I have an issue also, which is the health content as a separate package for download, what I discover is that people download the main program but doesn't download the health contents. And then we see on the list questions that are very easy to answer because they don't have the health installed. And for some reason, they don't get into the wiki page, the wiki pages. And also the worst of library office. Okay. What is really an horror is this one. Have you, have you met this guy? It is absolutely unusual. Okay. Not even try to find what is a cell object in the API. You won't find it here. It's crazy. I had to go to open up his API description to get it. That's it guys. Well, that's it. The demo I will try to do the demo later. Okay. About the health contents. And thank you for your patience and excuse me because it took too much time to fit the computer. Okay. Thank you guys. You can have one or two questions. So when you indicate what would be a good way for a developer to make a video or something of the future? Because video is visual. You don't have to translate it. And this would be a good start to go from. But I don't know how to do that. Maybe the developers know and we should just tell them that maybe even a developer is questioning himself how to do it. I don't know. Do you know what to do? The question is, can we insert multimedia inside the health? It would be nice. Where would you refer to the place where the media is going? Yes, eventually. Or more only for you who writes health files. So you know what you're writing about. Okay. That would be nice. A screencast about the future. Yeah. My answer to that would be also, on the other hand, what are the best views of the developer style? Again, it's enough to draft something. And for the presentation people would be able to publish that based on the information produced, also videos and stuff like that. If the developer spends time doing the videos, he cannot develop the next feature or fix the next part. So I think it's also important to find some runs. On the other hand, I would really encourage everybody from you to try the health content or that health offering extension. It goes really great. Thanks to Jace, and like every, especially we are pointed out like every even small description as he has used the one line from MiGlosh to write the health page. It just helps. So I would like to encourage you to do that. And if you're wondering, do you know how much mishap we have to get away from measuring that? No. No, I don't have. You have the button list. I have the button list. There is some open box because documentation is not there. That is not that much. Because when we switch to the new technology, we brought all the connections to the health content and we didn't change too much. But new features get inside the code and there is no documentation. So it's not that much, but there is quite a few. The new functions in Calc that I, Radke, and with free donkers are doing, for instance, I had to go to Microsoft documentation to get it. And it's not that easy because I cannot just copy-paste Microsoft documentation. That's not fun. We get trouble after that. So we have to write something new. Okay. More questions? Would it make sense so that you have this list of areas which are not documented? Yes. One thing that works really well for bugs is that we try to find the developer who to blame for something. And once you have a blame list and your name is on the list, you try to do something. Okay. So maybe would it make sense to build such a table with areas and next to the and some name. The developer can just go to that list and see if he or she is on the list. I can do that because I follow the development closely every day. I know who is doing what. It's quite motivating to get your name off from that list. More questions? So just that I got it right. So there's the weekend and there's the health content and it's maintained separately now. What's going on? So it works so that the XHP files are still the source and the L is generated for that. Okay. Excellent. Because that will be the next disaster. We are not duplicating the work. And also the XHP file directly affects translators mostly. Okay. Yes. In the health file which you open in the office, I don't know if you're here now, but if there are people that we can paste it in the health file, what would that be implemented if it's not existing? I think I press F1 and how to open a document saying there would be an explanation in the health file, but it's not necessarily that. It would be in the online version, but in the version on the computer. If you download the help locally, you will get the local help. Yes. If you don't, you get the wiki help. It's supposed to be the same. Good. It's supposed to be the same. But in the local help, there should be a link to the online health in the health file. So I can press that and then read and maybe add it to the online health. Right. At the right place. No. The problem is that the online version is not editable. It's still the... Sorry? I did not know. Yes. It's still that the XHP files that I have compiled, either to the online version or to the offline version, still have to be edited separately. Unfortunately, it did not have to make the online version editable. It just didn't come to the end. So the XHP files are still the source. So when you add the offline version, it's the same. That is what you would have in your online version. So it probably doesn't make much sense to have that link. On the other hand, Jay had some good idea that we probably could get some online editing, some easier writing, compared to what was done earlier today. Using some online, it's not editable. But you can see it as the pop-up. I think it helps. So people are likely to do the same thing.