 Okay, now we go with a few data about the project and before, I think we have to remember John McCrish, John passed away in early 2016, was a friend of many and it will be missed by the project. I think that John's heritage stays with us with the text of the manifesto that he wrote in 2010 and I thank John for the contribution to the project. He has been a friend of many and we will never forget him. I think we should applaud him and now to what we have done during the last 12 months in general and this is a map, countries in green are countries where TDF members are based. As you can see, we cover all of Europe, most of the Americas, quite a lot of Asian countries. Unfortunately, we are still not present in all of Africa but if people attend this conference and contributing to the project have not already applied for membership, I really invite you to do so and you can have the opportunity of speaking with membership committee members, one is Gabriele that has just entered the room, to ask what you need to do to become a TDF member. It is rather important because the Document Foundation is a member-based organization and only by growing the number of members we will grow the strength and the coverage of the Document Foundation. So this is something that I personally invite you to consider if you are not already a TDF member. And we, for the first time, we have a traditional annual report in TDF format. This year we have a printed version of the annual report. We have a number of copies, you can have a look and don't take it away but you can, if you are interested in getting it, you can buy a copy from Lulu. It's printed on demand and it's going to be shipped to your address. And as I'm thanking the members, I think we should not forget the people that donate to LibreOffice, to the Document Foundation. This is the trend of donations since we started accounting them in 2013. It's thanks to donors that we can have a solid infrastructure, that we can have a team that helps people in their daily activity, that we can reimburse travels of people attending conferences and so on. So of course, most donors are not in this room but I think that all people that are members of the project should be grateful to the effort of these people that mostly at download time give something to the project. Next, I want to thank and welcome, although some of them are not here, the new members of the advisory board. This year we had several new members in the advisory board. We had GNOME Foundation and KDEV. With this organization, we are exchanging the presence in the advisory board so we will probably help them in growing as much as they will help us growing the project. And it is important that open source project, free software project work together because only by working together, combining our efforts and helping each other, I think that we can help the growth of free software in general in terms of visibility, awareness and reputation. Most of the users around us are used to proprietary software and only by helping them to understand and educate them about free software we can grow our project. The next one is Canonical. I think that everyone knows Canonical is behind the Ubuntu project and Canonical is now a member of our advisory board and in this case it's very important as well because they help the outreach in businesses through their Ubuntu distribution. And last but not least of course, Free Software Foundation Europe. We have been to Berlin to their summit recently and it's again working with them and helping them grow and helping them keep on and advising them about their activity. I think that we can help ourselves in growing and getting a better space for LibreOffice in terms of penetration in the market. Of course announcements, we are now at LibreOffice 5.2 so during the last 12 months we had two major announcements, 5.1 and 5.2. This timeline gives you an overview of what has been done since the launch of the project in 2010. Of course if you look that with the developers' eyes you might question this kind of stuff I know but we don't have to communicate only to developers. We have to communicate to people that does not understand development and adding some clues to these helps people in understanding what the project has done during the last few years. So of course the picture is a lot more complex that this timeline is visualizing but this is intended not to communicate to you but to communicate to people outside the project. I think we will provide an updated chart. This is not updated to the last three or four months but this is the download trend. We have probably exceeded now 140 million downloads and of course if you look at the red line this gives you the cumulative number, the other ones are the monthly numbers. And thanks I think that the effort and the successful LibreOffice is the result of a combined effort of many components. Of course the first one are developers without a good product. There would not be any other activity that is deriving for the good product. On the other end I think we have been able to gain some traction from the media. I am going to show you some articles that have been out during the last 12 months and I think the positive outcome of this is I think that during the last 12 months the articles have reflected our message to media. So we provide some messages. Messages are about increased speed, increased robustness, stability. In other cases is about the user interface being incrementally updated and improved. And for the last version we insisted a lot on the business approach. So with 5.2 the message was that LibreOffice is ready for enterprise deployment. We perfectly know that enterprise deployments are a challenge because we enter an environment and an ecosystem where proprietary software is still more than 90% of market share. So I think that reading these kind of articles, of course these are only the titles but reading these kind of articles is helping companies and enterprises and organizations in reducing the number of doubts in deploying LibreOffice. In my activity in the local market, so in Italy, I use a lot what is being published on the media to help people that are deploying LibreOffice become more confident on their deployment. And I think this is an opportunity that everyone has got. If you read a nice article on LibreOffice, share it with your acquaintances. If you have a commercial objective, share with your customers. This is going to help everyone. We have to build a network of people that is confident about deploying LibreOffice because that is our best strength is word of mouth about deployment by people that is happy about their deployment. So these are the last ones and thanks to the Dutch Ministry of Defense that has sponsored that and to collaborate that has developed. The impact of the classification feature has been extremely well received by the media. It is quite important. Many, many large organizations will ask about this feature and today LibreOffice is capable of answering this request from enterprises and corporations. I finish with my partner and now it's Michael that will tell you a number of numbers that I don't understand but I know that are significant. Thank you, Talo. That's wonderful. This is my pet random selection as of very late last night of things that we've done last year. And I think this is a fantastic thing. I think Marcus isn't here, but I just want to pay tribute to his work here doing this crash report because it's been a long time since we haven't reported crashes and being able to get back traces out of these, not having to ask users to install the Windows debugger, set up the symbols, whatever, but just having a good statistical grasp of this, 17,000 or so crash reports already. Isn't that something to celebrate? Anyway, the good news is that we are fixing the top ones and it will just have a huge impact on quality. Obviously, we really want to improve the quality of LibreOffice as we go along. Here is another graph that's extremely pleasing to me, which is that our open regression count seems to have stabilized over the last year. So we have almost as many regressions as when we started the year and this is a great place to be because we also created a whole load of new features and shipped a whole load of new cool stuff. So to actually be relatively static is good and to see that trend coming down as something in the engineering steering committee, we watch this every week and try and agonize about it. So it's very, very encouraging and I was particularly encouraged to meet Aaron earlier and Aaron was like, oh, I just love fixing bugs. I just want to go and 10,000 to go, which is very, very encouraging. Unit test, of course, it's once you fix the bug, you want it to stay fixed. So it's also good to see the unit test coverage increasing and the number of macros and assertions and tests going up over the year. There is a whole load of really extraordinary work that's done primarily by Quaylawn but also other people in the team, just sort of beating back the perennial problems that come and bite us. So keeping the crash testing running and actually fixing the results of it. 92,000 documents were testing very, very regularly and making sure that they import, they export and to some degree that they validate. The covariate scan again, keeping the score out of the industry beating 0.00. We actually had a whole load of new issues recently which made this number slightly higher, which is good. So new tests and covariate showing up new interesting things. But even just basic stuff, CPP lint checks. We have a couple hundred of those in the last two release cycles. And life cycle improvements, code clean up, C++11, there's this whole load of things to make the code more beautiful, cleaner and readable and so on. We've done a whole load of things to try and make hardware acceleration more robust so that we pre-validate the or hardware drivers are actually going to work or at least we crash early and then disable them rather than waiting until later and crashing. So some good stuff to improve quality there. I think this last year has really been the year of continuous integration and I think we have Norbert at the back here to thank substantially for that. I'm making sure that the bill is constantly buildable, constantly releasable. It's absolutely fantastic. The CI stuff there and the hardware investment, I guess the CIS admins as well, Klopf is grinning there next to him, have set up some massive hardware infrastructure again funded by our generous donors to make this actually really, really work. And so it's now possible to push your code within a few minutes, half an hour, an hour to get an answer as to whether it runs really well and more importantly whether all these tests run on it. So we have had a whole suite of tests. You could run make check for years but they've not been the most reliable things in the world and some of the really nasty bug fixing there. Again, Red Hat, Michael Stahl and actually Armin, Tib have done some great stuff with Stefan to sort of wheel out these horrible race conditions, these nasty bugs, these weird locking problems to make those tests reliable and that goes together to make CI just incredibly better than it has been in the past. And a quick plug at the bottom for this Dev Central website that shows you some of this hidden infrastructure that perhaps you didn't realize was there and helps you get into LibreOffice development. So pretty. Then we've got some features. So we've obviously got a big focus on quality but also we like our features. I think Vitali raved about this earlier. He missed out core, however, which is terrible because this is a new and off in innovation, aha, yeah, here. So there we go, good man. So classification is good fun. And for those who don't understand what classification is, because I didn't understand it either, it uses cryptography but only to sign documents. Okay, so there's no DRM, there's no not able to get at the document unless you're magic, but you can prove that it has been signed off to be of a certain classification level. So it's very nice, at least that's my understanding. McLosh will give you the full details later. Yeah, I like this one because it's pretty. I suppose we should have included some of these nice 3D transitions, lots of open GL, acceleration, optimization, robustness work around that. One of the perhaps underloved areas of the project has been our help and documentation. So it's fantastic to have Olivier and I'm sure Florian will tell you all of his good work later. But working with I think Kendi and Regina and Jay and others have resurrected and improved this help authoring extension so that now it's easy to write your help. So when you've written your feature, please also write your help. See, Olivier, I'm sure he has a talk on this later. And also just some really nice stuff to help get people involved with the help, sending feedback online and so on, adding various functionality there. As I mentioned earlier, this is a completely random selection of things. I can't show you everything we did, but it seems pretty clear to me that Ika from Red Hat and Winfrey have done a fantastic job adding formulae and fixing formulae in all sorts of corner cases and making this just much more insroparable and consistent and beautiful. And Thomas has been doing some of this regression line stuff and charting and complex formulae analysis and wrapping. I don't know, Lauren's been doing good stuff. And here are the people that have been doing it. So this is individuals. So every month we analyze who committed and this goes up, I'm afraid, only to the end of month seven. I should have remade the numbers. But the punch line is we have around 80 people or so individuals, unique individuals committing every month. And here's how they break down. So you can see who they work for on the top. Assigned, incidentally, just means you've signed a copyright assignment. Or not a copyright assignment. You've sent your message saying, yes, I really agree with your license. We actually track that behind the scenes and hopefully Klopp manages the wonderful database of everybody to make sure that we really know what the rights are around the code. And we're doing this in a way that everyone has signed up for explicitly. So those are the people. So it's really good. So the great thing about this is there's a huge number of volunteers, which is probably the green magic here, which is fantastic. And they actually produce really quite a lot of commits too. It varies, I guess, depending on season. But in terms of commit volume, so this is the commits per month by affiliation as well. And you can see we get around 1,500 commits a month or so. And you can see how it breaks down there between the various people. For any aspiring volunteers who want to take on his mantle, his role, the blue at the bottom here, parallax, it's just one guy half time. That's Noel Grandin, so you know. And he's coming to work for Calabra. So there's a hole there. So you could be that guy, that's fantastic. Doing lots of clean up and awesome things with an automated testing and clang plugins and validation left and right. What else? So it totally talks about user experience as a key thing. And so I'll show you some of the user experience changes we've had. There's just been a huge amount of work around sidebars and toolbars. You'll have seen some of these if you use a recent LibreOffice and the changes and improvements. So for example, there's a laser thingy here, is there? It can kill people, excellent. So this guy here, being able to see which end of your lines, which are gonna get this much more compact. So you can show more in the sidebars, very nice. I can't remember even all of the things that have gone here. But all sorts of properties, better slide transitions, better arrangements of everything. Separate UX things. So some template manager things. This is brilliant to have this fixed, because this was a bit of a nightmare having a very old and ugly template management thing. And also the new and beautiful one. And yeah, so unifying those and making it look pretty is fantastic. Find and replace. You can now hide all of this stuff at the bottom. So your average user never needs to know that there's a regular expression mode because that would frighten them. Don't frighten users with too many options before you've taught them to love them. So again, a nice work there. Even more work on user experience. Bubbly has done some fantastic mentoring and being her fingerprints all over this with Yusuf as well. Just improving this sort of thing. Look at this nice pallets of things to insert that look more familiar and really, I think, preparing for the notebook bar future. So this is my last slide. So there's some other bits going on. LibreOffice Online, there's lots of work going on there. I'll talk about that in a few minutes. There'll be several talks through the conference about that as well. But this is a horrible subset of work. If you don't see your name on a slide, that's because I forgot to put it there. And if you don't see your feature, that's very normal. Most other people didn't either. My apologies in advance for missing yours out. But I just want to say thank you. I mean, I do very, very little of this work. I just stand here and talk. But there are people out there just putting their love and passion and sweat and blood and tears and debugging late at night to find that missing semicolon. And they're doing awesome, glorious things. And thank you so much for all the documentation, the translation, the help, all the good things that people put in. So you're rock. And that's me. So hello also from my side. I actually love this kind of traditional state of the project talk because it gives the opportunity to show what has happened. We've seen numbers from Italo. We've seen development and features from Michael. And I'd like to talk from my administrative point of view a couple of projects that have happened. And introduce you, first of all, to our team. Michael Italo has mentioned we have lots of generous donors. And they enable us to run projects and to have people working on them. And I'd like to give a picture to the name and tell you what our team has been working on in the last months. So first of all, we have met already Sophie. First and foremost for this conference, Sophie is the gateway between TDF and the local conference organizers. I think you have been running conferences since, I don't know, a decade or so. We met actually at a conference 10 years ago. So she's organizing all the bits and pieces, getting things together, helping the local organizers, organizing travels. And many of you know Sophie. If you're a TDF member, she's the gateway between TDF and the members, which have the refunds, all those sort of things. And Sophie is quite active in the native language community, helping them, guiding them, assisting them with all tools, with all resources that we have, answering questions. So, yeah, that's Sophie. Then Italo, you already have seen and heard him. Obviously Italo is doing marketing for TDF. And he's our main marketing contact, doing press releases, media outreach, organizing the local press release workflow that press releases get translated, get sent out, manages the journalists mailing lists so we can have a good outreach to the media. If you're a TDF member, you get a nice newsletter each month sent by Italo. He also volunteered for working on the budgets that we have started this year, the marketing and the community budget. Italo is organizing and coordinating that. He set up the certification program for TDF and a couple of other things that's done by Italo. Then also quickly mentioned was Kloff sitting here in the back. He's primarily our release engineer and the guy ensuring that the bills reach the mirrors that you can download them. Also, these with the app stores to get our apps out. They are Kloff's also quite active in infrastructure at the moment running info operations. Primarily the developer infrastructure, Garrett Jenkins, Buxilla and the like. Website, Superstripe, that's also Kloff and all other sorts of things. Basically Kloff's always around when there's something to do. Couple of new faces. I'm not sure if Haiko is here yet. Oh, sitting right in front of me, sorry. So Haiko is quite new to the team. I think since May working on user experience has been volunteering on that before and working on the user interface running the UX meetings, service doing research, doing everything to make the user experience in the UI of LibreOffice better to sum it up. We have a design block that's run by Haiko. He triages UX bugs so we can be more effective and move forward all UX related topics within LibreOffice. Then shortly after the last conference, Jan joined to mentor new developers to help get people on board it, to reach out, to work on easy hacks, to introduce them, to Garrett how the patch workflow works, to take them by the hand and help them to get involved. And that's quite helpful. He's working also on some developer bits on infrastructure running Hackfest, doing everything to make developers feel welcome, feel appreciated and give them the support they need to contribute in the best way they can. Early this year, Olivier started. He's Olivier, he's responsible for documentation that contains of course writing documentation, organizing the workflow, onboarding volunteers running the meetings. But also I think we've seen a screenshot of that before work in the help system is carried out to make that easier. There's a wiki and online help that those are all bits and pieces that Olivier is working on the workflow on the tooling side as well on the content and getting volunteers involved and that of course involves style guides, templates, all sorts of things to make people working on documentation having an easier life. Then there's a nice guy with a camera. Actually sitting there, Mike, he also joined early this year supporting Italo in marketing. Mike is publishing regular interviews on the blog. He's feeding all social media channels. He will probably ping you at the conference because you're right now working on a community video I think. So he wants to get some quotes, some statements from people contributing to LibreOffice present that. And he also created the nice feature videos to introduce what's new in a specific version of LibreOffice. That's the work Mike is doing. Lots of flyers, brushes, and a very successful month of LibreOffice contribution that we ran in May. And I think where we run in October or November. November, so stay tuned with that. So that's Mike. And then new in the team is Xesco. Are you here? Yes, Xesco is here. He will be working on QA, triaging bugs, be responsible for a bugzilla instance. Also, that's, as you see, is part of everyone's role to onboard new volunteers to work with the community, to optimize the workflows, to run QA meetings, of course, bug hunting sessions. We have been running regularly ahead of new major versions. That's stuff Xesco is working on. And of course, a Bible-secting and stress-testing LibreOffice Xesco has just started. And then, yeah, I'm trying to get all those bits and pieces together. And that's my role with TDF. Enjoy a lot of working with the team. We have, I think, a great team doing all sorts of things, very dedicated, very passionate about what they do. And that's what I appreciate a lot. Those are the people. And now a couple of things, just a random selection, what we have been doing in terms of projects, what's still running, what we have been achieving in the last months. So Italo has mentioned the advisory board has grown with four new members, which is great. The advisory board is the entity or the part of TDF for corporations to support, to exchange with the board, to fund, to get in touch with us. And that has grown, which is good. Sophie has been working on translating ledges. TDF is about transparency, and we try to give as much transparency as possible on the donations, on how we use the money. So we have actual ledges published and translated in the wiki. Then we have come up with a nice annual report, as Italo has shown this time, also in printed version. And you can download it, where we show what we have been doing in 2015, with lots of tags, lots of pics, statistics, covering all aspects of the project. Quite unknown yet is, if you want to have more merchandise, and you can get here at the conference, there's actually a merchandising store, where we have, I think, T-shirts, caps, covers for mobiles, and all sorts of things. And we constantly update and grow that. There is a store we can show you appreciation and support for LibreOffice, and can get some materials. If you have a nice project that you would like to run, and have ideas and have people to run it, and just need to funding, there's a grant request option, a couple of requests that we have funded in the past, certain trade shows, certain events to attend. Dashboard, that I'll talk about in a second, was part of a grant request and a couple of other things. So if you have an idea that is not yet in the budget, we have the options of working with grant requests, so TDAF can assist you with getting funds for projects you would like to carry out. In terms of budgets, Norbert mostly has been working on not only the infrastructure, but also the budget. This year we started to have a couple of buckets, like a community budget, a marketing budget, infrastructure budget to have an easier approval of expenses if that fits into one of those categories. And within the next weeks we will start ahead of time to do that for 2017. So local communities can make proposals what they would like to have funded, which events to attend, what materials to produce, so we can create the buckets accordingly and have hopefully rather streamlined refunding and payment process. Then of course, that's new since the last conference, in February a new Board of Directors started, is in place, has been elected by the community, and just today you will get an announcement if you're a TDAF member for the election of the membership committee. The candidates have been nominated and then the election will start tomorrow and run for a week, so you will get the credentials during the conference and please don't forget to vote. On that, the team has grown, we have five new names, I introduced just all of them to you, so TDAF itself is growing as well, and part that has been growing is the infrastructure, Michael mentioned it, lots of machines to do I think continuous integration and what sort of, I don't understand that kind of stuff actually. So lots of developer infrastructure has been set up to cope with the growing demands that we do have and what we have, a nice detail, we in the last days updated the statutes to have more proper English translations so you can read into the detail of TDAF. And from the marketing side, TDAF itself has a shiny new website since I think February, March, so we also have our business card and that in a nice decent design with a new block that features regular contributor interviews, the month of the LibreOffice contribution as mentioned and the newsletters that we do provide to our members. And then there is a couple of projects we don't run ourselves but we invest in and one thing is for the translators, for the localizers, the Poodle instance, there is an ongoing work where about 50, 60% have been carried out already to get new features, to get better performance, to get needed tools, I think like importing reasons for duplicates and whatnot to ease localizers' lives. That's something that we have been contracting the Poodle developers and of course will provide upstream for the wider Poodle community to participate. A dashboard is currently in the works and I was promised to get an updated link this week where we guard our statistics out of a Buxilla, out of Garrett and can extend by a couple of other services to see the activity, to illustrate the activity and to see who is contributing what, which will in the end also help our membership committee to do their work. Another item we fund is Askbot which is quite popular in user support I have learned and we invested a lot into getting multi-language support into getting localizations, a couple of features that we required because we have, as you can imagine, a rather heavy user base and lots of languages deployed. This is also funded upstream and then made available to the wider Askbot community. A couple of tenders are currently carried out that will make the Code of Libre Office better, provide new features, you see the list here and of course last but not least, the Document Liberation Project is quite prominent these days because the library behind it, the library DLP provides, is used by a couple of rather famous free software products which is amazing to see that the work that we do is shared with others which I think is a very integral part of open source and free software. So much to that and I see that there's a slide coming up by Klopp in detail on the new release that you're gonna do now. So Klopp, you join. I have to thank you. Thank you, you're all great. Thank you very much. Great to be here, thank you. And if I'm not mistaken, we're gonna do a live release right now, is that true? So you can be part of an actual release taking place. Okay, so we just by chance when we realized that we could release 5.2.1 at the conference, we decided to have kind of live release. So there is a big red button that I will not press because it's nothing happens automatically. So there's Klopp working there to make this live and then I will distribute the announcement on the usual channels. People will see them just after this. The opening session. I think all the non-developers should thank developers for keeping the pace of one release every month during the first few months of a major release of the major release cycle and keeping LibreOffice improving really on a monthly basis. Of course, 5.2.1 is not specific and breaking new feature is, as usual, what is correcting bugs and getting rid of regressions that were introduced, of course, not intentionally with 5.2. And I really invite all the non-developers to make an audible thanks to developers because that has been our main strength for the last six years and I think it will be our main strength for the next years to come. If LibreOffice has gained its role in the market, I think it is because we have a really exceptional group of developers, here there is, let's call them the core group, but there are many others outside during, it is just a curiosity, but in November, the number of developers that committed at least one commit for LibreOffice since September 28, 2010 reached the number of 1,000 and just by complete chance, 1,000 first developer was Jan Iversen. This is really, I mean, it's a total coincidence, but this is what was funny because it then started as being the mentoring new developers coming in, so let's call it as a sign of destiny that is the first one to exceed the 1,000 number, which is, by the way, a very significant number. We, it's now, we are over 60 months and probably even more of continuous attraction of new developers, which I think for a free software project is a real achievement because we have never had a single month without any new developer joining the project. Lowest month was December 2013 with three new developers, but we have always had more than three new developers per month since then, which I think is outstanding and therefore from my side and I think from all non-developers, a big applause to developers.