 Savadika or word for us howdy So it's wonderful to see you here today, especially it's late three days of sitting and talking with other people Meeting new people long-time friends and maybe already thinking about going home And with all the good reasons not to you show up at this park So I'm delighted to have you here and to tell you about my journey of the no-code contributor to the Wurtenpress Gutenberg GitHub repo and I'm here to tell you you don't have to be a developer to contribute to WordPress and have an impact So show of hands who in the room has contributed to WordPress either on Friday Why excellent well, thank you So which team meta yeah, just shout it out. All right Hosting yes, awesome. Thank you So and that's also part of the contributor journey to open-source projects There are a lot of reasons not to and still thousands of people all over the world after hard days work on the weekends Volunteer that time to make WordPress a better software and the internet a place for all people so Why contribute? Well each of us and if you were here for Harry's talk There were other business reasons as well, but each of us has their own reasons some of us Scratch the personal itch. They see something they can make better and they do it For others, it's the community to belong to and that's a wonderful community to belong to and for others it's to There are good business cage as well to be on the pulse of creation to be I also have influence in direction, but you need to be at there at the same time And for others it's a way of giving back after building a business or a life On WordPress and standing on the soldiers shoulders of giants So Did you know that one make on make dot repris dot org there are 21 themes No teams not teams teams And they have their websites there with their contributor handbook and everything So but not all teams contribute code the marketing team Documentation team community team are just a few examples and then there are teams who contribute code that I can still need help of non contributors to Being project managers being meeting facilitators to test things and to do bug reports for the system So it's about the Gutenberg repo. So what is Gutenberg? Confuses a few people Often we are also at the in the project. We are not very concise in how we define Gutenberg First of all, it's the name of the feature plug-in That is the beta plug-in for the new features on the block editor and site editors And people install the plug-in provide feedback test things and build things But for every word press major release The features added to the plug-in between last release and this release Get merged into core and then it becomes the block editor the site editor and blocks So and how that works for the core editor team Is what we're talking here so examples for WordPress 6.2 It will come out in March 28th It's now in beta 2 beta 3 comes out on 3rd on Tuesday We will have the features introduced in the Gutenberg plug-in from 14.1 or 14.2 to 15.1 and The Gutenberg plug-in code is to guest it in a GitHub repo So what our github and what is git and github just briefly get is the version control system invented by the same guy who brought us linux linus Torwolzen and It's a distributed version control system for tracking changes in source code for software development github Is the software as a service kind of website? It's the social network of developers and those who built the software It was It also has some some great tools for project management project boards and also for private and Public repos for companies as well. So it's a And it was bought by Microsoft a few years ago So github can be intimidating for non developers at first very so much So and it has some very powerful tools So I started my first bug report in 2018 and now I probably check its notifications more often than Twitter or email GitHub is also a sick So you don't have to be there all day every day This is particularly important for a worldwide project like WordPress Because with the time zones of course more and more repress and more and more repressed teams actually will Or use github also to the non-code organization of their work Documentation comes to mind and also the community team had just a proposal posted About changing their workflows to github. So it's not a wasted skill When you start now with your with github so the session promised you a case study on no code contribution So let's look at things but before we dive really in I just want to put that out if you want to be See what's all about and the core editor meeting. That's the where the team meets is on Wednesdays 1400 UTC which is 2100 and in the China team. I think Just correct me if I'm wrong, but time zone really Yeah, confused me More than I like to admit And apart from the meetings most time couldn't work developers or on github so what to do what do I do when I go? on On on github before you do that Just to run down. You need a wordpress.org account. You need a github account You create a WordPress slack account and then connect your WordPress org account with your github account These are the four steps before you even start just because then you want to be You get into slack and you get your contributions to github Registered on the profile of your webpress.org account I Don't contribute code to the project. I am a terrible PHP developer and My JavaScript knowledge is improving But it's certainly not up to That level that I can build software for millions and millions of people I and you definitely don't want me to But I use the block editor a lot Leslie told you about good work times the good work times is the production test site for the Gutenberg plugin and When I see bugs I create issues I Create issues, but I also create issues. Well, I mentioned the bugs and annoyances and also inconsistencies. Yeah But I also create issues when I test new features for an article or so I test release candidates for the plugin Release and I also create issues when I think about feature improvement because I have opinions Yeah, and that's okay to have opinions, especially on github Because it informs everybody. This is another aspect. So we need the so When I run into bug and annoyances I Have an example for you for each of the four items. So just to see how it all kind of comes together how the engagement is and what is all to What's happening when you create an issue? So? so the first one is I had the idea that Yeah, you see these are early Early work that's Gutenberg 3.01 and that was in June and I had a had the Habit was still have they have it that I create my list write all the paragraphs Yeah, and then I select everything and then convert it to list and back then the list conversion was in the toolbar and all of a sudden I couldn't find it anymore And So I said, well, that's about yeah, if you have a new release and the features are not there where you expect them to be just that can't be right I thought and Matias Ventura the spark of Gutenberg so to speak He told me that well we moved it into the transform section and so I was a Yeah, that was okay, but it also I Didn't know how how I should feel about that. Yeah, what should I be embarrassed because I didn't know that? Yeah, is it a user kind of thing and it's all that but you you get over that embarrassment and then you learn about two things one is Read a little bit more about what the feature is but also it informs the designers That they made a decision that where the user Not necessarily follows them and that isn't as a good data to have for designers and developers so don't be shy and think oh if I if They should yeah, if I find something Wrong, it's me or at not the developers I think that's kind of a shift that you get when you do it a little more often So the next example what I have is test a new feature and that looked at the Like this, so I had a I encountered a new feature But when I added to a widget there was a calendar widget to the widget screen. I get a list of error messages in my browser, so I've copied the error message here as well and then something happened I've labeled it as a bug and then one developer was able to reproduce it Pretty much the same day, so it was tested. It was not just my imagination my system my anything and then three months later Robert Anderson came in and said well I can still produce it so it hasn't been fixed and Then a month later six weeks later a developer came in Finally that is fixed so we can close the issue so that's Quite that could be a journey of a an issue that you file Especially when you have new features that aren't work and they fix it So for release candidates and good work, I Normally just do smoke test whether the smoke test I I install it and see if something breaks Smoke comes out of my computer. It's just literally and it is Something that is very helpful, especially when a release is not yet done So I had this warning as immediately when I Activated the plug-in from the release candidate file and then This is and and one of the developers came in and said, okay, this is probably a result from a commit Or a code change and then there was it was labeled For the release do not punt means you can't release without having this fixed And so we got that fixed before the 7.3 came out That's another Journey of that and the last one is feature improvements that issue was something that With a classic editor when we wanted to see the code of the post you Changed over to the code editor And I realized with the block editor I don't want to have the full page in code editor. I just want to fiddle with the HTML of a certain block So I was wondering if that could be a manual item or so a shortcut to switch to the HTML editing on block level and So I I even had a little Mockup of the design where it should go and then Quite a few people chimed in that might is a that's a cool idea or I agree this is going to be a much more effective one and then we're developers who tried to try their hands on it to fix it and And There were actually two so sometimes even when you have a good idea or a good feature It still takes a developer to pick up on that and follow through in in an implementation so It can certainly be a while so I filed this when you go when I go back I filed this in 18 and the last developer Still tried to fix it in in 2022 so We are not there yet But that can happen. Yeah, not everything that you suggest will will be followed through But it's important to have the conversation to bring the opinions into the fold So and now it's your turn how to create an issue But before you create an issue, there's it's a two three things one is isolate the issue To the core block editor or the Gutenberg plugin if you test it on a site that has other plugins installed There might be a plug-in conflict that is not a result from the Editor but from a plug-in conflict that shouldn't be in this unless you can isolate which Plug-in that is search the existing issues for a similar Issue with labels and keywords Very often I don't find an issue I file it and then three days later I said somebody closes it because said okay This is a duplicate of this issue which had a total different title or a total different entry But the effect for the developer was it's the same package So they label it as a duplicate and then make sure that you follow the use of the bug report issue template and What does that look like? So you go to the GitHub repo and Click on new issue and they get four choices one is a bug report one is a bug report from mobile And then a feature request that has a different template and then a report of security vulnerability that shouldn't be in Shouldn't be in the GitHub repo. There's a best a better Oops a better place for that So when I go up here So the new issue template comes with a give it a title. So That's very descriptive Then make an effort to describe What what you try to do what you did and what you expected to happen and what did happen? and then The the most important part is and these the series of steps to reproduce the issue to reproduce the The bug or something like that because that's how other people in the On the project can then double check how that can be fixed And then when you have screen recordings or screen shots or coach snippet That's definitely helping and the other important if you issue a part is also the environment Make sure you Mention which WordPress version you're using which couldn't work plug-in version you're using and if it's a browser issue Also the browser version most of things can be browser issues and then also just the two checkmarks down here Selection please confirm the research existing issues For duplicate and then please confirm that you have tested with all plugins Deactivated just to remind you again and that's how you follow the The template Descriptions step to replicate screenshots or screencasts expected behavior and then environment information because given enough eyeballs all bugs are shallow the more people Testings so that's a quote by Eric as Raymond in the cathedral And the bazaar Book of 1999 Some of it is still valid, especially this quote. It's also called the the liners law in Honor of Linus for Wilson the Creator of git and Linux So if you want to be Part of the WordPress 6.2 You could also help test the beta versions that come out They there is a make blog on the test team That outlines the instructions on how to set up a local system The list of features that need to be tested and also a workflow for the testing and where you can report those Tests that would be and that is really helpful for We have that Do I have it here? No, I don't have it here So that would be really good We can always help have more testers on 6.2 it comes out the Beta 3 comes out on Tuesday Then we have the release candidate the week later and then the final release in March 28 That's the schedule for now if you if you don't want to rush into this right now what comes next with With the repo if you kind of are comfortable or if you don't have any issue yet to solve Go to the needs testing label So every issue that is not clear Gets a label that says needs testing and right now we have 22 open Issues that have that label so That's also how you learn to write good Step to reproduce instructions when you follow other people's steps to reproduce the error So you can go in and say okay, so the navigation block custom when you're not imported And you click on this So here's the description and then somebody else and here are the steps to To reproduce that could be one or you could also say Gallery block doesn't respect option of opting out of base layout styles. That's something for the developers more So yeah, pick an issue that seems to be clear for you Or you can participate in discussions join the triage team if you want to do Need some toolbox. I have four suggestions. One is to help check troubleshooting Plug-in the WordPress beta tester plug-in the core rollback plug-in and the Gutenberg nightly, which is a almost daily Plug-in copy of the Gutenberg plug-in that you can Install on your system and you get the latest trunk version the latest merge features Sometimes it was born out of the necessity that people that when I Created issue there was a time I created an issue and then a developer saw it and said oh, I think that was fixed in Two days before but there wasn't a plug-in release for that So I could have saved myself and the developer quite some time. So there is the Gutenberg nightly available to That you can download here and it you can actually update it as well Oops Yeah, so that's it As you as I said, you don't have to be a developer to contribute to WordPress To have an impact. So now you have another option option to do that I'll be happy to guide anybody through the process I'm on WP slack as at BPH Also on Twitter DMs are open private messages are open you can follow also Twitter Gutenberg times on the YouTube channel and Subscribe to the weekend edition and the slides are yeah, you can not see that in this one But up here. That's the link to the slides That's it for for me today I hope I inspired you a little bit to get your hands dirty on a github repo even if you don't do a code you can help developers quite a bit in Testing and sharing your opinions. Thank you so much