 I am much too tall for this. Hello. So welcome everyone to our community conversation on core contribution mentoring. This is the team, or some of the team. There are a lot of us, and there are even more mentors who will be mentoring on Friday, of course, and during the week and all the time. So what we're going to do today is introduce ourselves for starters. So this is, I think, everybody who's here. And if we could all find a mic and just say your name and introduce yourself with how you got started with mentoring. So for myself, I started in 2013 at DrupalCon Austin. Start with Leslie. Hi, I'm Leslie from Boston, and I got started in 2014. Oh, sorry. I'm leading the first time sprinters, so if your first time is, welcome. I'm Benji Fisher. I think that Portland 2013 was my first DrupalCon and the first time I mentored. And this year, I'm in charge of triaging the novice issues so that we'll have a good set of issues to work on. On Friday, we have a session to do that tomorrow at 1 o'clock. Hi, I'm Ashwin Kumar. I started mentoring from DrupalCon New Orleans. I'm Tara King. I started mentoring unofficially at Austin when Tim Erickson, who was mentoring officially, promoted me mid-sprint. And this year, I'll be doing some diversity and inclusion sprinting on Friday. Hi, my name is Joel Patet. And like Benji, I was at Portland in 2013. And I was my first DrupalCon as well and first time mentoring as well. And yeah, I enjoyed that one. My name is Jordana Fung. My first time mentoring was last year in DrupalCon Vienna. It was an amazing experience and it's not that hard so please consider joining us. Hello, my name is Mauricio Dinarte. My first DrupalCon was Austin and I was a mentee back then. And the next one was LA and then I volunteered to be a mentor and it's been an awesome experience. My name is Matthew Radcliffe. I am Radcliffe on Drupal.org. I was in Munich in 2012 and the Coder Lounge a lot hanging out with Tim Plunkett and XJM and Kathy at SCT. And I saw how much work they were doing and I said, I want to be involved in this. And so I stood at the door for two hours and greeted people in Munich. But my first real mentoring experience was also in Portland. My name is Colleen Clarkson and I've been working with Drupal since 2009. My first DrupalCon was DrupalCon Denver 2012. And I'm part of the Drupal Diversity Inclusion Initiative and actually I've been kind of, I guess I'm a mentee, I've been a mentor and that initiative has been fun. I've learned a lot of stuff. So if anybody wants to help out with the website for DDI, please shoot me a message and I'm also kclarkson on Drupal.org and Colleen Clarkson on Twitter. Look, I'm loud enough to get recorded. Oh no, it's okay. I'm Fatima, I first mentored DrupalCon Vienna which was the DrupalCon before this one. So if I can do it, and I'm a sprint lead this year so if I can do it, so can you. And we're looking for mentors to help us on Friday. So the sign up to be a mentor. I'm also on the leadership team for Drupal Diversity and Inclusion. That stuff is really important to me so come to the DDI booth and talk about it or help Colleen with the website because he's done an amazing job. Sorry, I'm bad with time zones, so I was like. No worries, I had to adjust my calendar a lot. Okay, so this is most of the mentoring team from Vienna, I do believe. Just a few quick notes on mentoring. Generally, I suspect many of you are already familiar with the program but mentoring really helps everyone involved from the mentees obviously who learned and pair up with mentors. But also, when you're mentoring, you learn so much because you're being asked all these questions that maybe you didn't think about before and it really cascades from there. So just becomes bigger and bigger until you have this whole Drupal community. So here we are. So very brief history of mentoring. We kind of started in 2012 when XJM suggested a core office day at DC Denver and she said that there was this really magical moment during the day when the mentees started becoming mentors and were helping each other so there was less and less work for the original team of mentors to do as the day went on. I think that's really key to the mentoring and being mentored experience is and I always keep reminding myself of that. We're always progressing. It's not a singular relationship. We're always progressing and learning from each other and just reading what XJM had wrote in 2012, I was like, wow, we keep saying the same thing. So I have to keep reminding myself that it keeps happening, I keep getting reminded of that. So a lot of our time and effort is spent organizing things at DrupalCons. So the sprints for Friday and the events during the week to familiarize everyone with the tasks that we will be working on. We do get some assistance from the Drupal Association to get our tools out to the world and there are a few very helpful mentors who keep office hours online as well. So few people have been putting in a lot of extra effort in the last few years especially including Rachel Lawson who's not here right now. But she's been going to a lot of the events in Europe and keeping up that end of things. So we'd like to move on to Drupal Diversity and Inclusion and this project, Zaterra. So I am part of the same Drupal Diversity and Inclusion group, I'm on the leadership team of that as well. And a few like, ooh, nine months ago, Drew's released a blog post talking about where code contributions come from, how they're supported and there's like one line that said 2.3% of contributions are from women, we think. And there was no other diversity talk or data and it generated a lot of discussion among our group about what can be done. And some of that is out of our hands maybe, we can't necessarily change the way that data is collected or what types of data are collected. I think we might be able to, but we just kind of with a great burst of energy founded something called the DDI Contrib Team. And in the past nine months, we've been kind of figuring out what we do, why we do it. And our focus really is trying to address barriers specific to people from underrepresented and marginalized groups. And one of the things that I think DDI Contrib Team specifically is looking at is the fact that DrupalCon is expensive and as much as like the mentoring experience at DrupalCon has improved my life and the lives of many others, it's hard to get to, can be intimidating. So that's one strategy we're doing and we're still figuring it out. We're so excited to be part of this group and I don't know if Kaleem or Fatima want to talk as well. So far, I just happened to, if you're not on Slack actually get on the Drupal Slack because it's funny because I never understood how to use IRC really. They're like, go to this IRC and it's like, where do you, what is this thing? It's been around since before the internet. But just I never could connect with anyone on it. So when Slack happened, it made it a lot easier and I just saw this diversity inclusion room and I went in there and myself and my wife do a lot of consulting and diversity and I just kind of saw a lot of the things that were happening in that room and I just felt like I needed to be a part of it and we decided to do this website and I was like, oh, I guess I'll help with that. I know a little bit about some things and it's been a really cool experience. My personal job, I'm a one person show so I'm not around a lot of Drupal developers so I don't get to speak to people and learn things and we put together all these issue cues on what we have to do and someone volunteered to be a project manager and I've never worked with a project manager before and it was awesome. Like somebody tells you what to do. Like there's a list of things that you're supposed to do and then they tell you how to do them and they write down like what needs to be done and like the color codes, like everything was so clean. His name is Alex, Alex we miss you, I wish you were here but for me that was like a learning experience that I didn't expect to get out of it and now it puts me in a better position and maybe if I were to leave and go somewhere else and get it applied for another job I can maybe use some of that experience to help me so get involved as much as you can and that's pretty much it. I have a question actually. How can we get involved in the DDI contrib team? What's the, other than joining Drupal Slack and going to that channel, what are the next steps for me as a developer and mentor? So the DDI contrib team has a D.org project that's like called DDI slash contrib and as Kaleem was explaining there is an issue queue and here are the things that we need to do for the website and there's also meetings every week or bi-weekly. Actually yeah, twice a weekend once a month so we have a lot of meetings. Twice a week and once a month where the team pairs up mentors, mentee and another person, maybe you should explain this. We have a couple different teams, we have like the site team that's working on our site that does, they did a bunch of front-end work which is super exciting. We have a backend team that's kind of been doing some testing and supporting people through testing issues, testing learning. So we have lots of meetings. I have cards for the diversity inclusion team in general so it can help and then pop in the channel, there's not that many, I try to say hi to everybody and I will say hi to you and I'm also here all week. And it's kind of like a supportive environment? Yeah, things like people not knowing how to put a comment on an issue, right? Or put an intro div. Yeah, all kinds of stuff. Cool, great, thank you. So next we're just gonna go into a little nitty gritty on what exactly it takes to run the Friday sprints. And it takes the entire team. There's a lot of work to do. We honestly deleted a lot of bullet points because it was ridiculous but you get the idea, you can just ignore them for now but there's a lot to do. Moving right along, we have the mentoring lead coordinator. Okay, so this time I'm one of the mentor leads and this is kind of funny because when I started like, I barely knew Drupal. I went to my first Drupal con with very little experience and I was mentored by others. I learned a couple of things and I met some friends. The next year I decided that I wanted to be part of that and all of a sudden they bring me on board and they give me all these responsibilities that I was like, what? But that helped me a lot to improve, to get new skills that I didn't have before. Even speaking at a mic, I was very shy before. But to be honest, being a mentor lead coordinator or any lead position is really easy. In short, you are mentor of mentors. Basically what you have to do is come to an online meeting once a month to prepare for Drupal con. There is of course a lot of work in between the meetings but it's just like if you have the time and you have the willingness to do it, it's like anyone can do it and we're always open to new people to come on board because we need help. Thank you. Next we have mentor communications lead, which is me. So for this we put out a few emails leading up to Drupal con with sign up, get involved, put yourself on a spreadsheet and there's also of course the Twitter account. Same thing, just mostly announcing events and keeping people in touch. So that's honestly really straightforward but important to keep people involved throughout the year. Booth lead, Jordana. Basically, thank you. Basically we kind of just set up the booth to make sure that there's somebody there to instruct people, help people out, help them figure out what sprints are sometimes as well. And I kind of also wanted to say it's not expected for you to know everything. No one knows everything. There's been many times I'm like, well, what am I supposed to do? Everybody will just pitch in help and we'll figure it out together, right? So it seems daunting, it's really not. We'll figure it out together. That's kind of what mentoring is. That is completely true. As you can see, we're figuring this out together right now. Novice issue triage, Benji. So I've taught first aid to Boy Scouts so I have very specific ideas about what triage mean. I prefer the term curation. We want all the issues we can get that are suitable for novices to work on at the sprint. And this takes a fair amount of time going through issues. You can just click on a link and find a list of issues tagged with the novice tag. But they're not all up to date. So we have to go through them, figure out which ones are still suitable for novices to work on, make sure that there's information in the issue summary so that novice can look at it quickly and figure out what needs to be done. So I've started a little spreadsheet. We'll work on it at the session tomorrow at one o'clock. And I might have a few things I've noticed that need to be fixed that I haven't created issues for because one thing that tends to happen is that after you put a lot of work into curating the novice issues, people around the world steal them. And I want them to be there for us on Friday. If we're going to spend this much work into curating them, I wanna make sure we can use them. One comment about the word novice in itself, sometimes it implies that it is something like minor or trivial or not of a lot of value, but that is not the case at all. I have seen novice critical issues. The word novice in this context just means there is something actionable to do and you can do without spending a whole day to figure out what are the next steps. Basically, a novice issue is something that you can start working right away. And one more thing. As long as there's a mentor present, I think we can stretch the usual meaning of what is a novice issue. And if you're planning to mentor on Friday and you have some issues that you know what needs to be done next and you can help someone do that, that counts as a novice issue and we can use that. All right. Microphones up there, okay? Microphone? Okay, I'll use the mic. For all those people at home. So something that came up several times over the years was that a novice issue sometimes is more about getting to know the issue Q and less about the kind of challenge presented by the item. So very experienced contributors might be fixing a typo and just getting it all the way through the process is actually, there's a sense of accomplishment and it's not terribly straightforward. So it's worth also picking novice issues that they're actionable right away, but perhaps they let people focus on the kind of process rather than the technical challenge. Four to three. On the other side, we have major issue triage, which is somewhat different. So I do, or I am gonna be the lead for the major issue triage and this is what happens when people find an issue and think it's major and then tag it as major and then there's a bunch of major issues in the queue. And so what our job is to basically look at all the major issues, go through them, make sure they're still major, maybe test them, maybe upload some more updates to the ticket if it's really old. We have a flow chart that kind of helps you through this process. Really, it's about helping to clean up the issue Q, basically. It's easy. Show up. Matt? Are you sure? Yes, so this is the first time sprinter workshop in which we will teach new contributors exactly how to set up their tools on their personal computer or share machines. And I think there's been a lot of work to put in recently on some new tools. So we're gonna be using those on Friday. It's very exciting. Yeah, the only thing I wanna say real quickly is the goal of the first time sprinters workshop is to make it a great experience for first time sprinters. They come, we give them the tools, we set them up, we let them work on an easy issue. And to have them be successful leads them to be contributors going forward. So that's critical to what we're doing. And then we have the core mentored sprint room lead. Joel? I've never been in this position before, so I can get to try it for the first time. But I like, on previous, I usually hang out in the mentored sprints and jump between tables. And it's kind of similar, but I would be kind of helping out the other mentors in that room, making sure that they get what they need and can find who they need to help their mentees. I'll also be a sprint mentored lead. So we're probably gonna have, since it's a big job, and you have two rooms. So I'll probably be in the first time workshop, while Joel will be in the mentored sprint room. And just being able to coordinate with Mauricio to make sure we're finding the issues, we're seeing what we can do to help mentors and the tables and contributors move issues along. So we can get that accomplishable task by the end of the day. Great, so we are moving forward with some plans for the future. We've been doing a lot of retrospective contemplating lately. And I think we have a bof coming up on Thursday. Yeah, it's the last session. Yeah, the last session on Thursday. So definitely stick around for that. Join a longer conversation. Yeah. Should be good. We have a lot of planning to do, basically. And... So you have a live commit doing a sprint? That will be on Friday. On Friday. Yeah, so we will have a live commit Friday, hopefully. Probably. It'll be fine. Everything comes together in the end. So that's, I think, most of it, yeah. One thing that I want to add and something that is really useful for me in many ways, I am from Nicaragua, traveling to a conference is a little bit harder than people from the States. One thing that the mentoring team does at DrupalCon is that the association gives us eight tickets to distribute to mentors. So if you want to be a mentor and you cannot come to DrupalCon because it is too expensive, at least we can provide a ticket. There are only eight slots per DrupalCon. So, and usually more than eight people apply. So there is a selection process there that needs to happen. But that's one way that you can make DrupalCon more affordable. So if you would like to participate or you know someone who would like to participate but cannot make it without this type of support, we can provide those mentor tickets to those that need it. Thank you. So this is just a few of the things we've been working on most recently. Just a few highlights from the last year. Lots of work from lots of different amazing people there. And we do have one minute left. Does anyone have a question or an extra point? Michael. I have an extra point, a question or an extra point. I just want to thank you all for the work you do. That's all. So when our monthly mentor meetings we just changed the schedule for them to, and anyone's welcome to join. Actually thanks to Michael Hess for providing a better tool. So our monthly mentor meetings are now the, excuse me, are now the second Wednesday at 200 UTC. So if you're a Nashville that would be three o'clock I think, or two o'clock depending on the time shift or three or four in Eastern. We have a tool to figure that out too. We go to world o'clock, that's why it's in UTC. And yeah, everyone's welcome if you're interested in learning about mentoring program to talk and you can find all the juicy details and whatnot. Awesome, so I think I managed to circle in right over there mentoring Boff on Thursday. Definitely come to that. And if you are interested in mentoring we've got an orientation this afternoon. We've got issue triage tomorrow and a second orientation on Thursday. So that is your schedule for the week. And we might actually have the monthly mentor meeting this Wednesday at the usual time because it is the second Wednesday of the month. And there are some folks who didn't make it here. So we try to still include them and that's it, 12.25. Shiny. Thank you. Lessons were learned. Lessons were learned. We're here to learn. You're welcome. We're coming. Yay. We did it. Yes, I, absolutely. I should have said, yep, I'm doing that. Just keep it shorter. Thank you. Well, no, I'm still, thank all of you for doing this. Oh my gosh. Yeah. So great. I was like for clubbed several times. Like, don't cry. Don't cry. Oh, are you next? Kind of.