>> live from Boston, Massachusetts. It's the queue covering your red. Have some twenty nineteen. You buy bread hat. >> Welcome back here to the >> B C E >> C. We're in Boston, Massachusetts, right. Had summit the six time around for us here. The Cube, proud to be a part of this event. Once again, along with student Eamon. I'm John Walls. And thank you for joining us here on the Cube. Continue our coverage. We're joined by Stormy Peters, who was the senior manager community lead at Red Hat and stormy. Good afternoon to you. Are you going after him? All right. So you think about you know I love that, you know, community lead. You know, in an open source based company. You like Red Hat. Your job is very simply expanded. Evolved ecosystem, Right? So So I mean, how are you? I guess using that that company culture that embedded culture to grow, I think it's already pretty well established. What are your reputation is for how open you guys are right to the community. And what have you What are you doing in terms of leveraging that and trying to expand on that reputation? >> Yeah. Our goal is to make sure we're supporting those upstream communities. So all of all of Red Hat software is open source, and we worked with a whole community of individuals and companies, and the upstream opens our software. And we want to make sure that we're not just contributing features that we want but that were a good player, that we're helping to make sure those communities air healthy. And so, for a number of the projects that were involved in, we actually assigned a fulltime community manager a community lead to help make sure that project is healthy. So we have someone on everything from stuff and Lester Toe fedora Toe Cooper Netease. I'm just making sure the community does, well, >> stormy. You actually did a session for analysts about about a month or so ago, and I've been involved with open source for about twenty years, and you said something that made me do a double take and had to rethink the way I look at this commune unity. And it was we used to think of open source as well. May be I worked on a project, or maybe I spent a little bit time on nights and weekends and it was just kind of giving of time. You said that a majority of people working in this, they've got day jobs that is contribution to this. It's, you know, we understand that companies like IBM and Red Hat and Google often will have that. But the majority of people that are contributing open source now that is their job or a major part of their job. Could you stand a little bit about You know, how we saw that shift? And it's just me that snuck up on. >> So I think it's stuck up on us, all of us. But I really do think it's a fundamental shift that we need to consider so that we can make sure that we're helping the ecosystem the best way possible. So when open Source first started, it was people in their free time. You know, Linus Torvalds had a project he wanted to work on. You had it, it's described. You wanted your desktop to run free software, and so you put your free time into it evenings and weekends. And if you've got a paid job, working on it like that was something to celebrate like that was everybody's dream. And these days, with software becoming more complicated, more complex, and the solutions are even bigger and greater with the cloud there more than a one person project. They're like multi people, multi company projects. And so more and more people are getting paid to work on them and they're getting forty hours a week paid time to work on these projects. They might give more, but they're getting a full time salary. And so how we include not just the individuals but the companies that are paying them to work on it, I think changes how our project's work. I think it's a huge opportunity, >> and I mean talk about that shift a little bit, if you would then and how that has, I would say mature the marketplace. But certainly it's altered the the flows of jobs and innovation and development and all that, because I kind of passed time before now full time and what comes with that? I mean, what challenges come with that we're all of a sudden It is Ah, little, it's it's a little more parent, if you will, right and that you're a little more evident in wherever you're working because it is a full time commitment outs no longer just a of casual or less than full time pursuit. >> Yeah, I think it's a good thing, but I do think adds challenges. So, for example, on boarding process, you used to know when you had an open source software project you've got. Someone was giving up on our two of their evening TTO. Learn your project so you had to make sure that getting started docks worked for them within twenty thirty minutes. Maybe these days, you know, it's really hard to install a lot of this software in twenty or thirty minutes, but someone's doing it is their day job. They're going to have a day or a week. So the on boarding process is different, which I think makes it harder for volunteers and easier for paid volunteers and paid so little a little hard to distinguish. But for people that have all day to do it, they have a little more time to get on board into the on boarding processes are take longer. I think the problem is that we can solve our more complex because someone can spend an entire week. They're not breaking their thought process up like evenings. They have, like, all day. They can work with teams across cos he can pull in lots more expertise. We have a special interest groups and projects like Santos on where we're pulling in different companies to work together. I'm so like we're working on an NFI save with Intel and others. I'm so you get you get more diversity of people that could work on it. That can dedicate more brainpower to in one one setting. >> You can't. Can you talk a little bit about? You've worked on foundations and you support foundations. Talk about special interest groups. It's pay broad and very diverse ecosystem. Sometimes the outside rose like, Oh, it's thie, open source community and like No, no, no. There is not the open source community, their communities and lots of overlap. And they work in Iraq, maybe give us a little bit of context and love to hear some examples of some of the things you're working on. >> Yes, I think the first point is like projects aren't there. How they worked. Their governance isn't isn't static like it's always changing, like you might start a project on your own in your free time and it grew and you convinced all of us to join you. And now there's twenty people working on it and you want to be able to go on vacation and then you want to leave somebody in charge. So do you give him maintainer status? Do you create a board and let people vote? So you create a foundation like someone offers you money? How do you take it like I do? You put it in your bank account. Er, do you have to start it like a nonprofit to take this money? So I think they're constantly evolving. So an example that I have is the foundation we created the set foundation thiss year last year. Recently, um, and stuff has been open. Source It was it was open source created by thinktank acquired by Red. How we created a board of advisors around it to keep all those companies involved. And it had evolved to the point where people wanted to give it money. And so it needed to be something. You know, these companies wanted to collaborate on marketing together, So we created this a foundation as ah directed funded clinics foundation and had, like thirty companies joined in the very beginning, so I think I don't know what the next stage herself will be, but they're always evolving like that. >> But so what does it do if you will? Self? How do you pick projects out if you have thirty? Voice is a lot of voice. Is a lot of people raising their hands and let's look at this. Look at that. You know how to govern that. How do you, ah, assign work? How does all that work in that kind of? That's a really open environment that you're trying to corral a little bit. >> So So we're not trying to corral. We're tryingto like we're >> organized. A better >> word. Better word. >> So that the foundation was was enable people to collaborate on the marketing side, mostly a money side they wanted to give money for, like Suffolk on event. That's happening in a couple of weeks. There's a big annual event they wanted to be able to do Seth days. I'm things that you want to give money to enable it was getting really complicated. Will you pay for the beer and I'LL pay for the food and you know we'LL do it that way. The stuff project technically is led by a group of volunteers will have paid jobs and there's a project lead person for each sub project. And then they have a monthly meeting of all of the the whole project. And then each of those sub projects has a weekly meeting and something that stuff doesn't I think, is really interesting as they record all of their team meetings like it's a video meeting and they record it and they put it on YouTube and people watch the like. I think that's awesome. But it helps them with the time zone problem to record the meeting and put it on YouTube. >> One of the other things that I find really fascinating is many enterprise Cos now you know, we know they're using open source, but they're contributing open source. I remember back the future of open source survey that was done is think it was like half of companies that you know we're using it are also contributing. What do you see? You know, we've talked to users of the show for many years, is toe You know why they see value and why'd you do it, but it would love to hear your take. >> So I do think cos air. They're using open source software, but they're contributing on DH. People talk about what you contribute, the features that you want to see, but I think you contribute to the things you find exciting and that you want to participate in contributions. Starts at like very beginning level of just filing a bug report when you see it are coming to an events and going to the happy hour for that for that project of seven Cluster have won this afternoon. This afternoon. You know there's different get togethers and you participate by meeting the people, telling them how you're using it. I'm telling them what you'd like to see What's cool. I think a lot of people in the open source world, there's an opportunity for the developers to be very close to the users in the way that's harder and proprietary software. And it's really exciting, like if you're working on something and someone comes up and says, Hey, I'm using it and here's what I like Peanuts. It's fun. >> It's working All right. >> How about career advancement? You know, everybody I know in the developer world. It's like, Well, get really is your resume these days? So I gotta imagine that just the skill set and the education is such a huge part for so many companies. >> Yeah, with more people getting paid to work on open source and they can show what they worked on on that it's more, not more coming. It's very easy to move to another job, taking your skill set with you and it's very valued and you even get to keep your community of people that you're working with as you move around and help different companies with that project. How do you >> divvy it up in a community where you know the workload is kind of equally shared? Or there's a fair share of work being done and you and you want to. Maybe some people have a different level of expertise on DH, so there's some policing that kind of has to be done or argus. Some responsibilities assign whatever >> that could be >> a little delicate. Sometimes candidates you won't get the right people doing the right things, and you'LL love, willingness and enthusiasm. But sometimes you do have to kind of decide are you gonna work on this? We're gonna work on that. >> So some projects have done a really excellent job of defining the rolls and assigning them and having like, a mentoring process to get new people there. So, for example, Cooper Netease on the release team, there's like people that worked on the release team. And then, if you're interested, you raise your hand and you like work with the the person that's in that role for, like, an entire release. And so you get like a whole released to be mentored and taught, and then the next year you're the person doing the release and you can mentor somebody else. So I think the process is help with that. And it's, I think there's some really great work. >> You're building the farm team basically right. You're bringing them along on training wheels to a certain degree and then let him ride the bike by themselves, yet makes sense. >> So speaking of getting people ready, there was something new announced this week that I'm hoping you could explain. The Red Hat Universal Base image was explained to me that this is really a subset, Terrell or being roll ready. What Does that mean? How is that going to impact developers? >> Yeah, the idea is to help developers developed in containers on Lenox and in a way that they can so the FBI is based on, Well, it's a subset of rela packages. It's a it's a container, so in the clouds face and that you can develop your app on it. And then you can share that container with anybody. Whether or not there are real user, I'm so you can share it with anybody in the world had them developed on it. But then, when you're done, it is supported on grell and open shift so you can have full enterprise support for that's >> a show like this. Inject new blood new perspective into what you do. But I would assume this is a pretty good recruiting opportunity to in a lot of respects. And you stay pretty busy over the course of these three days, meeting with a lot of new people, meeting a lot of new faces, getting a lot of new ideas, a house to show kind of fit into what you're going to do the other three hundred sixty two days in a year. >> Well, We look forward to this show for three hundred sixty four days a year, so we're always planning foreign prepping for it. It adds energy. It adds excitement. We get to connect with people. They're using the software. Hopefully, they do come to the happy hours or down to the booth and talk to us and say, Here's how we're using it. We hope to get more people involved. People that are using software that want to learn about it, get him more involved. >> Well, you've got a great job of pulling the community together. We wish you continued success in doing that. Thanks for the time today. Here in the Cube. Nice tohave you. >> Thank you very much for having >> that story. Peter is joining us from red hat back with more in just a little bit. You're watching the Red Hat Summit and you're watching exclusive coverage right here on the Q