 Welcome everyone to the first webinar in our LFX series introducing the LFX toolkit today we're going to be diving into the LFX insights tool. So you'll learn today how you can learn a bridge data to make more informed decisions about your projects performance beyond the code. And just to get us started a few of housekeeping. Sure, we're all familiar with these zoom calls and how to leverage chat and webinars, but we will be monitoring the chat, as well as the q amp a very regularly throughout this. We'll try to address some questions, you know, live, excuse me, some questions live in the chat, but we'll also have plenty of time at the end to really dive into any, any more questions that that will come up throughout. So please ask away in chat, as well as in the q amp a feature and we will be on those sites. I want to introduce the team that's here with you today for our webinar. So she brought car will be the presenter. So he's going to walk us through the LFX insights tool, giving us some context around LFX overall, and then diving into a demo of the capabilities. He is our CTO and GM of products and so he's very very closely aligned with these the tools that we built out here. Myself, as well as our technical product manager such in Gupta will be moderating so we will be on the chat addressing any questions, we will be fielding the questions for the q amp a at the end. And if anything else comes up, we will be there to support as well. So with that, I'm going to go ahead and hand things over to shoe breath so that he can dive into what we're all here for today and talk through our LFX toolkit and specifically LFX insights. Thank you. Thank you for attending everyone. So, you know we have been working on this product, particularly the Linux Foundation engineering team for almost a couple of years now. And, you know, as we are bringing this LFX chain of tools, the primary purpose why we build these tools are to, you know, build more sustainable open source projects during the entire lifecycle. So, how can we actually help these projects succeed right. You know, again it's will be pitching to the choir if we say the world runs on open source, but the critical projects, they need more than, you know, a source control system or version control systems or a one off tool here or there. You know you need help growing these projects and become those category leaders. So projects. The first thing, you know, is that you know you need to have a finger on the pulse of the entire ecosystem, not just the code, right. And there are tools that you know there should be tailored to the key stakeholders right the stakeholders could be maintainers contributors community managers outreach committee members the governing board market years and much more. So, over the last decade or so the Linux Foundation and in all its sister foundations as an entity have evolved a proven methodology to help address these challenges and you know transform you know early stage projects pledging projects into those category leaders right. So, the LFX tool chain that we're going to talk about it essentially operate operationalizes this approach, or this methodology, and we have a set of tools to you know help. Those are built to facilitate every aspect of the open source development lifecycle. So there are 12 tools in the tool chain, and as we go through this year next year will be adding more and more of these tool chains into the kit. Today we're going to focus primarily on insights but just to give you a super high level in, you know, headline here. Security is the one that we have built to look at vulnerabilities in the projects, you know software bill of materials license compliance and whatnot. We have an individual dashboard which essentially serving creating a community profile. Also, primarily meant for users to, you know, get their badges, whether those are training certification badges, manage their code contributions, and so on. Obviously, many projects have been using tools like ECC LA for managing, you know, contributor license agreements, or whenever they are contributing code as an individual as a corporate. We last year we had in the same toolkit we had launched mentorship. Most Linux Foundation projects are already leveraging this platform to grow the community. We have a crowdfunding tool as well, which projects are leveraging to raise money and funds and spend it where they feel fit whether it be on infrastructure development documentation travel events or not. You know, we have a landscape utility which lets you, you know, look at the entire ecosystem in terms of like, you know, the commercial support the vendor support the partner support the tooling available for that open source project. We have a community events tool that we built, essentially if you're running your own project branded meetups. How do you actually raise money for those meetups how do you effectively, you know, run different chapters. We have a training portal where you know you have 40 plus training courses and certifications available to grow the skill set. And finally, these two project control center is something we are launching late this quarter. This will be focusing on automation of all it resources, legal resources, your project challenges that you face when you know you know bootstrapping a project or day to day maintenance or you want to grow those right. Remember supporting member companies, we're also building an organization dashboard so that you can actually see your impact on all open source projects at least those projects that are within the, you know, our home and find their home in the Linux Foundation. So today we are primarily going to focus in on insights. The platform has been created by the internal engineering team. And we obviously had a lot of partnerships like we leveraged others open source projects has is the norm. And so in insights, you know, fundamentally, right, why did we build it. So unless we start measuring how we are doing on those projects, there isn't much room for improvement. And often in open source projects is you know, the visibility is limited to an individual developer or a contributor or to a maintainer. How can we get an entire ecosystem view right. So, if I look into, you know, you'll see some stats on the right, and those stats are growing. So these are the numbers we we are already instrumented 375 projects and you know every other day we are instrumenting more and more projects that find home at the LF. But so far we have been looking at like code velocity right there could be lines of code like we already have like 1.15 billion lines of code, but how much is changing on a weekly basis right like how much gets added how much gets deleted. So we are looking at like how much is changing developers like is that contribution count growing right like our communities growing. Where do they work at like who are our supporting companies right so we really found out we were close to like, you know, 12,000 plus companies and these developers this contributors spread are spread across these companies. It really gives you an idea of how they're distributed and how diverse our community is. We have implemented, you know, 11,900 repositories and that count is going up. We're looking at like, you know, annually 8.9 million commits, you know, more than a million pull requests more than a million builds, you know, issues that are logged in Jira GitHub issues like in a bugzilla container downloads right like from your registries how on the downstream adoption how many people are pulling down those images. Right we have a variety of collaboration tools whether it's on chat on email. What are the formal groups right where are they communicating what is the activity there. So great metrics there's much more to look here but fundamentally what our projects have been we found out our projects are not, you know, bound to a particular stack as is the norm in open source we are distributed by nature and in our choice of tooling. We could be running our projects on GitHub, get lab, get, get it. We could be using everything from a slack to a rocket chat to hip chat to you name it like to a discourse to communicate you could be maintaining documentation at 15 different places and that's preserving that choice is important. Because, you know, not one slight size fits all for all projects, but how do we really get the insights with this distributed nature right so unless we get those insights. There are some problems everybody's trying to solve as the project right like yeah our projects code velocity slow. We have a big community of contributors, but where are those bottlenecks right our development pipeline is clogged we really don't have an idea of where exactly is it clogged is it in you know the. The workload on the maintainers is it clogged somewhere else we are able you know unable to identify who our top contributors are right and not just contributors in terms of code, but also influencers in our communities right it could be particular individuals it could be particular companies, and you know many times you know we put out great code but our user adoption kind of is not matching. You know our code velocity, but we don't really know it's just a lack of awareness, it's the code quality, what really are these issues right so this is our effort to give you those kind of insights, that's why we built this product. Okay, so different personas right one tool and we have tried to build different views for different personas primarily for the maintainers and the project leads we are getting trying to give you a 360 degree view. Right, there are fundamental problems you want to solve you want to avoid maintainer burnout, you know those are the key people in your community who are merging your PR is reviewing your code. Contributions come in left and right but you know the last thing you want to do is you know burn out your maintainers and longer term how do you ensure your project health security and sustainability right like security for many projects mean sustainability. For the outreach people in those projects you're evangelists right how do you attract more members more funding and grow your community and awareness right. Again, unless you understand, unless you're able to measure how your campaigns are performing, you won't be able to you know improve there. For our all our supporting members corporate sponsors for them, you know, a lot of these contributors are working with a full time employment at your companies. So how do you, you know measure your impact. Right. How do you not just evaluate or like you know, encourage like your employees making contributions to certain projects but also how do you encourage that behavior. And again, also in terms of when you are investing into particular projects how do you find out you know which other member companies are sponsoring those projects are participating to what level. And fundamentally for all developers open source developers in our community, like the goal is like where to focus your efforts on right. You know showcase your leadership, you know you have a lot of active contributors maintainers there are leaderboards there are some people who put in heroic efforts. But like you know we need to grow equitably so and the other part is like you know once you make a contribution. How do you manage that affiliation right is that contribution on your own behalf is it on behalf of your company how do you measure that impact. So these are the primary personas who can start using the tool today. List features you know this list is going to be endless but just as a snapshot, you know we have a multi dimensional 360 degree view it's multi dimensional reporting that you get out of the tool. We have utilities for contributors to manage their affiliations and their identity. We have created these leaderboards or contributor boards so every project can slice dice the data maybe use those for elections as an example. There's shared innovation whatever instrumentation we build whatever dashboards we build for a single project, every project gets it right regardless of like how big or small they are. We have a trajectory from multiple data sources and then we're also as we are increasing the ecosystem visibility we are looking into different areas right, not just code velocity what is your marketing impact just as an example. Today we support, you know, 15, around 15 data sources and it's growing and then by the next quarter will probably be around you know, 18 or 19 data sources. So the ones, you know, these are like fairly evident like from source control systems like you know anything get based get it based GitHub from issue tracking if you're using bugzilla GitHub issues or jeera for tracking all your issues. You know if your collaboration is primarily happening on groups.io. That's where majority of our community mailing lists are our mailman for a lot of other projects. If you're looking at continuous integration CI like we today have instrumented Jenkins from a registry perspective you're you know distribution channel. We've got Docker hub for our media, particularly if you're doing press releases contents indication SEO we have instrumented session documentation, Confluence, you know chat rooms we started with Slack, found out communities like Twitter use rocket chat we added those and there are more coming so I think the next set of wave you will see will be an increased focus on social media. So Twitter, LinkedIn, Facebook, we are increasing our focus on different type of build systems, you know, GitHub actions is coming up a lot, Travis CI circle CI get lab. We're mailing list so they're so distributed now we're going into Google groups right so this will keep growing but just wanted to give you a snapshot of what is supported today and what's coming relatively soon. Okay. Just talking about affiliations right this is probably the most important part of like how do we, you know a test credits for your contribution. So there are multiple ways this attestation is done. All these project data sources that you see here that's where we are getting our data from. However, these data sources could be GitHub, it could be get it could be a mailing list it could be a Slack server it could be a conference document it could be your social media board. Everybody uses a number of different IDs there's no seeing you know unique way to stitch these together into like saying that okay this was the same person. So what we've done here is, we are already like instrumenting and getting this data into our leaderboards. However, we have three ways to, you know, update the affiliation, the number way and way for particularly for projects who are primarily you are driven like there's a good DM methodology it was not a new concept was started by the Linux kernel years back and you know was used by CNCF as an example as well for their affiliations. So you know if you're making a pull request like you know your contributor data and in sometimes you might be you know contributing that code as yourself in your own individual capacity. Sometimes you want to that code contribution to be attributed to your employer, which is essentially a corporate contribution. So you can essentially issue a PR and that good DM repository is what we essentially integrate with our leaderboards. The second way to do it is which we were doing from a long time was have community admins essentially every project has a set of community leaders. And they essentially know who the community who the top contributors in those projects are and they can manage the affiliations on behalf of the community. But to make it really scale we went with a self serve approach. So we have built a UI and that UI is available in your community profile where you can as an individual contributor that contributor could be in any area doesn't just have to be a code contribution we discover your contributions and then you can you know self attest there you know how do you want your contribution to show up in these community leaderboards right and many people change jobs right. So how can you keep that continuity and while you are earning badges those badges could be you know speaking at events that could badges could be with your training certification that could be with your skill set, or you being a mentor those badges are also displayed in those same profiles. Okay. So quickly jump into a demo. Let me share my screen here. So how do you get to insights. First of all, so there are multiple ways. I think the easiest way is to do insights dot LFX dot dev. That gets into the homepage. Here, you will see there are n number of projects like we have a structure of cards. So projects which are, you know, clustered together in project groups, you will see, you know, they are grouped together like Academy Software Foundation, it's initially a project group. However, there could be a standalone project called as Bitcoin core. There could be a group of projects for if you look at CNC F, you know, cloud native computing foundation that probably has 70 projects underneath it. So that's how we just the modality that we have. Now within a particular foundation if you're just looking at. Let's take the use case here of hyper ledger. If I jump to the entire hyper ledger project group, you, you know, we have high level statistics that we have built to track like the performance of that entire group of projects holistically. And then you also have like, you know, that data project by project by project. So right here, out of the gate we are seeing, you know, 15 odd projects that are under hyper ledger and then they have a lab environment as well. And many projects they create like a commons, right, like which are like shared utilities so you can instrument those and look particularly as those but these are kind of aggregated numbers. So let's look at these snapshots in time. So, you know, if you're looking at a particular project, let's say, you know, if I want to go and look at a particular project areas as an example, you get that specific filtered view for the project. However, if you really want to look at from a group summary we aggregate the data across that entire project group. Okay, so let's look at some interesting statistics so we talked about source code contributions right. You know, if you start looking at commits, right, that's that's where we start. And the way we have been working these is like we, you know, start tracking those commits, regardless of the source they're coming in from and these are all time filtered the default range is always 90 days you can go back and you know look into last year last two years last five years. You know, pick relative scales and then we slice dice the data based on again this is based on your affiliation data, like you know those commits, which organizations are they coming from how many lines of code actually changed. You know, who are the active contributors, like, like in terms of diversity, how are those commits spread out by time zones again UTC timing. If you want to filter for a particular organization, you can. So, you know, you can just simply apply a filter like that. And in this case, you will see just a view for IBM, if you're just filtering for IBM, right, as an example. You start looking into you know, information around the authors, like who are the top authors in that time period like in again based on commits lines of code added removed average files. You're also filtering that by organizational impact. You're looking at repo by repo which are your most active repositories which are your most active projects. Again, this gives you a good handle on the velocity and then also like you know we get down into you know commit hash and like the commit URL so you can get as deep as possible, or you can you know look at it from our top down approach as well. However, you know, commits are great but what about the efficiency right so yeah there are pull requests coming in and you can have similar views on PRs. And as these contributions are coming in and similarly you can slice dice the data in terms of you know PR submitters repositories over time how these are doing. Again, how many are open how many are closed. You know who are the top, you know submitters of this PRs and so on, but we are starting to now go into like how are these peers doing from an efficiency perspective. We leveraged a lot of the best practices that were set by chaos as there's a big initiative there or a project they're called metrics and a lot of specifications and best practices were provided there on key metrics to measure right so if you're thinking about like, okay, PRs are great but I want to start looking at like what's the average lead time right to merge that PR. You know what's your kind of moving average there is it increasing is it decreasing. Is it happening more iteratively. If you start want to start looking at you know what your timing on disease right like average time these day open. You know you can start looking at those distribution charts like how exactly is the performance happening right. It's healthy 95 percentile of open time is decreasing that's actually a healthy pattern you should not want it to go up and up and up. Interesting metrics to look at. Similarly, you know if you wanted to just get into data like builds right so I'm going to go and use quite a few different projects because you can navigate and cross compare across projects as well. Okay, great code came in PRs are happening approvals are happening in if you're in the get it land you want to also look at like reviews and approvers so I'm not going to go into all those metrics but they are there. If you're looking at builds you want to really understand like okay what's my job performance right how many jobs am I running on a monthly basis quarterly basis, how many jobs succeeded how many failed how many unstable how many got aborted. Are there like large spikes like this happening into the system. This does not point to an anomaly. It could be normal. There might be a massive commit base came in or some re engineering done on you know improvement done in terms of you know your CI infrastructure. But again this is interesting to data to look at and analyze right we start looking at like okay what are your primary, you know, jobs like and you know are they how are they trending upwards downwards the bill duration of those jobs. If these jobs are running for days maybe that's a good area for you to start optimizing these right. Similarly, you know there are many more metrics here if you're really looking at you know your registries and let me go on to another project here. And if I want to track like okay how is my distribution doing, and I want to start tracking it from you know Docker her perspective, right like what are my top images again this is within this time period. How is like you know the pools happening and you can probably like if you start trending this over like a you know six months and year is this increasing decreasing right like what are the top images that are getting cooled down so it also points at an adoption this is not a user pulling down it could be a CI job pulling down your images, but you not starts looking at like okay how are we actually performing outbound right in terms of the adoption. Now, again, many more metrics for the technical consumers for the consumers who are looking at the ecosystem. You know you might want to start looking at things like, you know, your slack conversation so if I go into let's switch projects again. On the CNCF site and I want to look at the entire project group and look into like okay. Let's look at slack right a lot of projects on CNCF you shared slack resources. You know, again you can put a lot of messages like who are the top people who are the top participants in those official channels we are not looking at peer to peer conversations we are primarily focusing a lot on like you know the official channels which the projects want us to instrument and start taking a look at you know what are the topics in those channels like what is the purpose of those channels. Where are people what are people really discussing right what are they trying to solve. There are many areas where like if I switch back to a checks foundry. I might be able to even look at the same data but in this case for slack. You know there's a section here many projects have you know provided us some keywords to look at right. So you definitely want to eliminate all the filler words, but you want to look at like what's trending what's not trending are there certain keywords you really want to track. You can actually start measuring you know what's important what are people talking about in those communities right. But as I said, not everybody uses slack we had a similar implementation for a project like hyper ledger where instead of slack. They use rocket chat right so we tried to build similar kind of you know data interpretations, regardless of the chat system you are using. You know what the participants what are your top reactions what are the keywords should be looking at and whatnot. So this is again if you're looking at collaboration right many projects are using for email conversations groups.io. And then again you can see like who your key participants are which are your busiest mailing lists, where are these people participating from where are those recent messages so we are streaming in all these messages as well. And these are your most active mailing list right this is an indication of how you know your, you know your participation across the community is trending it's going up going down. So what are those like if you have an underperforming mailing list why exactly right, are they not important topics that are getting discussed how do you increase that. Okay. I'm not going to every section like documentation I think what one good thing worth looking at is, you know, earn media. So social media, yes, it's still we are going to publish it in the next few weeks, but right now we have got on media. Let me look at CNCF one more time. And look at like the own media so what do you start looking at under on media. So things like mentions. Okay. So if you look across the board, where are your mentions happening. You know, and which are your social amplifications channel. You know what are your hotspots right this is kind of a United States view. But again, these are like where your content is getting mentioned. Right, it's not just like where your users are, but where is your content trending. You know, you can break it down by cities you can look at like you know how that is trending international like you can look across the world. So look into like, you know, across the world where your, you know, content readers are right like primarily yeah the US dominates most of it but here you can also see like China is becoming a very big hotspot for CNCF in this example. Okay, you're looking at things like share of voice. So, again, a lot of these are like keywords based on what the projects want to track their share of voice but if you had like one. This is lamb down Kubernetes will always be the 800 pound gorilla in the CNCF group of projects. But again, if you look at project by project right which which is you're getting the most share of voice here you are just comparing against other projects in your group, but you can also compare against proprietary tools other open source that are out there right so and we are able to stitch this data. We have led done a lot of partnership with the content aggregators to pull this in amount of information. How is your sentiment doing right how much is positive neutral negative. If you're putting in some key messages how are they performing overall right and this could be like keywords based key messages based right. So SEO traffic doing right how much of traffic is coming to your side based on organic, you know, press releases or how much is it coming from documentation, you know your web traffic versus total traffic. So different ways to slice and dice the data to start looking at your impact also looking at like how to improve that some good things to look at. I'm going to again switch back to another project here. Here's an example of on app. You want to start using some of this data for voting. Right. And again, this is more around contribution data. So how do you do your TSE elections as an example right so you could just be looking at code, and you can see here, you know people with their names and you know organizations that are working on their email is not visible. I see it because I'm a super admin in your case as you will be seeing it without the emails, but you could be looking at okay code is one criteria. What about tickets, right or people who create issues. What about documentation contributions right is that like, do you want to capture and see a holistic view, you know, across the board, what are the different parameters based on what you're going to do a voting like who consider top contributor. Is it just the person writing code, or doing commits, or is it a person who is making an impact across multiple areas right so we can add more data sources you can export this data use it for a lot of, you know, election voting process as well. Another interesting thing to look at is. You can compare projects side by side. So if I start looking at Okay, let me look at like past three months and let's compare some like projects so if I'm gonna. Again maybe Kubernetes is probably not a great choice because it's a big super big project, but let's compare it against something like gRPC. Let's compare it against Prometheus. We are kind of in the same family of cloud native projects. Again, you know, when you are looking at, you know, see three months, six months. Is it the number of commits looks like it's trending down but is it necessary a flag, you should not draw interpretations from just the number of commits going up or down. You know, different set of metrics to gauge the health right so we are just providing you the raw metrics, but the analytics of whether a trend going upward or downward is pointing to health. A lot of analysis needs to go in there right so just if something is trending downward doesn't necessarily mean it's bad it could be actually be good. So we have been working with these projects to get a set of like what are the key metrics that are valuable to look at, but you can even go and you know, go across projects of a similar group so I can say okay. Let's look at Kubernetes versus fabric project in Hyperledger. Let's see how that does right completely different project different ecosystem. How do we doing on the same set of metrics now these are like very, very detailed we are trying to build some high level views as well though so we can easily compares again different timeframes per se. So, a lot of things I would really encourage you to check out all these features in there, and you know, check your projects in cases where you find like hey we don't have data. It could be that we don't have this data source for information to instrument. In some cases, we might not support the data source that you know your project is using. So if you want us to support that you want us to get data from that all you need to do is like log a ticket on our Gira system. Okay, so I'm going to go back to my deck here. Okay. And also want to talk about roadmap so what's coming next. So I'm not going to be able to demo all of this, but the next big feature release that we are going to do in a few weeks is social media analytics. Very deep dive social media analytics around you know your Twitter followers your LinkedIn posts how they are performing how you know who the who your followers are your Facebook fans type of content that's working not working images versus video versus text copy. Where are those people distributed are you gaining supporters are you losing supporters and whatnot right so this is coming very shortly. Later half of the, you know, q2 q3 onwards. We are obviously adding more data sources that's going to happen on a regular cadence. You know, all the CI systems is our next big effort, and also getting into Google groups Microsoft teams again we are taking these requests from the projects where they feel the critical mass it what are the key data sources they want to look at. We are also adding event participation project by project training and certification participation project by project events could be both virtual and physical. So that's why like when I talk about metrics it's not just code that's code alone doesn't make your project. It is the most important component, but there are many other areas in the ecosystem. There's another view we are trying to stitch together which is essentially looking at the entire pipeline. So think about like the core to ship pipeline or even you know all the way from where you actually log an issue to the way you know some contributor picks it picks up the issue works on it issues a pull request reviewer reviews the code merges it. I mean, and that particularly essentially as a maintainer it gets packaged into some build job, the build job runs it's put, you know, into some package management system, the distribution happens so can you look at it end to end right. And I think you will start to see this kind of an in I would say it's completely inverted funnel where you know a lot of inbound will come in in terms of issues feature requests but over as you go through this funnel. You know, the people who are towards the later half of the funnel are essentially your gatekeepers they are the most important people in your community, but we'll start to stitch this impact view end to end so you can start measuring different types of metrics on a plane. Okay. So opening up for questions. And before we go into more questions I just also wanted to give you some highlights into some resources. If you really want to update your affiliations you can go to this my profile screen. I'll show you how to do that there are like you know these are the links to the app, how to get connected stay connected with the newsletter, you want to get support add data sources your project is missing something. That's the place to go, you have general questions come to us, but I just wanted to show you one area where affiliations are done which is the self serve UI. So just here, this is my profile anybody who has a Linux foundation ID actually already has this. So if you log in, I am a developer I can see my code contributions across all these projects. And if I wanted to say like hey I'm contributing on behalf of the Linux foundation, or I'm contributing as self and maybe my data isn't correct right this was like source from LinkedIn or whatever data we had on, you know, two third party systems. I have an ability to say hey you know what, I don't really work here anymore. This should be based on. Okay, I am just as an example, I change jobs at this point I was working at Google, and I was a maintainer or a contributor, and for this project during this time frame. My contributions should be affiliated to Google, or it could be just affiliated to myself. So this is a self serve utility that every developer every contributor, again, contributions could be across the board they get to see and you can use this to update your profiles and once you update these in the leaderboards that you see in your insights dashboards, they get automatically updated so that's why you know for us communities to scale we are providing the self service utility. So let me stop there and open it up for questions. Awesome. Great. Thank you so so much she brought everyone if there's any questions please add them to chat or go in the Q amp a. I'm going to bring back that final slide so that we all can see that as reference with all of our links. Just give me one second here but please go ahead and start dropping in some questions. One that I know comes up a lot she brought that love to address is, you know how do we how does a project get access is there a cost for Linux projects, and how can a project get these dashboards, you know up and running for their for their project. Yeah, so for this tool is provided for all Linux Foundation projects there is no getting per se. The easiest way to get your project on boarded is to just create a support ticket in our Gira system the link of that is in our technical product manager such in heroes on the call will pick it up and help you with the onboarding the way the projects get on boarded is we give you a set of Google sheets where you need to provide us the data sources that you want. This project uses like what those endpoints are that we should be instrumenting. Many times we ask you for like okay what are the keywords that you want to look at right so provided that data we can on we have a lot of automation all these dashboards get generated in automatically, you will be able to onboard a project in a couple of days right it doesn't take more than that. From an cost perspective like there is no hard cost here like this is being managed through your membership support or the support of the membership that is done through the projects but it's one service that's provided kind of to all projects right like. Yeah, an individual doesn't have to pay for that. What we do have is there are some features like the ecosystem metrics because the members are primarily funding them. Those are gated for you know employees or all our contributors who are working with these supporting companies or if these contributors or people are part of formal governance committees of these projects like the TOC the marketing committees the legal committees the board. But for the technical metrics like anybody in the world can come and see that, but this whole thing is funded essentially out of the membership support that we get from these projects. So it's like, but again, that's primarily like infrastructure costs that are shared by these projects, but other than that there is no expense for say. Great. Thank you. One other question that I saw come up through the Q&A was around, you know, the understanding which data sources are connected for their project how does a project understand what the data source, which data sources are already connected for their project and be able to get, you know, other things added as needed. Yeah, great question. So if you don't mind sharing I can actually show you it's you can see it in the tool itself. Yeah, so if I share my screen, and there are a couple of ways to look at it. So the number one thing is just look at your project. And if you're looking at your project group. The quickest way to look at it is, you know, data source is not configured you can see here for pages like our documentation. There's no data source configured or there's no data here. But also if you look at your summary, and you're going through these main dashboards, you can see here with support, get it get up now your code could be not be on get it then you don't care. However, there could be a project let's assume you know you are in CI CD. And you see here Jenkins, we support Jenkins, but it's not configured for this project. Okay. Why, because my team doesn't have the endpoint for Jenkins to instrument. So if you just create a Jira ticket here and give us the endpoint, we can put in the enable this instrumentation or registry information right if you if your registry right now isn't Docker hub and you know you have a Docker hub endpoint or the actual Docker hub account we should be looking at. We don't have that information if you provide it to us like we can enable this like super quick. Does that. And again, this is the same thing like every section you go you can see like, you know, if it is supported. Yes, if it is not supported let's say issue management G it hub issues bug zeal. So this project uses get up these are the only ones we support tomorrow let's say we add a third or fourth system which is get lab issues. Right. So it's not supported yet but like if we don't if you don't have then let's say you know, you are using bug zeal and we are not seeing any for bugzilla that means we don't have your bugzilla information what is the URL what is the host, what is the port, and what is the key to look at right so that information if the project sleep can provide us in a Jira ticket, we can set it up right away. Awesome, great. So we might have time for just one more question here, if there are any in particular that have come up as we've talked through the demo that maybe we haven't addressed in Q&A. Oh, here's a great one. How let me go ahead and bring this up from our Q&A that we addressed earlier on how does a project or how does anyone identify the state of a project maturity is that something that can be understood in the inside dashboards or is that something that's coming on the roadmap. Yeah, from what we're it's a roadmap item for us but what we are trying to do is like look at certain best practices and like start creating some maturity indexes. This is a little bit. I would say subjective because like how do you define maturity now there are projects which have been there for 15, 20 years, and there are adopting some of these best practices, like the best practice could be like you know your PR efficiency could be a best practice. You know your contributions like, let's say you know more iterative contributions versus you know, one big bank contribution of a million lines of code. And there are projects, you know you can't enforce it as a hard rule, because there might be some projects the communities work that way, right but in general iterative contributions are a best practice, right. So what we're planning to do is we'll come with a set of specifications and will be creating indexes maturity indexes on different areas, right. Here we can actually post that maturity index but you have to take it with a pinch of salt, because you know it's just a recommendation. It's not an absolute hard rule because project communities can differ in their best practices from here or there so it's really based on best practices. So yeah, like, you know, from a maturity perspective. We don't have a set of indexes defined today. That's a short term project for us. Thank you. So, I think this is, we're at time at this point. If there are any other questions that come up. Please, you know, feel free to reach out and we just bring that slide back up to for everyone to see here. You know, feel free please is next steps, go in and update your affiliations, explore the insights dashboards for your specific projects and, and others. Please do follow us, stay connected on our newsletter, because we will be sending out, you know, all of the new data sources that she was talking about and other features will be sending out updates for that through through the newsletter. And of course, if you have any questions or need support on getting started, you know, reach out to us through our support channels as well as asking questions. And we will be sending in follow up, we will be sending out an email with our recorded webinar, as well as if there are any questions that you know come up in at the end here that we might not have addressed. If there's any feedback from from all of you who have attended our first webinar, we would love to hear that too. So thank you all again for joining us and have a wonderful rest of your day.