 to say this is a great pleasure to see so many people here today because the last few years it's been a bit rough with the number of people turning up for first time contribution not being that many so thank you everyone for coming means a lot I think there's a few people wandering in there's plenty of room here at the front if anyone's looking for space okay I guess I will get started so good morning everyone my name is Chris I appear on Drupal.org as Chris Dark that's my surname and there's various other mentors around the room is there with there anybody with a green t-shirt is a mentor apart from the tag one guy over here he's not yeah there's room up here at the front if you want so languages I speak are English and Spanish so if you don't understand something in English you can ask me in Spanish but if you're asking me in French I can't help you so one of the first tools that we want everybody to get set up with is Slack so is anyone here not got Slack installed on their computer or on the phone okay okay so you don't want to use that well can you slack on the browser do you think oh yeah you can I forgot that anyways it have you got access to Slack if anybody doesn't have access to Slack they can try and get that set up the conscious on the Drupal's Slack account which is Drupal.org slash Slack to get to it will give you access to all sorts of different channels for you know conversations around Drupal so there's for example bug smash initiative channel there's the Contribute channel which is the one that we want you guys to join up to now there's the for example front issues there's all sorts of different areas composer so the Drupal.org Slack is super super useful basically critical for doing any contribution in terms of collaborating with others especially when we don't want to necessarily be as close as we used to be even sitting at the same table as other people you can communicate a lot better using the Slack channels than sometimes with wearing your mask so everybody please do get on to Slack and get on to the Contribute channel so that's one of the the first things that we want people to do so why are we here why are we talking about contribution that's what we're going to cover first and then we're going to cover the types of contributions that we can do and how we can start doing those we're going to talk about the issue queue if we want to use the issue queue it's not necessary and then various other parts of that like merger quests and the tooling and Drupal part so who is this workshop aimed at like who am I expecting to see here in front of me people who are new to the word of Drupal they this is maybe their first Drupal con maybe they've only been working on Drupal stuff for like a few months sure people who've been working on Drupal for 12 15 years but have never actually done any Contribute it's it does happen there's plenty of people who just they work and they do tons of Drupal stuff but they've never done Contribute and they want to find out people who do do plenty of Contribute but they've only ever done one side of it and they don't know what other ways they can contribute they're also welcome so that really does covers everybody you know there's nobody here that you know we say oh no you shouldn't be here everybody is welcome to learn about Contribution so why do we Contribute there's plenty of plenty of reasons I'm gonna start off with the whole premise of open source is for open source to work you kind of need to put back into it if only if open source projects just sat there and people just consume them and just use them and didn't actually contribute back they would die really quickly so it does depend on you it depends on people contributing back to the you know to the project your contributions are valued so when you do contribute people really appreciate it you know call maintainers really appreciate people going and testing things and marketing has reviewed people really want that contribution so you don't think that oh yeah I'm gonna contribute but nobody's gonna care you get what you give and then some more so learning about the systems that you're working on when you contribute gives you so much back that you can then use in your work or hobby or whatever it's really valuable as a tool for learning about Drupal and they also just makes you a very integral part of the Drupal community you learn to well you get to meet people that maybe you wouldn't have expected to meet otherwise you maybe you're on the initiative like a project browser helping out you you know you know Leslie who's one of the Aaron Wimbled winners or you talk to Randy who's also a world winner or Amy June who's also an award winner you know you get to meet all these award winners which is pretty cool but no like you you get to know a lot of people who are integral to the community and that might be great for you even if you think about it personally as a professional thing down the line maybe you'll be on some project where one of these people is a lead on a project and they're like yeah I remember you yeah you helped me out on this thing so it's great to be part of that community whether or not you want to do it for selfish selfish reasons or not benefits yeah it makes you feel good to to help out and people be like hey yeah great thanks it's cool it does move Drupal forwards so all of these projects that we see like all the different initiatives and the different new tools that are being brought out those things move forwards because people are contributing back so yeah without that they would they might move but it'd be a lot slower so the more people contributing the more people doing testing doing documentation doing bug fixes it just speeds that up you get some Drupal Street cred so you get issue credits for example if you work on issues and that shows up in your account and you know as I said before if you know people and stuff that you know it's cool that everyone gets to to find out about you and you know what you can provide to the community and as I said before the more you contribute the more you learn so you start to work on areas that maybe you didn't use to do so maybe you're contributing in something of documentation that you'd never ever poked around in and then you actually read up on something that you were like oh this is actually really useful so yes it's very useful for that and in the past it has been you know seen as contribution is a development sort of thing but it really isn't it can't you can contribute without coding at all so there's people who contribute in all sorts of other ways that never have anything to do with code you can be a huge asset to this project don't think that because you are a project manager because you are a graphic artist or you know press writer that you can't contribute you totally can there's various different ways to contribute as I said some of the ways are just having a Drupal.org account will provide you some access to some contribution and the other way with the issue queue there's other things that you can do so with just your Drupal.org account you can update documentation on Drupal.org pages you can do translations on localize you can contribute financially by you know being a member of the Drupal Association you can give back to modules and distributions through Open Collective and Patreon which is another form of financial contribution and you can share your knowledge you know it's kind of what I'm doing here right if you have a Drupal.org account and you use the issue queue you can do things like issue triage which is going through the issue queue and determining if issues are still valid like what they were talking about in the keynote this morning you know going through and making sure that a bug is still a bug so on. Testing merger quest for example on issues using simply test or tugboat on the issues testing experimental features so for example field layout which is alpha right now so you can go and test these experimental features on your project and provide feedback about whether or not you find any issues providing feedback on changes that are proposed so you know you can find some other area where somebody is suggested like oh I'd like to do something you can go and actually test that out there's marketing materials for example is a lot of marketing stuff that needs to get done there's lots of other areas of documentation or writing logo creation for example with the project browser they need they still need logos created for a lot of the projects so tons of things that can be found there in the issue queue which aren't necessarily code related or anything like that so as I said you know everything with the Drupal.org login so one of the other things other than having the Slack channel signed up is to get your Drupal.org login if you do not already have one so everybody in this room if you don't have a Drupal.org login please sign up now later on you might need to for example have access to certain features which you'll need to get one of the mentors to unlock your account possibly on so it's great if you can get that done now so then later on if you do have that you can like raise a hand and you know find a mentor in the mentor contribution space and they can unlock your account because for like first time account opening I think there's like a time period before you're able to access certain features but we can open those up for you so yeah please sign up that is you know not optional really and I'm going to talk about one of the first areas in which you can contribute so Drupal.org slash documentation is a huge huge amount of documentation about everything to do with Drupal we've got the user guides the evaluator guides and the local development guides and these are curated documentation and the curated documentation is quite formalized and then we've got the Drupal wiki which is like the Drupal eight nine and ten guides and the developer guide and Drupal seven guide and these ones they are a bit more free flowing in terms of how they are edited I'll go into that in a bit we've got the API information so we got resources about all the different APIs that exist there's an API reference document which is built up from code and there's other ones which are handwritten and the Drupal documentation also has like guides and guidelines on using Drupal.org itself so about creating user accounts content guidelines marketing guidelines so on so there's a ton of different areas of documentation that do need a lot of work it's very well known people don't like to write documentation when they're doing stuff they want to just get stuff done and they don't want to spend half the time writing up about it so it's not a surprise that a lot of these pages are behind some of them are behind by maybe five years so like for example this morning when I was up sorry yesterday when I was updating these slides I noticed there was some documentation that hadn't been updated since last time I updated these slides it's just how it goes so the curated guides for example for the the first section I talked about which is a bit more formalized has a bit of a strict update procedure you do need to create these assidoc source files and then use the issue queue to update them so it's not as fast and easy to update as some of the other guides but if you do go through those curated guides and you see something that's wrong or that needs updating it is updateable and there's a way to contribute like that and you can talk to one of the mentors and they can show you how to create these these assidoc source files the community documentation is a lot more like you know like updating or any wiki entry you have a little edit button once you've logged in and you've been approved as a real human being you get this edit button and you click on that and you know you can go and edit things sorry go back to this you do have to provide a reason why you're creating making the change and it will show up with your username so if you go in and you know mess around you will probably get banned so you know make sure you're not you know make sure you're you're sure about what you're editing so you know don't put in like silly things but it is open to all users and for example you might be reading some documentation about theming and there's like they're talking about attributes and you realize oh that's a very old-fashioned way of doing it that doesn't tie into how it is on Drupal 10 anymore let me add a paragraph about that. Translations again super super important there's tons of people in the world who don't speak English and there's a lot of different languages on there which don't have that much support. If you go to localize.drupal.org you'll find a list of the different languages and how much the translation files have been translated and in some cases it's very poor so if you see a language there that you speak and you think you can contribute back great you there's a team for each language and you can join up and start providing translation files for these for these languages as I said before you can contribute financially so if you go to Drupal.org slash association you can become a member that membership is you know part of what helps these events happen so yeah that's definitely super great way of contributing as well there's experimental features as I mentioned so if you go to this URL and you can just google it Drupal experimental features then you can find a list of different experimental features that are available for testing and you can go in there find out about them maybe create some issues if you find any the people who are working on these experimental features they really appreciate sort of feedback on the daily you know on from regular users as to their experiences with these features and some of those experimental features they make their way into call I think they were talking about that this morning in the keynote so yeah it's it's great if these things can move forwards because some of them are pretty pretty important the contributor guide is an area where you can find contribution tasks to do so after these events if you're looking around and you're like oh you know I could do some contribution I've got an hour free you can find a task that's a very short you know small task that's for like a short period of time and there'll be a list of their of different tasks that people put in when they when they know about them they'll put in these tasks into this contributor guide it's not always totally up-to-date the issue queue is the most up-to-date thing but there is definitely tasks in there so you know you can poke around and see if you find something in there after we cover everything else in this workshop people are going to be taken over to the mentored contribution space that's across in the other side of the building and the dynamic of what's going to happen there is basically as follows we're going to find the table with other people hopefully you can do contribute on your own of course we we just want people to work together as a team when they're first trying it out we don't want people to be feeling isolated and like there's just stuck on their own doing something we want everybody to you know collaborate together and talk and you know it's a bit more fun that way then that table is going to find an issue to work on or maybe there is already an issue at the table and you're joining them and that issue could be some like logo design it could be something from the issue queue it could be documentation review there'll be something that you're going to figure out to work on and there'll be mentors to help you do that so you don't have to worry about finding it somebody will be there to help you find it but you kind of want to agree on something to work on if it is something in the issue queue you'll be updating the issue queue and writing hi my name is Chris Dark I'm at Pittsburgh 2023 I'm going to be working on this issue today and I'm hopefully I'll work on it for the next week you can kind of give some information about who you are how long you're going to be working on this and you know why and so if everybody on the team is doing that then the issue will have all of your names in it and then you'll be automatically signed up to receive updates on the issue and so even if that issue doesn't get resolved during the event later on you can keep at it or if somebody else resolves it later on you'll still find out about it and you'll be able to see your input in there and then after everybody signing up on to the issue or whatever the task is that you're agreeing to do everybody will kind of come to consensus on what they're doing so maybe if it's testing something one person will load the issue in the issue queue and read the steps another person will load simply test to run the the to load up the environment and test that issue somebody else will be for example taking the screenshot and drawing a circle around the area where they saw the the bug and then uploading it into the issue and somebody else will be writing up you know a draft of oh this is the problem that we found with this issue so everybody having something to do on the issue kind of shares the load and it means that you're trying out different things without just being like stuck doing everything so yeah the mentors will be talking to you about all of this so don't worry about memorizing it now it's just so that you know what's going to be happening obviously if you want to work on something on your own that's fine that's great but you know if you do like to work with other people this is how we we do it and yep yes there'll be cute sorry the question was is this stuff for qa yes though the most likely will be qa tasks of various different sorts yes the once you get over there the mentors will be finding stuff that you're interested in so if you say I'm interested in qa tasks they can find something and during the time that you're doing the meant the contribution the ideas as well that you keep the issue updated if it's an issue in the issue queue so for example saying we have loaded the site on simply test and we are now trying to replicate the issue and posting that in there and then maybe an hour later or half an hour later or whatever being like okay we found the issue and we're creating screenshots all of these things they it might sound like a lot of noise but it kind of shows to other people that you're working on the issue and it also allows you afterwards when you're looking at the issue later on maybe a year's time to remember what you did and how you did it and you know what were the steps and it's a good way to keep a record of it so keeping the issue updated and not just you know working away and leaving it ignored the one of the other reasons for keeping the issue updated um is so that other people who maybe are elsewhere know you're working on it not to you know try and work on it as well um and after this event is over when you go back home or you know in a few weeks time or whenever you've got some free time um yeah try to keep contributing if if this issue that you're working on hasn't been resolved or you're doing some qa and you're queuing something that hasn't been finished or you've got some logos that you've left halfway designed um hopefully you keep the momentum going and you can carry on and finish those things um but even if you don't um just keeping track of the fact that somebody else maybe finished off the stuff that you did that's great you held a part in that so um yeah definitely try to keep the momentum rolling it's it's very easy when you get back to your your own lives to kind of forget about stuff you did at a conference but um we don't want this to be one of them um so i keep talking about the issue q and some of you might know what the issue q is and some of you might not um the issue q is a list it's a list of tasks basically they might be issues the word issue might sound like a problem but they're not necessarily problems they're just tasks so sometimes they are like sometimes it's a bug sometimes it's a feature request sometimes it's a you know just okay we have a situation here where we've got two different types of language used which one do we want to use um so anything that's a decision-based sort of thing um any sort of tasks just like you might have in JIRA that goes into the issue q we are talking right now about the contribe sorry about the core issue q we're not talking about the contribe issue qs but every single contribe module has its own issue q um during this event we focus on core because we can't just focus on on everything um but every single contribe module will have its own issue q um so yeah in the issue q we'll be reporting issues updating them triaging them which means you know to go through the list and sort of check are they still valid have they got the right details etc um creating merge requests which is a git process for um you know basically requesting that code be pulled in um providing feedback so for example looking at somebody else's contribution and saying oh this is my opinion about this this looks great or this still needs work etc um testing so yeah okay somebody made a patch pulling that in running it seeing does it actually resolve the issue that was originally defined so to get to the issue q you could go to Drupal.org slash project slash issues slash Drupal that's one way to get there that will just bring you up to the full list of all the issues for Drupal core um and you can also use this bit.ly which is uh Drupal dash novice so bit.ly slash Drupal dash novice and that will bring you up to a filtered list of novice issues so we go through and we try to find issues that we think are good starting issues for people to work on during one of these events now sometimes these issues end up lasting a lot longer and become not novice but they still have the tag on them we try to spend time doing issue triage before this event to weed out those ones that have become overly complicated or that have no longer they're no longer relevant for some other reason so if you go to this URL and I'm going to go to it now on here let's see is this showing up hang on hopefully this loads but yes the bit.ly basically takes you to this URL and you'll see this is with the advanced search enabled I don't think I mean one of the reasons you need the Drupal.org login as well is the advanced search I can't remember it didn't used to work without being logged in so if you can't see the advanced search options that might be because you're not logged in but in there you can add a tag of novice and we've also added a tag of Pittsburgh 2023 so if you type Pittsburgh 2023 it should update except it's not for some reason did I spell it wrong no there it is so you need to choose it from the autocomplete if you don't choose it from the autocomplete it won't actually use the right tag so and you want to choose is all of you don't want to choose this one off because otherwise you're going to end up with issues that are either novice or Pittsburgh 2023 so that's how you would find issues for this event but for example if you know there's other tags so I think the bug smash initiative has a tag so you might want to look for novice bug smash issues so you might want to add instead of Pittsburgh you might want to choose a bug smash tag so there's lots of different ways of finding things on this issue queue you can filter it by things that need work by things that need review you probably don't want to look at closed items so there's a few different you know there's open issues at the top we'll find anything that's open in multiple different states but yeah if you want to be doing something that needs review then you can choose that for example there's different categories there's different Drupal versions there's different priorities components so there's various different filters that you can use to find something that you think might apply to your skill set or your interests once you've found one of these tasks you can click on it and take a look and see what it's about and the wi-fi is a bit slow so apologies that it's taking forever to load maybe I'll go back to the slides while that's happening I'm going to show you the moment that the issue will need to have seems I have no wi-fi that's great okay so sorry I can't actually put into presenter mode um the issue will need to include various different elements as part of the description for you there we go for you to be able to properly work on it no it's not working ah okay so the issue will have a problem or motivation so it'd be like the text on this menu item is not readable because the colors don't you know there's a problem with the colors so proposed resolution change the color of the hover state to this or the active state or whatever it is uh remaining tasks um let's say somebody's already worked on it and the remaining tasks uh you know load this up on multiple different browsers um test and confirm set post screenshots and then you know write up what you found uh ui api changes so if it's actually a ui element for example you might want to post up this is a change to the ui I've discussed it with other people who are involved in the sort of general Drupal core ui team and you know they agree this is this is good um as I said screenshots if needed these are all things that you want to have in the issue summary um if you don't have for example the remaining tasks you might end up having to read through 20 or 30 different comments to figure out oh actually they have done it it's just waiting testing or they did do it but there was actually a problem with the fix and it was missing part of the fix so we still need to do half of the task so having the remaining tasks actually listed and up to date is super important let's see if the issue queue is caught up okay um is this the one I clicked on yes this one okay so for example in this case changing the enabled alignments checkbox options to title case and somebody is saying you know here this is what they the problem of motivation is um ideally this issue would have a bit more in terms of information up here um so there's no headings or anything like that normally you'd have something that's the heading like problem and then another heading which is remaining tasks and and so on so this issue itself uh as a novice issue is workable but also another contribution thing that you can do other than actually working on the issue is going through the issue reading what's in the comments and actually filling in those missing parts of the issue description so if you click on edit you can go in and edit the information about the issue and so for example here's the novice the issue tags for example but here in the issue summary you'll see it doesn't have very much information and there is actually down here some links about um issue summary templates and so if you open those you can find out about what you should be putting into the issue summary field and if you see here there's an issue summary template for example so you can see okay problem of motivation uh steps to reproduce so on and so in this case you might want to actually update this issue and put in those headings put in the remaining tasks put in anything else that you think is relevant to the issue and then in that way you've contributed just by updating the issue and making it more readable is that a personal it's yes it's just the wi-fi it's a bit slow yeah that's okay we got a man on the internet speed so good stuff um yeah so updating the issue to make it more readable to make it more clear what is left to do is in itself a very important part of the contraband um if you heard of the keynote where they were talking about bug smash you go through and you find there's tons of bugs that are just sitting there because it's not really clear what is left to do and people they're trying to find something quick to work on they go okay that's just going to take me far too long it's going to take me half an hour to read through uh i don't have time for that i'm going to find something that's more clear so updating that there's updating that there's the categories there's the status for example so in the case for example it maybe just needs review so you change it to needs review there is information here about the status value so there's a link here where you can follow through and read up on what these things mean so that you don't put it into the wrong status component information one thing that we don't want to touch is the assignment we don't want to ever assign it to ourselves call issues stay unassigned please um but then once you've actually put in this information you've put in that you've updated the issue summary um then at that point maybe you're going to say you're volunteering your own time so you check that or you're putting in time for a company so this ties down to things like issue credits uh companies can get issue credits from work done or you as a user yourself you can get issue credits um so when you actually make an update and then that issue gets followed through and gets resolved you will get an issue credit for the work that you put into in this case updating the issue so as we said the format here is not really consistent with what we're looking for in an issue we need more information but once you've actually updated that either you or somebody else can carry on and work on it and go okay now we know what the next steps are um so it's a great first step to get used to the issue queue um so I'm just seeing where I'm at okay and some of these issues will have patches so you'll see here this patch and it says it fails at testing so the old way in which issues that were had some sort of code or something in the code base were updated was through patches and patches look like that and this is how it used to be you'd have all of these line changes so you know they're adding and removing lines of code um we are no longer doing that so the patches are still there but going forwards we are using issue forking and merge requests so for everybody who isn't planning on doing anything to the root of the code base don't worry you don't need to know this if you are working with a code base then yes you do need to know this um um there is a whole page about uh issue forking merge request there's a video you can watch about it there's tons of information um but what you would see on an issue if it doesn't have an issue for because it's got create issue fork and there is other issues which do have an issue fork let me see I think this one might again it's slow so this one here has an issue fork and if you click on it it will go into the fork and git lab and so you can see the changes in here I'm not going to go into all the in-depth how to use the merge requests and the issue fork of git lab there's a load of information about it and we don't really have time to cover it right now but in the mental contribution space you'd be able to find out about it you'd be able to find out how to create a branch and uh within your issue fork and then create a merge request say this is my result resolution to the problem so on and to also test it and check that um but to that point um if this again loads um the merge requests which you will hear mentioned they basically just mean we've got some change that's happening and we want to bring it into duplical uh so for those of you who don't know what git is it's the version control system that we use to keep track of the code base and that code base might be code but it's also documentation it's also lots of different things it's not just but we call it code base um and within that version control system you can have forks you can separate out a new version of that code and make changes on that and so what we're trying to do with what we're doing with merge requests is you have your own separate copy of everything you make changes on that and then once you're happy with that and other people can contribute to that they can then you can then make a merge request which brings it back into the fold back into duplical and so then at that point people can test those updates and check the code do a code comparison check and see what's going on okay this is great this needs a change um it means you don't end up with like 50 different files which is what we used to have with patches where you'd have to make um a patch of a patch and an interdiff that says the difference between the patches and it was a nightmare so this is a lot better believe me um so as I said with uh forking merge request you create an issue fork which is within that button that's on the issue um then you create a branch on that fork for your issue and then you make changes and you make a commit with a meaningful message and then you can create a merge request and then somebody can um merge it into the project so for these things we do need some tools so some of these tools are useful for development some of them are useful for testing uh for qa for documentation some of these tools are relevant um there's a bit of a gray line like some documentation does require updates to code to update the documentation that's in the code so once you might not know anything about code you can still fix uh you know typographical error in a document block within some code so it's a bit of a gray area in terms of what is code and what isn't so I'm just going to cover the tools that we can use for all of this stuff if you go to Drupal.org slash tools you can see a list of different tools that are available we have testing tools for example and I mentioned this before simply test simply test.me sorry simply test.me allows you to spin up a version of Drupal with a given version with specific contrived modules with specific patch files load it up on the browser test it out you can log in on there you can log in as I think it's admin admin as the username and password and you can go and do whatever it is that you want to try out on a Drupal site so for example let's say there's a problem that you've seen when and I use it for this sort of thing when say for example you've got one module that you've just installed and it's looking weird and it doesn't track with what the documentation says and you're like oh is this actually a problem with the module or have I got something else interfering with it with that's breaking it so you can just go into simply test spin up Drupal core with the same version you're using and just install that module and nothing else and then oh okay it works so what else have I got working running at the same time that maybe is interfering with it and maybe you add that in and until you find it and so it's great for hunting down these sorts of issues but also if a ticket if an issue has you know oh we've done all this here's the update here's the patch because there's people to do using patches you can then take that patch file and add it in here as a link and then confirm that that fix has been done so very useful for testing if it's a merger quest you can actually spin up live previews using tugboat so it's not always there if it doesn't say view live preview there might be a problem and somebody needs to go and press a button somewhere there's some very smart people who deal with all of the background stuff that happens that takes these pull requests and you know spins up environments and you know creates these testable environments sometimes these things do have a glitch so if you don't see view live preview then and it does say that it's you know it's all green it's all testable then do let somebody know maybe somebody can go and take a look at it if it says suspended that just means that it's actually dormant because they don't want to have them running all the time if nobody's looked at it in a while it's just going to shut down until somebody tries to view live preview again so there's two different ways that you can load up a version of Drupal with a fix in it to test it and for visual regression for qa for just review and test by community processes it's super easy to do and you know it doesn't involve any technical knowledge to get these things going for development tools for actually making code changes there's various different layers of or levels of development that we can use so Drupal pod is a tool that we've been using the last couple of conferences and it's great because you don't need to download or install anything you okay take that back you need to install a chrome extension or a five fox extension but that's not very painful so that's one of the first tools we're going to talk about but there's other ways that you can set up tools there's local development environments that you might already have like you might have maps set up and you've got your setup for that or there's a ddev quick sprint setup which you can download which will get you going as well but Drupal pod is the one that we want to focus on for these events because you've seen me having trouble with the wi-fi connection if everybody here is trying to install docker at the same time you'll be here in five hours time and you're still stuck and that has been the problem in the past when we used to have a lot of tools installed people will be trying to install stuff and three hours later they're still not getting anywhere we want you to be contributing and learning and not stuck there looking at you know very slow progress bars so uh the Drupal dot Drupal pod project I think you can go to you can go to github.com slash Charles slash Drupal pod um Charles the guy who who sets it up but I think you can also go to Drupal pod.com or something I think if you google it it will show up sorry I forgot the URL um and that will allow you to download an extension and there's also a set of instructions on that page and he'll go through like all the steps that you need to do to get everything set up it's very simple you do need to have a github account and I know Drupal is on gitlab that's very confusing but the authentication method for gitlab doesn't currently work with this so you do need to have a github account which it will use to spin up um it's basically git pod behind the scenes which is a remote working environment and it will use ddev to install Drupal on that so okay um so I'm just getting a note if I do have issues again I'd be asking everyone to turn on airplane mode so uh yeah if I do that just be ready to turn on your airplane mode for now we're fine um but yeah once you actually get the um the Drupal pod installed or the quote sorry the extension installed and you go to Drupal pod it will ask you to authenticate with github and so if you can do that yeah you will need a github account but then after that you can spin up a development environment uh it will have a preview so you can actually view the the code the the site sorry you can share that url with other people so you can bring up um a code base that's already there an issue that's already there bring a top on your computer see the preview on the top corner uh share you make a change in code share that url with other people in your slack group that are working on the issue together they can then also see that change make a screenshot of that uh you can share your workspace so you can actually share the url for the code so they can also code in the same code base at the same time as you often your browser last year oh it was in Prague we had a guy we were experimenting a bit we had a guy do it on his laptop uh his ipad sorry so you can uh yeah you can do Drupal development on your ipad if you want to um there is xd bug on there there's uh vs code and php storm are both available in this remote environment so if you have a preference of those ids you can use it um and yeah you can bring in with the extension you can bring in a branch of an issue fork to work on or you can bring in a patch and it will load it into the environment that you're working on ready to work um sorry i got ahead of my slides so yeah so vs code or php storm you got private and public site previews you got xd bug shared development um but do follow the steps on the drupal pod um read me because there is some caveats again the using the github authentication not git lab and there's a few other steps there there's a a checkbox that you need to check one time um so once you follow those things pardon me if you have a problem with any of those steps so you get stuck talk to one of the mentors maybe they'll be able to help you out you might need to go back and reset something um but all of this is running on your browser there's nothing being installed on your machine other than the extension so if you've got a laptop that's locked down for work and you can't install things um even if you don't have the extension you can still get this working you just need to there's another work around for that um but basically as long as you can hit a url you can get to it so for example if somebody else has the workspace set up and they share that url with you you can just load that up in your browser you've not even installed the chrome extension um so yeah it's really powerful for these events just to get up and going and get contributing and again when we're working at the tables with other people and we're working on an issue together we want to be on the contribute channel and we want to create a comment on the contribute channel like hey we're working on this issue post an issue link um and then within that thread because in Slack you can do threads within the messages within that thread you can just chat about the issue together so you will get into the thread and then you can post and share links and chat and especially when it's a loud room and these rooms do get a bit loud everybody's wearing masks everybody's starting to talk louder and louder and louder it can be hard to hear so sometimes it's just easier just to type on Slack um and in that way as well everybody else who is helping out in the room can go and look at your conversation and see all the stuff that you're working on and oh yes we can see in this chat they're talking about this thing I think maybe they need some help with something I'll go over and talk to them so it allows us to to help you guys and girls and everybody sorry English expression um it helps us to figure out whether or not somebody needs help or to actually just get a feel for how things are going uh we don't want these contribution efforts to happen in a vacuum we don't want it to be something that was talked about in the room and then you forgot about it and you can't really remember what you were doing or who you were doing it with we want it to be something that's on the record that you can then go back to and you can check and you can remember oh yeah I was talking to this guy let me just fill out with him or I was talking to her you know like so having everything on the contribute channel and everything in the issue queue helps us keep a memory of that so yes again super important that we have that and then finally we also do have videos about a lot of the stuff I've been talking about so if you go to bit.ly slash drupal-contribute there's videos where you can go and check um how to do like things around uh documentation or there's a video for example about how to use drupal pod um so you can go back and watch these videos if you want in your own time maybe next week or you know if you've got half an hour and you're not doing anything right now before you go and do mental contribution but hopefully you will um yes you can go and watch those videos and uh oh that's the wrong link please ignore that link I forgot to update the last slide um I will um I can post these slides into the contribute channel later on so if you get onto the contribute channel I will post these slides sorry it's been busy um but yeah that's all thank you very much for being here and uh now we're taking questions if anyone's got questions just put your hand up there'll be a microphone moving around over here the fake mentor what sort of uh system does uh does the drupal.org used to keep track of the tickets like I've used JIRA but how does drupal.org have its own system uh for keeping drupal magic for for keeping people on track having so many especially we got a whole room full of people nine issues to work on in the novice queue uh how does it how does it keep things together so there's nine issues that you're seeing right now there's actually other meta issues that aren't necessarily in that list that we create other issues from the issue queue itself is a core part of drupal that they're trying to move into gitlab um but right now and from you know since a long time ago it has been basically a you know uh homebrewed uh issue tracking tool soon it'll be all in gitlab yep and there you'll have canband boards and you'll have issues you have better ways of organizing right now meta issues are our main way that's an issue that has issues it's just simply that and we have issues for some of those as well and some issue issue issue those are called initiatives and there are initiatives that have meta issues that have issues yeah and so many different ways we're doing the best we can folks yeah any other questions no what is that sound uh that sound is a sound of your destiny turning to go to the mentor's contribution space and get started so yeah everybody if you want to go and do some contribution if you walk that way as in uh down the hole towards the light walk towards the light and then walk through the light and out the other side and you'll find your way to the mentor contribution space before the mentor contribution space is the general contribution space don't go in there unless you actually have done it before because they're trying to be a bit quiet in there um but past that is the mentor contribution space and there'll be Greg at the door he'll be talking to you finding out what you're interested in working on and finding somewhere for you to work so uh thank you very much for coming everybody we're a good flow going and then he did anyway