 Okay, we're going to go ahead and get started with the life cycle of community again Leslie Hawthorne unfortunately is not going to be able to join us today as she did fall ill, but I will welcome my partner in crime Amy Marish and myself Cara Delia both red-hatters. I actually sit on Leslie's team and So Leslie looks after the vertical communities within our Ospo at Red Hat. We sit in the office of the CTO. I focus on Financial services and sustainability focused around climate change as opposed to community sustainability, so Just want to go ahead and talk about some of the experiences starting with myself building community and and then Amy's experience really living and breathing in an established community. So the community that I started As a community manager was OS climate. I think you've heard a lot about OS climate today OS climate is an open-source project that was welcomed into the Linux Foundation last August of 2021 and it is focused on open-source tools around sustainable finance red hats contribution to this project is a data commons platform and What that allows is data ingestion from public data sources and proprietary data sources Predominantly through a data vault if it is from a proprietary standpoint I will go ahead and apologize if you are a visual learner. There are not many slides today So this will be conversation based focused So one of the things that was unique about OS climate is that I was bringing together a disparate group of stakeholders and that many of them were technical and But the predominant were non technical and they were also dealing in the financial services space very regulated as you can imagine So open-source readiness, which is something that we focus heavily on within the Red Hat Ospo Was an area of being help being able to help them understand What the value of open-source is and so I always like to open Gab if you haven't met Gabriele Calumbro, who is now the leader of LF Europe He is amazing very passionate about open-source and I always like to share this quote from him and that is around the Open-source being a strategic tool to drive innovation and especially within financial services Innovation is while it might not necessarily seem to be the most interesting It is a predominant driver, especially on the consumer side if you want to go to the next slide So the evolution of community engagement and that is around you know being able to get your those disparate sources You have finding your key strategic partners So one of the things within our Ospo, I talked to customers talked actually to to many customers Out in in Dublin this week I've been very fortunate to meet them face-to-face instead of just a tiny little square on a zoom call, but um But helping them to understand that the obviously developers are going to be their key technical stakeholder but the ecosystem of Stakeholder management within ospos or within open-source is The the non-technical side as well obviously code gets us there But it is through the amplification of that code And the good work that the projects are doing that we're able to to share that to share that vision and so I like to Mention it as you know if a tree falls in the woods and you've created this beautiful piece of code Who's going to know it so so that's where you need to get in you know your marketers your brand and But very much your legal and compliance To make sure that you are you know obviously not taking on any unnecessary risk And but these are key stakeholders in building community while it might be from the the ancillary piece Not within the actual day-to-day of a community It is kind of that halo around the community And one of the other pieces that I talked to our customers about a lot is the value of ospos Obviously, we've heard a lot from the to-do group and and in folks Here during during Ospo con Ospos are truly the next phase. I mean Google was in AWS certainly were Kind of the frontier folk of of Ospo land and Now what we're seeing within you know the horizon is that ospos and in our source are usually it starts with inner source and then Helps to feed into the larger Ospo strategy are becoming more and more and This is heavily for industry and one of the other areas that I'm seeing this especially in Europe is around the public sector. So ospos within government There's going to be a lot of conversations in Bernou later this week Yes, this is Thursday. So tomorrow Time is a little relative at the moment, but um tomorrow and over the weekend They're going to be talking about, you know, what does Ospo in the public sector in government actually Look like and how can we use the the common? principles of of open source around Collaboration Innovation to be able to leverage that way actually within government and I like to think That also this is going to help with sustainability goals with climate change to be able to co-create For getting to net zero that much faster So I think there are a lot of challenges in open source from Optics standpoint, you know within this group we are within this conference. I think we also see the values, but I like to always have in maybe it is just because I deal with financial services and usually it's the risks and the Blockers that the first question so helping to bring people on For realizing that even though there might be silo teams There might be technical debt, you know being able to showcase that these challenges up here Are actually going to be able to be mitigated through open source I don't know if you anyone had the opportunity to hear martin sweeney and the folks from IBM talking about the next one And then IBM is our parent company, but the The risks and security vulnerabilities that do come about within open source are are easy to or not easy, but they are easy to at least answer and be able to identify what does that supply chain look like Next slide please So In kind of parting, you know sustaining communities and their innovations. I'm certainly an advocate of open source and You know the sustainable communities I think do you have more of a motivator especially now with the climate crisis with and And this is going to be able or the focus here is to move beyond just the day today And the the short term mindset to really that larger strategy Thank you. I'm going to hand it over to amy. So I didn't really talk much about almost climate If you do have questions about us climate, absolutely find me through here find me on linkedin And because I did start the community, but really I would like amy to give her Her tech or her knowledge around the communities that she works in that are much more established Right, so we decided we would start with how to start a new community And then i'm going to go into an established community and a changing community So the established community i'm involved in is open stack Open stack is not dead y'all We have over 40 million cores out there, but we're no longer the hype cycle Um terry keres presented yesterday and actually pointed out we have the same number of contributions as kubernetes But y'all think kubernetes is the hotness So just something to keep in mind We do also as the technical committee meet with the kubernetes steering committee We all have the same challenges of getting people involved Finding developers finding code contributors Finding documentators So all communities no matter where they are in their hype cycle do have some of the same challenges So it's important to still be out there talking about your project And just talking to people coming to conferences giving talks on them And just spreading you know that you do exist Um Cara kind of mentioned governance make sure your governance is in place and it's solid um Even an established project uses legal Um in the case of open stack we name all our releases and we had a big discussion about going to numbers and i'm like no You want to put numbers in the code? That's fine Marketing and for community aspects the name is so good because if you ask me what version of open stack i started on i'm not going to tell you it was 20 01 blah blah blah i'm going to say i started on grisly You ask someone else they're going to go i started on mataka The name is so important in holding your community together and the strict developers didn't quite get that So we handed naming back to the foundation to take care of The went through legal to get the names before we voted on and we're going to be antelope Why we're not art bark. I can't tell you why art bark did not pass legal I also I knew we were not going to get yoda. We got yoga But i wanted yoda so badly You know so sometimes you know you're still going to use legal no matter where you are in your life cycle um so The established community you have your contributors and you're going to lose contributors because they want to try something new A lot of them come back if they really love the community I like to call open stack of family And it's a family we get together a couple times a year and we just like slip into that relationship Whether it's virtual or in person you hang out with your crew You see someone who's alone you invite them to your crew Because that's a strong community And it doesn't matter that it's not the new hotness Because y'all are family um So going into a changing community I'm involved with sento s sento s Yes, we did change where we are We did change what we're releasing so we're no longer a repackaging of rel We now lie between fedora and rel Now the great thing about this Is that you can now contribute to sento s Now we do admit that stream eight has some workflow issues And when everyone complains about stream, they're really complaining about eight We have fixed Or are really fixing the workflow in nine so that you can become involved so We met as a board at devconf for our first face-to-face in a while and One of our number one action item is onboarding documentation Because it doesn't matter where you are in your process If you do not have good onboarding documentation, you're not going to get new contributors So revamping the website onboarding docs things you wouldn't think an established project needs But very very important. I mean even in open stack. We go through all everything occasionally and make sure that the workflow still work Do I set up my Memberships and accounts and the software does that still work? and over time it doesn't because Open stack changed from open stack foundation to open interest foundation So things changed on their location. So we had to update all our documentation So keeping up with your community, even if it's established is very very important To make sure that you as a leader are making the right decisions from a technical aspect As well as an overall aspect So one thing we didn't get into Or not or maybe just touched on with the mention of finnows is a foundation versus a foundation in your project Open stack started with the open stack foundation quickly after So there's a board of directors that comes from sponsoring companies As well as the community. So we get nominated. We have to get 10 nominations Before we even go on the ballot to become a board member December and january very stressful You just cross your fingers that people recognized how much work you did Um So we do budgeting for the foundation I mean we're very hands-on with the money and the decisions and more some board members are more active than others Um, but sent to west on the other side is a red hat project We have events, but we don't have the visibility into that budget Um, we are now doing open board meetings. You do have to get invited But it's open for any members of the community and that's new for them So i'm trying to bring in open infras for opens To a different community to get them more open We do not refer to the rel developers and the community Everybody's contributor And you have to stress that with both sides Because it's not in us and them in your community It's in us How are we doing on time? Okay, so some other things that when you have a more established community marketing is important onboarding legal all all things that are mentioned But also just double checking and checking in with your community Throughout the year is everyone doing okay, especially at these times making sure you're not burning out your developers um Open stack is a little different And because it has a main project, but then lots of projects within it So even checking, you know at the time of elections Do we have leadership for that other project? Can we find a volunteer? Do we need to retire that project? What would that be the impact of retiring that project when the within the larger project? So Always keeping an eye on what's going on within all aspects of a community from a technical point is important But also from a community aspect Is there anything you want to add? So I think in closing because I definitely want to open it up for some questions, but you know, I think two in What Amy was saying is the contribution piece is is is super key Especially in a new community And especially with the community that might not necessarily be technical first And so that clear documentation is 1000 and the governance piece as well Anytime you are also dealing with data is having a clear data policy And understanding your data lineage understanding your um your ingestion pipeline um In addition to is being inclusive. I think that community engagement piece is So much is so key because so much time now you hear of imposter syndrome my background not technical um, I mean I have understandings of concepts, but it's not technical and Many times I talked with my peers and they're saying well, I can't contribute to an open source project And so it's really as a community member And as a community manager it is to understand to to be able to Um broaden your community is to be able to include a multitude of types of contributors to your Come to to your community and that key of checking in so important truly these and in these times And I know that was one thing Leslie did want to say is that during the crisis It's you know community engagement is super critical So did you have any So your contributors aren't just code documentation Meetup leaders So it's important that you include all of them and still call them contributors Because those are also the best way to get new people into your community They might go to a meetup. They might volunteer to lead that meetup next time Well, hey, there's something wrong with the documentation. Let me fix that You know, this is kind of cool. I want to learn how to code that I can make this one change. It'll take me two seconds And you get them hooked They want to do more because they like the community. They like what you're doing And it all started from going to a meetup And as far as imposter syndrome one of the most technical people I know who you would think Would never suffer from a given imposter syndrome talk And then it was like wow if he's gotten imposter syndrome. Oh my god So then you're now standing up and giving talks Because you notice that if someone if you didn't do it, maybe no one else would So those are all important things on growing your leadership as well encouraging person to do one thing then it grows from there I'm just gonna say I think that's a great point and opening it up for questions Or concerns Sure and the question is Being able to attract more of a Beyond the newcomer so being able to attract Um, and it's someone that would be advanced that into your community I will say from os climate From perspective it was working with the uh, the business leaders that were contrary or that were essentially the paying members of the project To be able to essentially give them a sales pitch This is the value give contribute or convey this value back Um, and in many ways in other communities i'm a part of not just os climate It is create it's creating that value statement for them and letting them know that they that they would really Be of value to this project. I mean who doesn't want to be a value And so being able to convey that is a key piece um, and clearly Yeah, kind of the same thing from the very early days of the open stack foundation Platinum members had to contribute full-time equivalents So if you wanted to be a platinum member you had to bring An employee or two a developer or two you generally um, but if there's people That you have targeted It's such a compliment for you to go up to and go hey, I know you have a similar interest in this I think you could bring so much value Whether you can bring code if you can mentor someone else Because mentoring will help bring those newcomers up and they'll bring them up quicker And sometimes it goes back to that imposter syndrome thing. Maybe they don't realize they're that person you're looking for So they don't even think to volunteer or to come join. Yeah, they're interested in it, but you know Yeah, what's one more line of code gonna be but they're gonna bring something beyond that one line of code Yes, so So for the audience way, um, which saying is that it is From the first approach with when you have the business buy-in it is going to be easier for the um to get on the docket Essentially or get on the meeting calendar for that developer because obviously there is um known value there Would you say that's a fair? Okay. So the other piece is um, so it's contributing or sharing the value And then it is instead of boiling the ocean it's giving them the one thing that you really need them to do immediately and So in in os climate what I would do is I would Work with the different work streams and identify the one thing that needed to be That was a real crucial area of need And within the next you know one to three months And typically it would take about a month to get someone to do that So it was being able to identify that with the work streams But then the next step is identifying what that is and having an office hours or open source readiness hours Is what I called them to be able to bring those different people together And it was a quite small group explaining the value of the you know Just high level never more than 15 minutes to a half an hour because everyone has a busy day um, and just being as concise as possible and um, and a lot of times that would have to be an iterative process and um and in addition to that The is making sure that within the contributor guidelines that I was sharing that so it wasn't just I had to have a meeting with someone That this was asynchronous asynchronously Accomplished as well either through a pull request or through um a hack and defile And as far as you know getting someone who's very busy to Participate one thing we've learned from having community events Where we were onboarding people but we'd ask questions to make sure people were listening A sticker would get someone to answer a cookie would get someone to answer There was a really good talk on monday during the chaos con which will be available on um youtube about badging So sometimes that teeny tiny little reward that you wouldn't think would make a difference Will get 10 minutes of that person's time in order to look at your issue And then they'll say that'll take me a second You know so something just a little reward to get participation is enough to get someone who's more experienced in Because you're all the way back here So my question is what kind of meetings would you mentioned already office hours? Like in my project we have basically developer meeting But now we see your need for okay, how do we do onboarding? We have governance me So what's kind of like typical meetings? Would you kind of recommend a project has for doing onboarding the developers and all that stuff? So one thing open stack has done and like I mentioned we need to work on centOS is onboarding So i'm not going to discuss it because that's all work in progress Is at events we would hold what we called upstream institute Day and a half. We would teach you governance. We would help you set up your machines So it was a commitment for you to come to a conference early, but we were going to help you through Everything you needed to get started We have really good step-by-step documentation on onboarding. We hold a sig meeting So there's lots of things you can do virtually online When we had virtual conferences, we would still have a set up session It's a little harder because you can't walk over to someone's machine and see the error they have But we'd have enough people that if we needed to break them out into different rooms And share screens we could do it But it all depends on the tool set you're using Open stack is one of the few projects that use Garrett. I love Garrett I think it's easier to get patches and commits in I suck at pull requests. I mean you would think I'd never contributed to an open source project When I do a pull request and then I have to squash a million and one because I'm used to just patching on top of patching So an understanding of your tool set and how to use them is important and it should be documented We did try to do videos But by the time we do the videos and get them finished they were out of date Um, so I think trying whether it's virtual in person to have you know onboarding at events is very important So with os climate, um When I had the weekly office hours and that was more for folks that had just general questions um monthly all hands meetings and that was more Opportunity to give the feedback of what was happening on the board level On the technical steering committee level and uh from the project work streams But to get that engagement piece. I did have um by By monthly so twice a month. I was going to say it by weekly. It was not twice a week. Um two times a month. I had open source readiness or I had just project readiness sessions for anyone that had any kind of general questions, but then I had deliberate half hour and this was weekly office hours for contributing and A lot of times what I actually would do is go after the contributor because and that was uh Folks that had been identified that they wanted to be in the That they wanted to have to be a part of the project So I would I would have it be where it was almost a one-on-one with us and I would have One-on-ones with a lot of folks Where people because people didn't want to necessarily Feel like they didn't have the right answer in a group setting Yes in the back I think that's a great point and so for the audience it's um the recommendation and wonderful Concept is to actually refer to office hours as drop-in hours so that it is More inviting to be able to ask the questions And I think the perception is with office hours is that you are going with an issue already And sometimes you don't even know the issue or the question that you need to ask and And so I think too that would probably help the types and also the other piece of that is that the drop-in hours could Be more inclusive for folks that might not Feel like the the contributors that might not be asking the questions and that have very valid questions within the community Now not necessarily meeting Related but your mention of twitter brought this up to my mind One thing we found with the open stack operators is they weren't getting the messages that were tagged for them on our mailing lists But we found out that they were reading twitter so we made a twitter account So whenever we want to send something for like at the ops meetups We send it via twitter and we get responses So know where your audience resides and the best way to contact them And one I absolutely 100% agree with that and the other piece is is just ask the community That was one thing. So I wouldn't have normally chosen to have my Calendar filled with all these meetings But one of the reasons why I did have it Is that I was asking the community and also it was a global community or is a global community And so, you know, my time zone might not be someone else's time zone. And so Being able to have the asynchronous part is important But it is just asking what are your preferred methods so that you are where the the You're you're bringing the content You're you know, you're bringing the information to where the audience is able to consume it Any other questions? Well with that, I want to thank you all for your time and space for spending time with us and Hope you have a great rest of the conference. And again, we are down at the red hat booth This is Amy Marish Caradelia signing off