 So, first of all, thank you everybody attending our session about localize. I'll give you the introduction. Thank you all for coming. A while ago, while Drupal Dev Day is again, we decided to launch a new initiative in order to localize Drupal.org to Drupal 9 and now Drupal 10. We'll see what is localize and what about this initiative. So, first of all, who are we? We are members of local community groups. We all have an interest in Drupal being translated. All kinds of people, translators, developers, UX designers, sometimes Drupal, for example, some first-time contributors. My name is Philippe. I live quite the opposite from here, Perpignan, which is very south of France, very north of Catalonia, depending on how you view it. I'm the maintainer of the French translation of the user guide. I help to translate in French on localize too, and that was how I got involved in this initiative first. I'm a languages enthusiast and also maintainer of some modules. Hello everybody. I am Nicolas. I'm the current treasurer of the Drupal French Association. I am also a maintainer of multiple projects, and I had the chance to obtain this awesome initiative at the very beginning. I'm glad being here to present it to you. I'm Thomas. I'm a French developer, mainly a friend of Nicolas. That's why I'm participating and also contributing to translation while ago. We had, as Philippe said, it was last year that the project began. It was at Drupal-David's Day Gant. Many people helped us migrating localize and hope, including that you will join us this week. Come on and join us. In the contribution room, we have our home on the table. We have a special salute for the others. About localize.drupal.org, it's still currently built in D7. It enables the community to translate Drupal code, but also contributed module. You can also share with others. That's the point. As I said, it's a translation server. It shares translation files, lots of translation. It's a collaborative tools, translation, languages, teams, and so on. That's the main dashboard, I will say, where all the languages are. If you have already contributed to use Drupal, the magic comes from there. That's the current interface of the tool, the one we hopefully want to bring to the newer version of Drupal. It all started, as Philippe said, in Gant in 2022. We had several meetups and events, Drupal events, where we talked about it. Our goal is mainly to bring people in the adventure. We really wanted to work with more people. There is much work yet to do. Here again, in Drupal.con.lil, our message is the same. Come and join us. We will pursue our communication efforts, but that's the message. Where are we today? That's the main question. Can we just check right now? First of all, everything is entity right now. We've got entities for releases, for projects. We've got entities for basically whatever concept that exists in the D7 version of localize. That's super cool, because it works. We've got the working UI. The D7 version, let's just show how it works. It's basically the same. You can have your source text and translation, and everything works perfectly fine. There are still little bugs here and there in the UI, but it works. That's fine. The word is alpha. Yeah, it's an alpha. As you can see, we already can grab every possible Drupal project. Here, it's Drupal.con. With any kind of version, with the alpha version of Drupal.con here, and you can download them and you can translate them, import, export, PO files, how you would do it on the current version. Obviously, there's still work going on. We have awesome people here working on the UX spot. We can show you some examples of things that should move in the future. We are trying to improve the UI a little bit. There is still much work here, because we are in between finishing the work with every features we need to port and obviously trying to improve things a little bit. It's an in-between work right now, but we are planning some real good improvements here. We had some great architecture choice. I think it's you, Thomas, who was supposed to talk about it here. Go on. Yeah, as I said, it's still in this version. Mainly, what we made is to port as... Sorry. Yeah, we more or less changed nothing on the way how it works on this seven, but we mainly focused on the adoption of D9 APIs when we began. Now, on T10, we use entities, modules that bring us... I will say newly powered of T10. We more or less now not rely on the database query as it was on this seven, because it was lots of custom queries that provided the result. And for some technical reason, it slows it a bit. So we are all reworking the thing using Drupal 10 APIs. And we also try to benefit of new technologies. For example, for the search, are we going to use Solar, for example, to have a proper result and be more accurate on the results showed to the end user. As I told, already said, the development began last year on a D9 version. Now we are using... I migrated the site on T10. More or less, it was quite smooth. The only problem, we had to change or to replace Sica, to replace the 4th to 5th, and it was pretty smooth too. So we have a fully functional D10 site at the moment. The only downside is that we created the core initiative on the community with the name... The title was D9 port, so we need to update that now for D10. Yes, my bad. Where are we standing right now? Here at Drupalcon. Up here in country rooms, we will be working. One of the issues is to migrate data from Drupal 7 to Drupal 10. Some part has been done by Stefan already. The specific Drupal part nodes, users, files, groups, is okay. But then we have some decision to make about the millions of strings we have, tens of millions of lines that are in the database, and maybe migrate is not the good tool here. So we've got to decide on a strategy here. We're working with the infra team, with Fernando Larez. So soon we will have a staging instance, so we will finally have a demo on local instances. What we need here is to switch Drupal 10. Okay, thanks, Thomas. Good documentation for CIS admins, and also migrations should be ready by then. So as I said, we have a really huge volume to process regarding L10N localized data, and also hundreds of gigabytes of .po files, which contain translation, which are downloaded from Drupal.org generated every time localized needs to process data, localization string data. So we work on this. Yes, I know my slides, do I? So as I said, you're welcome to work on this or on other issues, and really it's, well, I don't know how to deal with it, with these hundreds of gigabytes of .po files, even on a local instance, it's not so easy to deal with. Tomorrow, there's a buff on crediting system. This is your number. So it will be in room 21 during the afternoon, and we will be wondering how we can capture credits just as we do on Drupal.org, because we're trying to do it to count the number of translations done by everybody, but there's a catch because somebody, you've got to correct the string, and you've got, as a moderator, the credit instead of the contributor, and plus all credits are not captured on Drupal.org, but on other websites. So we need to discuss about it, and then how to implement it, because we're still in the first phase, in the porting phase, we've not reached the point where we can provide new improvements. We've got a roadmap, which is quite cool. It sounds easy, but it isn't, when you have to coordinate an initiative like this, and you don't have much time, unfortunately. So now when you come to Contrib Room, we can tell you the roadmap and tell us what looks good to use, what you'd like to work on. One of the main subjects I was talking about, and you were talking about earlier, is this part of the screen here, the onboarding thing. We've got a separate localized repository with a Kickstarter thing you can easily install on your local machine. I think it's public, you can just go on it and install the thing. Yes, it's on githlab.com. If you go to the roadmap, you've got other links to go there. Right, the thing here that is overlined with red thing here. We definitely want to onboard as many people as we can. The objective is install this, test it, and help us make it better. And you've got also a meta issue here. I don't remember the number exactly, but come to us and we'll give you it. It's our roadmap, there are plenty of things in there. So as I said, join us, come on. You can find us on Slack on the localized channel. We've got the roadmap just right here. Here's the number. And we've got our weekly meeting on Thursday every Thursday between noon and two for every people that have calls or whatever at their jobs. So join us. We don't bite, I promise. And hopefully we can make it go further. Can you just next? That's just another one. So thank you very much. We'll be around in the contribution room upstairs. Join us. Even if it's just to talk about translation in general, the issues you're meeting with the current localized instance or whatever. Well, feel free. And I put it in one of his fables. Language is the worst and best of things. So be on the bright side and help us make it, make localized a better platform. So if you have questions, do we have some time for it? Like team effort. So no question or perhaps issue you want to share or remarks. Okay. No. Well, hopefully, hopefully before Drupal.org in May. Hopefully. I can take, I won't promise anything for the team. As soon as possible. Yesterday is a bit, yeah. Okay. Thank you, everybody.