 Hi, today we want to present the status of the tender of a membership application tool and the reasons behind the tender. The basis was the MC has a well-defined process for application for new members or the applications of members and the tooling was set up quickly in the early days of the foundation and kept persistent because nothing is as durable as a provisory so but it reached a point where we honestly thought about a new solution and so we designed a new application, a web application specification for the tender made a tender and by now today half an hour ago I got an email from developer that we can show something here just in time and we want to say some also some sentences on what this changes for you and if there is time enough we will talk also about tendering a little bit but that's not that important. So let's start with the process used by the MC as you can see here now. The whole thing starts with an email for members which are about to expire. Yeah if you're already a member. If you are already a member. If not you have to go to some web page and fill out a form and in the end we get an email. And yes in the end your answer on the reminder email or you go to that web page this is the actual web page but in both cases at the end we end up the MC ends up with an email and could you please describe your specialist for the script? Yeah we have basically the tooling is a set of fresh scripts with text files which get modified by the script in Git and the voting happens in Gerrit. So we have basically the problem that not everybody is able to handle the best script. The setup is not that easy. The first problem is you have to copy to paste and copy the emails into text form. No. To integrate it in the Git. You have to make this text batches out from the email. This isn't automatic. No. In Gerrit you, so everybody get an email. Mostly somebody is sending the patch to Gerrit. We're frozen. Okay. Yeah. We saved us a picture. So we have that Gerrit patch and then we can vote and so that nobody, not that everybody has to search what the person had written in that mail or in the form somebody has to put the content in the Gerrit patch and most likely we try to search for more information if it's not a well-known person for everybody or if you're a member of the body that's quite easy. Yes. Or if you simply post a link if you're developer to Gerrit. Hey, this is my change set and it's really easy for us. So we have only to put the link in the Gerrit and everybody can verify that this person did something useful. Some people tend to answer on this reminder. Yes, I want to refresh my membership. Yeah. And that's all. And so research from our side starts if he has made some contributions and if he can accept it. Or for example, yeah, I translated as every year the application and okay, what was the user name of that user and let us look up some old contributions. No, the old Gerrit from the last year may hopefully be posted the link there. Yeah. Yeah. So this is a lot of manual work at last. And so after this is done, we decide to accept or to deny it those applications and then the applicant gets a mail of the result. This is the process by now. And to get this process, this is the tooling described Git and Gerrit and bash scripts, which just preferably work in linux. Yep. Not on Microsoft. At least out of a box. And you said not any, not every member. I only knew two members, maybe three able to handle it. Yeah. Maybe even four. But it needs time to what was it. I did it ages ago, for example. So this was the starting point. And so we started to develop an idea. We have to say in the beginning of a document foundation, most members of a membership community were developers. So they know how to handle and set up the base scripts, how to clone Gerrit, and how to use that. And mostly every dev is at least in our community, a linux dev, linux user. So that was not a problem at that time. Nowadays we have was quite normal for them to use those tools. We have marketing guys, we have only translation of event organizers. And now we have a problem that only a few are able to handle this script. And that plus it's really much manual work. Even if you can have these, it's a lot of manual work. See, just at the moment, we got a lot of mails back, which I rejected from our mail server because of some, I don't know why. Bad configuration. Bad configuration. Not of the mail server, but of the scripts. We have to change the scripts again and again. No, it's just a configuration. Oh, okay. Yeah, but doesn't help. They come back. Yeah. Okay. So this is one, one thing is to make handling easier. The other thing is some years after the GDPR, we have some concerns with that because if you use a git repository, you distribute all those personal data all over the world. And this is not what we wanted to do anymore. So we love to have basically are not allowed in certain ways. You have to do a lot of paperwork to make it possible. Let's say this way. And so we prefer a centralized solution with this clear access rules. And also it is, you know, kid is made, made and constructed to never lose something. And not really useful for this question. This is really hard to delete outdated records out of, out of a git record. So I will not say it is impossible. There are ways to do so. But it is really complicated. And you, you lose your comments in the carrot. And this is also basically for our work to have those scary commands related to those kids entries. So we designed a web application was a small database on it in its back. And so we wrote a tender on this. We had a tender process and decided to have a community member, Marco, to develop, to make the development. And yeah, it's the next one. We can have a look at it. What Marco just wrote. Oh, I just, I just go, I just leave the presentation and make a live demo. So this is, this will be the new application web page. The design might be updated. The design might be updated. This is the page you get if you are not a member. Where does it know if you are a member or not? It's quite easy. It will be behind the single sign on of the TDF. We had a long discussion in the beginning of this process. I didn't like it to have it like this because it is, it is a restriction of access to, to, to apply. But basically you need for everything nowadays. Yeah. So if you, if you're really contributed to Libre office, it will be really hard to avoid it to have a single sign on because nearly every resource of the TDF you want to use is, is, is protected by this single sign on. So it's most probably you have one. So it isn't, it, it isn't that hard to sign on with this single sign on account. And it has a lot of advantages. One of the advantages, it's, it protects us from spam on this page, of course. The second advantage is this, this page normally will be pre-fueled with your data. You see an empty page. I said, this is a new application. Okay, there is nothing to pre-fuel because you are not a member now. So some, some, some one we want to, to have here Torsten. Wrong. Marco wrote that would work. Okay, we should change this. Contacts Italo. Okay, Italo. So we make, we will change this design. This is, this is far too big here. And you have, you have also a comment field. What we have. What's new? This is new one. We want to know if you're full age, just because there are some GDPR rules, especially for minus. So if you're not a full age, your name will not be shown on the list of the members in the, on the web page in public. And the other aspect is if you're not full age, following the legislation of your country, you are not able to run for to be a member of one of the bodies of the TDF. Because if you get into the board of directors, there are some legal liabilities, which you are not able to fulfill. If you're not full age, at least you would have a written permission by your parents and all those stuff we want to avoid. In this case, it's much easier for us. We don't have to ask again. Yeah. So we ask it here. So we can now can submit this. That's all. And next time, next time this person comes on this page, his name and his age and everything, even, even his, even his contact persons will be pre-filled. And so it's really easy to, much easier than, yeah, to reapply. So what's about how we are in time? Some do we have some time? Oh, yes, we have. So I have a second, I have a second one from whoops, this will be the piece of work we're working with. So this is, this is just the back end for the members to accept or deny the applications. So we need all. Yeah. So we see here Torsten, which I just just added by the application form. And we see here his pending and it's not voted down. So this is the start of the process. And now each member of the of the membership committee who works with this can now do a vote. And this, this would be here. Most emails will be automated and we don't have to do the manual stuff. Yeah, you'll see, you'll see this is the details of the, of the application of Torsten, which is, which is surely, surely able to get it more compact on the page. And you see, we have also a second button, which was just missing on the web page. If we ask, we will ask you if you're more than 13 years old, but we will only ask this if you say you're not full age. So we didn't see that. We want to know if people or let's say, otherwise around the TDF won't accept members, which are below 13 years of age, because this has a lot of legal implications in Germany and we don't, we want to avoid them. And I think it's quite fair. You can't, you must also be 13 or older to get a Facebook account. So I think that's okay. So that's, that's for, for the first, this is just a mock-up as you could refer because the user interface is the last thing which was, which is built, the functions, the functions are before that. And so this is, this is the last one Marco will build. So, okay, I'll close that again and go back. Okay. We have seen the draft. So, so what for you and your concerns? If you don't have one, get a single sign-on account. You may get every information on this, on this wiki page. There is described how to get the account and what it's worth of and everything. But I think most, most of, most of us have one. So, so for the timeline, we hope we can start, start next year. That's the tool for the, for the first quarter of the next year, starting this March. Maybe we may use some functions of it. We haven't, we haven't talked about a dashboard. Maybe we may start that before, but we don't know exactly. So, just for the tender process, just, just for those who are interested, we, we had a tender, we had overall six, six enterprises or persons running for this tender. From all the world? From all of the world. One was from India, one from Indonesia, another one from Germany, this little of Italy, Marco comes from Italy, knows in Italy. And we had, we had a wide, wide scope. This little company wants about 50,000 euros to build this, this thing. This is, this is far too much. And we had, we had just, we hadn't seen that. And, and, but okay. So, at the end, Marco Marinelli won. And yeah, it's really, really good. And it was, it was especially pleasing me because he's also a community member. And we, we, some, some, we got some offers written down in DocX format. So, you may, you may, you may think about what these, these people follow. So, so it's a, it's for you. If you're not become a member. Exactly. If he's in this room, everybody's a member. Yeah. And if you don't know why the next board of directors gets elected in a few weeks. And so, so hurry up. Hurry up. You have still, still about one week for to, to apply to, to come into rather time to be part of these elections. Thank you. Okay. Thanks, Dennis. And we actually have a question from Marco himself. And he's saying, show us what happens on the application page if you choose no on is full age. Okay. We may try. You see, this is the 13 years and older. I didn't try that before, but I had enough confidence in our developers. Interesting question. Is there a country where 14 years is full age? Ah, okay. Yeah. But yeah, that seems to work. That was it? Or? Ah, yes, we don't have any, or actually, Marco just said, also try no there on over 13. There's a small test who says PDF cannot accept applications from persons younger than 13. And the, the commit button disappears. Okay. So this turned into a live testing session between the contract. Yeah, yeah. We just got the mail an hour ago or something like that. Yeah, half an hour, an hour ago, it was, it was just ready. Before that, we had just a screen mockup. So they did really, really hard work and quick work to, to get it working for the presentation. Thanks for that. Thanks, Marco. Yeah. All right, for Marco. So here input in the room. No. Okay. Any more questions? Questions are here. We are, we are in pictures. Picture, picture. I'm not seeing any more questions in the chat room. So yeah, thanks a lot. And we'll wait some minutes for Gabriele's video to play. Okay. Bye-bye.