OpenHatch: An Open Source Volunteer Opportunity Finder

>> Hello, everyone. Thank you for coming out to the talk today about OpenHatch. I have with me Asheesh Laroia, who is the co-founder of OpenHatch. He’s also a former Google Summer of Code mentor from 2008 were he worked with the Creative [INDISTINCT] Project. He left Creative [INDISTINCT] to co-found OpenHatch with Raphael Krut-Landau. The two of them who’s right here–the two of them met while they’re in college together at Johns Hopkins University. Raphael works on the user interface for OpenHatch. So, both of them traveled here today from Philadelphia, Pennsylvania. So please join me in welcoming Laroia and Raphael >> LAROIA: Yes, so I can tell you guys some things on the topic of how you can be involved in OpenSource and how your products can get more people. So, I have some questions, I’m going to structure this around. First of all, if you don’t know what you want to work on, how can you become a contributor to a project, find a product that you needs and find issues to tackle in that project that particularly even enough to keep you going as you’re a core developer there. How can–as a product maintainer, how can you attract new people? And make sure that you–the work you’re giving them is actually something they want to do and that they can do. And that how as sort of long-standing contributors, how can we tell our story to the community and say what we worked on and finding things to work on based on that. So I’m asking these questions, I admit, because we have some ideas or so, I’ll say, the suggestions from us to how you can use our website to do it. And, but I want to hear from you guys how you–what you’re experiences have been, if you think what we have–what we’re showing you is useful and how you mind yourself using it. So, Raphael talked a bit about how you might find >> LANDAU: Okay. Thanks, Asheesh, yes. This is my favorite part of the website. So I was just talking to Chris earlier, well, a few minutes ago and so I think Chris is kind of perfect example of what we want to talk about, I think. He’s a talented developer here at Google and–but he haven’t had much OpenSource experience. And he sort of beginning to think about, you know, “How do I get involved?” So the first part that we’re going to be looking at–well, what’s the on-boarding process like? Like, what’s it like to kind of arrive on the Internet and say, “Well, you know, I like making software. I want–I use the OpenSource software and I want to be part of this kind of world, this culture, you know. Where do I begin?” So we’re going to show you a tool we’ve built to make this, hopefully, a little bit easier. So, you know, supposed I’m Chris and I arrived at the OpenHatch front page which you see here. So the first thing I want to do is, you know, he sees, you know, what are some volunteering opportunities at OpenHatch that has to be here? So here’s the next screen And this our volunteer opportunity finder And what you’ll discover here are–it’s mostly bugs, but we also have documentation requests and other kinds of request for help and this is from across a lot of OpenSource, so a lot of different projects here. So, this is a kind of a good place to begin if you’re not really sure what project you want to work on. You might, for example, have in mind a particular language that you know, or a particular kind of project that you want to work on, and so, what we’re trying to do is sort of connect you, you know, who has information about you, you know. What–you know about your interest, you know about your skills, you don’t necessarily know what project out there is going to be useful for you, so we’re trying to bridge the gap there. So, take a look at this page. On the left, we have bugs in different languages; the second column list different projects, so the way to explore the database. And the one thing I want to look at right now is this third column, toughness, and underneath I see there’s this link called bitesize. So what do we mean by bitesize? Well, there are many projects in OpenSource who decided that they want to make life easier for new comers. So they go to their bug trackers and they identify bugs that are appropriate for new comers. So, for example, a bug like this is–as a good way to kind of get a feel for how the project works, so I’ve learned the ropes. It’s not a very big, intimidating bug, it’s–maybe one that you can solve in a day or a few days. And it’s supposed to

