 And I didn't repeat it for the, anyway. Hi, I'm Ellie. This is my presentation. It's called Mentoring Metamorphosis. Moving on. I'm E.K.L.1773 on Slack and Twitter and pretty much everywhere. So if you need to find me, I'm either me or other me. Pretty Google-able. That's me in a tree. So a little background on how I got into this. I started with Drupal in 2013 or so. I was teaching myself to be a web developer. I've not quite succeeded in that because I've become a communications and marketing person for the moment, but I am still writing some documentation and contributing to Drupal in non-code ways, like organizing mentors and helping out the Drupal Diversity and Inclusion leadership team and cheerleading, generally. But I came to Drupal because of core mentoring, and I went to just a random open-source event in the D.C. area in 2013. And I don't think Jesse's in the room, but Jesse Beach was there and said, hey, you should come try Drupal. It's a really wonderful community, and there are core office hours. You can join on IRC at the time that introduced newcomers to how to contribute to Drupal. And it's kind of similar to what we do at Drupal Con's now with the first-timers workshops. So unfortunately, core office hours are no longer a thing, since we've gotten Drupal 8 out the door, and primarily now we're doing mentoring and workshops at Drupal Con's Drupal Camp's other large events. So that's how I got involved with the team. We've got Drupal Con Vienna on the left and Drupal Con Seattle team on the right there. So historically, we had the core office hours online that really focused around enabling newcomers with tools, with understanding the issue queue, with getting an account on Drupal.org, with joining IRC, now Slack, and just getting more contributors to make even the smallest of contributions to Drupal core on board to do that on their own. And at this point, we're as Drupal Diversity and Inclusion person, I'm also very interested in encouraging more people from underrepresented groups in contributing to core, but I think that's a slightly related talk. So what do mentors do? It's not giving you a fish, it's teaching you how to fish. This is something that XJM taught a lot of us, that you really need to show where to look for the information you need and how to ask when you need help. So that's how to dig into Drupal.org for various documentation and guides and getting involved guides, all of that, and also what channel to ask for help in and how to ask. Ideally we are providing a neutral and friendly route for new contributors to approach contributing. That's getting you in the door without saying, oh, here's an issue, go for it, or no, no, you did that wrong, start over, we're pretty objective and hopefully very helpful. Has anybody here actually been to the first timers workshop yet this week? There's one on Tuesday, no? Okay. Well, there's one tomorrow morning too, I was hoping to get a quick vote on how that went, but that's cool. And we have the same tools and documentation to support new contributors at events and afterwards, so you can continue on your own. Drupal Core Mentoring, if you saw the keynote on Monday, I gave a similar overview, started around Drupal Condemnber, XJM got us going with the Core Office Hours and sort of metamorphosed from there, is that the right panacea? And there are a lot of people to thank along the way, so XJM and SCT and Allie Mack for my very core mentoring team for me, like really got me started with the concepts, passed along a lot of wisdom, and got things going for everyone to use. So at this point we're more focused as a mentoring team on organizing for the large events, Drupal Con North America and Drupal Europe. There are also subsets of the team who focus more on Drupal camps and use some of the same materials for those, and we're always iterating and changing, which I'll get to a little later in the presentation. So what does it take to run mentoring at a Drupal Con? We have all of these wonderful leads and I left the dots at the bottom because I'm terrified of forgetting someone. But we have folks who are running the first-timers workshop, we have folks who are running novice issue triage, so there are pretty straightforward issues to work on straight away for newcomers. We've got the booth downstairs you've probably seen, there's always somebody there to help you get started, or if there's no one there, we leave materials on the table so you can self-help a bit. And we're also always available in Drupal Slack. Yeah, I could call everybody out, but get the idea. Mentoring lead coordinator is the role I usually play. It's often running meetings, organizing things, keeping track of issues. We have a planning issue for every Drupal Con that tracks similar tasks just to organize everything from the booth to the workshop to the novice issue triage, so it's all documented where we can all find it. And also being a mentor to other mentors and coordinating the efforts. So it's a lot of project management, honestly, and that's mostly my role. The photo is from Drupal Con Nashville, we organized a community panel, so these were all the leads, mentoring leads for Drupal Con Nashville, and everybody presented for a couple minutes on what their role entailed. Communications lead is a role I have done in the past, and I am super happy that Merrill is taking it over for this Drupal Con, and that's another thing we're really working on is having deputies in each role, so there's always somebody sort of in training to take over, so none of us burn out, and I'll probably talk more about that later too. This is our Twitter page, we try to put info out at least around Drupal Con, we usually do email communications from MailChimp as well, but we've got some GDPR opt-ins to collect first, it's an ongoing process, and also just coordinating with the conference organizers, whether that's the Drupal Association, who have been really fantastic supporting us and shipping things around the world from our banner to the box of supplies, and just arranging the contribution space as well, putting up walls and TVs and all that, so communicating with the conference organizers is also quite key. Boost lead, this is actually just from yesterday, we've got Ray Gutt and Merrill sitting in our booth downstairs, Boost lead organizes other mentors to sit in the exhibit hall at the booth, we've got a spreadsheet, everybody signs up, try to cover all the time if possible, and the booth is also a place where any mentor can hang out and greet passers by, whether they are folks who want to be mentors or folks who want to be contributors, we've got a handy sheet available to help you participate in the booth, just so you can answer some basic questions or point someone to another mentor who knows the answers. This role also involves the logistics, like stickers, task cards, and mentor shirts, the task cards are these things down here, they are color coded, sorry, the task cards are in the lower half of the photo, and they have sort of steps on them for what you might do in that role, so there's one for documentation and just some steps through that, and you kind of go through them in order if you wish, or skip around, take a look, they are downstairs, they don't think the exhibit hall closes quite yet, and yeah, and we're right next to the DDI booth, so we often sort of overlap a little bit, a lot of the mentors are also diversity inclusion folks, diversity inclusion folks are also mentors, and whoever is around in a booth can often greet folks at either, which is kind of cool, Navas issue triage is just collecting some issues for folks to work on that won't be super intimidating to start, so that's something where a new contributor can come in and get into the issue and have a good experience with it, so they're not going to be reading through 200 comments to figure out what's happening, it'll just be pretty ready to roll with, the bit.ly link there is for issues tagged with DrupalCon Amsterdam, the tag on Drupal.org is Amsterdam 2019, I didn't pour myself water, that was foolish, and we run the issue triage on, I think it was Monday this week for collecting the issues in advance, and they should all be ready for you tomorrow. First time contributor workshop, we used to only run this once a week, thank you, but we found that there were a lot of folks who maybe couldn't stick around for Contribution Day, maybe, thank you, pardon me, and folks couldn't stick around for the Contribution Day, or what's really helpful for conference Wi-Fi is getting tools and stuff installed earlier on, so then a new contributor is enabled to keep contributing throughout the week. Either way, we've now got two different workshops at most DrupalCons, and I think it's going really well so far, oh I should also say that that's, the workshop introduces you to a lot of the core tools, whether you are doing a code contribution, or documentation, or organizing, or marketing, or what have you, there's some training that will work for anyone, and then if you do want to work on code, stick around and install the tools, so forth. Then the Mentored Contribution Room lead sort of sorts people out into the room, get you to the right table for an issue you want to work on, or initiative, or whatever it is you want to do, that one's pretty straightforward, and then we're on to my update section here, which is good, I think I'm making good time. What is next for Drupal Mentoring? So as I said about the workshop, we had some discussions after Seattle about how the workflow happens in that workshop, and it seemed like I think we were starting the workshop saying start installing the tools, start downloading, start running this process, we'll go through some slides, show you some of the basics, then we'll come back to the tools installation, which actually left a lot of people who didn't really need the tools stuck in the installation process, so this time around we've changed things a little bit, and we're hoping that we just enable everybody to do the basics of contribution with the issue queue and Slack and other tools like that, and then continue on to tools installation, technical tools if needed, and the tools package I'm talking about is something called Quick Sprint, it's a wrapper around the DDEV local development environment tool that provides just some of the basic stuff you might need if you don't already have something set up on your laptop, so and this chart was something Gabor put together to illustrate how you might select what room you're going to, so maybe you want to contribute, you have some time to do so, yes and you have the tools that you want to use, if you don't you go to the workshop, if you do just need help with the process like finding a task, then you can head straight to mentored contribution and learn how to do the process of contribution, so this float chart inspired us to make a bigger float chart, which is actually a little small for even me to read right here, but similar, I'm not going to walk away from the mic, similar idea, there are different types of contribution you can do, which are represented in the colored boxes there, yeah, you get the idea, we like float charts, I like float charts, I don't want to speak for everybody, and this was Chris Dark's work and he also put together this for once you're inside the workshop, just as a simple way to say what do you want to do today, I'm here to work on code and patches, go to Drupal.org slash tools and follow the instructions to start downloading the tools and otherwise I want to contribute in other ways, there's a sample list of other ways to contribute, just wait for the presentation to start and you'll learn how to use Drupal.org in the issue queue and so forth. We've worked on a lot of other kind of new stuff recently, so the toolkit itself started evolving a little bit and that's always a lot of coordination over time zones and what is going to be in the toolkit, what do new contributors really need to contribute, which is something we're still defining in an ongoing process, but overhauling the workshop was kind of our big change for the past year, before that there were changes around transitioning away from the big push to Drupal 8 and the push to Drupal 9 has been very different, I would say, and yeah, the other important exciting, I hope exciting new thing that we're working on as a mentoring lead team is actually defining our roles better and talking more about formalizing our governance and how we can bring in new people to take on the roles, how we might evaluate people for those roles and just, I think it's a sign that we are growing in a really good way that we need to formalize that process more, so that's something we've really just started in the last couple weeks and that's the metamorphosis part. So, I've got four minutes left, I think. Do join us tomorrow? Questions? Not one question. I need to start talking slower or something.