 Welcome to the latest webinar in our LFX series. Today, we'll learn how easy CLA can help you streamline the process of enforcing contribution policies and why this is crucial to maintaining your project's health. We're gonna walk through the various user workflows supported by the tool from sitting up a contributor license agreement for your project to signing a CLA as an individual or on behalf of your company to managing and approving corporate contribution lists, corporate contributor lists, excuse me. We'll also introduce you to some of the features from our latest release, which will make the process even easier. So for those of you who have used a prior version of Easy CLA, the, we're gonna walk through kind of what those new features are and what that means for you using version two. Now, before we get started, just a few housekeeping items. First, this webinar is being recorded and we're gonna be making this available on our YouTube channel. So feel free to revisit this material or share with your team later on. Secondly, we really wanna make sure that this is as helpful and relevant of a session as possible. So feel free to ask your questions either in the chat or in the Q and A feature here on Zoom. And we'll also be taking plenty of pauses to take questions live throughout the webinar. At the end, we'll also open up to live questions as well. So we really wanna make sure that this is as engaging and helpful as possible. So let's go ahead and begin. First, I wanna introduce you to our main speakers. Pranab Bajpai is a senior product manager for LFX and he owns product development for Easy CLA. Steve Winslow is our VP of compliance and legal here at the Linux Foundation. And he's played an integral part in the creation and continued improvement of this tool. They're going to be joined by David Deal, senior engineering manager who works on and owns a lot of the development for Easy CLA as well as myself and will help address and field questions as we go along. So now I'm gonna go ahead and hand things over to Steve who's gonna give us some context around contributor license agreements to kick things off. Thank you, Stephanie and hi everybody. Welcome to the webinar and thank you for joining today. So as Stephanie said, I'm just gonna give some some of the framing for what CLAs are and just at a high level what the process looks like with Easy CLAs to help orient you when we get into more of the demo. So for CLAs generally, the first point that I would make is just to be aware that not all open source projects use CLAs. So CLAs being contributor license agreements. Some projects use them as their contribution mechanism. Many other projects don't use them at all. So for instance, the Linux kernel and many of the other projects that we support instead of using CLAs, they use the developer certificate of origin or DCO sign off process. So anything like that we're kind of setting to the side for this call. This call is really focused not on should you use a CLA or not but specifically for those projects that have decided to use a CLA, what then is the process for getting them signed in an appropriate way to help them accomplish the purposes that they're put in place for. So, and kind of alluding to that for projects that do decide to use CLAs, they may be pretty easy to do in a manual process if you have a small project, but for projects that start to scale, the process of getting CLAs signed and tracking who can contribute under those CLAs is something that can be extremely time consuming for project maintainers to manage all of that manually. It can also be challenging for new incoming contributors to the project to be able to go through the process of getting them signed. So the goal of easy CLA is really to help address some of those pain points. So to help ensure that the right processes are in place for getting CLAs signed by the right people and to help streamline the workflow of managing who is authorized to contribute code after a CLA is been signed. So Stephanie, if you can go to the next slide. So all of this is very easy for an individual CLA, for somebody who's an individual just contributing code on their own behalf, not on behalf of their employer. For that, for an individual CLA, it's very simple, you just have the individual sign it. And so that problem is pretty easy to solve and I think what we found with, before we started building easy CLA, what we found looking at some of the other tools out there is that they take that model and they apply that not just to individual CLAs, but also to corporate CLAs that they would just ask the person who's contributing code to just sign the same CLA. And I think the problem that we saw as we started looking into that was that there's a lot of nuances in the ways that corporate CLAs work that aren't necessarily handled by that sort of approach. So for a corporate CLA, so a CLA for a company that is contributing code, there's a number of things you wanna have. You wanna make sure that it's the person who's signing it is somebody who's actually an appropriate signatory for that company. So a lot of companies, particularly as they get larger will have only certain people who are authorized to sign agreements that can make commitments on behalf of the company. So we wanna have a workflow that enables the right person to be able to sign it who may not be the person who's sitting there at the keyboard contributing the code. We also wanna enable out-of-band reviews. So for instance, many companies will wanna have their legal department take a look at the CLA before it's signed, which might not be easy to do if it's just presented to the developer or the contributor to sign directly. We wanna also enable different models of managing authorized contributor lists. So after a CLA has been signed, typically the way the CLAs are set up is that there will be some subset of contributors from that company who are authorized to contribute code. And different companies have different ways of wanting to manage this. Some companies will say, we've signed the CLA, we're fine with all of our employees contributing. Other companies because of their own, either because of the context in which they operate or for other reasons, they may decide we only wanna allow these two particular employees to contribute code. And the tool that manages the CLA for a project should be able to support all of those different models. Another thing is that contributors from a company, they might know that their company is signed a CLA, but they might not know how do I get on that authorized contributor list? Who do I talk to who's managing this from our company? And then finally, the companies themselves and other, and I'm saying companies here, but this also includes other organizations beyond just commercial companies. They want visibility into what's been signed, who's currently authorized from their organization. They wanna have read-only access to this sort of information as well across their company and across their projects. So you can go on to the next slide. So a few definitions just quickly, because you'll see these terms coming up as we go through the demo and through some of the other details. So an IC, oh, great, thank you. An ICLA is an individual CLA. So again, that's a CLA that somebody is signing just on their own behalf, code they've written maybe in their spare time, but not for their employer. So code that they own themselves. They'll sign an ICLA to contribute it. A CCLA is a corporate CLA. That's for when a company is contributing code that the company owns. And then within a company, we have a few different roles that are filled by people. The contributor is the person who's actually submitting the poll request or who's actually submitting a patch or code to the project. We call them the contributor within the ECLA. The CLA manager is the person from a company who manages a list of authorized contributors for a particular project. So after a CLA has been signed, it'll designate who the CLA manager is and from that company to that project. And that CLA manager is the person who uses ECLA to manage the list of authorized contributors. And then finally, the CLA signatory, like it sounds, is the person who actually signs the CLA. So this might be this is the person who's authorized to sign on behalf of that company. So those three roles, the contributor, the CLA manager, the CLA signatory, those might all be the same person or those might be three different people entirely depending on the company. And that'll vary company to company, depending on its size, depending how it's set up and other things. So ECLA tries to work for all those different use cases. So you can go on Stephanie. So again, so then high level for ECLA, what the process looks like is this. Again, for an individual contributor, it's very straightforward, you just sign the ICLA. So it's just an easy click through, you fill in the fields for the ICLA and you sign it on behalf of yourself. For a corporate contributor, the process looks like this. The contributing company's CLA signatory is the one who actually signs the CCLA. In that signed CCLA, it'll designate an initial CLA manager. And after that CCLA is signed, the CLA manager manages the list, uses easy CLA, uses the tool to manage the list of authorized contributors from that company. And they can also add additional CLA managers so that multiple people from their company can manage that approval list. So let me pause there. That's really the high level framework for what easy CLA is trying to solve and kind of at a high level how it works. Before we go on to talking more about LFX, are there any questions that anybody wants to raise? So I'm not seeing any, I haven't seen anything in the chat or the Q&A. So I think if you have questions, feel free to drop them in. We'll all respond in line if we feel like we can or we can save them for discussion at the end of the further on in the webinar. So Stephanie, I'll go ahead and turn it back to you. Awesome. Thanks, Steve. So I'm going to go ahead and have a quick poll for everyone that I'm going to go ahead and share out. Basically, we just want to understand, based on what Steve's covered in the various roles involved in the easy CLA and the CLA process in general, I just had a quick question to understand our audience better in terms of, which role best describes you in that process. I'm going to leave that up for a little bit as I jump into the next section here. Now that we have a bit of context around CLAs, I want to share a little bit more about, what easy CLA is and the larger LFX toolkit that it's part of. So LFX was really built to buy the Linux foundations, operationalize our proven methodology that helps projects transform into category leaders. Ultimately, we recognize that while the world now runs on open source, projects need more than version or source control systems to scale. I'm sure all of you understand that this takes more than just these systems. They must have fingers on the pulse of their entire ecosystems, must have tools catered to help drive this development. And easy CLA is one of these. So you can see here that easy CLA is part of this larger toolkit, which is really built to add value at every aspect of open source development. So whether you're a project manager or a company that's invested in open source or an individual contributor, we really have worked to build out a number of tools that can support your needs here. Diving into easy CLA specifically, Steve kind of really walked us through what this tool does. One thing I do want to point out here is that easy CLA is really that only tool that supports both individual and corporate CLA workflows. So really working to streamline this process for everyone involved in contributor license agreements. Breaking that down, what that means for project managers is it really helps put your CLAs on autopilot, really helping streamline the process, helping you set up and configure CLAs for your various repositories to make sure that everything is enforced for contributors. Really it's, you can get kind of get going, start contributing code faster, making this easy to understand when you need to sign a CLA, making that process very straightforward, as well as kind of having you covered for future contributions to those projects. As a corporate CLA manager, you're able not only to easily manage your company's authorized contributors, but you have flexible configuration. So you're able to really align this with your company's policies and you are able to understand and see which CLAs your company has signed and who within your company is authorized. And likewise with signatories, whether the CLA manager and the signatory is one in the same or you have a separate individual signing the CLAs, just making this a straightforward workflow for you as well. And based on the poll, I'm seeing a pretty even mix of roles that we have here, which is great. Again, we're gonna be walking through the workflows to kind of cover all of this. Real quick about the features, I mentioned that Easy CLA is really the only tool that supports both the individual as well as corporate CLA workflows. We've really focused on making sure that these processes are streamlined across the board, providing improved CLA visibility. So in the organization side, you're able to see who is covered under your CLAs and from the project side, you're able to kind of control and see, where your CLAs are enforced. I mentioned, especially for contributors of one-time CLA approval. So once you have gotten approval for a CLA or for a specific project, you're essentially covered for future contributions. So it really is able to really streamline the getting you kind of up in and encoding faster. Multiple ways to authorize, so whether you are an individual signing on, for your own CLA or on behalf of a company. And I see that there's some great responses here on my question around GitHub or Garrett. Easy CLA works with both. We also have flexible repository management. And I'm gonna add here in, I've mentioned throughout that we have a version to kind of release that we are in the midst of, which adds additional capabilities, such as role-based workflow support, making it more clear and more helpful for each of the individual, for the roles, whether you're an individual contributor, CLA manager or project manager. Ability to auto discover for new repositories. So essentially that means when new repositories are added to your project, you're able to have those kind of auto discovered by the system and be able to determine whether the CLA should or should not be enforced for those. And branch protection, which allows project manager by one click to enable Easy CLA for all of your repository branches. So before I go on, I'm actually gonna take a quick pause here and see if there's any questions about what easy CLA does or any of the features that I've covered. I'm gonna go on next to talking about the release version two, which is gonna be especially relevant to our audience who's used a prior version of easy CLA. Okay. Stephanie, I see a question in the Q&A and I'll go ahead and answer it from Oleg asking about whether it's possible to use easy CLA for other kinds of contributor agreements. And yes, Oleg, that is something that we've done for some projects where we've had something that is not strictly speaking a CLA, but it's still something that is an agreement that we wanna have as basically a gating item before contributors get access to contribute code to a repo. The specifics of it can get kind of into some details. So I'll reach out to you separately on that. I think I owe you an email on another related topic. So there's some potential to be able to do that and we can look through the specifics. Awesome. Thank you, Steve. I'm gonna go ahead now and jump into what's new. So I mentioned some specific features. Ultimately, our version two of easy CLA is all about improved user experience and usability. So we've really streamlined the workflows, provided some contextual help and tool tips to make it clearer based on where you are in the flow and what role you have, kind of what you're needing to do and help guide you further in that process. We've also introduced audit logs. So now there's clear records of key events or changes to the CLA groups or your authorization lists. So whether you're a project manager or a CLA manager, you're able to access audit logs. For the corporate CLA workflow, we've improved our searching and filtering. So you're able to more easily search and filter through your authorized users. You can also export a CSV of that authorized user list and even download signed CLA PDFs. Project managers, you, as I mentioned, the auto-enable repositories. So now you can enable new repositories, especially under a GitHub organization and auto setup of that branch protection for default repository branches that I mentioned. So what this means, especially if you are using a current version of EasyCLA, ultimately, whether you're a contributor or a CLA manager, your workflow is gonna be the same as it was in a previous version in this new release. For new contributors, so those who are gated by EasyCLA who have not yet contributed to a project that has a CLA enforced, you're gonna follow the same process as before. So if you're contributing on your own, you're gonna be prompted to sign an individual CLA. If you're contributing on behalf of your company, you're going to be prompted to get a corporate CLA signed or contact your CLA manager to be added to that list. CLA managers, you'll see improved functionality, making this, managing the CLA is easier. So as I mentioned before, streamlined workflows for adding authorized contributors, being able to search, filter or download authorized contributor lists, and of course being able to download those signed CLAs as PDFs. Before we jump into a demo, I'm just gonna pause and see if there were any other questions that came up, especially around what this new version looks like and what that means to any of our existing EasyCLA users. Okay, not seeing anything come through. We're gonna jump now into a demo. I'm just gonna pass things over to Pernop who's going to lead this. And again, feel free to ask any questions on chat or in our Q&A feature. We will be pausing at the end of the demo and I think Pernop will pause throughout to answer any questions as well. Okay, gonna go ahead and stop my share now. Pernop, go ahead and take us away. Okay, thank you, Stephanie. So I have a prerecorded demo, but before the demo starts, I just wanna give a note about CLA group. CLA group is a group of repos either in Get It or GitHub that are governed by a particular CLA agreement. Okay, and let's start the demo. Do a demo of how Contributor Console works in V2 version of EasyCLA. But before I give that demo, I wanna give you some context. So we are going to use this CLA group. This screen is the PCC, Project Control Center, the Project Admin Console for the, or the Project Console for EasyCLA. And here we have a CLA group called February 23, 2021 demo. That CLA group is enforcing CLA on a project group and it's child, test project group and test project, it's child. And it is enforcing corporate CLA, individual CLA and corporate users have to sign individual CLA. Now this is, I just selected all three options for demo purpose. Mostly CLA groups have either corporate or individual or they have corporate and individual. That's it. So right now these are the templates, ICLA and CCLA that have been assigned to this CLA group. And yeah, so one person has already signed the CLA. There is a CLA manager associated with this group. You can see, download the signed PDFs. You can export the signed information as a CSV. You can also search for people's names and all that. Sign CCLA, sign ICLA is all of those. Okay, you can see the approved contributors. So let's see if there are any. So approved contributor is the same person who is the CLA manager, approval criteria. Yeah, so we have added two people as approval criteria for this company. And so forth. So now I am going to take a new user, a test contributor. So this user is called test contributor December 2020. And this user is already stuck on CLA. The PR is stuck and this user is now going to try to commit that PR. And we will take the scenario where the user is coming from a company that is not there in the database, in the CRM database. And this user will become a CLA manager, add themselves in the approval list and then commit the PR, okay? So let's get started. So we click on the LFX Easy CLA. Takes us to the contributor console. As you will see, it gives you the explanation of what a corporate contributor is, what an individual contributor is and so forth. The user chooses to proceed as corporate contributor. And okay. So now here, this user's organization is not there. Let's say zero, two, 23, 20, 21. This organization does not show up. So user clicks here, organization not listed. They create a website. Then here, they give the name of the org. Okay, they click Next. Now the system is asking if you want to become a CLA manager. So if suppose the user said no, then you can identify somebody else in your company to be a CLA manager. You can give their name and email address, right? But otherwise you can just go back and you can say yes, here we are gonna choose yes. So it's gonna assign me as a CLA manager in the background. And now it is saying that you will have to log in to Linux Foundation LF login, the SSO account. So you should have, you might have to create one, okay? So this user does not have a SSO account. So let's say proceed. Okay, so since the user does not have a SSO account, the user chooses to continue with its Gmail account and they say, okay, test.assemble2020.com. So we logged in using our Gmail account and we will give us a new username for the LF account. Okay, so create account. So now the system is taking us to the corporate console. It's configuring initial CLA manager settings. Click on proceed. You will be redirected to the organization dashboard, which is the corporate console, okay? So you can always go back, but I'm choosing to proceed. The GitHub session has been preserved in current tab and new tab is opened with corporate console. Okay, so you see that the new company that I created got assigned to my user, right? Test.contributor.desember2020. Okay, so now for this company, for this project, there is no CLA signed. I will start the CLA signing process. I'll say proceed with signing. Are you authorized to sign CLA on your company's behalf? If you choose no, you can again identify authorized signatory, okay? Give a name and email address and email will go to that person and they can sign it. But let's say yes. So now you review and sign CLA, corporate CLA. Put in some values. Now here a neat feature is that if you have a cop, some corporations have got separate entities, legal entities that are responsible for their intellectual property. So you can always edit this name and you can put the name of that intellectual property unit, which is signing the CLA. If you want to, that is. So like I could put IP unit or whatever, right? But I'm not doing that. So I'll just type in some values. I'll be done with this finish. Okay, so once the CLA signing is done, the CLA manager page is what will be seen. So it'll take some time for this page to refresh. Let us give it a few minutes or a minute or so. The page should refresh on its own because there is a delay between DocuSign and the database. By the way, this problem has been fixed now. I guess we'll have to refresh the page. Okay, so now this is the CLA manager page. We see that the CLA has been signed, project, project, projects that are part of that project group, the name of the CLA group, status sign, sign-on, signatory, and you can download the signed PDF, okay? Now, this test contributor user has been assigned as a CLA manager for this organization, zero, two, 23, 20, 21. And this person can now add anybody else as a CLA manager and give them the same rights so that they can also view this page, okay? And make edit updates to this page. Now, the other thing that this person, test contributor needs to do is to add themselves so that they can commit their PR, right? So they need to add themselves to the approved list of contributors, okay? And let's do that. So add, so let's add them by this. So let's say test.contributor.e20.com. Let's say save, so, okay. Okay, so what that message was was that the test contributor needs to do another step with CLA where they need to acknowledge their association with this company. And then once they have done that, then easy CLA check will be over for them forever, okay? So we also have the CLA manager can see events, audit log, who has done what, and they can see statistics for their organization, what is going on, okay? All right, so now we go back to GitHub. We are still stuck, right? But we have been added as an approved contributor. So let's see what happens. So we proceed as corporate contributor. We select our organization. So it was zero to 23, 2021, right? This one, proceed. Okay, so we had set up the CLA group where it requires corporate CLA users to also sign individual CLA. So we need to sign the individual CLA. We do sign CLA, we say continue, okay, finish. All right, so at this point, the system has done the requirements that the CLA group was set with. ICLA is signed, CCLA signed. The users association with the corporation has been completed. So the page should refresh and we should see the CLA check is no longer blocking us, let's see, yeah. So you see that it has turned green. Now we can commit our PR, okay? So this is what the contributor console looks like. Now, for most people who are on version V1 and moving to version V2, all of this will be migrated from V1 to V2. So if you are already a contributor on V1, then you would be in the approved list in V2 also and you won't have to go through the CLA block but a new user from your company who comes in can be added. So let's say, let's do another test. Let's go here and let me show you what happens. New contributor, test PM December 2020. And this contributor is not in the approved list. So let's see what happens. So if I go to report two, I see, okay, let's go to read me and make a change. Create a pull request, create a pull request, okay? Easy CLA block. Now at this point, this contributor clicks on easy CLA. Now this contributor is from your company. So it was a corporate contributor. So let's say authorize a left engineering, proceed as corporate contributor. The organization was 0-2-23. Let's see, yeah, the search found it, proceed. Okay, so now the system tells us that there is a CLA manager for your organization. So you can select the name of the CLA manager that you want to approach and then you can click on request authorization. We'll be notified to authorize off your request to be authorized for contributions. You'll be notified via email when status has been approved or rejected. Okay, so you exit CLA. Now I have the email open. So here I got an email approval request for contributor test PM, okay? So it is saying approval can be done here, okay? So let's click. Now I need to log in as my user. I'm logged in as close this. And then this, let's start contributor.design.2020 at email.com, okay? Okay, so then here I come to the corporate console landing page. I see my project, test project group ID. It will take me to the CLA manager page. All right, so here I can add this other user as a contributor. So I can say test.pm.desember2020 at gmail.com, save, okay? So now I have added this user. Let's see what happens. So now the user is test.pm, yeah. All right, so we go here. Okay, proceed as corporate contributor. Organization name, we are doing 23 proceed. Now it gives us the same message that you have to sign ICLA also. Proceed, sign ICLA, start. Sign, sign, finish. Okay, so now the CLH should be lifted and we should be able to commit our code. Let's see. There you go. And that's how it will work. Okay, so I see, I'll pass it over to Stephanie if you have any questions. You can ask, go ahead. Great, thank you for not gonna go back and get back here and share my screen, just give you one second. And I see there's been a number of questions that have come through, which is great. We will also spend some time at the end to address any additional questions or kind of talk through things live as well. One second, apologies everybody. Okay, we're just gonna go ahead and share this way. Apologies everybody. We're just gonna go ahead and share like this presentation so it's not working on my computer for some reason. So before we jump into Q&A, I just wanted to share a quick sneak peek on what's plans in 2021 for the ECCLA tool. As we mentioned, projects are being migrated. So existing users of our ECCLA version one or prior are being migrated over to our version two, which is what Pranavis just walked us through. We're also going to be increasing our GitLab. We're also gonna be expanding to GitLab support and enhancing our handling of bots. And of course, as we go, we're really focused on fixing any bugs that we encounter from our rollout. In H2, we are going to be launching, we're just gonna start as a limited access beta of our organizational dashboard. So the CLA management capabilities that Pranav blocked us through for ECCLA, those are gonna be part of the larger organization dashboard hub that we will be rolling out in the second half of this year. I now want to open it up for any final questions that anyone will have. We are kind of at time here, but we will go ahead and spend a few minutes, just to make sure that we're able to answer any final questions that the participants have here. And I'm gonna go ahead, you know, feel free. I'm gonna go ahead and allow everyone to talk here. So feel free if you have any question, to ask it live, you know, we wanna make sure we are able to address anything. First of all, thanks a lot for the presentation and for a lot of materials. I had a question about GitHub integration. So how do you currently implement it? Is it a GitHub app or is it GitHub actions both the team would need to configure? Yeah, I can take that. Thanks for the question. For GitHub, we have a GitHub app, which is also called a bot sometimes, which typically managers install. So if you have organization owners or project managers would install the bot into the application, into GitHub, that adds the hooks such that we are able to receive notifications when PRs are created and open. We then go through checks because we got the notification and we can then update the status on GitHub. So that's how the integration is done. Thank you. So follow on to that. Does that mean that with that GitHub support that if a project is out there, even if it's not on an LF project that we would be able to use this? Generally you need, there's two parts of that. I don't know, Steve, you wanted to pipe up for that as well, but you have to log into the Project Control Center, which typically is a project manager's role. They would then set up the CLI group, assign which legal documents, and part of that workflow is there's a step at the end where you click and then you navigate over to GitHub, you install the bot, and then you come back. So generally that has to be done through the Project Control Center. Sure. And as far as having it for what projects it's available, currently because this is all integrated into the LFX platform that Stephanie was sharing earlier, currently we're doing it just for LF-hosted projects, but we're, I think as part of the roadmap going forward, we'll be looking at what's feasible to offer for additional projects. Okay, and I'll assume that that's a second half plus. I kind of finger in the air, I expect that's likely, yep. Okay, so it's not included in the current GitHub plan, so that's what I was wanting to confirm. I think that's right. Yep. Okay, thanks. Now just to be clear, within a project that is, within an LF project that is set up on LFX, and I think I may have mentioned this in the chat for some of the conversations as well. repo, once a project is set up on EZCLA, it's open to be able to configure it for multiple GitHub organizations and multiple repos within that organization. So it is, so where there's an LF project configured, it can be used with multiple different, different orgs repos. Another question. Do you have templates for standard CCLAs and ICLAs configured? So for example, in our case, we use Apache foundation like contributor license agreement. Would we need to replote it somehow or would it be possible to configure that right in the system? Yep, so great, great question. Like, so what we have set up as a default is CCLA and ICLA that are based off of the Apache software foundation, CCLAs, we have modified them, is substantively, they're exactly the same as Apaches in terms of the scope of the license grant, other things. There's a couple of kind of operational, say like administrative details in the way that we've changed it to make it fit, to make the authorizations in the CCLAs fit better with the EZCLA workflow. So I think for, I believe I owe you an email on some of the details around that. So I'll share with you what those templates look like. But yeah, we use those as the default templates, but it is possible to, we can configure it on the backend for other CCLAs beyond those, yep. Okay, thank you. Yeah, for one contributor and one repository, is it possible to require multiple ICLAs signed? Do you mean multiple different kinds of ICLAs? So like you have to say this? Yeah, we have some complicated use cases when maintainers define their own ICLAs, though formally we still have for organization-wide ICLAs applied. So yeah, it's not a short stopper for us, but I wonder what it's supported in the system. Yeah, I think given where it's currently at, I'm not sure we could support that kind of operating as two fully separate CCLAs both being required at the same time. There may be some ways we could look at handling it via kind of incorporating both of the CCLAs into the same document and having the document just signed all at once, but it might be some nuances that we'd wanna look at, yeah. Okay, thank you. Sure. Awesome. Any final questions here? Maybe have room for one or two more questions to close us out. Okay, great. Let me just switch us over here to kind of what's next. In terms of getting started, as I mentioned, the release of RV2 will be rolling out in phases over the next few weeks. So reach out to your program manager or you can contact us at lfx.dev forward slash questions. If you have any questions on timing or status of EZCLA usage, or if you have any other questions about the tool. Here's some other great resources that you can access if you wanna learn more about EZCLA. You can read the blog post on RV2 release notes. Feel free as well to stay connected with us by following us on our newsletter. And then of course, as you use the tool, whether you're a project manager, or a EZCLA manager, or just contributing, we have a support channel as well. So lfx.dev forward slash EZCLA-support and we'll be able to help you out. Awesome. Thank you everyone for joining us. We really appreciate the time. Again, this will be recorded and we're posting this to YouTube and I'll be sharing out these and other useful links in follow-up as well. Thank you all.