be a sort of rewarding and engaging bug for newcomers. And I don’t mean necessarily newcomers to OpenSource, but some just good for newcomers to the project, maybe you’re moving from Project A to Project B. So we collected as many of these bugs as we can find. So I’m going to click on that link and let me scroll down the page and you’ll see the most recently indexed bitesize bugs from across OpenSource since a variety of projects here. There’s about 1,500 total open bitesize bugs right now. Well, you know, I’m thinking, “Well, you know, this is a lot of stuff.” Let me drill that. Let me get more specific here about what I want. So let me go back up of half the page and, you know, we pick up language that I know like Python. And then here I see there’s just 100 or 200 bitesize bugs at Python And if you look under where is this project, you’ll see that there’s a whole bunch of projects, for one that catches my eyes supposedly twisted this, this is a framework for developing a high performance networking software, now maybe I don’t know that, maybe I’ll just kind of, you know, browse it. So I click on Twisted and I see that there are 33 bitesize bugs in the Twisted project. So I can keep exploring the–scroll down the page and I see that there’s–it’s a whole bunch of stuff going on here. So I can explore this bug about dependencies, for instance. And the whole idea is that we’re going to try to push you out to, just bring you, you can begin solving the bug. So, for example, there’s a link here so you can go to the original bug tracker. So, you know, I can click that, here I am at the Twisted bug tracker and here I can learn more about the bug when it was filed. I want to go back to the OpenHatch Volunteer Opportunity Finder and see what other resources we have for this new contributor who’s much learned more about Twisted. So, let’s go back. Here’s that bug we were looking at. And on the left, there’s this link that says, “More about this project.” So, let me check that out. So, this is our Twisted project page, and what I see here is a variety of different stuff when we–that OpenHatch has got a–that concerns Twisted So on the right here, they see that there’s this button that say “I’ve got to help.” And when I mouse over it, it’s quite, you know, it’s bit much specific. If you click this button, you can add yourself to a list of people who want to contribute. We’ll talk a bit more about this button later, but it’s one of our newest and I think the one of the more exciting features. If we scroll down the page a little bit more, and you’ll see the OpenHatches’ sort of started a discussion forum going. And we’ve seeded these discussion forums which questions that we think are really important and that are not really being asked enough. So, for example, this question says, “How can I pitch in if I don’t want to write codes today or if I don’t know to write it? Nobody’s there to do it.” And of course, there’s tons of things to do in OpenSource projects that don’t involve code, like answering questions, managing bugs as they come in and categorizing them, explaining how the software works. In an OpenSource project so I’ll just need the technical people. They need great writer, they need good explainers, they need to go to like social, people with good social skills who can kind of manage their project, organize meet-ups and things like that. And you can see whenever a contributor says, “Come in I lovingly prepared a great deal of information about Twisted and how to get involved as a non-coded contributor.” So, now let’s–I’m going to look over the other side of the page and I see that there’s a list of other contributors So, let me go, see who’s on this project And if I click that button, I’m taken to the OpenHatch People page. And this on this page, I see the list of variety of people who contributes to Twisted. Of course, this isn’t a remotely comprehensive list. This is just people who’ve signed up for OpenHatch and also who contributed to Twisted. And one of the nice things of this page is here you can figure out whether or not there are people who worked on the project who live in your area. Because if you’re looking for an OpenSource project, that’s pretty–it’s a pretty nice thing to be able to go and be actually hang out with the real human being, you know, in the flesh unlike–you know, have a drink together a something like that. So, you know, suppose I live in San Francisco, I can stroll up the page, and there’s this field here that says, you know, search for people in the project Twisted, and I can search near a particular location. And log the whole dirt if someone who lives in my area and who works in this project. I will show you a little bit later about how you can contact people so you can come and get the ball rolling and say, “Hey, you know, we want us to meet us together and talk about this project, you know. I’m kind of new but maybe you can show me how it all works.” And I think that a lot people at OpenSource find that this is the most valuable moments they have; when participating in the community, so were trying to make more of these kind of things happen. All right. So, we have this tool and what’s actually new about this? Well, the first thing is that this is, I think,

