 Hi, my name is Anna Jimenez and today I'm here to talk about DEF-RES, VRM, and community building within open source program ops. So let's get started. During the years, companies have realized the many benefits open source has and a lot of them started to consume open source projects, but also, some of them they started to contribute to open source projects. I can give you an example, for instance, Samsung, Samsung, it's a company which software has open source components and they realized that consuming to them wasn't enough, so they started to contribute as well to get their contributor accepted in those projects. And also, there are other companies that even release new open source projects and the benefits that that can have, for instance, the many benefits can be, for instance, to attract talent and return talent. So there are companies that do all of this, there are companies that just focus on two or one part of this. So there is not only the inbound part that will be consumed open source, but the outbound part. So companies realized that to accomplish all this, we need specialists from all different fields. We need legal, we need community building, we need human resources. So they started to incorporate in their company a place called open source program offices in order to have a centralized place to achieve all these different tasks, all these different activities. So today's talk, I would like to focus on the area of releasing open source projects and the main specialists that should be involved in there and talking about community building specialists. So when we talk about community building specialists, the first thing that might come to your mind will be maybe project managers, community managers, marketing specialists. But what about dev roles, because I know just a few dev roles are getting into open source program offices, but it's not being mainstream at all. And for me, dev roles are community building specialists too, and can bring a lot of value to open source program offices. So let's bring a little bit of context about dev role first. So developer relations roles are diverse. And what I mean with that is that depending whether they have been hired by a foundation or by a company, and depending whether the software of that foundation or that company is open source or not, the objectives are going to be different, they're going to change. And not only that, they can be reporting to different departments. I've known dev roles that report to marketing, for instance, and I've known dev roles that report to engineering, which is a completely different area. And even others reports to support. And this makes really, really difficult to measure success in dev roles, because they are going to have different KPIs, different OKRs, depending on the department they belong to. So what does that role do, actually? So I would say look at their name. It says developer relations. And that means building relationships with developers. And some developers might want to get users to the company or foundation. So users will be the one that asks questions to GitHub or GitHub or to form. Others would like to get contributors. So those that not only provides questions, but provides answers. And other ones might like to, would like to get maintainers that are the ones that provides code to pull requests or to match requests, for instance. So from an expert point of view, what's will be the code? So I think that it's important, will be important, really interesting that a goal will be transition from users to maintainers. And that's something a dev world can perfectly do. So to achieve this goal, I think it's really important to understand first the developer journeys, because there are multiple developer journeys where the developer might be and start to know what was the starting point and how, what is the journey that he or he is having, OK, he's having. Also, it's important to understand connections. So of course, developers are not just in one platform. They are not only on GitHub or on GitHub. They are on mailing lists. They are on chats. They are on forums. So it's important to understand the different connections and where a single developer is across the different platforms and how those platforms are changing when we are looking at the different stages of the developer journey. So OK, that's great, but how can we achieve this? How can we know this? So as Lord Kelvin said, to measure is to know. And here's a quick story. This is about Chaff. Chaff is one of our current customers at Victoria. So Chaff had also user community and contributor community, and they had this goal of, OK, we want to transition from user to contributors, right? So they identified their main platforms where their community is. So they know their communities in this course in GitHub and in Slack. And when they become contributors, they start to add more activity on GitHub. So with this, they were able to understand the developer journey and the different connections between platforms. And this will help them to know how much support and how much internal efforts and how much internal developers to add to the different platforms. So when we think about what to measure, it gets clear. Metrics involving knowing your community should be involved as well. So to get this traditionally marketing, this has been done through CRM, a customer relationship management. But is that enough for several specialists and community specialists? Because actually, developers behave quite differently. So developers have different touch points, different motivations. And different ways to interact. And traditional CRMs cannot achieve all this. So I came up with the idea of the community relationship management. So to achieve this, one important key point is the identity affiliation management. So this will help us to know who is who because of different platforms and avoid multiple identities. So there are some existing tools for that. One of them is Searching Hat. That it's part of CrimoLav software. That is also part of the Linux Foundation Chaos Project. It's a CrimoLav and Searching Hat are 100% open source. And we are always looking for contributors. So I will give you the URL to the GitHub repos in case you're interested and you would like to contribute. And also just to mention that Searching Hat has a user interface, the one you were saying on the slide, that it's called Hasso. And that makes it easier to declare organizational affiliations, even correct attributions of contributors. So to sum up, let's bring up these three main ideas. So the first of all, Dev World can help to transition users to maintainers and that help open source ecosystems within Osgold. Also, traditional marketing platforms are not enough to achieve all these goals. And affiliation management system is key to build CRM for the Stanford community. So the story about it here, we are the core developers of CrimoLav and Searching Hat and we are software development analytics firm and we are helping companies and organizations to understand the software development projects that matter to them. So that's all for today. Thank you so much for staying until the end. And if you have any questions, just feel free to ask. Bye. Hello. Welcome. Thank you for staying here until the end. So now we are going to go through questions. I don't see any questions right now. So I will just invite you to ask any questions you may have about this talk. Let's wait maybe two, three more minutes because we have plenty of time. And yeah, I'm here to help you. OK, so what are the top three metrics that Dev World should look at? Well, as I mentioned during the talk, depending on the department that Dev World is there, that Dev World is reporting to, they might be having different ways to measure the effort and ways to measure that success. But I think having Metric Relaguarding Community Building should be also there. I'm not saying that it's the only thing, but it should be definitely be there. Actually, a long time ago I created a blog post talking about those kind of metrics that we should have, such as the developer engagement. I was talking about the developer activity. Let me, I don't know if I can write you something here. OK, so top metrics. So let me start with you the blog post, because I think it's going to help you better than start mentioning some of those metrics. OK, here it goes. OK, so, OK, I think you can see the link. So there I talk about some metrics regarding community metrics. And I hope it helps. So next questions. What would you suggest the Dev World professional to get started with getting data to show the ROI? OK. So as I mentioned, first of all will be the community and start looking for metrics regarding community. And after all, of course, depending on the department you are, then start looking for specific, for instance, if you're reporting to marketing, then should be specific metrics for marketing. If you're reporting to engineering, specific metrics for engineering. Next question. What is the easiest way to manage community metrics when you're new to the, sorry, GL, Samantha, I don't, if you can let me know what GL is, sorry. OK, I will wait for your answer and then I will answer the next one. What are the top, OK, that one was already answered. How can I find mentorship to improve that well? OK, actually, I don't really know how to answer that. I will think about it. And if you can follow me on Twitter, my name is Anna. Well, it was on this slide as well. But if you reach out to me, I will answer to that. Grimoire Labs, OK. OK, OK, got it. So coming back to. OK, I will say if you have got to the G-Lab repo, in there there is a lot of documentations regarding exactly that answer. So I would suggest you go to first chaos community. So it's this URL for long. I need to OK, OK, so go to that URL. And then in software, you will find the Grimoire Lab repo. And in there, there's a lot of documentation where you can search for that exactly. OK, OK, what else? OK, how can you community with all the members of the community, users, contributors, maintainers? So I will say first, learn where those users, those contributors and those maintainers are. Because they will probably be on different platforms. Like, for instance, maybe your users might be in this course. And maybe your maintainers, maybe, and contributors, maybe on GitHub. So first, you need to know exactly where the different community, like where your users are, where your contributors are, and where your maintainers are. They might be also mixed. Like, for instance, when I talk about Chef use case, they say that sometimes you can find users also on GitHub. But mainly, they will be on this course and Slack. Because they are not contributing actively to code. They're just asking questions and getting into the platform, into the software. OK, can you give an example of how metrics have been used to understand a developer's journey and how those insights allowed growing the community? OK, so as I was saying, Chef is a clear example. So they had a lot of users, but not so many contributors. And what they wanted to do is go from users to contributors. And by looking at the different platforms, they could understand the different touch points and the different interactions they were having when being on Slack. And then when those people that were on Slack on this course moved to GitHub, from them, it was already a transition. And that can be done through the affiliation management, and any affiliation management identity management. Sorry. That can also know who is who across the different platforms. So if a person was initially having activity on this course and then moved to GitHub, this affiliation system can know that that's the exact same person, even though we are talking about complete different platforms. What else? OK, and I think that's all. Yeah, I'm not missing any question, I think. Yeah, just to come back full about the mentorship question, just if you messaged me on Twitter, I will answer to you. I will think about that and answer to you in a short period of time. OK, so I think we have four minutes left as far as I know. Thank you for staying here until the end. OK, what are the top three metrics? That's already done. What's your Twitter account for community nodes? OK, yeah, I will answer to you. So this one. Metrics to measure inner source. OK, so that's a different topic, but there is a community called Inner Source Commons. And they are working on exactly that where you mentioned it. Let me give you the link for that. We're also in Victoria actually participating here on building those metrics as well. So if you go to this link, yeah, so if you go to that link, you will find more information about metrics to measure inner source. I don't think we've got the link. OK, which link? The criminal lab or the chaos link? Samantha? So OK, I'm going to send it to you again. In case you cannot see, if you have my Twitter account, just message me and I will send you the link there. OK, so this is the link. Scrimmel lab, yep. OK. And yes, OK. Well, it's working well, this platform. I think that's all and it's already 45. So thank you so much. And yeah, I don't know how to cut this, but bye, everyone. And thank you again.