 So, good morning and welcome. So, I'm Joachim, a member of the GDF Port Correctives, and everything I say here is not an official message from the GDF Port Correctives. I was hoping, having like the 930 slot, that no one would be here, but then we had this thing with a bus, so everyone is here apparently. So, sorry for the trollage title. If you were expecting means and stuff, there is no means at the stop. There's one tweet, but that's not it. And I want to talk a bit about maybe, well, maybe also, you can see this as an introduction on how the board works. There was a question in the opening session on why doesn't GDF or Neoprographers do this and that. And answering these questions and maybe why some things are not that easy is what I'm aiming for. So, this is the title and if you really closely, you probably come up with questions, lots of questions. Questions like this. I mean, what's an open source project? What's the leadership? Who is the leader of this and what's HR? And I want to go into these a bit to just give you a hint on what I'm actually aiming for here. So, when I talk about an open source project, I mean, a real open source project, not some open core thingy that what a huge company has, and then some binary with code falls out in the end, but something that is actually produced by multiple vendors that has a strong community and that tries to bring all these people together to work on something together. So, this is what I talk about, what I mean, open source. And volunteer contributions, we will get back to this because volunteers, I mean, volunteers are people who are not in the board usually. So, looking at the next slide, what is leadership? This is the definition you find in Wikipedia right now, if it wasn't and vandalized when I look at it. And there are some things in there to lead and guide other individuals, teams or organizations. The question and the thing where we get into interesting areas is if you have volunteers who do whatever they want on the one hand and leadership and guiding people on the other hand. This is where things get interesting and this whole sentence ends with a common task. So, what is a common task for LibreOffice? Fixing box. So, what are the goals of LibreOffice? What did we start with? There was the next decade manifesto. I think it's okay if I am. So, there was? No, it's fine. So, there was the next decade manifesto. There was a post with the creation of LibreOffice and even before the government foundation was created. And it was the mission statement for TTF for LibreOffice for the next 10 years, 9 years ago. So, the shelf life of the next decade manifesto is almost over. And this. This? No batteries, I try that one. Okay. So, it's time to maybe look back at what the goals in the next decade manifesto are and what the next decade manifesto would look like. That's maybe something we should do at this conference and come up with an idea for foster and so on. I think some things will stay the same. And mostly the stuff about the project because project goals are pretty much forever. The way we want to work together, the way we are seeing the relations in the community should stay the same. But maybe the product that we are creating changed and the goals for projects changed over the last 10 years. And we might need to update the goals to the changing situation. So, this is just as an idea of what the common task is. And I haven't put up the next decade manifesto yet. Does anyone actually, so I have a show of hands. Who knows what is the next decade manifesto? One, two, three. Sorry, maybe you can have a look at it again. And because we might need to really investigate what we actually do there. So, how do you do this leadership towards goal? There's this thing called project management. And if you look at the first sentence, it says it's a practice of initiating, planning, executing, controlling and closing the work. Initiating, planning, also goal. Executing, wait a minute, we were talking about the quality as well. So, which volunteer wants to be executed? Or controlled? Or get the work closed? This is not something you easily get volunteers to convince you. And you shouldn't because they're volunteers. And once you hardly get them to give you quality to these things, they're not really volunteers anymore. I mean, you can do this on a tip or tap base, but in general, this is a hard thing to do with the volunteer community. So, I already said that volunteers are strong base in the LibreOffice project, but there are other things that contribute to LibreOffice as a project. There are volunteers, there are commercially sponsored contributions. There is the TEF team and their TEF members. And we put some hints at how you can improve the contributions for each of these things for volunteers as you can very directly, what volunteers want to do, because we want to have everyone who shows up at the opportunity. And that's the thing that he wants to do, is to leave the office down and leave a wreck. But in general, we want everyone to be able to join and contribute. The same for commercial sponsored contributions. And you saw in the opening slides maybe that, if I remember correctly, that three commercial sponsored contributions are in half of the commits that are doing LibreOffice. So, this is also an important source of contributions. And then there is the TEF team and the TEF members. So, how does this all work? Most of the communities are self-organized. So, the marketing, translation, documentation, any of the support, for example, ask for communities, QA, UX, development. And some of these have like forums and get organized and share their work. For example, the QA has regular details. And the most visible of these is for development, the Engineering Student Committee. And if you look at all these, what these sub-communities do in LibreOffice, the development is special in that way that pretty much all work that other teams do needs some work in development, too, or to show up on the project. So, yeah, you can do translation, but if there is no change in development, there is little to translate and so on and so on. So, you can back reporting to reality, but if nobody faces the box, nothing will show up on the program. So, the Engineering Student Committee, this is why it's one of the... It's informal, but it's still one of the most formal things that we have in these sub-communities to organize themselves. So, how does the ESC work? Simon posted this, but he didn't say this. But this is essentially how the ESC works. If you go on the ESC, the assumption is that you do something and then you can also ask for things. And with that, we can move the project forward and share workloads. So, the idea of the ESC theory is it's a real bizarre where you go, but there's no things like, or really things like, we need to do this and you do that and you do that and you do that. Because everyone is on the ESC, it's on the ESC, pretty much, if they work for a company, they are sponsored to be there, but they are not sponsored to work for the ESC. So, yeah, this is pretty much what I just summarized. But I think the last point is really, it's already a conclusion of that, because if the people who are in volunteer community or on the ESC were together, if they are doing what you want them to do, then your only way to maybe get that, if you are able to do that yourself, is to ensure that there's growth in the community and that there are more people and that you can motivate some of the bigger community to share your goals. So, your way to prove this is to just motivate towards your goals and to prove community in general, but there's little way to match or force someone in the direction on the ESC. It's always a given take. So, the first line is pretty much the guideline for every interaction in the LibreOffice community and it's actually a century old, although the second formulation is, well, you can see that it's a century old, but the upper one is sections of what we can use in the LibreOffice community. Thanks. Okay. So, that was the community part, which is not the TDF part. For TDF, we have this wonderful thing. I hope you all know this roughly, which was in the annual report about how it's important that you are a TDF member because you can vote and then we can vote for the TDF board and the TDF membership committee does the whole election thing. We also have an advisory board that advises the board and the board spends pretty much half a million to a million that we have each year. And decides where to spend it. But then they are supposed to not do the work themselves. Sometimes you end up doing the work yourself, but in general it is the administrative and the decision making that is done in the board and not the actual work itself, which is, for example, in the DSC and so on. So, you're not getting much tit for tat value being a director when you're on the DSC. So, which brings me to the whole AGL thing that we had in the title. AGL was a new thing 20 years ago, almost 20 years ago. Before that software development was done like bridge building. So you started, you made a plan, then you started building one thing and the next thing and one thing and the next thing and at some point you reached the other end of the river. The problem was when you do that in software you do one thing, the next thing and then the river is at a completely different place because everything changes in between. So the idea was to, if you had the old way to do a plan in big corporations, it was very slow and you go all the planning at the beginning and then all the implementation and all the testing at the end and not like an iterative process. So AGL was supposed to change that and do a little bit of planning, a little bit of execution, a little bit of testing and so on to close into the title and adapt to changing environments. Of course, the way open source software was developed in the most cowboy coding way was the most AGL in the most flexible way. So if this is water source and this is AGL early open source software developed in some way here with no process at all and totally flexible and totally more AGL than AGL but sometimes you actually want to communicate with people who are not the developers like the users and other community members and stuff. But the waterfall model is a breakdown of project activities into a linear sequence of sequential phases and each one goes through the phases of conception, initialization, analysis, design, construction, testing, development and maintenance and then we have TDF tenders which are conception and initialization is done at TDF analysis and design is done at a contractor then testing is done at TDF and development and maintenance is done at TDF. So our tenders are pretty much done in a way as software development in big corporations was done more than 20 years ago which is painful for everyone involved. So the HR manifesto then said well we want to have processes and tools but we want to have individuals and interactions to be more important than that and we want to have comprehensive documentation but working software is more important than that and we want to have contract negotiation and nobody wants that but we have to have contract negotiation and we want to have customer collaboration to be more important than that and we want to have a plan but responding to change is more important than that So that was the original HR manifesto and then there was a lot of relation coming out of that but in general the idea was to not do everything in a nailed down way which was reacting to change. Yeah, I'm just giving this slide. Looking back at what we have at LibreOffice and the Document Foundation there are the areas where we can do project management and the areas where we as TDF or LibreOffice cannot really do that. The areas which are not really having project management are volunteer contributions because you can't really tell someone you will do this over the next half year with some volunteers you can do that but in general it's really hard to do a plan especially doing something sequential like first you do this and then you can build on top of that So the way to get out of that is not to do planning and project management but to grow the community and have more people working on the stuff that we are doing. The same is for the contributions which have their own project and project management and we have to ensure that we are just open to people contributing to the project. On the other hand in TDF team and TDF tenders we can do some of this project management but this is a very small part of the whole thing. So one thing we could talk about and I talked with Florian about this for doing some of the HR technologies or the HR methodologies in TDF this is just to allow more visibility of the stuff that is being done by TDF without compromising on the important things like individual detections and stuff like that. But we will not manage our volunteers because you cannot manage volunteers and if you really try to execute control and close your connections with volunteers they might just run away. So we have to be kind and inviting and get more people involved and motivate those that are joining us and this is the way to go forward with the community part of the leader office. So basically this is the slip there some areas where you can actually do project management but most areas, the most important areas for the leader office of TDF they have not so much product management but really getting a community that works together and growing this community. OK. Well handled given the technical difficulties.