 And over the last, oh, six months with OpenStack, we're very new to this. So that's what we want to share today. What we know so far, what we're still learning, how we want to shape this, how we want the help shaping this, right? So where are we now? We actually, just in the last three months, participated in the GNOME outreach program for women. It's very much like the Google Summer of Code program where they invite open source projects to submit ideas and bring mentors, then they pair them up with students. And the unique thing about the outreach program for women is that they are going to pair women with hopefully female mentors. It doesn't have to be, but it's really awesome, right? So it's part of that inclusion, part of getting women excited about open source, part of helping people understand you too can be part of our community, and it's your community too. We also want to work in the Google Summer of Code like process, but what's happened is our release cycles haven't really matched up well. But I've been talking to lots of people this week who want to make that a goal for 2014. And there's also companies that have people working as interns, one is up here on stage today. He's been doing two interns with two different companies. I also talked to Lou Tupper this morning at breakfast with the board and he is getting Cisco interns to work on OpenStack projects as well. So this is a big ecosystem that we can start to shape and build and see what we want to get. But I want to dive deep into the details for the GNOME outreach program for women. So who can apply? This still addresses women directly. It invites them specifically. It tries to get on mailing lists where we know developer women hang out. It tries to get groups of women collaborating with each other, right? The other thing I love about this program is the participants had to put in a commit as part of their application. So you know how OpenStack is very interested in active technical contributors. We count them, we analyze them, we make fancy graphs. Well I love that this program actually helps them feel welcome and they can even start before they, they can start looking at different open source projects, seeing how their patch gets in, seeing how hard it is to patch, how easy it is to patch, what's interesting about a patch. We also were really excited that they are connecting women one-on-one with mentors. They've been doing this since about 2005, 2006. So I feel like this is the kind of experience we can learn from, what works well specifically for women. And then also for the outreach program for women, they know that not all women are coders and some just want a little interest, little interesting project to work on. So how can we involve non-coders and get them a project like documentation? Of course, that's exciting to me. How can we get them involved in maybe marketing? How can we get them involved in community outreach for OpenStack? And this really appeals to this group. This also allows not just college students. And to me, when I saw that, I was like, that is a really interesting idea. I have mom friends who I would love to get working on OpenStack. This would actually enable it if they could find the way to get involved in the program, right? And it also has a component where all of them are required to blog about the status, the process, how they're doing every two weeks. And I don't know if you guys saw, but one of our interns blog posts was retweeted by, like, the CEO of Rackspace. Like, this is important because they were communicating their experience with Rackspace with OpenStack. And it showed, like, everyone has to start somewhere with OpenStack and she could show us how she got started with OpenStack. I thought that was awesome. This is the part. The manageable tasks are actually really difficult to find. If we're gonna talk about that a little more, how can we make sure that the tasks are enough that they can do in a three-month period, in a two-month period? And then we also have set up an IRC channel for the interns and the mentors. That was actually a lot of fun. I thought this last three months was, like, hanging out online. It's totally fun. And then the other awesome part is that they encourage you to bring people to in-person meetings. The OpenStack Foundation funded three interns to come to the summit so that we could meet in person. They could be involved in our development process. This is awesome. Thank you, Foundation, right? But what if we still... So that's kind of a... I wanted to do kind of a... Show you what one program is like, how it worked. But I also wanna talk about what we need, right? So the most important thing right now is we need more mentors in OpenStack. Everyone in OpenStack is super busy. But mentorship takes about 10 hours a week and you have to be the type of person who can answer the new questions and answer the IRC queries, like, how do I do this? I'm stuck. Get people unstuck, right? You also have to find really interesting projects. Now, I already explained the outreach program for women enables, like, not just coding projects. And then the Google Summer Code is like, you cannot give us a list of bugs and expect interns to work on this. So there's different programs have different ideas for what people should be working on. Bring me all of your ideas and we'll collect them together, right? Foundation has been outstanding for funding. Rackspace and Red Hat funded the last round of OPW interns. We want to keep that funding going, keep that encouragement from, monetarily, sure, let's invest in this. And then we all want to make sure that we have built a real relationship with the interns and that they feel part of the community, that it's their community too. How can we make sure we stick with these interns? Offer them jobs, offer them more opportunities to learn. We have one person up here who did an intern as a bachelor degree and now he's doing an internship as a master's degree. That's awesome, right? And then lastly, but the most important thing is we need interns. So get with your college professors, reach out to your alumni groups, find people who are interested in interning and learning about OpenStack. All right, so that was my introduction. I went a little long, but we're gonna kind of keep it on track. Next, we're gonna go to the panel discussion portion. So these are our interns, our lovely interns. Laura, Al. Hi. Emmy and Maki. And Vicky Martinez, famous for OpenStack 101, I must say. And then our mentors, I served as a mentor for the documentation with Laura. And then we have Julie Pichon. She is a dashboard horizon developer and she worked with Vicky. And then we have Icha Sethi. She works at Rackspace and she's core on glance, the image service. And she worked with Anita, whose back is hurting so she's sitting over here. So now I'm gonna hand it over to Julie to go through our questions we came up with. Okay. Okay, so many thanks to Anne. We, in addition to being a mentor, was also coordinating the different internship projects. So thanks for making this happen. And we have a few prepared questions and then we would love to hear what are your thoughts and question about this kind of programs. So first I would like to ask Victoria about her thoughts on how we can welcome newcomers like Inter and Beta into OpenStack. And I know you have a lot of ideas about this. Well, thanks. As a newcomer of myself and as the creator of OpenStack 101 and space for new people getting started with OpenStack code, I think that the most important thing is that newcomers get emotional support. I think that that was one of the things that changed everything for me when I started coding for OpenStack. I really felt comfortable having that. A lot of developers willing to help me to give me ideas and to cheer me up when something goes bad or was frustrating for me. So that's one of the most important things. Also, when talking to a newcomer, you have to forget everything you know about everything. You need to learn how to express your ideas in terms that a newcomer will understand. And finally, I also think that you have to help the newcomer learn to learn stuff. You don't want to give a newcomer everything done for him. You want to give the tools so he can learn by himself. So some app supports a treat with him as you don't know anything and give him the tools to do things by himself. Thanks. Thanks. So the next question is for the mentors. How would you describe the time commitment for a mentor in the project? So the time commitment of a mentor differs during different periods of the internship. So it can differ from the minimum of two hours a week to a maximum of 10 hours a week, like Ann said. So during different phases of the internship, the intern goes through different things. For example, when they're just starting off with the internship, they're getting introduced to the whole community, the process, the project. So the time commitment of an intern goes to a maximum of at least 10 hours during the first week. And during different phases of the internship, when the intern is going through a task change, when they're moving and changing and moving on to the next task, they need an introduction to the next task. And so some more time is needed at that phase. But during the course of the internship, it's pretty much self-sufficient. So the most important factor is building support, like Vicky mentioned, that if we build a network of mentors, not only you, other developers and open stack to help and support the interns, they're not reliant upon you. So they have other people available to help them at any point of time. To give you an example of how Anita and I worked as a mentor and intern. So we would do the agile methodology. We would do everyday stand-ups, like every morning on IRC, she would type and she would tell me what she did the previous day, what she's going to work on today, and if she has any blockers. And these blockers not necessarily have to be resolved by me. Anyone in the open stack community can resolve them for her, and I can be the bridge to introduce her to that person. And apart from that, once in a while, we would do Google Hangouts as necessary so that she could get more face time with me and my more one-on-one attention. Thank you, Richard. So, Emilia, you had a bit of a different internship experience than the other on the panel. What would you describe as being the ideal lens for an internship? So for the... Actually, there is no ideal lens for internship. I made both small and big internships. The first one was only three months at StackOps in Spain, and it was really too short to be involved in a huge project, like a concrete project in the company. The time, like Vicky said, the time to be introduced in the community, to learn how to learn open stack stuff, it's maybe two months. And the time to define what can I do for making new open stack things for the company and also for the community, it's maybe one or two months. So that's why I think the most important thing is to define the project before starting the internship. And also maybe to define the lens of internship, it's depending also of the schools. My old school was a university which allowed me to make three months internship only. And now I am in Master Degree and I can work in part-time. So I'm working three days a week in my company during two years. So it's better for me since I can be involved in the developer teams, not like an intern but like a regular worker. So that's fine for me. So if I have to say a good length, I think at least six months, it's good to be involved in the community and maybe after to continue in the company. Thank you. No question for the coordinator of the project. If I have ideas for an internship, how can I let the community know about them? Yeah, so I'm glad to say that I want to be kind of a lightning rod for these ideas. I want to kind of be able to have a place where we can all kind of think about the ideas. So what we did for Google Summer Code application process was started an ideas page on the Wiki. And so what I think we should do is kind of expand on that so that any professor can come to our Wiki, look for ideas pages for projects that you consider to be kind of able for an intern to do. Now what's interesting is we've also got ideas for like Summer of Cloud, which would be like maybe even high school students. So let's get those ideas on the Wiki as well. One of the ideas was using Heat's API to do an orchestration of a Minecraft server that your friends can play on, right? These are ideas that we need to just bring in and everybody can like look to match either an intern to the idea or a mentor to the idea or both. Now when you bring an idea, ideally you'll also be knowledgeable enough that you could offer a mentor to help with that project, right? Because I think people have great ideas, but we really need both ideas and mentors. So let's kind of keep that together. And I actually have an idea that we could do internships where people start out with bug fixing, then they write QA tests, then they do actual blueprints. And so it would be the same person over different periods of time, right? That's worked at companies I've worked at before in the past is this process that's over years. So how can we start to get that mature in our internship programs? Let's bring ideas to the Wiki. Thank you, Anne. And finally, what happens to the intern after the internship? What are your plans? Do you plan on remaining an active contributor or is there another path? Well, I think that's actually up to every intern. My goal for this internship was to learn how to be an active, free and open-source software contributor and also to remain one. OpenStack community is very welcoming and like Wiki said, that's actually very necessary at some point because we all know OpenStack can be overwhelming at first, especially for a newcomer. And I think this supporting network really works also as an engagement process. So even when this internship is over, we still have ideas and things we'd like to work on and carry on the next month. And even our presence here is actually a proof that OpenStack is really interesting having us as long-term contributors. And even if we are maybe independent contributors or working full or part-time like we before are doing, I think we'll all stay around and we'll be certainly involved with the OpenStack releases and projects for a long time. So we'll meet around. Okay, thank you. No Q&As open to everyone. Do you have any questions or inputs or ideas? We would love to hear ideas. Or we could find more questions or send them. Oh, please. Do you have that mic on? Do you want to just step up? Thank you. Any questions about the application process? Yeah, so what I'm thinking is it's a... We're trying to find the best programs in open-source and then OpenStack goes to them. But what we could start working towards, and I see stuff as in madly taking notes, right? Do we need to have some sort of centralized application process? I don't think so yet. But the jobs board at OpenStack does have intern listings as well. That's probably your company, right? Events has one now. So the application process might vary by program or company. Okay, we have it organized by AusAids, the Australian names. Okay. And the applicants, in order to get them kind of in the trivia, he or she has to find their own mentor. Interesting, okay. Someone that he or she happens to know or may be introduced... Interesting. That is a good turn of... So another thing I've noticed is that Google Summer of Code is asking students to bring project ideas to the project. So maybe we'll enable both ways. I'm reading Susan Sandberg's book, Lean In, one of the chapters is called, Are You My Mentor? And it's a play on this book, Are You My Mother? So it's... I see a little bit of a trap there for women, especially having a hard time approaching someone in the community. And women have historically been told, unless you get a mentor, you're not getting anywhere. And in fact, it's... That's really tough. As a woman, I would not go up to Vish and ask him to be my mentor. No. Oh, goodness, no. Right? That's really tough. No. Oh, goodness, no. That would be out of the norm. So anyway, I really want to play on that, though, because I think there could be unsung mentor possibilities that community members could flesh out. I'm not fleshing them out, obviously, so... Yeah. Okay. I look at stuff like, you're doing this too, right? Awesome. Absolutely. Yeah. Yeah, good. All right, so I'm getting waves from the back that we do want to try to keep on time. Do we have five? Okay, one more question, two more questions? I did not plant a question. Yes, okay. Good. How to work with a community in which you have high-skills guys and trying to be like another contributor? When you make a patch, you don't have to be like an intern. You have to be like another contributor. Even if this guy is working since two years or an open stack, we don't care. So you need to... It's very difficult, but that's my best experience to learn how to work in the community. One of the things that I learned is that when working with a group this size, one of the most important things that I have to do first is figure out where the code goes. I did... I spent quite a bit of time... I would push up a patch that was just a placeholder. It was just sort of like, if this is the right place, here's what I intend to do. So some of my initial feedback in my reviews was, yes, this is the right place or this actually should go over in this project or this file. And then I would start building that out. So place. And the other thing is that to push small patches frequently because rather than a thumbs-up, thumbs-down, a better approach is to have a conversation. It's just like, here's the seed of what eventually is going to go here and how do we, with the reviewers, work on actually building out this patch so that it works for everybody who's got an investment in this particular functionality and make sure that when it's merged, it meets everybody's requirements. One more question? Yes? Yes. That is what I'm finding is interns will approach us before we are organized enough to... I mean, OpenStock's very popular. OpenStock's very interesting, especially for computer science people. Yeah. I thought it meant something. Yeah. Yeah. Let us help you chunk it down. Let us help you eat the elephant to bite at a time. Yeah, it's an elephant. Yeah. That's a great way to organize the ideas, page two. Yeah. Small, medium, large t-shirt sizes, sure. Yeah. Low-hanging fruit. Yep. Yep. All right, thanks, you guys. We appreciate it. And thank all of you for participating. Thank you all.