 We're here to talk to you about Project Browse. It's going to be mostly an update format, tell you where we're at, tell you where we're headed, and give you plenty of opportunity to ask questions about how you might want to get involved and how you can get involved. So we're here to be a resource. So I'll turn it over to my colleague first. Hi, I'm Leslie Glenn. I am one of, I'm sorry, I'm the Manager of Client Success at Redmond Solutions up in Portland, Maine, the Drupal Agency. I'm also one of the initiative leads for Project Browse, and fortunately I was elected and was on the Board of Directors for the Drupal Association for a couple of years. So that was very enlightening. I learned a lot there as well. So thanks for coming, and we're looking forward to giving you a lot of information, especially about how you can contribute and how you can get involved in this initiative. And just to keep going, Leslie's also an Aaron Winborn Award winner, and she'll never say that herself, so I always have to say it. So congratulations to Leslie for all her contributions to the Drupal community, of which this is just the end of a very, very long list. I'm Chris Wells. I'm a member, which means I'm like co-owner of NLLC in America, like a GMBH or a limited company. So member and CTO over at Redfin Solutions, as well as Leslie and the other co-leader of the Project Browse initiative. I built my first Drupal site in 2004, maybe 2005 with Drupal 4.7, and we've never looked back. So we've been a Drupal shop for the last 15 plus years, and also happy to be here and talk about Project Browse. It's finally time for me to get in and get involved in contribution in a big way, so I just kind of kept showing up to meetings and ended up co-initiatively for Project Browse. And you can find all my stuff at chrismredfin.dev. I used to have a very bad online identity problem where I had like different handles everywhere, and then before DrupalCon Portland, I just changed everything to chrismredfin, so you can find me just about everywhere at chrismredfin. So we first wanted to talk about what is Project Browse. You probably know by now, and you probably know if you've seen the keynote, what we're after, but it's really from Dries's vision for moving Drupal back to a sort of no-code, low-code environment. When we made that leap from Drupal 7 to Drupal 8, it got a lot harder for site builders to just spin up a website. They had to use Composer, they had to solve problems in a lot of very technical ways, so it's about getting back to that. And so in Portland, Dries released his vision that Drupal is for ambitious site builders, and so we want to empower those people, the ambitious site builders, to work on their Drupal site. And so as part of Drupal 11's strategy, we wanted to be able to discover great modules from right within Drupal without having to go to some external website, without having to go to drupal.org or the old drupalmodules.com, and we want to install those modules with the click of a button. So the prime directive from Dries was to make it easy for site builders to both find and install modules, and that's what we're after. All right, so what problems are we trying to solve? My example here is to make an easy breakfast. So you go to the grocery store and you see hundreds and hundreds of different types of cereal. How do you know which cereal box or which module to choose? How can we make that easy for folks? I think there's something like 60,000 modules right now, contributed modules, and how does somebody who's new to Drupal have any idea where to go to find what they're looking for? That's the problem we're trying to solve. So you need to have some direction. You need to have a path to enable you to narrow down your search. So we'll show you how the project browser helped you to do that. And then check out. Once you've decided you have a module, you've looked at it, it sounds like it's the right thing. How do you then go and install it? So that's the check out. How do you actually get this into your Drupal site? One thing that I don't know if I made clear yesterday is the modules, when you search for them, when you go to the store and search for them, by default it's only going to bring modules that are compatible with the website you're trying to add them to. So I don't know if I was clear yesterday in that, but that's really a key so that you don't have to worry about going and searching for modules on Drupal.org right now. You might come back with a Drupal 7 module or a Drupal 6 module even. Now you're only going to get modules that are compatible with your version. So that's a huge one. So I can answer that. Yeah, it's going to use Composer under the hood. So if a module depends on C-Tools, it's going to pull C-Tools in automatically as well for you. Yeah, and we'll go over the fact that the button changes some download if you don't have it yet to install if you've already downloaded it to installed if you've already downloaded and installed it. So it's very clear the user interface, but we'll get into that in a bit. So the first thing that we wanted to approach is kind of the MVP of Project Browser. So if anyone's used Agile development methodologies and their projects before, what is the minimum viable product? What can we ship that will bring the most benefit with the least amount of effort? So what have we been aiming for? We have the ability to browse module projects in Drupal in the Project Browser today. And those are, like Leslie just said, compatible with the version of Drupal that Project Browser is running inside of. So it won't even show you something that's only compatible with Drupal 7. It's only things that are useful to you on that site. So that's that shopping experience. I want to see what's out there. I want to start comparing. And if you're in the grocery store, you might not even know where to start. So you know that you need to find a healthy breakfast. So I might need a signpost that says, here's where the breakfast foods are. You might want to start around here. So we've implemented some of those signposts so far. For example, we will allow you to filter by a category of module. It's using the same categories that you currently use today on Drupal.org to narrow down the modules. And then TBD. Let's say you actually find your way to the cereal, but now you want to compare and you say, all right, well, I'm actually looking for, if I want a healthy breakfast, I want something that's lower in sugar. So the advanced filtering will actually let you go in and sort of read the labels and say, okay, between this cereal and this cereal and this cereal, which one do I actually want? So we do have some advanced filtering built in now. And there could be more to come as we continue to discuss with the project browser. And then right now in the MVP, our goal was to provide instructions for how you would do the checkout portion of your healthy breakfast. So I don't know if we have these in Europe, in America. We've been pushing more and more labor onto the consumer. So we have things like self checkout machines in America where you have to take your own stuff and scan it yourself and put it in the bags yourself. That's kind of the analogy we're using here. Right now when you click install, you're going to get a modal window that tells you how to use Composer to install the module yourself. But we are actually very, very close on advancing that and getting it to where it will. You saw in Driz's demo, if you were at the keynote, we have a branch going where we've been integrating with automatic updates to automatically install and run the Composer commands for you under the hood, which is amazing stuff. And that we've been doing all of this in the contrib space so far. Our goal is definitely to get Project Browser into core. It's what we want. It's what Driz wants. But being in contrib lets us iterate quickly and make some decisions that might be a little bit riskier and get them in and get them iterating. It's part of that strategy that Driz talked about in the keynote of getting things done faster. And we can do stuff faster in contrib so we've been focused on that space. So that's the MVP that we've been headed for. So we do actually have a beta version of the module that's out. You can get that module today. You can compose or require Drupal slash Project Browser. Pull it into your project in beta. You click Browse from the Extend menu. You can filter by categories. And it provides some default filtering that we thought would be the modules that we would really want to push and suggest. And those are ones that are covered by Drupal's security policy and are in some sort of actively maintained type of status. It actually uses a few different of the statuses on Drupal.org to determine whether it's well maintained. But that's already there today. You can go ahead and download it. And we encourage you to do so. Check it out on a demo site. Try it on your local. See how it's working for you. See how these file issues against it. So what have we done so far to get to the point where we're at today? So we started Project Browser. The goal of the Project Browser is for site builders and those new to Drupal to be able to easily find and install modules. So we started with that community. We started with those new to Drupal and site builders. And we held listening sessions or interviews with these folks. And asked them, you know, if you were going to look for browser modules today how would you do it? And then eventually how could we make it easier? So those listening sessions which we're still holding today we had some UX listening sessions yesterday. Reach out if you want to engage with us and walk through the current beta version and answer some of those interview questions. But those were extremely helpful in trying to gauge the community and how we can best build this because it's for the community. It's for those new to Drupal and site builders. So how can we get their input to make this something that's going to be useful to that group? So we use listening sessions to do that. So that was our first step. Then as Chris spoke about a minute ago what should the default filter criteria be? If I'm somebody new to Drupal and I'm coming to browse for modules when I see the first set of modules what criteria should they meet? So the first thing was you're in a Drupal project you're using the project browser now not on Drupal.org external to your website but right inside your website so the first thing is needs to be compatible with your website. So that's the first default filter. The second default filter is doesn't have security coverage because again in our interviews with folks that was the most important thing. I'm not sure that the modules I bring in are secure. So that's the second default filter criteria. And the third one is as Chris mentioned is it maintained? So people are interested in modules. One of the first things they look for out on Drupal.org now is it actively maintained? Are there maintainers that, is the number of open issues, is that number dropping? Are they actively upgrading their module? Things like that. So the three defaults right now are compatible with your version has security coverage and is it maintained? So that's what we decided. As Chris said there's a lot of advanced filtering for you more advanced people in the room even though our goal is to have site builders and those new to Drupal. We want everybody using the project browser. So advanced people should be able to say hey find me something that's not secure or find me there's something that might not be a full release. So that's another thing that's a default criteria is needs to be a full release of the project. So we don't by default bring back alpha, beta, that kind of stuff. It's got to be a full released version. The third thing is we got different feedback on whether a grid view which is cards which you're very familiar with has the name of the project, the logo, a very short description and the categories that it belongs to is a card view the most useful is a longer list view more useful to you. So we provided both. The default is the grid view, the card view but you can also get a different view a more of a list view. You see fewer there but there might be a little more information on those cards. And then the next thing we did was the categories. So modules right now in Drupal.org there's different categories you can assign to a module and I'll talk a little bit more about categories in a bit but for right now what we did was we had a group of folks from the community like you try to define what those different categories are because right now they're listed you can select them but why would you go look for media? What does that really mean if you're searching a category called media or security what does that mean? So we gave definitions to those. Those aren't yet being displayed in the beta version of Project Browser but they will be so we can use help with that as well. So those are some of the things and Chris will go over a few more here. Oh, that's me. Yeah, descriptions for the categories. All right, I'm up. So one of the things that's holding us in beta and we want to really move and advance is the way that we are currently getting the data from Drupal.org is that we're actually downloading we have to generate a gigantic JSON fixture and when we install the module we load that to your local Drupal site. So that has to be periodically updated. I just did it last night and Tim got it committed so if you get the latest version today it will have data as recent as yesterday. With that said, if you installed it yesterday that data was about five months old. Last time we updated it was in May. So we're still trying to do maybe monthly is what I hope for but hopefully now quarterly updates of that fixture data. What we really need is we need Drupal.org or some portion of Drupal.org to be on Drupal 9 so that it can expose this data to us with JSON API and search API. That's the endpoint that we're using to fetch live data from Drupal.org. So we need collaboration from the association to be able to spin up a live Drupal 9 server where we can fetch this data real time. That's our goal and I think that's probably the thing that's blocking sort of a 100 release but besides that functionally the project is all there. So we do have that mock. Then we have in a project browser now you can actually look at a detail page. Early on in the project if you were looking at the card view and you clicked through it would just take you to Drupal.org to the project page there. Now we actually do have a skeleton version of a detail page built right into the project browser so you can get more info read the full description. That's wonderful but it's not quite there yet. There's an opportunity to contribute in that arena as well coming up that we'll talk about with our contribution opportunities as well as updating that category data. And so we did release an alpha and then eventually a beta version so that's a big accomplishment that we've made thus far. And like I said before you have instructions for installing via Composer but that is very, very close that we'll actually be able to click and have it run the Composer commands for you under the hood. We're waiting on just a few policies to get short up and we're collaborating very heavily with the automatic updates team to work on that. And then this is probably one of the coolest features that we have and my boyfriend is right here he's done so much work in this arena but allowing for multiple sources of where you can pull data from. So right now we have that mockdruple.org plugin we also have enabled a plugin where you can search for core modules to see what already comes with core and what you might want to install. This is super great and super important for some of our audiences for example in higher education at colleges and universities they might have a set of modules that they are limited to or maybe you're at an agency and you have some of your own features or meta packages or custom modules that you use from project to project to project you can define your own plugin source and get a new tab on Project Browser where you can search for just your agency's modules and install those as well. So one of the things that I hope to accomplish at this Drupalcon is getting developer documentation ready to show you what is the contract that you need to adhere to to be able to provide your own plugin. So what are we looking forward to? That's what we've got so far what are we actually headed towards? Thank you Chris. One thing on the project source there if you're new to Drupal that's not displayed by default so don't worry that that's going to show up on your default project browser there'll be configuration in project browser where you can turn on things with the different sources. Just want to make that clear. Alright so what are we looking forward to doing? We want to re-examine the project detail page on Drupal.org and in the project browser so some of these listening sessions that I spoke of earlier we're talking to folks and say when you go to Drupal.org when you go to the project page what are the most important pieces of information that you look at there when determining whether you're going to want to look further into a module or actually install the module so there's all kinds of things a number of new issues who the maintainers are there's the project description itself but none of this is standard across modules if you go to Drupal.org and look at the project pages each and every one of them is completely different everything's in completely different places so we're trying to think about can we standardize that in such a way so can we put a template in there especially for new modules as they're created and they follow a template versus just put everything everywhere module maintainers are great they do such great work for the community but they don't often think about how are people going to consume that information that they're putting on those detail pages so the project browser content strategy the content is critical to project browser project browser we have the tooling all done but it's only as good as the information that's displayed there, the content we're trying to work on the content as well so what can we do to shore up the Drupal.org detail pages so we display the things that are most useful to the community on those detail pages at the top you know maybe we'll display it all eventually and there'll probably be links back to Drupal.org page because we may not bring it all over but we want you to be able to use project browser in itself and not have to go to Drupal.org every time so any help you can provide any insight would be super helpful to us on that alright so one of the initiatives that this team has been working on especially the site builder subcommittee and we'll talk about the different meetings we have but is on the card view in the project browser there's three important pieces there's four important pieces of information the name of the project or the module a logo so a logo appears and some of the logos you know like the web form module has had a logo for a long time you see the logo and you know it's the web form module there's a lot of modules that don't have logos at all so if you're a designer out there or a front end or you're interested in graphics at all you know creating those logos for the modules that don't have them that's a easy opportunity to contribute so right now we're working on the top 100 most popular modules again the default project browser brings you back the modules with the most used ones first so the ones you're most likely to install will be displayed first those are the ones we're working on trying to get logos for we're also trying to create short descriptions now not 200 characters or less but not only short descriptions but descriptions that are core users the folks new to Drupal and site builders will understand right now if you go to Drupal.org look at the project pages they're very technical the descriptions you know a lot of times they're written by technical folks so we're trying to get people like you to help us create non-technical short descriptions just display on the cards and project browser you'll be able then to link to the more detailed description which could be much more technical but we want somebody to be able to on the card just quickly scan and say is this something that I should look for further into is this something that I might want to install on my website and then the categories I told you the categories and we'll talk again about those in a minute but there are like 55 categories some modules have up to 30 categories assigned to them so when you're looking for a module and you're looking for categories I go look for Meteor and I get back these I don't know mapping modules so we're trying to straighten that out in some way so one of the things we're trying to do at the top 100 most popular modules is select three the three most relevant categories that we feel when folks are going to look for modules in the project browser if they select these categories you know these types of modules will appear so we need help with that as well alright the next thing I went to but let's go up to the there we go Chris fixed it for me thank you provide a base template for project description so I spoke about that so that's creating some kind of standard you know the body field right now is just a free text field where you can put anything in any order so we're trying to come up with a template we have a buff to a day today actually today for the project description it's at 15 o'clock 1500 1500 there you go so we're trying to figure out how to create a template to use so those body fields so that we can make that stuff more consistent from module page to module page and the next thing on that is getting maintainers involved how many people in here maintain modules awesome thank you for coming so we haven't yet got the maintainers involved as much in this initiative as maybe we should have we're trying to get the community first because we want to make sure that this is useful to everybody but maintainers are super important so while we've been trying to do the top hundred modules it's going slow three pieces we're trying to do category short description logos if the maintainers on your modules want to help us out and suggest what those three things would be we're going to have to take what the community has given us and create an issue in your module queue for you to actually make those changes to the description and the categories and all that if you want to start that yourselves you know as long as it's a non-technical short description by all means you can certainly help us out module maintainers you can also give us feedback on what we talked about here the template or anything like that so thank you for coming module maintainers and with that I'm going to pass it over to Chris quick bit of trivia before I get started shout out your answer how many categories is the add this module tagged with no cheating how many do you think is the add this add this what's your guess closer yep 30 okay how many is the third most popular module for Drupal 9 is path auto how many do you think it's tagged with zero right okay so we've got to clean this data up this is like one of the most important things we can build the best slickest looking tool but if garbage comes in garbage goes out so we've got to focus on that stuff super important so what are we looking forward to I already talked about this we want to migrate from that mock API to a real live Drupal 9 backed API that's basically that proof of concept is done it's working and like I said we're waiting on really infrastructure and the association so that part we're pretty excited about replacing the install instructions with actual composer commands that is very very close as I've said before so like in the demo Shristi had said if you have the experimental version install which is not really experimental it's just some kind of branch that we have that she was able to install but we need to get that merged into mainline and we'll be able to actually one click install to add modules to your Drupal site and to its code base which is very cool we also I tried doing this in Portland I hit my head against the wall a bunch of times and I eventually gave up but we loved to capitalize we were one of the projects that were empowered to use GitLab CI instead of Drupal CI thanks to Tim Plunkett and some of his knowledge of testing we were able to get Drupal CI spun up but not GitLab CI anyone with some DevOps experience I know a good amount about GitLab CI but I don't know a lot about Drupal CI or how tests are run and that sort of thing so we're looking for collaborators on that that's definitely something we'd love to focus on like Dries said those tools are going to empower us to just move faster and that's what we want to do so looking ahead of that and I don't know if you knew this but Dries was talking about how great it would be to have a prototype module built with the modern front end our front end is built in Svelte we are using Svelte to build the components out for the project browser we are committed to leaning as hard as we can into getting this into core with Svelte but one of the things holding that up is when you decouple all of your theme ability gets lost you have to override the Svelte app or you have to build your own Svelte front end so we are trying to pioneer the way to make the Svelte markup themeable using a Drupal system we have a proposal for that Ben Mullins has thought long and hard about how we could do that that needs people with enough of an understanding of that to look at it and review it make suggestions and see if that's a way forward that we want to go because if we can not lose Drupal's theme ability and get a modern front end framework that's the brass ring we are super excited about that so I don't know is that an expression that anyone knows the brass ring or a cell a merry-go-round you used to be able to reach up and if you could reach the brass ring you could get a prize so that's kind of like what you're going for so that's what we're going for we really want to make the Svelte side themeable so we hope that there's some people that can jump in people who know a little bit more about all those pieces that I do to review that and the other thing that I really wanted to touch on is how much all of these initiatives tie in together the grand vision for Drupal 11 so we have been working non-stop with Ted Bowman and people in the automatic updates initiative to look about how we can do these automated installs we knew that we were already automatically running composer update why is it so hard to run composer require we were able to collaborate with that team Ted himself did a lot of work towards abstracting what he did in automatic updates into the package manager sub module that will let not just us and not just automatic updates but your module if you want whatever the next thing is that comes along to update Drupal's code base from the UI so I think Ted is giving a presentation about abstracting that out and what package manager can do for you later today so I may see there as well but also I am so so excited about what's coming up in the realm of Drupal recipes when we started early on we were talking about the idea of we don't just want to filter by category we really want to think about what is the use case that I'm using Drupal for I want to add mapping I want to be able to put locations on a map I want to build a cookbook site I want to make a blog I want to add a publishing workflow all of these things in Dries's idea of composable core we can now I'm looking forward to extending project browser to be a recipe browser so that you can go through and say well what kinds of recipes multiple modules and config put together will solve my use case so I'm very excited to see what happens in distributions and recipes so we can help them build a browser for that functionality alright so why should you contribute and help us out alright just one thing I thought about while you were speaking about what we used to call use cases which are now recipes instead of distributions where you bring the whole chunk of stuff in and you couldn't add or delete recipes will just bring groups of modules in so that you can add you know this recipe and that recipe to your fully functioning Drupal website it's not going to be it's based on a distribution and you're kind of locked into that so I just want to make that clear so that's going to work a little different it's really exciting for us to be able to have a user say this is what I'm trying to accomplish they might not have any idea which modules they need but they're trying to accomplish something so let's bring all that stuff in so we're really looking forward to what Alex and that initiative team are doing and they took it off of us because originally that was more down the road list so that's that's cool all right so but the first one now I have two that's all right there you go all right so why should you contribute the folks in the room here contributing we're trying to make it easier and easier this is one of the best initiatives to contribute to because you can do something like you know I don't have it up here so go and add a logo create a short description those are small you can do that you know you're stuck on something at work spend 15 minutes a half hour and contribute in those little teeny ways you don't have to spend 4 or 5 hours and do something really big you can do all these little small things just when you have time so definitely think about that but as a chance of site builders and those new to Drupal to contribute as I said we had these listening sessions they're reviewing some of our descriptions to make you know to say do these make sense to me could I go in and look at these category descriptions or these short project descriptions you know is it helpful for me as a you know somebody newer do I understand those so if you're new in the room here don't think you can't contribute you definitely can contribute there are so many non-code contribution opportunities and project browser more than so many others great even just you know especially if you're a non-native English speaker can you come in and review the 200 character English description and make sense of it does it make sense to you great you can review it and say this I think this is good you just need so much of that and then it's a holistic approach to the to the project content on Drupal.org so really as Chris said earlier content is king content is the basis of the project browser so we need to get the content in good shape in order for the project browser to be successful so you're helping that will be great and then you know using some of the new tools Chris talked about like Svelte and GitLab CI etc you know if you're interested in those tools if you want to learn what Svelte is and how it works and how we use it in the project browser by all means we're not just looking for new folks we're looking for experience contributors as well to come in learn these new tools and help us learn some of this stuff as well so if you know GitLab CI by all means come and help us out or Drupal CI as Chris said earlier so there's opportunities for everybody for that so there are so many opportunities here at DrupalCon for you to contribute and we'd love to see you there oops too late for some buffs yesterday we did listening sessions and usability testing with that said we got really great feedback we had about five people show up it was the perfect number for us to be able to keep up with people but still doing that you can do that on your own by spinning it up and just some feedback in the issue queue you can find me in the general contribution space if you see me there I'll help you get spun up and just have you play around so there's still opportunities to do that so today at 1500 we are going to do a buff to look at those Drupal.org project pages let's pull up a project and let's look and say useful not useful useful not useful wish we could fix this love to hear your feedback on that it will inform both the in browser experience and the experience on Drupal.org and then tomorrow at 1500 we will be looking at those project categories I keep going back to the fact that we have a cck category on Drupal.org we haven't cared about cck since Drupal 6 is it time to get rid of that category to retire it like we did ie6 what a good funeral say we love you cck thank you but you do not serve our community anymore can we get those 55 down to something can we get the descriptions that make sense so that we know what to tag them with so would love to see you there Friday all day we've got tons of opportunities Leslie will be in the mentored contribution room if you have not contributed before and you just need help with some of that process if you have contributed before you're able to contribute to Drupal then you can find me in the general contribution space we've got front end issues, spelt issues devops and workflow with GitLab CI back end issues ideas that need someone else to put their brains on it and a lot of more usability feedback design UX experience so we'd love to see you on Friday if you're still here in Prague for the contribution day and then ad hoc I'll be around, she'll be more in the mentored contribution space and I will be in the general contribution space in between sessions so would love to have you like I said I'm also wanting to do a bit of technical writing and documentation while I'm here so would love to have you work on that with us today after Drupalcon if you would like to get involved pound project dash browser on the Drupal Slack site builders and so those focused on the data, the content on Drupal.org and focused on the user experience and user interface that is, oh you fixed the times thank you they're a little bit late, that meeting is a little bit late it's 4 p.m. Eastern but at 2200 European time that meeting happens it is asynchronous so we'll run that meeting and we leave it open for 24 hours so if you have feedback the next morning that's totally acceptable and you'll get credit for participating in the meeting the general meeting is a little bit more focused on the coding the doing, issue triage that happens at 1600 European time and also of course the issue queue just has stuff that you are welcome to look at and pick off so I just wanted to thank all the contributors who are here who have helped so far I spoke about the categories descriptions Martin back there was instrumental in creating all those descriptions saw you back there so I want to make sure I gave a shout out to you and all the others that have helped out so far alright so this Chris went over some of this before in the middle on Friday there is a, actually during the week there are these first time contributor workshops to get the tools to get you set up with contributing don't be too concerned about that you can come and contribute in some of the stuff that I talked about the descriptions the logos that kind of stuff without having any tools on your machine at all you just come I'll show you how to spin up the issues we have a Kanban board that has needs work and then needs review so you can come and review things that people have already done or you can create these things on your own so but there are three sessions there for contributing workshop I think there's only one left on the 23rd which is Friday from 9 to 12 30 and then there's the mented contribution room if you want to work on the the stuff that I've talked about those three major things for the top 100 come to the mented room if you want to get more into the coding and more into Svelte and get lab and CI and all that you know go to the general contribution room with Chris find us anytime during you know today tomorrow stop us say hey I want to talk to you about the project browser you don't have to wait especially if you're not going to be here Friday reach out to us today just stop us wherever you happen to see us we're all great opportunities in I don't know if you realize that you get contribution credits nowadays not just for doing code but all these non-code contributions you know helping us with any of this gives you contribution credit and the community really appreciates everything that everybody does for the project all right we've got about five minutes not as much time as I thought we'd leave you for questions but happy to field any questions in the last five minutes you can see this gentleman here we we translate Drupal but we don't translate Drupal.org so you're moving a piece of content and management stuff from Drupal.org into the local Drupal site and you know the top 100 modules and etc when we're pushing things back to site builders down the road is there like an idea that all these modules and things need to be essentially translated so that we're essentially making the site able to be in any context and also be extended and stuff like that so I mean that's a huge thing you guys are building an app store right essentially but and I'm saying well what about but I just wanted to say is thoughts about that yeah I can speak to that first of all I love that so one thing that is really wonderful we are able to you know wrap Drupal T around stuff even in script now so we are really I was actually hoping to engage folks today you know we are at let's say in Spanish where it may be 20% of strings translated just today because downloads already been translated module has already been translated for some of the other languages where maybe at 8% we are trying to by utilizing this in browser we're trying to enhance translation capability and I don't know to what level we will be able to translate things like the full detail but that's something that I have an eye on and would love to be able to do we need people to think about how that's technically possible but that came up early in our discussion and I would love to do that good I saw a demo of the project browser and it says it has a default set of filters on the right on the left side I saw there are three filters which says it's compatible with your version of Drupal its security updated and maintained so I saw that those are radio buttons but then we also talked that for advanced users they want to search for modules which are not secured or nothing else but don't fall into any of those categories being it as a radio button also reduces that you have to select at least one category I mean you cannot just neglect so is there any update part saying that it will be moved from radio buttons to checkboxes so that someone can just eliminate all the options and look for any kind of module that they are looking for this is feedback that we have received in the listening sessions actually there was a couple of people yesterday that mentioned the exact same thing as you so that's something that we'll create an issue for you know we'll look at that you want to speak technically to that anymore so we actually had those matching what was available on Drupal.org before and letting you pick from checkboxes when we moved to having optional back end sources like for example being able to put my own github of 10 custom modules up there we decided a little bit to simplify the contract where you can say show me just things that are well maintained or show all so you can still see things that are not secure things that are maybe stale or not maintained but they really fall into one of those categories show me the stuff that's well maintained or just show me everything so we decided both for the technical reason but also to make it easier as a filter to get rid of some of the Drupalisms that are tied to it to be able to just say give me everything or give me just what is recommended and good so we understand that's not the perfect solution it still gives you that functionality but we made it simpler so that we could make it more extensible Hi do you I foresee some security concerns regarding giving writing permissions to the main I don't know have you plan something to do it to the UI or what I can talk a little bit about how that composer process runs first of all one vision that I have I'm not sure if we should separate this out but if you think about a config split right where you might have stagefile proxy only enabled on your local development environment you might only have a project browser enabled in your local development environment and not on your live site so that will allow you to only run the composer commands where you would have been running them anyway from the command line also the way that package manager works is it actually runs the full composer environment kind of on a cloned version of your site and make sure that everything validates it's never going to upgrade a version for you for example and it's never going to upgrade to a version that is not marked as covered by the security policy so there is some of that happening but the idea is that you'll only theoretically be doing through the UI what you would have been doing on your command line locally before now if some people treated a little bit more like the Wild West and they want to run that on live you're welcome to do that but it's kind of up to you but we do have some things in place to sort of mitigate what's going to happen with composers so we stage that all in an area make sure that it meets all the criteria and then it gets applied to your live site after the fact so we have a little bit in place to help with some of that and I encourage you to talk to Ted Bowman as well and learn more about automatic updates they solved a lot of that before we were even involved as well so there's good stuff happening there so we're a little bit over time I think there are people coming in for the next session so we can answer your question you can come up or we can do it outside it's a very quick question slightly related to translation my question is how does the description text relates to the info file the description because the translation is already solved so we don't want to reinvent the wheel probably and also it has a very grammatical structure as a translator I remember many maintainers start these description texts it allows you to do and the verb so maybe it's I'm just the question that how does it relate to the short answer is I wish more but it doesn't we've talked a lot about how do we integrate the data that we get from Drupal.org over the API and the data that we're already providing in an info yaml we've really leaned heavy on the Drupal.org data and not really at all on the info yaml with the exception being if you enable that experimental core source plugin I think we read some of the data from the info yaml there or the categories in order to figure out how to categorize them there has been a I've definitely heard from the community how can we bring these things together and that's something that we need more input on but are looking ahead to if we could pull descriptions from info yaml or if we could pull categories from info yaml and consolidate all those into one grand library we would like to do that but we can't yet thank you so much find us wherever you see us always happy to talk fill out your session