 Hello, everybody. I'm Jérôme Irbine from the Arawa Company. We are a French partner, a gold partner of NextLoud, and today I will now I will talk to you about making contribution to NextLoud and how to make it even greater based on one year of contribution. So I'm talking in the name of the company because we are several people, several employees that contribute to NextLoud. There are a lot of ways to contribute to NextLoud, but we are mainly contributing through two access Github for bug reporting and code source contribution and also translations, wordings through trans defects. So this is what we did within one year. On Github, we've created open 60 issues about its rounded value and we've got 50 successful poll requests in the source code of NextLoud and also we did more than 2,200 translations and more than 600 translations reviews, I mean translations made by other people. Before giving you some tips and good practices about contributing to NextLoud, I would like to give you some feelings that we have when we contribute to NextLoud. So we are very proud to contribute to a project which is used by tens of millions of people worldwide and also staff on NextLoud is very kind, so this you have to notice that and also there is a very active and kind community worldwide, so we love it too. And finally, developments of NextLoud are very wise, we think, and organized, so this is a very good point. Now let's talk about good practices to contribute to NextLoud through Github, I mean bug reporting, feature requests, poll requests, and I'm not talking about pure technical things, but about human qualities and methods. First contributors, I'm talking about any contributor, must have some human qualities, I mean that a human is always centered in the project, in open source projects and human aspect is very important, so every contributor has to be friendly and team-oriented spirit to work properly with other contributors and to make contribution successful as possible. Then also when you ask something on your or you propose a poll request, always ask yourself if what you want to do is targeting the common benefit. If it only targets your personal wishes, it may not be successful. This is an important question you must ask yourself before creating an issue or creating a poll request. Also be involved by giving a lot of details in each one of your contributions. So as you see with this meme here, when you create an issue and just tell, it doesn't work, don't hope that your issue will be taken in account. Finally, this is very important to follow up and close issues that don't make sense anymore. I mean, if your PR or your issue is targeting a very old major version of NextLoud, for example, NextLoud 18, just go in your issue, your PR, check if the problem still occurs. If yes, add a comment and try to follow up correctly your contribution. And if it doesn't, just close it and it will make things easier for other contributors when they are searching for an issue. This is easier to organize to search inside GitHub. So it's better for NextLoud and better for other people who contribute to NextLoud. So all this is very obvious, but you know, we are all humans and we can forget some of these crucial things about contributing. So we have to note it. Now I will give you some good practices and tips about contributing to NextLoud through TransEffects. So this is a translation platform used by NextLoud for every app of the project and, first, a very important thing. Bad translations can damage the UX, UI, and reputation of NextLoud, even because of a small app, a very small app. So we have to know and to note and remind that wordings are as important as source code, features, and design. When we contribute to translations, we have to be rigorous and impartial. Rigorous, I mean that if we don't know the context in which the wording is used, just don't translate and let other contributors do the job. This is very important because, instead, this will screw up the UI. Also, please check the grammar and spelling. Take the time to do proofreading for each translation you are making. This is crucial also. It seems obvious, but sometimes I see mistakes. It's not often, but take the time to re-read what you're doing in translations. Secondly, we have to be impartial. I mean, natural. We all have personal habits, personal glossary when we are talking. But we have to choose words and sentences, expressions that are used by the biggest part of people and also by the biggest part of apps and NextLoud workspace. So forget your personal habits. Consistency, it's a very important notion. When you have an action in a button or a notion, it must be expressed with the same words, the same sentence, throughout the entire app or throughout the entire NextLoud workspace. I mean, a dummy example. When you have a model that, and you have a closed button, if the tooltip is in one app, close the pop-up and in another app, close the model and in another place, hide the pop-up, it cannot be, it's not consistent and it's not, it's bizarre for users. Another example is in French, we have at least four ways to express email. And I've seen in French translations, these four ways to express email and this is not consistent. We have to choose the one which is most used in our language. So we always have to think about it when we're contributing to translations. And last but not least, priority. In Transifex, you have priorities in projects. So we have to translate first what is the most urgent because NextLoud needs it for the next release of an app or next major version of NextLoud, which will be released in a few days or weeks. So have a look at priority, this is important. So thank you for listening to me and if you have questions, don't hesitate.