the only–this is the only way you can search for bugs across projects. And so really this is a good place to come if you don’t–if you want to get involved but you don’t really know exactly what project do you want to hook up. Secondly, I think that a lot of bug trackers are–they are quite well designed for some [INDISTINCT] for people who are already in the project. So, if you look at the bug tracker and there’s a lot data on every bug tracker page about all the open bugs and what needs to be done. But to make it more efficient it’s a lots of jargon. And if you are newcomer, a lot of jargon can kind of turn you off and it can be the reason you don’t participate We’ve tried to make this volunteer opportunity finder intelligible for people who are not aware of this jargon. I think that hopefully, this can make a bit of difference and, you know, create a more friendly atmosphere for newcomers. And finally, one of the features: that you can find people who live in your neighborhood, which is very nice. So, the next part is something that Asheesh has said and done. I know he wants to come up and talk about it >> LAROIA: Yeah. So, I think that one–as some of you who works on our product and given a [INDISTINCT], you might want to help people to join their project. And so, somebody who has a lot in OpenSource, my colleague has a site and start at this like document an OpenSource contributions where we say, complete a story together and import the projects you’ve worked on into your profile. So, let’s say, I’m Will who maintains Miro and [INDISTINCT]], two of the big python projects. The space–I start here and sign in with my Google account or other open I.D. and I’ll end up at the portfolio editor where I can, upon clicking here, start entering in my identifiers like my [INDISTINCT] user name, the username that you commit subversion repositories, email address that [INDISTINCT] in birthing control systems. And then we’ll slowly start to import those things from across the Web. And, once we do that, we’ll give you a space to write about your project and what you’ve done for it. And Will have written a lot in that box But the most important thing is the last sentence where he writes, “I do a lot of work for Miro.” So, upon saving this you go back to his profile and see Miro in his own profile as one of the products he’s worked on. But from here, if you might click on the Miro link and find out what is this or perhaps the thing about? How can it help me get people to my project? And right here, we see there’s an “I want to help” button that Raffy mentioned just a moment ago. And that’s something that new contributors can click on, assuming they find the OpenHatch page for Miro. He’d answer some of these questions, like how to contribute and other ways in writing code. Miro is a big desktop, rich and beautiful video application And so it needs–it runs on Windows, Mac OS and Linux, and needs testers on all those platforms. So he’s written a note about that here. But I want to draw your attention to this question at the bottom which is something that I thought would be really interesting to ask project maintainers. It’s something that always people ask me, what’s something I haven’t been working on because I don’t want to think about it? In my case, I maintain a packet called [INDISTINCT] in WN and there’s a patch, somebody who has written that’s not properly licensed but everyone wants it in WN. And it instantly adds a very useful feature was the reading mail for, you know, schools Very useful if you, you need an [INDISTINCT] on a system administered by [INDISTINCT], but that’s me. So there’s actually a bunch of people on the bug, but it’s really tough for me to solve that problem so we’ll write about it here. And if someone else comes by to the site and find the OpenHatch product base, they might say, “Oh, yeah, I could write that.” And this is the only place that there is to say what stresses you out, not just what needs to be done. But Will is interestingly getting more people on this project. So, what’s he’s going to do is pull up this “I want to help” button. There’s a link that says you can imbed the “I want to help” button inside your own site. So, you can just click there, grab the source code, copy it to the clipboard, and go out to the Miro website, find the Wiki for Miro and add this “I want to help” button to use as a Wiki. When new contributors find that button and click it, it will take them to OpenHatch and say, “Hey, if you will sign in and tell us about yourself, we’ll add you because people want to help. And that’s exactly what’s written on the Wiki. So, this is kind of new. First of all, Will has been able to build his portfolio of projects he’s working on. He’s stuff from Launchpad and all of the other resources automatically. But, once people who click this button, if they do, we can with that in a minute, he can reach out to them, knowing what they–knowing what these

people know. So, if you click this button making it a profile on OpenHatch, you can say, I want to, I want to write in French, and if there’s work that he’s going that way, Will will know. And by adding this people, this list of prospective contributors, we showed them right on top of the current contributors so it makes them feel them like part of the community already. And I actually think–so at OpenHatch, we’ve had a source code center link on the websites sitting at the bottom We talked about how the AGPL, the big three project, you can get the source. We’ll link on one person on the IRC channel [INDISTINCT] that. Then we add this “I want to help” button And we’ve had 11 button clicks over the time, and we have three more people on the IRC channel who’ve asked us to get–how to get to the source, and let it build on Arch Linux and the system that we don’t support well, that we don’t run. So, I’m actually seeing it very anecdotally, a big uptake in interest. Dozen of people have clicked the button and think, “Oh, when I clicked the button, then I could probably do something.” So, I wanted to have Raffy to talk a little more about what happens then >> LANDAU: Hey, I’m just going to tell sort of continuing the story of Will, the project maintainer, who works on the URL and I’m going to show you a bit more completely about how you can use that “I want to help” button to make your project clear. So, here, we are back at the Miro page. And on the right hand side of the page, you know, I see that there’s someone who has clicked on that button, Matthew So, let me go check all those profile and see maybe he can help. And on the left hand at Matt’s profile talks a bit about what he knows, he does some computer languages, he also do some natural languages, and he’s seeking this Russian that kind of gets me thinking, “Well, hey, you know, in Miro, I was this big TV distribution platform.” And we have a bunch of Russian users. And we’re about to come up with a new release. You know, we’re really–actually you can use someone to translate our release them to the Russian. So I can–so that will take awhile and I want to contact Matt so I can send him an email and just say like, “Hey, you know, I saw an OpenHatch, you know, how to write Russian, and that’s why [INDISTINCT] help in Miro and help in Miro. Well, actually, we have something for you to do.” So, that’s one way can use that button. You don’t have to go to the button You can just search for people out right So, here’s our kind of people page and see a big map with everyone the site. And if you like, you can search for key words. So, let’s say, you want to do some Mac testing. You know, you don’t have time to do it yourself [INDISTINCT], maybe someone else out there is willing to pitch in with some of their Mac skills. So, it turns out there are, there’s a few people. And you can click this button, this link in the middle of the page, you can see people who specifically said that they can pitch in with their Mac skills, not just that they know something about it, but they’re actually willing to help you out with their Mac skills. So, you’re the [INDISTINCT] here’s

