 Good afternoon everyone. I was told to get started right on time, so I'm going to get that underway My name is Chris I'm here to talk to you about the project browser strategic initiative where we're at and how you can help so we've been making a lot of wonderful progress over the last couple of years and We'll share where we're at and how you can help Also, this QR code goes right to the slides, which is the same as that link That's kind of in the middle bit.ly slash PB Pittsburgh 23 So if you want to follow along in the slides you can go ahead and scan the code or pull up that link and There's a bunch of links also in there. Yes, sir. Oh because it's not the You do it because otherwise the whole presentation Do you like getting with the link in view or something? No in the actual Google Docs sharing settings So we'll get that underway ASAP. Thank you for that heads up. So what is the project browser initiative? Dries talked about a little bit this morning in his Dries note And as we'll see he talked about it a couple years ago in his Dries note as well So at Drupalcon North America in 2021 he talked about the project browser His vision for it his goal for it was to make it easy for site builders to find and install modules And then in 2022 he clarified that a little bit further He says people want to be able to discover great modules From within Drupal without having to go to Drupal.org and then install those modules with the click of a button So who are these people? He's talked at length about the idea of sort of ambitious site builders and who they are and what they do But to us we're really looking at getting back to some of the Drupal roots of low code no code making it easy to expand your platform without having to be Super technical without having to know a ton of the Composer Incantations that you need to do so it's important that we remember that our target audience here are those site builders And those new to Drupal so one thing that can happen from time to time when we present at camps and conferences is we end up speaking to a lot of Really wonderful, but really technical people So I just want you to remember who we are targeting here with this project and what we're trying to go for as we look ahead So what do we have for a project browser now? Website Drupal.org you can go to build and modules and you can use the search criteria here And you can find the modules that you might want to use Or a lot of people also do these searches just on Google and Sort of bypass the Drupal.org search interface and end up finding modules that way so these filters are Maybe a little overwhelming to some of these this target audience I'm new to Drupal, so I don't necessarily know what stability or the security advisory coverage means Or you know I'm a site builder and I just really am focused on what does it do? Right and in these results we have a little bit of also inconsistency around How these descriptions are laid out it's kind of up to the module maintainers to decide what's important some of those descriptions end up being Highly technical and not necessarily written for our target audience So where we have landed today is we do have a module in the contrib space called project browser at this point It's fairly useful We are on a beta 4 version and what we're working towards is getting an MVP If you're not familiar with that language from Agile, it's the Minimum viable product. So what is the absolute minimum that would make project browser useful and functional to our target audience? And so we're working towards that MVP. We're currently on beta 4 And you can try it now by clicking the try it now button So what have we accomplished thus far? We have a De-coupled architecture around the project browser So the front end of the project browser is actually written in Svelte the JavaScript framework of Svelte And we have a pluggable source system So that is to say when you go and you get the list of modules that you want to display To your users and install them You're actually making a request to your Drupal site from your browser from the front end In that decoupled way and then it's going and fetching data from somewhere else in order to figure out what data to display That's implemented as a plug-in, which means you can extend project browser by writing your own source back-end And we actually have Example code for how to write your own source plug-in and back-end. There's an example module to do it It's really only two methods. I think that you really need to worry about So that's very easy to do and as long as you're giving data back in the right structure will present those modules to you So this makes it really cool really easy for you to say If you're an institution of higher education, you know a university or something and you only have you know a hundred modules That are approved you could write your own source plug-in and Give access to your users to add and install only those modules, which you've approved kind of neat We also have a faceted search with sensible defaults So thinking about that ambitious site builder that someone new to Drupal We want to give you sensible defaults of the kind of modules that we Recommend that you install for example only ones that have security advisory coverage only ones that have a stable release as A power user you can go in and you can clear those filters and you can get more modules presented to you If you kind of know what you're doing, but we want to give you sensible defaults And then you can drill through and filter by category, which we'll talk a little bit more about at length We also have accomplished actual click to install so you can if you have enabled all of the right Dependencies for example, if you were at the automatic updates talk this morning They may have talked about package manager from automatic updates package manager is the sort of sub module that we rely on that Is the glue between your Drupal site and Composer so if you have package manager enabled and you meet some of the other requirements that can allow it to be turned on then You can actually hit add and install Watch it go it runs the composer commands in the background for you gives you a little spinner and Enables the module for you at the end of the day so that if you want to turn on the admin toolbar You can turn on the admin toolbar with the UI We also have kind of an alpha stage Drupal API endpoint So something that we've been using in order to build this system without having a real endpoint on Drupal.org To date is we created a mock fixture. So we used to It's a bunch of mumbo jumbo for a giant JSON file that contains all of the data from Drupal.org about You know what projects what usage what compatibility they have and we've been actually Taking point-in-time snapshots of Drupal's data and loading that in with project browser and Using that to sort of mock up what the API would look like But we actually do have an alpha stage Drupal API real JSON API endpoint that Fran from the Association has been working very hard on over the last few months So we're very close to actually being able to deprecate that sort of snapshot mock back-end and use a real live back-end of Drupal data and we have tests I would be remiss if I didn't point out that we have a lot of really good automated tests written For the software that we've written so far. So on the back-end side, that's a lot of what we've accomplished We didn't introduce Leslie, but Leslie Glenn is my co-initiative lead here and also my co-worker at Redfinn and I'll turn it over to her with some other stuff that we've accomplished Thank You Chris. I'm gonna take this off because I'm very soft-spoken. Can everybody hear me out in the back there? Okay, perfect. Thank you All right, so some of the things we've accomplished we have a site builder subcommittee more of looking at our target audience site Builders those new to Drupal making sure that what we're building is going to be useful to those audiences and to everybody That's going to be using it so some of the things we've been doing is we Started the process of creating logos for all the different modules So in order for it to show up in the project browser It'd be nice to have a nice logo for the for the module. So we've been working on those And I'm going to talk about each one of these in more detail in a minute We've been creating short Non-technical descriptions of the projects and that is so that when people go to the cards and they say his you know I'm going to look at project browser and it returns these different modules You can get a quick glimpse in a non-technical way of what that module will do for you okay The next thing we've done is we've worked hard on trying to reorganize the categories and I'll talk again about that But there's 55 categories right now if you go to Drupal organ That's it's just a way to filter for different types of modules and we'll talk about that But we've been working hard to try and cut that number down Because 55 is overwhelming when you're trying to go look for a module. You have no idea which category to even look at so we're trying to make that set of Categories much smaller so that it's more of helpful of a filter for people who are looking for modules And then we're working on the project detail page as Chris said in Drupal org It's very technical very long. They're not consistent. Chris will talk about that in a little more detail So these are some of the things we've been working on All right, so how do you get involved? Everybody in this room can have a role in project browser You could all contribute in your own way. So let's talk about some of the ways you can help us with this initiative All right, so the first thing you can do Very straightforward. You can go to the project browser contribute module page and just Check it out. Try project browser out. Give us feedback. What works. What doesn't work? What do you understand? What is too technical? So that's one thing you can do so on the project browser page this highlighted down there in the bottom It says try it now Basically you click on that button It'll spin up a Drupal pod instance of Drupal 10 With the latest version of project browser install So it'll create a Drupal site for you with project browser installed and you can just walk through that and give us feedback All right, so basically once you do the try it now, it'll spin up this Drupal pod site for you This you know will show you the code so you can actually look at the code in the background But really what you want to do in the top right of the screen There'll be a way for you to look at the actual website is built so Where that's pointing to up there that allows you to get a full screen version of your Drupal site so click on that and Then you'll come to your website and basically you want to log in here. It's very secure Don't tell anybody what the login here. It's admin username admin password again. It's on your local so But that is the login to get into Drupal pod and then you're going to go under extend like you do in the admin toolbar Anyway, go to extend and we have a new option there to browse modules. It's a very straightforward So basically you can help us just by spinning this up on your local machines going to this Site is it is built and just giving us feedback. All right, so First this is what the project browser looks like and I'm going to explain it just in high detail right here But the first thing you should do is take a look at that note up the top Chris talked about your real-time syncing of the data It only syncs it when when we do a manual update of the data So what's on jubal.org isn't going to 100% match what's in the project browser This is just a project browser the data as of the last manual sync that was done. Okay, so don't be confused It's not going to be so if you look at some on jubal.org you say hey How come it doesn't come up in project browser with the new description? It's because it hasn't been synced yet So the default filters These modules that it returns will be compatible with your version of jubal, which is really cool So I'm running a jubal 10 site. It's only going to bring me back Projects are modules that are compatible with jubal 10. It's not going to bring me back to pull seven modules Not going to bring me back to pull six module where you get a you know go through and figure out what's useful for you It's only going to bring back modules that are Compatible with your version of jubal Only but the default is only brings you back modules that have security coverage and Also that are actively maintained So that set that comes back to you is hopefully going to be for our target audience Most helpful to them. Those are the ones they want to look at first now Are you somebody that's more technical and you want to look at something very specific? You can go to the advanced filters and you can you know look for different things I want to bring back that the dev versions of modules for instance You can do that but the default is has security coverage and is maintained and is compatible with my version of jubal And the default sort the order here is by most active installs So the things that have that are the most popular will be at the top of the list can This is sort by you can sort by other things you can sort of alphabetically there's different options there But the default is based on the number of installs All right, so these are the card views so for each module is going to bring you back the logo The name of the module the short non-technical description there which categories it belongs to so the Automated automatic updates initiative Allows you to install modules on your site without going out and using composer So our target audience if you say You know you need to go to a terminal window. You need to run composing you need to run all these commands That's sometimes overwhelming So this allows you to do it right through the browser So you can just click on the button that says add and install and if I want to install path auto I clicked on that button and then I see down the bottom right a series of messages as it progresses through It'll go from in process to Requiring modules and we'll have different stages down there. So another way you can help us is By just going into the project browser through the try it now as I just showed you and try and install some modules Walk through see the different messages you get are they helpful? You know, does it does it successfully install? What do you see that feedback is super helpful to us as well? So that's another way that you can help us out now It also looks at dependencies it runs composer in the background so Because token is a dependency on path auto if I install path auto It's going to install token for me as well. Okay, so it does that automatically You don't have to worry about what are all the dependencies? What other modules am I going to have to install to get path auto to install does that for you? You'll see they both have the installed at the bottom once it goes through the composer in the back end You may have to refresh your screen to see that token was installed that was something that still needed to be worked on So just refresh your screen. So the Ajax will show you that it did install both All right, so now what's another way you can help any designers or front-end people that interested in making logos in the room at all Okay, so Yeah, exactly, that's great. That's a that's an easy way for you to contribute So we have a meta issue meta just means it's a big issue with all the child issues for all the different Projects or modules that need logos created for them So basically you go to this meta issue and you just can select a child issue to work on This is something designers can help with so You can Next one. Sorry the arrow got me child issues. Oh, yeah, down there. Those are the child issues. Okay There you go So to add a proposed logo what you want to basically do is create a logo. That's 512 by 512 Needs to be PNG format No animations and the file size should be 10k or less so that it pulls up quickly in the project browser So those are the requirements It is using GitLab now for to pull the Logos from so if the next screen Chris down here, this is in GitLab. So this is more for the maintainers So the community will create the logos anybody that wants to contribute create the logos Somebody in the community views them and says yep, it fits the requirements. It's 512. It's a PNG then we move them the Issue over to the maintainers the module maintainer They're going to go in and actually make the change and the project page on Drupal org Okay, so they're going to go and add this logo to a PNG file and Then the logo once you do that it's going to show up in GitLab It's going to show up in the project browser and it's going to show up on Drupal org So that logo is going to be used across all of those once it gets added to the code base now one thing I should point out is When we started this project a year and a half when we started creating some of these logos The initial thought was we were going to use the first image on the project page Instead of using we didn't know that we were going to be using the code for the logo dot PNG So if you did if you are a maintainer and you did add The logo as your first image we recommend that you take it off the first image and then you put it in the actual code base Because that's where we're pulling from now See us afterwards if you have a question or not All right as we're going to be updating the logos We also need to update those short descriptions I showed you on the cards where the short description comes in if I'm browsing for a module That's the first place. I'm going to go to say You know, do I think this module fits my criteria? So that's why we need the short Description that allows you to You know go through a vetting first does it sound like it's going to be something that I'm interested in We need documentation experts anybody that likes to just write information, right? You know technical. This is how something works. You could help us with these short descriptions So we're trying to answer the question. What does this module do in a non-tactical way? In 200 characters or less So that's what we're trying to do with these short descriptions who can help with this as I said people interested in documentation site builders Can help us and pretty much anybody can help module maintainers. You're welcome to help as well. You could make these Short descriptions. We just have to make sure that they're not too tactical Alright, so how does a maintainer add this short description? Where does it go? Once the community has created this short description, somebody's reviewed it made sure it fits the criteria Again, we send it over to the maintainer They're going to update the summary field on the project page on Drupal dot org. So again the maintainer needs to do this So they're just going to look at the description field open up the summary And that's where they're going to put in the description. Where does the description appear? It appears on the cards in the project browser All right, so how many maintainers are in the room? Anybody So maintainers you maintain modules projects great So what you're going to do is you're going to get two new issues You're going to get one issue update the logo for compatibility with project browser And you're going to get another issue update the summary on the detail page for compatibility with project browser We'll tell you what the community has suggested or proposed for these things and then you can make them In Drupal dot org on your project page. Okay, so maintainers. We will be giving you these two issues All right, let's talk for a minute about categories. I mentioned categories before When maintainers go to add a project they say if somebody's looking for a project in these different Categories of these different filters They can add as many categories as they want right now. So we have modules that have no categories We have modules that actually listed under 30 different categories Now that's not very helpful if we're trying to you know use these categories in in the way that they were intended So we've come up and we've spent quite a bit of time doing this with a lot of time We've come up with a list of 19 categories From the 55 so what we need this week is Is For folks to fill out this form Anybody everybody would like everybody to do this. There's a QR code there or you can go to the bit.ly PB for project browser category feedback Basically, what this does is it gives you the list of the 19 categories It gives you the scope or a little description of what each one of those does and we just want you to tell us Doesn't do these make sense You know these descriptions, you know, would they be helpful if you were searching for modules and did we miss anything? Before we can give these 19 out or whatever we come up with for a set out to all the maintainers now remember How many how many modules did we say currently we have? Over 50,000 correct So before we say okay update your modules We want to make sure we have a good set of categories because we're not going to go back to the maintainers a second time Right, so we really need your feedback are these categories You know going to be helpful or did we miss anything? So if you could all do that if that's the only thing you do to help us out this week That would be super helpful. We want you to help us more, but at least at least do that All right Chris. I think Thank you Rob. This one is where we're starting to sort of bridge the gap and I'm Just before this presentation started I Reclassified this one as being I think part of the MVP even though it was a little bit mark not but I'm feeling very ambitious Ever since trees said that word a few hours ago So what I would like to do is have a real Project detail page inside of project browser So if you see the card view you read the 200 characters and you say I think this is what I want But I'd like a little bit more information We can have you click through to that and just go to the page on Drupal.org Or we can present you with a somewhat streamlined interface inside of project browser to help you get that additional information So we are trying to decide what is most useful to people We've had a fair amount of discussion around that content hierarchy. We did a buff in Prague With the folks and talked about that we sent a survey out recently and collected some data about what's useful So I feel like we generally know what we want to present and we need help Getting it there and so it's a great issue to work on if you're Feeling like you want something a little bit meatier Maybe you do want to touch the spelt side of things and wire up if you have any experience with decoupled Fetching the data getting it and displaying it and some markup That's a very good issue to work on So before I embarrass myself further I'm just going to say that on this next slide This is what I have done to try to get some of the plumbing in place to make this work with with zero design sense whatsoever so This is kind of where we're at today and we still don't even really like this and a lot of stuff We didn't even have the the data in the API for and I think we may even want to get rid of this release data in this initial interstitial step So this is a area where UI and UX people can help where front-end JavaScript people can help where back-end PHP people can help to collect data and push it out to the API call that we're making It's kind of a big piece, but I think it would be a huge boon To be able to have sort of a second level of information page Inside of the project browser so that there's even less of a need to jump off to Drupal.org From your site because that is as we saw in that second quote from Drupal I want to be able to use the app store or the project browser right on my site and install modules with a click so This is a great issue for people who are who are kind of wanting to sink their teeth into something So like I said the front-end is De-coupled and it's built with Svelte So everything that you see between the header and the footer is Presented by Svelte so you kind of see basically the whole content region if you're familiar with that parlance is all One empty div that gets mounted with JavaScript with Svelte We like Svelte we have some sort of cursory Buy-in from folks on the core team that we could probably get Svelte into core That's one way to get a modern front-end framework into core One of the reasons it makes a little bit easier is it's compiled code So you don't necessarily need a specific version to lean on so for example if you're trying to get react into core Much like when we got jQuery into core We kind of said oh jQuery core ships with you know 1.7 and then you need jQuery update if you want to use 1.9 Loading react into core would be similar with Svelte You just get vanilla JavaScript at the end of the day and you can then ship that so that's one of the main reasons why we lean to on Svelte for our front-end framework, so we're gonna see where we get with that We are trying to Work against the Drupal design system, which is not necessarily something that we did early on So there are some elements in our UI that are not Compatible with the Drupal design system or don't I shouldn't say compatible adhere to the Drupal design system That's something that we are working on there is a proposal To make the Svelte side now Themable and that's going to be a little bit of a tricky Drupalism that we're going to overcome we have a core not a core conversation, but we're going to be discussing Some proposals around that tomorrow I believe So that is an important aspect here is once that front-end is theme-able you can then Do things on your own to you know change classes Change the design of the project browser yourself Add data points to it and that sort of thing if you have additional data coming in from your Say your custom source plugin Accessibility review is another thing that people could be working on and right now There's a meta issue for UX improvements the UX group went through and made a bunch of small issues And a lot of those still need to be worked on And there's you know in addition to what I've said here are yet more front-end issues that could totally be worked on Here this week, so you know doing things like matching the Drupal design system Or right now the image on that card view doesn't click through and we probably want it to Oh, of course, we do this at 2 o'clock guys. I got to take my medicine Very persistent alarm is going on. I have to solve a math problem before it'll stop. Okay Sorry about that Right now in the categories list We don't show you when you click that facet there click through to say the accessibility category We could show you that when you click here there will be through 35 modules. We don't do that now But we want to There's a big blocker here this improve UI of results count It needs a good review a good technical review and it might even need a pretty hairy rebase So that's definitely stuff that can work on There's some lightweight things here that is just you know if you click the X and clear the search box It doesn't research with the With the keyword empty and we need it to do that So there's some good kind of novice issues in there if you're looking at to do something kind of lightweight and dip your toes in and we have Some code issues that you can work on in that On the back end we have some meteor things So one thing that we can do is we can add add add to our code base And then we can even uninstall but they'll stay in our composer code base We want to actually remove them using the project browser UI and you know issue like a composer remove right? We don't have that at all now. We have some MRs open that have started to advance that work, but that needs some help Like I said, we want to switch to using the real Drupal.org JSON API endpoint and deprecate the mock And that needs a good technical review as well. And again a little bit of novice issues The tab order we probably want to change We probably want to be the first way that you install modules and not the third tab in that in that list now And then of course like I was describing around the project detail page We definitely want to implement whatever that is and whatever we decide there So really what is next for project browser number one is actually Not project browser related, but it's getting package manager into core Since that's a dependency of ours and of automatic updates We want to get package manager into core Adam. How close are we on that? What's that working on it? We've got a few open issues like a Bunch all right, so that Good good for you Adam is non-committal but And and that's what we need we need to get package manager into core before project browser can get into core so we definitely want to throw as much effort that way as possible as well and Then we have issues tagged as core MVP So these are the issues that we actually do want to go into the MVP that would make us say This is a good minimum viable product and we can put it into core as it is This originally said 13 issues, but like I said about an hour ago I added the project detail page to the core MVP list and I'm just gonna stay optimistic that we can get that Taking care of It's already plumbed in the Svelta app. It's just not fully complete and So we could undo it and just link to Drupal.org, but I feel like no, let's get it in there So that's that's our plan. That's what's next So I'm gonna turn it back over to Aaron when born award winner Leslie Glenn for To talk about contribution All right, so why contribute a project browser? Well, the most important thing is This is the first place people will go to they install Drupal The next thing they're gonna do is try to add functionality to their Drupal site so Wouldn't it be cool for you to be part of that everybody that installs a Drupal site that see project browser You say wow, I helped build project browser So we really think that that's a great win for you to get involved with this Anybody can get involved we you we can use any type of individual with any skill level you can be a beginner You could be a super expert maintainer. We need all of you to help us out. I do have a bitly link there Bitly PB contributions for project browser contributions. I try to keep that updated So even once you leave here this week, that'll always have opportunities for you to contribute to the project browser So that's a one-stop shop to go to get all the different links that Chris and I have talked about today Definitely, you know Take a take a picture of the QR code or go to that link and just follow that and you can give that to your colleagues when you get back And continue to contribute So where can you find us this week? Chris is going to be in general contribution every day most of the time when he's not at a session that's related to project browser We have two buffs tomorrow for those of you who don't know what buffs are they're like discussion groups They're birds of a feather people who are like-minded thinking of the same type of you know thing They want to work on so we have one tomorrow from 8 30 to 9 Updating content on the project pages. So that's kind of what I talked about with logos descriptions How you can help with that and some of the challenges were happening with that and then from 9 to 9 30 We're having a hands-on so come You know try things out give us feedback We'll help you out getting that try it now working on your machine anybody that wants that so you can come to those two birds of a feathers On Wednesday, there's the Drupal initiative keynote, which I'm speaking at That's just a real high-level look at all the different initiatives They're going on and seeing where you think you best can fit and then you contribute for the rest of the day To that initiative so definitely come listen to that whether you choose to do project browser or another initiative It'd be great if you just come listen to that at 9 o'clock on Wednesday and Stay for the day and help contribute and they'll be mentors all day So there'll be people to help you so don't be intimidated. I can't contribute anybody as I said anybody in this room Everybody in this room can contribute. We all started with you know going to our first contribution event and then Thursday There's then general contribution all day so you definitely can come help on Thursday as well So how can you join it beyond this week? Go to the Drupal Slack and join the project dash browser channel. That's where we have meetings We have a site builder meeting that I run on Tuesdays at 4 p.m. Eastern There's also a more general on Wednesday at 10 a.m. That Chris runs those are asynchronous They're in slack so we just start threads and people just contribute to the threads So if you're not in our time zone or you have a meeting at that time check in later on that day And you can just give you our feedback give your helpful comments to us in the slack channels You can work on the issues that we talked about check out the issue queue and I want to make sure I thank you We've had probably a hundred people contribute things here and there over the past year or so to the project browser So thank you that everybody that has contributed and to everybody that in here and that will contribute and Chris and I that's how you can reach us on project browser at Chris from Redfin and at Leslie G And I just wanted to thank Redfin that Chris mentioned earlier For supporting some of our time on the project browser initiative and now I think we're ready for Q&A So who has questions? Yeah Any questions Right so the court the question is For the short descriptions do we have editors or do we have folks that are reviewing the short descriptions that are created to make sure they fit the Requirements in they're not too technical The answer is you're all reviewers anybody that wants to in the community that wants to review those issues can So you don't have to be an editor you don't have to have you know documentation skills Anybody can read those to say oh, I wouldn't understand this. I think that's too technical or it's too long It's more than 200 characters. So You know you create the score short description somebody else in the community reviews it So there is a second level there before we give it to the maintainer same with logos You can create the logos or you can just go and look at the logos to make sure that they fit the criteria No, but we were the question was we do we have somebody dedicated to make sure that all the descriptions and such are Consistent the answer is no We have some people that have done multiple reviews would love to have that if there's somebody in the community or a group of People who want to review those in a consistent would love to have you have one board to help us out I'll just add to that. There is a process for all Drupal issues which require that they go from Getting written to then going to a needs review status and then that someone else will review it and say it looks good or bad Then it goes to reviewed and tested by the community So at that point then it always kind of falls to Leslie or myself to then at the end when it says our TBC We are always taking a final look at it. So At the end of the day, we are probably responsible We're kind of the two at the end of the day to make sure it's consistent and non-technical So there is a process built in but it's a lot more community oriented than maybe a publishing workflow would be inside a university or something Other questions The question is where does the actual contribution for logos and descriptions happen? So there is a issue for each Logo and description for each of the top hundred modules. Some of them are closed now. Yeah We're targeting the top hundred sort of most popular modules, but you know, we can continue on from there So the issue opens with something like create a new logo for XYZ And then as we go down some people will upload some ideas for a logo or for a description Other people will chime in and say I like that. I don't like that needs work and then ultimately we update the issue summary with the proposed description or the proposed logo so that What we've kind of reached consensus on is right there in the top in the issue summary And then it will go through that same process, you know needs review reviewed and tested by the community And then the maintainers themselves actually will say, okay, this is good I do agree that it meets all the criteria and then we'll move it over to the Maintainers queue. So if it's like a logo for the token module, then we'll put an issue in the token module Issued queue for them to say hey put this logo in anything else Well, we are happy to be here for you If you have any questions or want to come say hi feel free to find us like I said I'll probably be in the contribution room most of the time Leslie will be all over the place probably most of the time Anything else that you want? Yeah, I just wanted to say hopefully you've all found something that you can help with Whether it's on our initiative of some other Contributing back to the community is super important to the to Drupal to advance the project So thank you for coming and listening and come and let us know if you want to help out We'll see you all on Wednesday on contribution day. Hopefully Thank you