 mae'r symun. My name is Simon that I'm from AQUIA. I'm here to introduce the Drupal 4 initiatives keynote but I want to say I'm really excited to be here. This is my tenth Drupal con and this is the first time they've let me on the big stage, so it's a really big occasion for me today. I've got exactly three minutes, clock is here and I thought what should I do and I thought I'll give away some shoes so with anybody like a pair of these fantastic trainers right so can everybody stand up we've got the lights on in the house everybody can stand up what we're gonna do is you're gonna find one special person in the audience to give away some Drupal con aquia Drupal converse trainers to so I thought fel gweud bod nhw'n credu gwirio'r cymdeithas gan ei wneud. Ac fe wnaethwn gwirio'n bod ni speudioau y flynyddiadau yna yn ei hoffywyr cymdeithas, a ddweud y dychydig o gwirio eich cymdeithas chi. Felly, os gallwch, mae i chi fod yn fwy y gwael cymdeithas yn gyrwy Covid, wnaeth gyd yn dda? Fydno eich gwael cymdeithas yn gyrw Covid. Ac fyddwn i chi'n gael y gallwn rhywbeth yn GT. Mae'n rhaid i'r fwyllt wedi bod ymdeithas y gwael dim nhw i'r gwybod for being like long standing members of the community. So thank you to everybody who's just sat down. Well done. Right, next question. Do you own a pair of Drupal or Acreosocks? If you do, can you sit down? I thought more people would sit down. Hang on, if I give you these, will you sit down? And what about you? There you go. Thank you very much. Right. Now then, have you been to a locally organised Drupal camp before? If you've been to a locally organised Drupal camp, sit down. I've got a long list of these. I wasn't sure how long it was going to take me to go through them all. Right. Have you made a contribution on Drupal.org? Some documentation, something to a module? If you have, sit down. We're getting through the crowds here. Do you own a Drupal mug? Don't worry, I'm not going to throw mugs at you. But if you own a Drupal mug, please sit down. Right. And do you have a profile? This should get a bunch of people. Have you got a profile on Drupal.org? Ah! We're doing really well. I can't really see over there. Can you wave your arms if you're still standing? Brilliant. Over there. That's worked really well. Great. So we're going to change the competition a little bit now. It's going to be a hands up or hands down competition. When I ask the question, it's either hands up for one answer or hands down for the other answer. This should kind of get us down to the last few people, hopefully. What are the currently supported versions of Drupal? Is it hands up for Drupal 7 and 8, hands down for 7 and 9? Hands up or down? What do you reckon? What do you reckon? 7 and 8, hands up, hands down for 7 and 9. Have you all decided? Good. Right. If you were hands up, it's time to sit down, I'm afraid. Ah! The currently supported versions of Drupal are 7 and 9. How many people have we got? One, two, three, four, five, six, seven people, eight people left. Right. This is a question that comes up all the time in this community. Is Dries Belgian or is he from the Netherlands? So, hands up if you think he's from the Netherlands, hands down if you think he's from Belgium. Have you all decided? Everybody round these people, I need you to witness this so we don't get any changes of mind. So, what do they say? Hands up for the Netherlands, hands down for Belgium. Right. If you've got your hands up, it's time to sit down, I'm afraid. How many people have we got left? One, two, three, four, five, six people, right. We've got two and a half minutes because of the extra time. So, I'm going to keep going through it. Lucky I had a long list of questions, isn't it? When was Drupal first released? When did Dries start using it for his first project? Was it January the 15th in 2001? Or January the 16th, 2001? Right. If you think it was January the 15th, put your hands in the air. If you think it was January the 16th, hands down. Everyone decided? We've got a high bunch of people who've got this. Right, his hands in the air, January the 15th was the day that Dries says that he started using Drupal. Right. What else have I got on my list here that I can ask you? When will Drupal 10 be released? I mean, this isn't a promise by me. This is a current projection. So, will it be released hands up for December of this year or hands down for January of next year? How many people have we got? One, two, three, hands up for December, hands down for January. It is December, so one, two, three people left. Is that all we've got left? Three people? Four people? Right, I've got 50 seconds left. Right, I'm going to ask one more question and then we're going to go for like closest to a number to find the last person. So, when was Drupal last in Prague? Was it in 2012 or 2013? Hands up for 2012, hands down for 2013. So, the answer is 2013. So, if your hands down, how many people have we got left down? Can you just shout out? One, two, three. Okay, I'm going to ask you all a question. You've got to shout out a number one by one. We'll start over here. How many members are in the Drupal community? Whoever gets closest, this is how many people have registered to the Drupal community in the last, how many years is it? You're in charge, you must know. In the last long time since the Drupal, 21 years, in the last 21 years, how many people have signed up to be a member of the Drupal community? Can you shout out a number? Ten? I think you can sit down now. A thousand. Right, who's next? Is there somebody over here? A million. Who's over here? Is anyone left over here, one person? A million and one. That is some sneaky guessing. The exact answer, the actual answer is 1.39 million. Can you tell me your name, please? I can't hear you, let me run over. That was a long way to run for Lee. If you come and find me on the Acre stand later today, I'll give you a pair of these smart trainers. If everybody else can welcome the newest member to the Drupal community, Lee. With that, I'm going to hand over to Gabor, who's going to run the core initiatives keynote. The initiative leads the keynote. We have this keynote here because we think it's really important for you to meet the people that lead these initiatives. I think it gives a lot of insights into how they build their teams, what they are struggling with, how they organize their work, the happenstance of open source, how you can be involved, what kind of skills open source initiatives need. There's a lot of different aspects that you can learn here. Also, you can meet them in person. You can see that they are very friendly people. Then you have the chance to meet them all throughout the conference. Anybody can be a part of these initiatives that we are talking about here. They are the leads that are making it happen. That's why we have this session. For here, if you have a question for this session, there's going to be hand mics distributed throughout the venue. If you install the mobile app or if you are an online participant to the conference, you're not here, then you need to use this online tool. If you have the mobile app, then you go into the program area. There, you pick the keynote and there's a live Q&A tab there. You can submit your questions there. People can vote on the questions and then we'll use them as part of the Q&A at the end. This also gives a chance for our online participants to participate in the Q&A. You can either submit your questions there or use the mics at the end. With that, I would like to welcome all of our initiative keynote speakers on stage. First up is Ted Bowman, then Alex Spott, then Marine Gandhi, Daniel Drum, Leslie Glenn and Larry Escola. I would like to invite Lenny Moskalic, who's going to lead the Q&A as well. This is a strange keynote because I will sit there as well. I usually don't speak at these keynotes, but unfortunately, Bjorn Brawla couldn't make it to this keynote, so I'm stepping in for him. But first, let's hear from Larry Escola about CK Editor 5. I'll talk about the differences between CK Editor 4 and CK Editor 5. CK Editor 4 has served as well for the last nine years. As always, software comes to its end of life at some point and so does CK Editor 4. So, let's take a look at how the current experience is with CK Editor 4. I'm dragging an image to the editor and if you look at the source, it was uploaded as a data URI. That's not ideal. So basically with CK Editor 4, to upload an image, you'll have to enter the image upload dialogue. Realigning the image or adding a caption also happens to the dialogue. This is kind of distracting my editorial workflow. So here comes CK Editor 5. We can do things better with it. So CK Editor 5 is a full rewrite of CK Editor. It comes with a better UX, accessibility, and a vastly improved developer experience. So let's take a look at how all of this looks like with CK Editor 5. I'm dragging an image to the editor. So instead of a data URI, the image was now uploaded to Drupal. So that's better. I can also enter an alt text using the CK Editor balloon instead of a dialogue. Adding a caption also happens by just clicking a button. So this is great. So how do I get to use CK Editor 5? All you have to do is enable the CK Editor 5 module which ships with Drupal 9.3, 9.4, 9.5. And then you have to go to your text format and switch from CK Editor 4 to CK Editor 5. And our automatic upgrade path takes care of the rest. Please review the changes manually because it's not a one-to-one conversion. The goals for the CK Editor 5 project has been to ensure that there's zero data loss. So what that means is that with any configuration of CK Editor 4 and any kind of content that is stored in the database, when content is being resaved with CK Editor 5, there should be no data loss. Basically your content should still remain the database as a result of that. The second goal has been to make the upgrade path as smooth as possible. So as you saw earlier, it is as smooth as just switching the editor on the text format. This is true also for contributed modules that support the CK Editor 5 and provide an upgrade path. Our third goal has been to rebuild all of our integrations to match the CK Editor 5 built in UX. So for example, we've had to rebuild our media integration to match the experience that we saw earlier on the image upload. So media can be realigned and caption can be added without never having to enter a dialogue. So Wim Beers gave an update earlier this year in one of these initiative-lead updates at Drupal Dev Days. Back then we had plenty of upstream blockers, missing functionality and critical box remaining. So now six months later and 150 completed issues later, CK Editor 5 is finally stable in Drupal 9.5.0. So who's behind this? Here's all the contributors who have helped us get where we are right now. So let's give a round of applause for everyone who's contributed. None of this would have been possible without the help of CK Source, who is the company behind CK Editor. They've put an enormous amount of effort into making sure that Drupal can upgrade to CK Editor 5 and CK Editor 5 is fully compatible with everything that Drupal needs. Give another round of applause for them as well. We could use some help with testing the CK Editor 4 to CK Editor 5 upgrade path. We've prepared some documentation that provides instructions for how to test the upgrade path on your site and how to report any problems that you run into whilst you're upgrading to CK Editor 5. Now is a good time for contributed modules to start updating. We've started making very good progress on updating CK Editor 4 modules to CK Editor 5, but there's still a lot of work that needs to happen. So if you're a contributed module maintainer that depends on CK Editor, now is the time to do the update because our CK Editor 5 module is stable, so the APIs are not going to change anymore. We're going to run CK Editor Office Hours tomorrow at 3pm at the D8 1x Internet Room where we can provide help if that would help you to port your module to be compatible with CK Editor 5. We're going to have some folks from the CK source there and I'm going to be there. So let's make this happen. Thank you. Thank you, Laurie. I would also highlight Victor's session later today about CK Editor 5, what to look forward to. I think it provides a really good insight into what else CK Editor 5 provides and all of the advanced functionality that is made possible by the new version. So that's a good option to go as well. So next up is Leslie Glyn and she will talk to us about the Project Browser initiative. Hi, I'm Leslie Glyn, one of the Project Browser initiative leads. After introducing you to the Project Browser initiative, I hope to show how everybody in this room can contribute to helping us move this initiative forward. I have the slides at Bitly, PBIL 22, which is Project Browser initiative leads 22. There's a lot of links in the slideshow there for demo purposes only though. So what is the Project Browser strategic initiative? The initiative was first introduced by Dries at Drupalcon North America in 2021. The goal was to make it easy for site builders to find and install modules. In Portland earlier this year, Dries emphasized the goal, want to be able to make it easy to browse and install modules. So what are we probably trying to solve? Creating a Drupal site is easy then what? One of the first things people want to do is to add functionality to the website. It's like walking into a grocery store. There's a million modules, a million serial boxes. How do you begin your search? The Project Browser is currently a contrib module. We released a beta version of the module in July, thanks to all the contributors that helped with that. If you click on the try and now button on the Project Browser project page, you can spin up Drupal site using Gitpod. Gitpod will create a fully functional Drupaline site with the Project Browser installed. What you need is a GitLab or GitHub account, or you can just sign in to use Gitpod. Once a site appears in the top right corner of the screen, just expand it and your website will open up in a full window. Once you get there, you'll get a URL that you can share across the internet with others so they can use your fully functional site as well to test things out. Log in with admin-admin, and then click on the, there's a new link under extend to browse modules, and that's how you get to the Project Browser window. The Project Browser today. The default filters we've come up with are modules that are compatible with the version of the site that you're running Drupalon. They have security coverage and that are maintained. The default sort is the most popular modules. So you'll see, when you search, you'll see categories, you'll see a card or a list view of the modules. So we have a lot of contribution opportunities this week. The first two are later today. We have two birds of a feather sessions on usability testing. So come, check it out, try it out, give us feedback, what works, what doesn't work, what we can improve on. That would be super helpful, easy for anyone including those who are brand new to Drupalon. The content is critical to the success of the Project Browser. We're going to go browse for modules, but the first things you see are the most critical. So the first things we're working on is adding a logo, adding a project summary, which is just a short, non-tactical description and updating the categories. There are meta tickets that we created for the most popular top 100 modules that are created that you can work on, very simple. We're going to review the three child issues there. We're going to create the logo, the short description in the categories, and then we'll get these over to the maintenance to actually look at what we suggest and put those into the modules. So the first thing is to propose or review a logo. We feel that logos are helpful, so we need designers. If you're a designer out there, spend 15 minutes creating a logo for us. Really easy contributions, so please help us out with that or review logos that others have done. The next thing is to propose a short, non-tactical description, something that someone, our target audience is those nudigrupal and site builders. Give us a nice description that would be helpful for them when they're searching for modules. Limit 200 characters, so start with that. The thing after that is the categories. Right now there's, I think, 55 categories. So think about what the top three categories are that people would want to find this module using that search and help us suggest what those top three should be. We have a combine board for the top 100 modules. This makes it easy for you to just go to this link, find things to work on 15 minutes in your day. Help us create a logo or a short description or some categories. So there's a needs work, which are the issues, the modules that need help. Needs review. Come in and just review something that others people have done. Anybody can do this. We're looking for site builders and new people to help with their too. I talked about the categories. They're going to be a key for finding modules. There are currently 55 of them in our interviews with our target audience. It's completely overwhelming. So help us delete some of those categories, add new ones, combine some of those. The same with the project detail pages on Drupal.org. None of those are the same. They're not consistent. It's very difficult for our target audiences to know what to find where on the project pages. So, you know, what content is most important for people when they decide what modules to use. So we're working on possibly a template for the project pages to help with that. Because that's what's going to be displayed on the cards of the project browser. More contribution opportunities Wednesday and Thursday, both at 15 o'clock. First we're doing the project pages. I'm sorry. First day we'll talk about the categories. Just come discuss that with us. How can you help out? Chris will be in the general contribution room. And I'll be in the mental contribution room all week. So how can you join after today? Join project browser on Drupal Slack. We have a site builder subcommittee meeting on Tuesdays. We have a general meeting on Wednesdays. Both of those are in Slack. And check out the issue queue. Two other initiatives you're going to hear about today. One of them is the automatic updates with Ted Bowman and the distributions and recipes with Alex Pott. Those both have a lot to do and really help the project browser out. So, you know, come to anything this week about those two things as well. And tomorrow, right after the keynote, Chris and I are having a more detailed presentation on the project browser. Where we're at, what have we accomplished, what do we hope to accomplish. We hope to see you there. Thank you to all the contributors who have a ton of contributors. I couldn't create a slide we've had so many like you did. So thank you all. Thank you. So I really like the project browser initiative because it makes all of the work that you do all on Drupal.org much more visible for Drupal users. It brings all of this functionality that's available in Drupal, but many people don't know about them available to them. So I think it's really powerful for the future. And with that, I would like to introduce the next speaker, which is myself. So you haven't had me in a fun stage yet. So I'm stepping in from Björn Brala because I thought this is a really important topic that we should talk about. And it's this project update bot. And actually what I would like to talk about is more the open source case study behind the project update bot, how we almost accidentally worked together with multiple companies to make this happen. That's very critical now for the community. But first, why do we need the project update bot in the first place? Is that because with Drupal 8 onwards, we've introduced this system where we have new APIs and deprecated APIs in a major version. And then the next major version, we remove the deprecated APIs and keep the new ones. And we need to support the community to go through this process to adopt these new APIs and remove the use of the deprecated APIs. And we wanted to automate as much of that as possible. And we do this by detecting what needs to be changed, by fixing these changes in this bot and then posting the changes in the issue queues for people to review them. So these are three areas where we needed to have tools. And as I've said, kind of accidentally, we now have all of these tools in place. So what it ends up with is a patch in the issue queue. So this is the JSON API extras, which is one of Björn's modules. It posts a patch in the issue queue. And then it needs humans to come in and review the patch and the CI systems to run and make sure that the tests pass. And when the humans review them and commit them, make releases, then it's available for the whole community. But it all started back in 2019 with Matt Glamonet-Sentaro, who was working on code quality checking tools with Centaro Toolbox. And he kind of accidentally stumbled on the possibility of using PHP 10 for deprecation checking. And they got roped into writing Drupal check as a deprecation checking tool for the community. So that's where all the checking things started. And then Zoltan and myself in Hungary decided that we need a user interface on top of this to make this easier to use. So we built upgrade status on top of this, which is project-aware and rush-integrated. And it has a bunch of additional checks on top of what's in PHP 10 Drupal. And also has environment checking. So this can be used to check the readiness of your whole site, not only a specific code basis. But at the same time, Dwayne at Pantheon decided, totally independently of us, that we should look at the country projects. And he wrote a shell script that was checking 1,600 country projects readiness for Drupal 9. And then he posted big spreadsheets of data that we started looking at and analyzing. And so we had an idea of where country readiness is for Drupal 9. And then Ryan at the Drupal Association decided, oh, this looks nice. What if we automate this under the infrastructure? So he wrote a script that runs every week for the past three years now, and runs this same process. And now we have data of 9,000 country projects every week and their readiness for the next major version. So this is all built on top of each other. And this data was used by Dris in the Dris node in 2019 October to present the readiness of the Drupal ecosystem to Drupal 9. So that he could show, like, this is how far we are. And he also called for automation of these fixes. So that's where the idea of the project update came from. But before that, I looked at this and I decided that, by the way, it would be much better to have this data that was in the Dris node available for anyone. So I built the deprecation status dashboard that takes the data from project analysis from the DA and displays it in a much better digestible form. And so it's available for you to dive in and see project status and it helps us prioritize work on things. A half a year before that, Dazio at Pronovix was already experimenting with Drupal 8 Rector. It was not ready for prime time yet, but he was experimenting with, what about this code quality fixing and deprecation fixing tool? It could be useful for the community. And it was useful. It was already around when Dries said that we need this fixing, but it was not ready so offer. And then at Pellentier decided that we should fix this up and add a bunch more checks to it. We started with Drupal Rector based on Drupal 8 Rector and added a bunch of checks. And then Pellentier continued to fund Matt Glyman on wards to add even more checks to this tool so they have a complete check system. And this allowed Ted Bowman at Aquia to put this all together and write the project update by itself in collaboration with the Drupal association so that now this checks the readiness of projects and also runs these fixes and posts them in the issue queue. So that was ready for Drupal 9 and it was fine for Drupal 9, but it was not yet ready for Drupal 10 and then the time came for Drupal 10 and we need somebody to step in and that's where Bjorn showed up and one of the Drupal 10 meetings then said, by the way I can help with porting this to Drupal 10. So he's from the Netherlands, he was working with porting this to Drupal 10 and to Drupal CI as well so to have it run as a general tool. And that's where we are now. So this runs, upgrades status first and checks if there's anything to fix. Then fixes it with Drupal Rector then runs upgrade status again if there was anything left to fix. If there was nothing left to fix it also fixes the info file on the composer file and posts the patch. If there was stuff to fix then it posts the halfway patch that's already helpful for people. And this is the accidental collaboration of all of these companies that sort of came together showing up because they had an interest in solving these problems. Sometimes because they built something for themselves sometimes because they've seen the call for help on these different areas that we are. And there's more opportunities to get involved in this because now we need to make this work with GitLab merge requests because patches are not going to be there for long anymore. So we need somebody to stand up and work on making this compatible with GitLab so that it can post GitLab merge requests and update GitLab merge requests automatically instead of posting patches. Then the next step would be to integrate the writing of rector rules and PHP standard checks somehow inside the core development process so it's not an afterthought that two people on the side do but more integrated in the whole process so that would be really nice to figure out, there's still in discussion and then finally it would be really important to make this happen earlier so it's not a big bang update at the end when a new major version comes out but more like a regular cadence where the country projects can be updated for the next major version as time goes on this requires some changes to the rector rules as well to have backwards compatible code in them too so that's an exciting challenge as well for somebody in the audience but in the meantime if you have a Drupal.org project it's very likely that the bot is there with the patch in your queue so look at your queue and check the bot patch verify it, see if it works and thanks to all of the contributors I mentioned all of the companies that funded their work to make the project update bot happen so that's how Happen stands of various companies' interests in open source contribution makes a critical tool for the community happen so as a reminder if you have the app of the conference then you can go in the program find the session find the live Q&A tab there and submit your questions there this is not live so there may be questions so go there and submit your questions and also vote on the existing questions or wait for the mic at the end of the session but we have a bunch of more speakers with interesting content and next up is Neil Drum from the Drupal Association so I've been working on the GitLab acceleration initiative with the Drupal Association and the main goal there is to improve contributor tools on Drupal.org so it's not just GitLab we have a couple other tools in there as well so, yeah, I'm Neil Drum I work on the engineering team at the Drupal Association so we're the ones to keep Drupal.org running including all the sub-sites DrupalCI of course git.drupalco.org and more stuff behind the scenes so with git.drupalco.org we decided to install GitLab to improve the developer tools on Drupal.org because we're a small team and we started out not using all the capabilities to GitLab and we only use more of that because there's more that GitLab provides on top of just the repositories that we're using so it's a lot of parts of this project are kind of attacking in parallel despite only being a couple people and a lot of this also helps create Drupal.org which is unfortunately still running on Drupal 7 so account creation this is the part that's not GitLab it's basically we want to improve the whole contributor experience make it easier to get an account easier to log in we have a kind of bespoke single sign-on system called Bakery that we're not going to want to use in Drupal 9 or 10 it will look a little different pretty soon in the next couple weeks you'll see the email address that you edit on your Drupal.org profile move to git.drupalcode.org and don't be worried if the login page looks slightly different in a few weeks couple months once we get that launched projects and releases, those aren't changing too much those are staying on Drupal.org there's a lot of integration with packaging that Drupal Core expects and the composer integration at packages.drupal.org has some stuff that we can't build on top of GitLab and getting ready for the upgrade to Drupal 9 we want to simplify Drupal.org kind of get rid of some of the stuff that we shouldn't upgrade so notifications GitLab's better at its own notifications of course SSH keys GPG keys, those are all managed on GitLab project pages will have a little bit of simplification most of that's done already so you may remember last year there was account net commits that's just pictures of the maintainers now and now that's because we were maintaining a database of all the commits that was just that was the most of the maintenance on the old systems so anywhere where there's commit counts it's being simplified and we're going to lean more on GitLab to do statistics and everything and link over to you your get.drupal.org profile for more the main thing that's in progress right now is GitLab CI a few projects have opted into that and it's going to since it's a more generic tool more powerful tool it's going to require work from all the project maintainers on drupal.org to switch over there's going to be a GitLab CI email file that we want to template out and get as much of the heavy lifting done as possible but every maintainer will likely have to commit a GitLab CI email file to leverage that template and we're overall trying to make the transition easy and we have to transition everything we're going to shut down drupal CI when this is done both core and contrib current drupal, legacy drupal 7 all the steps that you expect from drupal CI and we want those to run smoothly out of the box and that's all because GitLab CI it doesn't know what a patch file is so projects will switch project by project when they switch over their testing and once a project is switched to GitLab CI then that maintainer is also saying they don't accept patch files anymore everything will be a merge request and what we're trying to do is make sure we preserve the collaborative nature of drupal.org I think there's many more people working on any given issue in drupal than other communities five people per core issue and we want to also preserve the issue credit system so right now our plan is to rebuild it on drupal unless GitLab gets some tools for that so we want to preserve that as much as possible because it's helped to motivate a lot of people and companies to contribute and before we do the migration there's all these references entity references to issues throughout drupal.org which is going to stop working when it's on a separate piece of software so all these red and green issues everywhere on chain directors everything those will change and then the actual migration so we've gotten a head start on some of the scripts for that so we have a proof of concept and eventually once the projects are on GitLab CI then they can move to issues project by project so that's everything we've been working on a lot of stuff in parallel so we're going to see more changes in the next few months as we get through that backlog and start launching single sign-on and finishing up the last bit system of planning drupal.org and GitLab CI issues so we'll have a general drupal.org update session tomorrow there's a meta issue to follow on drupal.org join us on drupal Slack and look for ways to use GitLab more use the merge requests if you want to help with the templates for GitLab CI help get that working for everyone thank you Neil I'm one of the beta testers of the GitLab CI initiative and it's been a great experience with how things move forward so next up is Marine Gandhi and she's going to introduce us to a whole new initiative introducing for the first time ever in Drupalcon Prague a new initiative in a world where Drupal 10 is on the verge of release a major tool in our ecosystem is still running on Drupal 7 and it's localized at drupal.org this undercover website operates in the dark to provide localized strings to all our agents in the world and so a small group of people has decided to take matters into their own hands and to modernize it and they call themselves the localized initiative coming soon very soon as in today soon so it all began in Belgium in April this year and I remember it well because I was there and I saw it all a group of French speakers decided to follow around Gabor and Drum and just ask them endless questions about code they made 15 years ago and we were pretty much like puppies around them like help us out and so that's when we decided to make it an initiative so I'm not actually the initiative lead I'm just a place holding here for Philipp and he will talk to you more in detail in a session later today and you can ask him any question you want and you can find us with our nice t-shirts and logos so what is localized because you may not be familiar with this website at all so you can call it L10N because we like to make it simple but basically it's a translation server this is where the translation team from all the countries go and collaborate and translate the English from the Drupal core and modules to their own languages and we need to thread carefully because it's used very much and you download strings so it's a simple Drupal so to do that we have a plan and this is our roadmap so first we really need to just take the Drupal 7 code and make it work with Drupal 9 so check if we can use any other tools instead of staying on Drupal migrate the data port the modules all that stuff and then if we do all that it's done, right? well, wrong after that we have of course to a refactor and probably we will change some elements with more modern approach like maybe use the REST API but we don't know yet of course we need to focus on performance because this is heavily used and maybe make the code consistent because there are lots of us working on the same code base then of course we want to make it ready for you so that you will want to use it the front-end team is basic but it's working but I think we can do better so that will be our next focus also we have feedback from the teams that the UX might be quite tricky so if we can make this better then of course we will then of course make it reliable because it's a Drupal.org website and we need to be sure that what we push will not break everything so we will test test and test some more then finally, we will get to take it live and make it available to everybody and working with our infra team and how we can deploy this with the least amount of downtime is yet to be defined so this is one of our big challenges and then of course when everything is done we can always improve so we will make it better by introducing new features because once we are on Drupal 9 then obviously it's much easier to add up to that and you can actually help us do that by filling out a feedback form that we created so it's very easy you just scan our QR codes you will find them on our country room and in the next community events table you can grab them and if you've ever used the website before please come and feel that it will help us in the long run you can also join our initiative for a number of other subjects like if you like coding of course PHP and front-end developers are always very welcome but you can also be interested in data migration, that's a big part of our problem here and there's actually even more to do because we are very interested in documentation like how do you use this website that you may not even know about so every help is welcome organization, you know how it is we're a team, we're all in a different country so we need help the funny slides though it's already covered, sorry but obviously the more the merrier if you don't know this website at all yet please go and check it out now because while we're working it's still open obviously it's still working, get familiar with it just get a grip of how it's working because then we will need your feedback in the long run and your translation teams locally will really be happy with it current status then we're still in step one obviously we have a working Drupal 9 instance we decided to stay on Drupal because it made sense for us we can see projects and their release and the frontend theme is working properly, thank you for that but then we have still a lot of things to do, we have to get user groups working, that's very important because there are different roles not everybody can just translate any string, that would be a problem and then we have a number of bugs and of course the infamous data migration so if you want to know more please come today to our full 20 minutes session with other members of the initiative and then we will have birds of a feather tomorrow in room D2 and you can find us anytime with these T-shirts in the room C3 we have a spot for you thank you very much thank you, I think this is really great example of a random group of people that showed up and they said that we want to make this community initiative happen without anybody telling them that they would need to do that, so thank you a lot of people will be grateful for the results and will be happy to be involved in the future as well so next up is Alex Bott and he will talk about the distributions and recipes initiative hello everyone I'm here today to talk to you about distribution and recipes initiative I'm going to tell you about our goals what we've been doing what we're going to do and our future plans but distributions are not new back in 2006 Dries wrote on his blog distributions I hope it all works out so we're still here, we're still talking about distributions and he wrote that because the space had been really successful at introducing Drupal to the World and he was envisaging a world where people would be able to start their Drupal doing all sorts of fantastic things but 11 years later he wrote we've improved the underlying technology for building distributions and we will continue to do so for years to come but unfortunately some distributions haven't managed to stay the course because it's tricky to maintain distributions so we've created this initiative to improve that so our first goal is to improve distribution discovery when you start to install Drupal you have three options you have standard, minimal and demo umami that's not all that's there there's commerce kickstart, there's open social there's viabase, there's fantastic ways of starting but you don't see them you wouldn't know that they existed but also once you've made your choice if you start with standard you can't then later on have another distribution so we want you to be able to have more than one benefit from more than one of the work from the distribution so if you want a great blogging platform you can also have a great commerce platform by using the commerce kickstart distribution and as I was saying this should happen at any time in the project cycle not just when you meet the installer and go okay I'm going to use thunder or open social it doesn't work, your needs change as your site develops you might want to start selling things you want to use commerce kickstart you cannot use commerce kickstart because your site is already a blogging site we also want to make it easier to update we've had too many distributions do really great contributions that haven't managed to get to the next version of Drupal and last but not least we also want to enable distributions to ship demo content it's really important that when you install the distribution to see how it works we suffer from that when you install standard you just get to an empty page which might welcome you to Drupal but you don't know what's the next steps demo will prove the value of having default content there you install the demo you see some great recipes you're like oh that's how Drupal can work so what are we going to build we're going to build a new thing not distributions, we're going to build Drupal recipes it's yet another YAML file and what it really is is a list of steps you can achieve the same thing by clicking through the user interface but it's much quicker if a machine can do it for you so what recipes what will they be able to do they're going to be able to install modules as you'd expect, install themes they're going to be able to create an update configuration they're going to be able to create content and they will be able to also apply other recipes but what won't they be able to do so recipes won't be able to have their own code there's nothing dynamic they're not going to be another module another way of providing the same functionality again and this is really important because if recipes describe just what the site can do then we don't have to worry so much about how do we update complex APIs and stuff recipes are a description of your site they're not functionality themselves so what have we built so far we've written a lot of documentation because some of these concepts are quite technical that how we want recipes to not be changeable how we want them to be descriptive of your site but we've also already got a patch that can install modules create an update configuration and apply other recipes what are we currently working on we're looking at converting standard and Demu Amami into recipes so that we can learn from that experience so that we can share that way of building recipes with the other distributions like open social and commerce kits so they can use the same base recipes and we're also starting to work out how to do default content once we've done that, we're going to have a UI and core for applying recipes we're going to try and host recipes on Drupal.org and obviously we want to have certain recipes selectable from the installer and to do that we're hoping to leverage the project browser that Leslie was talking about earlier and once we've got all of that done, obviously we're going to eat some cake and then we're going to build some testing harnesses on Drupal.org so that recipes will be tested without you having to work out which versions of modules and Drupal core that they apply to we also want a Kli and a GUI tool in order to help people build and contribute recipes back to the community where are we doing all of this there is our own project the distribution underscore recipes project and this project contains instructions of how to apply the patch to your project and all of our documentation who is doing all of this work well, at the moment a lot of it is just me but there is also the Drupal association MixerLogic is helping improve Drupal.org for the way that it manages distributions already there is people like Fabian Bircher who is helping me work on the config side of things I've got distribution maintainers who have got a lot of experience in building these distributions saying hey have you thought about this but I would really like you to come and join us because we need more people so come to my talk tomorrow at 5.15 in the room C1 at Acria to learn more come to the Friday contribution sprint there will be a table there with recipes on it and join us in Slack hash distributions and recipes we have a bi-weekly meeting every Tuesday every other Tuesday thank you just imagine the possibility of project browser with recipes where you can get all of these projects pre-configured with demo content and would make it much easier to explore all the functionality that's being hidden in those 9000 modules on Drupal.org so I'm really excited for what all of this would bring and to top this all off Ted Bowman is going to talk about automatically updating all of these things and how the community made the automatic updates system even better hi, thanks, I'm Ted Bowman Ted Bowman Drupal.org I'm a software engineer at Acria and the tech lead for the auto updates initiative and I'm going to go through our progress since Portland and that Portland and also how we're helping out the project browser initiative so in Portland we did beta testing because we had a beta module at that point and we had about 30 plus beta testers there and more later we had 15 bugs and features that were fixed there and it was really useful to get people's eyes on the module who weren't the people who were seeing it day to day and missed the small things especially so there was a lot of UX improvements so for example Adam P found that during the update process the site goes into maintenance mode and then we take you out into maintenance mode but at the end of the process we were still telling you you were in maintenance mode so we had just missed that so he found that and we fixed that another example is Shiraz Dindar found that on our experimental module automatic updates extensions which let you update themes and modules you couldn't actually check for the updates you couldn't refresh so if you knew a security update had just come out you couldn't check manually and see the update so we added that Michela Herman found that on the available updates page with the update module provides we still had download links to tar files and of course that's not going to work with our new composer based system so we got rid of those and now drumroll there is links to our form on the available updates page and we removed the links for any of the particular releases that you wouldn't see on our form and we left the release notes which then will tell you how to install it by a composer on Drupal.org and Sarah Corbyn found that in our beta test and instructions we had particular instructions for if the module couldn't automatically find composer this is how you can set it in settings.php but we didn't actually have those same instructions in the in module help so we were able to transfer that to have it so basically you don't have to just be a beta tester and Lisa found out that in certain situations the update would time out and when it's applying and that's the most dangerous time to have a time out because you could have a half updated site so we've fixed that so that process can take as long as it needs to apply the update to your site T. Franz found that in certain situations composer was not running with the same PHP interpreter as Drupal itself so we have a more flexible way to actually find the composer executable and finally our caller found that we had messages about backing up your database and code before you started an update just in case something goes wrong but he was able to help us really improve the documentation the links to documentation and the in module text to really warn you like you should really do a backup and that was a really great help so that and a lot of other work has led us to a stable version of the contrib module it can update Drupal core we have an experimental module to update themes and modules so please try it out more at 8.x2.1 now and this is available today and also while we're here we're going to do more testing right after this in D2 if you come by we're really looking for testers that can test on remote hosting we want to test this as much as possible as we go towards core so yeah there's instructions if you come we'll sort of like walk you through the process and then there's a report form and get contribution credit for trying it out tell us what went well if it didn't go well you'll probably find some improvements that we missed like the people in Portland did so yeah afterwards we have two sessions back to back because sometimes it makes take longer but it's in the schedule it would be great to see you there so with the project browser team we've been working to let them take advantage of our composer operation functionality we have the automatic updates module we ship with a module called package manager which then calls PHP library made called composer stager and the project browser will also use package manager and composer stager to install modules in a composer native way so that's in progress work right now and so we're moving a lot of the validation that used to be only an automatic updates down to project browser down to package manager so anybody can take advantage of it for example a lot of sites are going to have modules that aren't installed by a composer even though that's the recommended way so we're doing a lot of validation to make sure that any new modules you install or any dependencies that are updated do not conflict with something that's not managed by composer so we tell you oh sorry you need to figure out this in a more composer friendly way first the other thing that we're working on is the update module in Drupal core wasn't really meant to check on security information for modules that aren't currently in your code base but of course with project browser installing new modules we need security information we need to validate that security information with the update XML from Drupal.org so now any module that you install or update can be validated and make sure it's secure supported and published on Drupal.org so all of that and other validation we're moving down to package manager so that project browser or any other module that wants to do through the UI composer operations can take advantage of it probably recipes will be doing some composer operations and so they'll get that validation and as we continue to add more validation so package manager if you're a module developer this is ready to be worked on to be extended you can help contribute anything you contribute to sort of the package manager ecosystem will benefit automatic updates project browser and hopefully more software modules find us on Friday at the contribution day tomorrow I have a sort of developer oriented session about package manager so please come by thanks thank you Todd so imagine the combination of all of these with your contributions that may show up in a future Drupal con with your friendly face on a slide that would make Drupal so much more powerful so looking forward to involving you in these things right after this session both the project browser and the automatic updates teams are doing their 2 hour user testing sessions in the buff rooms so look for them there and pick your topic and with this I would like to hand this over to Lenny who's going to lead our Q&A thank you Gaba so that's like you had your share of fun guys with talking so now it's for the audience to have their share we have questions of course that were posted online but of course we would like to hear from you guys who are present over here so go on raise your hands and let's get it started okay so you are warming up so we can start down with the questions that we received online so the first one is that's got the most the biggest number of the woods is how would the project browser initiative work with composer managed projects so we have the sub module package manager that now is being is basically package with auto updates just because we needed one place to have the sort of stack that we were working on in core depending on if automatic updates were to get into core first before project browser then project browser would just use that module there it does actually do it does do actual composer calls it's not like a it's nothing sort of it is special but it's not unique a different way of doing it it stages any composer operation in a separate directory and then so we can check certain things about it make sure it's secure make sure it didn't update things we weren't expecting so then it transfers everything back over and that last step is not really composer aware but it's just basically you have your active site that had the composer operation done on done on it and then it transfers over so your code's updated your composer JSON, your composer lock files are all updated in the process yeah so just for those of you who aren't quite as technical in the audience project browser will not only allow you to go out and find modules right from within your website but also to install them for you so you're not going to have to go out to a terminal and figure out composer and all that stuff so that's a huge win and Ted's team is working on that thank you the next question in that case is from Alexander and he's wondering if we are getting read of patches yes, yeah GitLab the big goals to move to issues on GitLab and that means merge requests for the code changes and yeah that will require GitLab CI and none of this knows what patches are it's all going to be merge requests are you migrating the existing patches to merge requests that's more of a stretch goal probably not we're going to migrate all of the files that have been attached all the screenshots, patches, everything but getting a patch into a merge request I would say it would probably work 20-50% of the time if you trusted the computer to do it but you would have the patch available as an attachment all right thank you any questions from the auditory all right, everyone is using applications so we are very happy about that okay, the next one then what is the timeline to upgrade Drupal org to Drupal 9 slash 10 slash 11 that's a good one yeah, that's a good question yeah it's hard to predict since we're such a small team and stuff like I don't know if everyone noticed but especially for the European time zones GitLab was git.drupalco.org was pretty slow the last month or so so stuff like that takes days or weeks of our timeline to fix the production infrastructure that one we took a little extra time because we wanted to get our configuration management updated so we can roll out new servers maybe a server local to Europe so it's even faster work quickly so yes we provide a honest timeline since we're such a small team and things take time Mariniw want to answer it as well yeah, even if it's only a part of Drupal.org we don't have a timeline for localize either because yeah, we're more yeah, we're more than your infrared team actually but we're still doing that on our free time and there's so much to do that it's hard to get in sync sometimes so yeah it's about volunteers showing up to do that would help a lot importing a lot of things so most of the sites are very well contained like if you want to work on api.drupal.org or localize.drupal.org then you can work on them then localize has its own team now to make this happen right, thank you next question then receipts what are the solutions for default content being considered for example, default content module so we have an open issue to discuss that we are considering anything I mean, in demo umarmi uses a CSV file and uploads from there some of the distributions use default content the default content module personally I like that one because it means that the entities are all stored in YAML which would make the same as the recipe YAML and the config YAMLs there's a consistency there but we haven't made that decision yet so yeah, there's an issue please come and contribute thank you for your answer the next question is what happened to commit count on drupal profiles the commit count of drupal sorry what happened to commit count on drupal profiles and module pages yeah, yeah, yeah they took it away the moment I had more commits than Dries so the main effort we put into maintaining the old get infrastructure which was pretty amenable it was maintaining a database in drupal of all the commits so basically a mirror of all the get metadata in drupal database with entities and everything and since GitLab's extra work to do all of this migration and integration that's what had to fall off all of that syncing and everything and GitLab can count commits itself and knows how to count those a bit better than us right, thanks the following question is related to the automatic date and Christopher is wondering does automatic dates work for the multi-site systems so right now we don't support multi-sites because two people can't update at the same time and there's a lot of things that we restrict during the apply process so basically the very last point where you're applying your site is sort of restricted you can't uninstall modules because it's really dangerous to have your code being updated at the same time you're doing actions on your site so if we allowed multi-site right now we basically would have to have some locking system outside of drupal itself to tell all the sites that okay you can't do these particular operations so as an MVP in the contrib module we decided not to support it if people are we actually haven't got many requests or any requests in the issue queue to support it but if people are interested in the problem please come on Friday or post an issue it's a very tricky very tricky problem one thought I had was to say okay maybe in sites.php you would specify this site can perform these operations but the rest of them won't but you still have to solve the problem of okay if one site can do an update all these other ones have to be made aware that the update is happening so they can't do certain things while the update is applying so it's a tricky problem but if people are interested in solving it we could use help all right that's a wonderful answer and the next one is where it's there boards so does the board detect deprecations on the dependency modules? no so it can only install a module if it can install of the dependencies in the environment in Drupal 9 currently so it's checking the deprecations within the module itself but if it depends on APIs in other modules the php10Drupal would go through of the APS of the APS of the APS so it would go through of the APIs that it depends on and detect the deprecations for those but for any code that's not being used from the dependent module in the module being checked it would not find those deprecations thank you Gaba now let's jump to the GitLab so who will pay for the CI runners and is that a large cost point for the Drupal cessation so overall the costs will be approximately the same you know there will be some superficial changes like they will run via Kubernetes instead of spinning up in the EC2 instance but overall the same amount of compute costs the same amount no matter how you tell AWS to run it the the we do have to be careful about Drupal CI has some kind of rails in the UI so you can only select one configuration like one version of PHP one version of MySQL for the default testing for issues and GitLab CI there's no affordances like that you can make a matrix of all 100 combinations PHP, MySQL, the other databases all the other things so if everyone does that, that will cost more we likely will need to put a number of minutes limit for each project getting some help with some contractors to make that possible in GitLab so there will be kind of a base amount of minutes we think is enough for most projects if there's a project that is doing good things almost gently needs more minutes we'll give out more Drupal core, we'll need a few more minutes for testing but we're keeping an eye on cost because Drupal CI it's $3,000 or $4,000 a month for that compute which is generously paid for by our supporting partners so thank you for your answer Neil now the next one is for the localisation initiative finally will we be able to run this localisation server ourselves this could be really useful in enterprise environments what's initiative localisation can you repeat I don't hear you very well so will there be the possibility to run the localisation server ourselves for the yeah I guess if you want I mean the code is all open source it's just find the modules starting with L10N and you will find all the country modules that make it work so obviously you can take it and try it yourself sure right that's good to know I guess the next one is regarding GitLab CI so will you provide the default GitLab CI configuration for small modules that only need simple link checks CI for small modules yeah the default will probably yeah will have to find like the right balance of yeah have it work out of the box for a small module basic configuration and then the GitLab CI my understanding of it is just layers of the apple so you can layer on more complexity as you need it okay there is one more question for your name so is there a risk that removed commit counts on the desensitized cross collaboration a risk of yeah so is there a risk for removing commit counts on Drupalorg so it will desensitize cross collaboration so the commit counts have been gone for at least a couple months now five months and yeah it's hard to say how that affects the community because really the main driver it's the project itself it's Drupal 10 is coming up there's a lot more you have the rector bot posting patches like that's what drives the development cycle so the product it shouldn't worry about counting things but I think that's where this question is coming from it's not about the count itself it's about making people more so do we have any metrics that would help us we could look into it more but as far as actual development it's the Drupal core really cycle that drives things and also commit counts those are only counted code contributions we also want to keep the issue credits and that counts more than code contribution and we want to make sure we're looking at all of the effort that goes into the project not just code okay thank you so I will check once again if there is anyone who would like to ask a question directly here okay then we keep working with the online questions so the next one is it makes sense to migrate the issue related data to GitLab we make Drupal org a brochure site and separate the code contribution and modules themes on GitLab so it's about comparison like if it makes sense to use GitLab or Git Hub so once again it makes sense to migrate the issue related data to GitLab we make Drupal org a brochure site and separate the code contribution modules themes on GitLab so yeah there's a lot more on Drupal.org than just the just the issues and so there's also the change records that Drupal core mostly uses to help inform people about updates the issue credit system that and organizations and the organization's marketplace and yeah there's a lot to it and really we can do some splitting up of the site API and localize being separate sites I think has been good but especially with the marketplace we want to be able to entity reference to all of these sites and any kind of negligible benefit we have from simplifying the site we would have to replace with all sorts of data syncing to do the marketplace ranking and sometimes more sites is more work OK great thank you so the next one is related to the project browser again so can I tell you if the core modules will do what you need when it was starting out I was constantly searching for modules for tasks when what I needed was in core so perhaps it's related once again to the problem of the description that you were mentioning so you were asking about core modules yes yes so can basically will be project browser able to tell the developer the contributors if core module will do what they actually need to be done yeah so when you're searching for the modules by default you're going to get contrib modules we also have implemented something called sources which is hidden behind an advanced filter where you'll be able to bring in other sources of data including the core modules maybe you're at Stanford and you have your own set of modules so you'll be able to use your set of modules or aqueous or whoever's sets of modules so those like advanced filters but the logic in terms of what to bring in I think relates back to Ted's update initiative where it decides what libraries whatever you need to bring in so that's a little more complicated than just where the person searching for the modules is searching but the default is the search contrib and then you can go out and search other places as well thank you so the following question is related to CK Editor 5 so will CK Editor 5 have a help wizard for new users to see new features and how to switch to new version easily so we have some documentation on Drupal.org about the upgrade process itself I don't think we have documentation on Drupal.org about the new features of CK Editor 5 itself there's documentation about that on CK Editor 5 documentation and we have two sessions at the Drupalcon about that as well where we have both CK Editor 5 folks talking about this from their perspective and then I will be presenting on Thursday from sort of Drupal's perspective a little bit more the upgrade path so we have some documentation maybe not necessarily exactly what has been asked there but sort of along those lines alright and I think we can continue a little bit with CK Editor 5 as a follow-up question there is will the CK Editor 5 integration pave the way for real-time collaborative editing multiple editors at the same time so CK Editor 5 one of the reasons why CK Editor decided to rewrite CK Editor was to enable real-time collaboration features in CK Editor I know that the CK Source is working on a premium version of the CK Editor module that provides those features I believe that they will be mentioning and providing more information about that in their session they also have a booth here where I'm more than certain that they would be happy to provide more information about those things the reason why those services are provided as a premium service is because it requires a third-party component so Drupal itself can't provide it as a piece that is required for the conflict of resolution but yeah I think it is sort of paving a way towards that kind of future where Drupal could be used for real-time collaboration so we have time for one more question and yeah there is is there any update on the decoupled menu initiative is there any update on the decoupled menu initiative so I think it's really close to being at a decor there's been progress on that there's been some changes in the people who are working on that because people have changed jobs they've had changes in their lives because of COVID and other reasons so because of that it has taken a little bit longer than we anticipated but yeah it is moving forward and I think it's going to be done sometime soon all right and that's why we are out of time so I will take a moment to thank everyone of the speakers as well thank you everyone who posted your questions and for being involved in this conversation thank you so it's the freedom to create new capabilities without starting over to roll out multiple campaigns in any language to build and pivot and build again giving you cross channel continuity across the entire customer journey putting monolithic solutions behind you and getting out in front of customer demand that's the power of Acria DXP