someone who knows a bit about Mac and that’s going to help you, and you can go to his profile And here, he’s mentioned and you can, you know, you can email him. So I’m thinking, “Well, you know, I’ll–if you have this kind of Craigslist style email forwarder, so people can feel free to share their contact information And, you know, here, you know, Will’s typing up an email to Andy saying, “Hey, if you’re going to help, we’ve got something for you to do.” And that’s just one other way to you can use the tool. I think that’s your slide So I think, yeah, the first few things we’ve talked about already >> LAROIA: Great >> LANDAU: Yeah >> LAROIA: Yeah, so Raffy was just talking about how you can get people to test your software on a Mac or write out these notes in Russian. But I don’t want to have all this point that OpenSource projects are about more than just code. So, when you think about OpenSource projects, you think of all these attributes right. You think the software is beautiful, fully-tested, simple and easy to use, and has flawless documentation. So, while these are true it’s because of effort, a huge amount of effort, by the developers but also by other people, not necessarily coders. You can reach out to people who use your application and say, “Hey, would you download the latest release? Maybe–then we can find some of these bugs before it’s too late, before the new users, before one of my friends see it.” Maybe you can reach out to people, like Raffy said, write a documentation and help people know how to use the product. So, I just want to take this moment to inform you guys, using OpenHatch or not, if you write OpenSource project, reach out to these people. Ask for help and you’ll find that if it is something you want done that isn’t code there’s probably a user that’s willing to do it. So, a lot of the question that we’ve gotten is these lists of helpers right on the corner, why don’t we just make list of email list–mailman list of something of people. You can flash out a message and say, “Dear 1000 people, would you please write me some of these notes in Russian?” Well, in Raffy’s example, the Russian as an example is a sort of opportunistic You find someone willing to help in that way, so he tried at something at that person. If you know people can help you, you can ask them especially to do something that they can do. Also, there’s something nice about being personally invited to work on something, receiving the one-way email is a lot nicer than a mail to a big mailing list, and you’re actually more likely to do it. And finally, if nobody answers, it’s OK. No one will know There’s no public archive of me emailing that need help button. But there’s a archive of the emailing the giant helpers list, so it will be sad to look over that archive months later. I mean, it’s actually this is sad on the Debian mentor’s list. We have all these excited new prospective Debian developers

and they have packages that they want someone to look at and there’s just such an influx of request and half of the time, there’s a good discussions like, “You didn’t do this correctly, you did this right but you could do it even better if you use, compile a new format.” That’s the best case. But the worst case which happens half the time is no answer And that’s just no fun to look at, you know, guys. So, I only have to take a minute to reflect about where OpenHatch is right now and then talk a bit about where we’ll take this. So, by the numbers, we have more than 200 projects whose bitesize bugs we index And that’s probably good bitesize bugs that are good for your numbers; not just bugs at all. We have almost a thousand members and they come from every continent. You might be thinking Antarctic is a continent. And there’s a user who says he’s from Antarctica Actually, when we discovered–we distributed a bug in our macro. We usually expect that to happen. We turned–we need to make that taller to allow room for that place on this side. There’s dozens of projects that have started conservation about how you can help out and–but dozens more people who clicked that I want to help them to say they want to help in a project. And this is just like 163 days, little less than five and a half months with OpenHatch. So, we have a bunch of big products participating but I really I want to work–part of why I’m here is have you guys like, maybe, we can, you know, speak about trackers and help you find ways to get more people involved. I really want to use this not just in quality and quantity to get more projects, reaching out. The real power of Volunteer Opportunity Finder is that anyone can go to it and click a few times and narrow the whole open source world down into how they can contribute and what they can do So this right now is a big ball of code in Django, and it’s running on just one virtual machine and that worked out really well until they got slashdotted, and everything collapsed in an out-of-memory disaster. So, let me do a lot more caching and we can get by pretty well on just one VM. We’ll see how things go. I see all that because I’m happy to say that it doesn’t take a huge amount of overhead to run the site. And the backend code, most of it, most of the exciting stuff is scraping data out of bug trackers or code hosting sites, like I can get the profile information. And a bunch of bug trackers did APIs but I think, I think with the only API–the only bug tracker type, all we–sorry. For all the bug trackers that we indexed, Bugzilla, Trac, and Roundup, and Launchpad; most of them have APIs, but we have to scrape the pages of three out of those forms because there’s some information not on the API. And also, we have a nice series of test; that means that when we breaks up,

we usually have reason. So, the future, invite a lot more bugs into all opportunity finder We are working on getting new, getting local meet-ups. So Raffy talked about finding a project where you reach out to someone who lives near you and say, “Hey, I want to join Twisted. Come and see [INDISTINCT] or something with me. But–so what we want to do is get meet-ups of new contributors saying, “Hey, a dozen of us live in Philadelphia and we all want to do something. We don’t really know what–let’s all sit down together, get our laptops and browse until we find something.” And definitely we’re going to be doing in the next couple of weeks, team building. We also, as I’ve said, if you’re going to talk with contributors and project maintainers and find out how this matches what you want and what new contributors might like on top of these, and there’s a lot of maintenance work to do, as always. So, the team is Raffy and me, working on this about half-time; but we do have, and I said, 11 people who clicked, “I want to help” on this site. And that’s just such–it gives me such a warm fuzzy to know that people are excited about what we do. And I think that fighting the sort of fear of isolation in OpenSource, you know, I hope it would happen a lot and makes a big impact to make all of you happier and helps people find projects to work on. But, you know, if all we do is help project maintainers feel less lonely because people click this button, I think that’s huge. Right, yeah Burn out is enormous [INDISTINCT] than in all the other projects that I’ve worked on So, well, as I’ve said, we’ve had these three or four people, three recently and one in the past, have installs in the site and work on generating patches. And we have–thankfully, Google Summer of Code student that would be accepted on Monday. And like, I think, yay, the Google Summer of Code student. So, John Simper and I came up with this idea of adding training missions of a hatch. So, in order to participate in OpenSource, you–-there’s a bunch of skills you need to know. You need to–you might need, for example, to know how to use patch. There are people who say things on how to configure page like, “Oh, it’s easy to sign up for a project. Just join our IRC channel, or send the patch in the bug tracker, or make a format-hatch file using git. And, so a bunch of people did all seem very reasonable But that’s not after the majority of perspective contributors. A lot of people haven’t really

use IRC, even though their good programmers that’s not really related. And many people haven’t used diff. Many people haven’t used git format-patch. So, we sort of, in OpenSource, we end up accidentally excluding people from the community by using this jargon and forgetting that there are different types of people They don’t have the same experience with you They can totally help out if we reach out to them. But it’s not like–I mean project maintainers wants to sit down with every prospective contributor and teach them how to use IRC That’s often what they say. If you can figure it out, great; otherwise, I don’t care. But robots might care. So, what we’re going to build is the automated engines on this site that you can enable for yourself and say, “I want to learn about,” let’s say, “tarballs.” I want to know how to make a patch file.” So, we’ll give you training mission that says, “Take these two files. Unpack them with this command right here, no mysteries, and make me a unified diff and upload it to OpenHatch And if it actually is unified diff, not a contact’s diff, we’ll say, “Great.” And if you made a mistake, we’ll identify it. If at some cases the mistake you’ve made, let’s say, that was contact’s diff, you didn’t pass [INDISTINCT]. Then we try to do thing that annoyed project maintainers and the kinds of things that robots can do to the people So, yeah. And other–I’m really looking forward to these training missions. We have some planned out for subversion and git and making tarballs I mean I–it’s only very recently, I’ve actually memorized the command syntax to make the tarball Like–yeah, this is always our comment that we can teach people automatically, if interactive [INDISTINCT]. So that’s–could be a possible thing to do Google Summer of Code and hopefully we’ll have, you know, more excited and that’s at the end of the summer saying, well, you know, hopefully, other people will be blogging other insights about how they learned these tools without bothering project maintainers So, it’s really important as a community that they listen to new contributors and listen to what they find difficult to do and pay attention to where they dropped off. And so that’s really the core focus of OpenHatch as a project and as a website. And I want to just conclude with a few highlights, thanks

and get your feedback. This is really crucial, OpenSource projects live and die based on more than just code. They live by based on the feeling of the people working on it. As few of you is smiling about my ironic–people think I might–I want to help them. And they also live and die based on–if anyone knows about the project. And that’s something that seekers or writers of any natural language cannot do it. And so you can help get more people contributing to your project. You can–-on your own bug tracker, independent from OpenHatch, that’s where you can label bitesize bugs And if you want to import them, there’s an edit link on the OpenHatch search page that says, “Add a bug tracker.” It will give you a form to fill out. And for the prospective new contributors here, I sort of discovered this a few years ago and it’s something not a lot of users of OpenSource have discovered, which is that, you can be contributing to software you are using and that feels pretty great. So, we want that to happen more. And as a developer, you can reach out to users, help them know, help to know what they can do and then bring them in. So, thanks to Ellen for bringing us here. The, yeah–-the website art that you see, that cartoons on the People page, those are drawn by Karen Rustad. She will be again joining the Berkeley School of Information in a few months, I guess. And Nelson Pavlosky is this invisible link that is how Raffy and I met at Hopkins and he helped bring us out of our–the other lives into this new life at OpenHatch. And, of course, thanks to the people who used this site and let us know what they you like. So that’s the site. And contact us, and I want to know what you guys think, and what would be useful here. Thanks. Raffy is–in the beginning, Raffy was described as a weapon user experience But a lot of the code in this site is [INDISTINCT] programming and collaborating [INDISTINCT] So, it’s not just you and I, we’re worth [INDISTINCT] >> LANDAU: Yeah >> So, one question is whether you support the Google project costing for that Google account >> LAROIA: Right. We don’t have it in [INDISTINCT] right now just because we haven’t found any projects that Google [INDISTINCT] side on it, but it’s pretty easy for us to export data from it. So, add your project to [INDISTINCT] And I said we do really prioritize projects that label bug in bitesize >> Right. And the other thing is how are you trying to solicit people to come as contributors? Because I was talking with some friends or faculty at UC Merced >> LAROIA: Yeah >> You know, and their university is up in the middle of Central Valley, so that they don’t have a lot of high tech around and they keep wondering how they’re going to get their students enough experience. This actually seems like a great way to get their students accounts to actually starts doing real development in the outside world, so they have something

to show on their resume >> LAROIA: Yeah >> So it will be interesting to see how you get faculty at small colleges to know about this >> LAROIA: Yeah >> So they can [INDISTINCT] their students there > LAROIA: One thing that we’ve been doing is working with the group called Teaching OpenSource. That’s primarily takes out of the [INDISTINCT] of that. And they’ve been reaching out to universities and running so called POSSE events. I can’t remember what that stands for. But basically they get professors to run a semester course teaching students about OpenSource and they’ve actually written a textbook a few weeks ago. And so I guess to answer this very good question about Mercer, is that right? >> Merced >> LAROIA: Merced, like have that person–that professor and Teaching OpenSource that are working to meet up. And they can do that–you can do that by either emailing me or then going to the site, probably better do it right now in case they forget. Yeah, I think that students are really–like students are a huge population that could use the site. But I think it’s also important to remember that so many other people who can’t do >> There’s a website–an organization, I’m trying to find a name of because I don’t remember, right now, that maintains a bunch of mailing list related to getting women and their represented communities into not just OpenSource but technology in general >> LANDAU: Yeah >> And I’d be happy to track down the name and do URL and send it to you because they’re eager to find out about things around OpenSource so that they can spread the word to their community about it >> LANDAU: Yeah. That’s so great. We should–I can’t wait. We–like the representatives–it’s–in tech, as whole, women are about between 20% to 30% of employed tech workers. And in OpenSource, it’s 2%, maybe 1, depending on what you are to say. And that’s just tragic because we’re just leading on the floor, few numbers to affect the contributors. And I think a lot of it has to do with how the way people learn about OpenSource is mostly to a friend networks And the way you gain these skills like, knowing how to use patch, knowing what–knowing how to use [INDISTINCT] control skills, it’s from interactions with people. And so, to speak in the most grandiose, I’m [INDISTINCT] hope the robots help us get more [INDISTINCT] OpenSource And of all time the people too. I mean the immersing problems in OpenSource women are just the most obvious category in missing angle. Yeah. So, especially I’ve understood to–if there’s any–if there’s people there who did have some OpenSource experience and in the modern technology groups, we can really help them tell us what would help them the most >> Okay. It’s good too because the group has sub-list specifically for small community colleges, regional schools, et cetera >> LANDAU: Yeah >> With the idea being that the tech community needs to reach beyond the big population centers >> LANDAU: Yes. That’s awesome >> I guess just a comment that, you know, I really like that UI that you have. It’s just on the site. It’s really easy to use It’s very clear especially because you’re trying to attract new people. So, from that perspective, it’s just really easy, simple to use, and navigate through and kind of find what you’re looking for. So, I’m really impressed with that and I loved the images that you have been scanned. You can–even tell you to try to build the community and you’ve brought people along there and really try to engage them. And so, that’s really cool. And >> LAROIA: Let me just say thanks to Raffy and again to Karen for controlling the place for most of that >> Yeah. And a lot of the OpenSource projects do work in silos, so it’s really encouraging to see something that’s in a project, you know, you mentioned Launchpad >> LAROIA: Yeah >> There are few right there but it’s really encouraging to see that some of it is kind of bridging across the various projects to bring it together and know all the task that need to be worked on and encouraging participation across all levels and not just college >> LANDAU: Awesome. Thanks. Yeah, I think >> Thank you >> LAROIA: One of the reasons that we try to reach out to all the different projects is because we’re doing something kind of new So, we can’t afford to–we need to get people attractable to like I say, from wherever they are. First in the Launchpad, the Google code and get hub or whatever >> Okay. Thanks >> I loved your message about OpenSource is more than just code >> LANDAU: Yeah >> And I was–I, actually, I’m going to Portland next week to talk to students at OSU OSL And I was–that was actually my intent to talk about how OpenSource is more than just coding and all the other different opportunities And so now, I’m going to refer them to your site as a way for them to, you know, find opportunities. Is there anything else that you think is important for them to know, like or like a message that actually pass along about your site or OpenSource in general? >> LAROIA: I’m going to talk OpenSource, in general. One of the most, I think that there is–one thing I like about our site is that non-code contributors are highly and just in the same way as code contributors. They are part of the list of contributors, you’ll see the same little badge of your profiles and I think that that’s true on our site but it’s not true in the entire community. So, and I think that there is a like a second classiness of non-code contributions that people feel. And so I think that if you can get credible people to say that non-code is that important, I mean, you’re not going to be able to operate in a dozen project maintainers who are all–but, if you’re great, if you could get someone to say, “I don’t like writing release notes. Someone else could write them I want to be something else.” And, you will see that they actually want to read them then you will realize how important it is. As for our site, I guess, I can’t be able to talk, can you help me on this >> LANDAU: What I would say is if you’re, say you are designer or a graphic designer, you have an opportunity to make a really big difference because a lot of projects need acknowledge of that >> Okay >> LANDAU: You know. And, yeah, although I think, as he’s sure, I mean, yeah,–it’s true that there’s, historically, in many systemically code is priced more than non-code contributions If you walk around and talk to a bunch of people and you ask them about this kind of thing, they all get really excited about at the UI, the need for UI; the major people who have a sense about project management So you are going to make some friends pretty quickly if you had a–to do the UI stuff >> LAROIA: Right >> LANDAU: Of the details >> LAROIA: And from that sense that getting product maintainers to make the whole stories more incredible, but I think there’s sort of a shyness or fear, the half of these prospective non-code contributors that their work wouldn’t be valued, in fact, it would be. The other thing is that like, I write non-code and also write code and I, actually, I’m mostly got started–the first product I really collaborated on was Xbox Linux were I put together with the missing documentation for how to modify Xbox’s software without modifying the hardware And that was usually valuable. And I know that and either one of them. I think that >> LANDAU: Yeah, some of the documentation you came up with this is now very essential in the Xbox Linux website >> LAROIA: Yeah >> LANDAU: Yeah >> Oh, thank you >> LAROIA: Sure >> LANDAU: Okay >> LAROIA: Yeah, I guess that’s why he tells me click, I want to help. I mean, and also it tells me to reach out to project maintainers, right? I mean I’m talking as if project maintainers all want to spend their time reaching out to people, that’s not always true. As we, all I’m doing anything based in the call on these people, they would have to reach out to you. But, a lot of the people I’ve talked to who are core developers say, I don’t want to deal with more people. But then there’s like second tiered developers or communities, sort of, people, of documentation writers and those are one of the teams say, “Oh, we’d love more people.” So, basically, keep reaching out. Tell them that that’s really the most important [INDISTINCT] >> Okay >> LAROIA: Yeah? >> So are you doing anything to, train maintainers on how to break up problems well on how to set up but do some training out, that kind of stuff >> LAROIA: Not yet. I guess that would be read though >> I have a suggestion actually >> LAROIA: Yeah >> I actually came upon one of those buttons [INDISTINCT]. It’s just the “I’d like to help,” when you click that, you feel like you’re committing to something. I think if it was “How Can I Help”, more people will click it >> LAROIA: Okay >> Good. All right. Yeah >> LAROIA: Yeah >> LANDAU: You probably would say, “How can I help?” >> Yeah. Just instead of “I want to help.” Less [INDISTINCT] because you’re taking to an information and you’re not taking them to signing or sign up for something >> LANDAU: Oh, I see. Yeah >> Well, I guess maybe, you know, “I Want to Help”, and then the next page they can just fill stuff in so >> The point is, I didn’t click “I want to help” rest on. What actually came upon it because that I was committed and I have no idea what I’m committing to >> LAROIA: Right now, you’re committing to [INDISTINCT] list >> Right. I realized it, so it’s was actually fine. Mostly for the one that appears on other sites >> LAROIA: Yeah >> It’s relevant for when it appears on that site that you mean “I want to help” otherwise you’d be clicking it >> LAROIA: Right, yeah. Yeah, in our case, I think that’s taking just out of page, and then, well, that is [INDISTINCT]. I mean there’s a way to get out of it, so >> Right >> LAROIA: Yeah, I guess you didn’t get out of the commotion. I mean, are there feedback or questions? >> LANDAU: I think what we’re looking a better one. The Holy Grail would be a way of, a very lightweight [INDISTINCT], but >> Yes. Yes >> LANDAU: Once you’ve made it, you’re kind of, oh, you know, you’re registered in sort of affiliation to the project >> Yeah, but I still think you want that after I’ve been your site >> LANDAU: Right. And may will be >> From a deal more transparent >> LANDAU: Yeah, and we can just like add a little, yeah >> LAROIA: [INDISTINCT] >> The only other feedback I had in your–in browsing projects on the front page, the first thing you see is the list of bugs. If you, I think, it would be imitators, if somewhere there goes a big description to project for a link to their main page or something that’s [INDISTINCT] >> LAROIA: Right. It’s on the, do you mean >> Like if you’re surfing through the bitesize bugs >> LAROIA: Oh, yeah >> You clicked on it and it comes out with sizes of the bugs and >> LAROIA: Right >> Okay. I think right at the top, just had a little just this is what the project is, to be able to motivating >> LANDAU: Just on one OpenHatches or one of the individual? >> What the names on the project is such strong >> LAROIA: So, on in this page, in particular, you might imagine like you’re saying that when you click on Python and looking the bugs there >> Yeah >> LAROIA: Put a little box in here, for example >> Sure. Just a suggestion >> LAROIA: Yes >> LANDAU: Yeah, and go, that’s perfect >> LAROIA: Yeah. I mean, right now, you have to open the bug and slow down and find this link >> I see. Right >> Because you already have that information that people have filled in that probably is about >> LANDAUE: Yeah, great >> Looks good, cool. Awesome >> I like the idea. I once took a class where I was supposed to–I was trying to get–do an OS project for an OpenSource project and I spent–I actually got a really bad grade in the class because I kept trying to find projects and fill in >> LAROIA: Right >> It’s really hard; it turns out in the current environment >> LANDAU: Yeah. And the thing is that the project maintainers know so much more than you do. They know how hard that bug is, that’s why I haven’t touch, I’ll find, know the code What is this I’m saying. But, right, like all these bugs they’re rate from such range and–so some people asked us how come you don’t automatically categorize bugs? And if you’ve maintained some of the code, you’ll know that it’s difficult to know from the title of the bug or from the description of the bug what that means in terms of the code based and how much effort it takes >> One sentence means re-factoring the entire project >> LAROIA: Yeah. Or just, it’s impossible Yeah >> [INDISTINCT] >> It knows, the fact that you’re using, you know, bitesize, so, especially for new contributors, I think that’s really important is to have a handle on something that they feel they’re going to be able to finish and they can see something they’ve done and they can live on Otherwise, if they go into this, you know, come get it done, it will not having encourage them to continue participating >> LAROIA: Yeah. And–yeah. I’ve run an evening event on Python a few months ago where we got–just post it on the door and said, “If you want to contribute to OpenSource projects and you haven’t, come in to the door.” And, it was 11 o’clock at night, we got two people And, so, of them, we re-browse the long term opportunity to find it here and found something to work on, and actually, we all found bitesize bugs and Python [INDISTINCT] them. I am the other person wrote some documentation that was missing and the third person started looking into one of these Python bitesize bugs. And, yeah, like the idea that, at the end of the night, this person you could never like runs a version before can use as generated, a dead file and attaches the bug tracker and dispatches and then merge, that sounds pretty cool >> Should that explains the other really cool thing is that, at least, the next episode you were able to get feedback with really small >> LAROIA: But >> I assumed, you’re actually able to accept them and check them in? >> LAROIA: Oh, I know. I don’t work on bug >> Okay >> LAROIA: Now, and so I actually waited like two or three weeks for the patch to get reviewed, but then it wasn’t [INDISTINCT] >> So, it wouldn’t be cool to get actually get the projects to say, “Okay, now during this week, we’re going to have, you know, overnight turn around or do something.” >> LAROIA: Yeah. And to label bugs beforehand And actually, this is one of the good things about Google Summer of Code; the project tells me. Like, it’s really nice to have all these code written over the summer, but it’s only one or two or three or four or five students But, their project list that–the project list make up, like, those are really valuable because now the projects know when someone else comes by, “Oh, you could do this. It will take you summer, maybe half of summer,” but we know what it would take to do it, yeah And so, just thinking through the process of labeling bugs as bitesize in the bug tracker and then showcasing that can be really reliable Thanks