 All right, welcome everybody to October 26th. This is the Hyperledger Technical Oversight Committee call. If you've been on the call before, you already know this, but for those of you who haven't, two things that we have to abide by. The first is the antitrust policy. So there are many people on this call from different organizations. So we must not participate in any activities that are prohibited under any of the antitrust and competition laws across the world. And the second thing that we have to abide by is our code of conduct, which is linked in the agenda. Basically be respectful of others' ideas and opinions and thoughtful in your communication. For announcements today, we have the standard Dev Weekly Developer Newsletter that goes out each Friday. So if you do have something that you would like to include in that newsletter, please do leave a comment on the link that is in the agenda and include whatever information you have. The second item that we have on the announcement is the TOC nomination period has started. It does end on October 31st at the end of day Pacific time. We currently have five folks who have nominated themselves. If you are interested in nominating yourself, please do add an issue there to the GitHub repository. There's information in the link that's in the agenda that tells you how to go about doing that. The next announcement that we have is that we have a workshop on atomic cross ledger transactions between the Hyperledger Basu and Quarta ledgers using Hyperledger Cacti version two that happens on November 16th. And if you are interested in joining that or participating in that, please do click on the link there in the agenda and register for that. The next announcement, I don't know who added that. So please. Okay. So some of you may have noticed that you got a lot of issues assigned to you recently. This is a widespread CVE that crosses almost all of our projects. As you can see, you know, it's, this needs to be fixed. I created dependent bot alerts as you can see for a lot of these, not every single one of them. So if you go to your repo and check security, you should see that you have a few dependent bot alerts having to do with, having to do with this. Please fix this. And if you're working on fabric chain code node, please fix all these critical issues as well. Anyway, just to notice, I didn't go through and click every button to alert everybody because I got some feedback that people didn't appreciate getting 50 alerts from GitHub. So please take care of that. What is the vulnerability? Is there any, can you give a brief overview of it? Well, just reading this, it says it's vulnerable to arbitrary code execution, arbitrary code execution. When you. That's about 99% of the vulnerabilities that everybody can say exactly that. I just, I just wondered if you had any, why you highlighted this one in particular? Because it was so widespread across all of our projects. It seems like so many repos use Babel. That is basically, it's so widespread and that's basically it. Okay. Next. I also have a question. I mean, right? Do you know that, I mean, the fix offered by Dependabot, is it safe to just apply when we have to check? I have had, I've been bored before where I just said, oh, okay, just apply, apply, you know, merge there and then it broke stuff. So I was like, oh, shit, we have to reverse that. I think I looked at it was like one of the 86% or something like that. So not a hundred percent, but a reasonably high. If I remember correctly, I mean, I look at a lot of these and I tend to balance between, you know, that's about the type that I actually take a look. Oh, there you go, 94%. I take a look, sorry, I run through the code like the demos as a test versus just merging it. A lot depends on whether our tests all run. Of course, if the tests don't run now, that's just a given, you don't, but, yeah, that's... And Ryan, do you have any insights in particular for this case? Well, I would just do as Stephen said, you know, run the test. I haven't checked all 300 of our repos. I'm surprised. What have you been doing during the night? Trying to sleep. All right, thanks. All right, thanks Ryan. Any other announcements that anybody would like to make today? Nope, okay. So for quarterly reports, we do have the caliper report that came in last week. I think we may still be waiting on some comments there. Actually, it looks like everyone, you may be the only one. I haven't seen Timo do any reviews recently. So I think that when the two weeks goes by, we'll be able to merge this one. And then for Sawtooth, we did get that one in this week. It was due today. And we do have some folks who have already approved it. So if you haven't had a chance to look at it yet, please do go ahead and have a look at that. But any questions on either the caliper or the Sawtooth report at this point? Okay. We don't have any upcoming reports due next week. I think the next ones are due sometime in early November and Steven, just for your reference, they are the Aries and B and Anancred's ones. So I think that's like the, I don't know, the 9th or 10th or something like that, whatever the Thursday is of that. Oh, thanks, Ryan. The 9th. I have been duly notified. No worries. Just giving you some advanced warning there. I know it probably takes a while to put those together. So no rush on that, because it's obviously a couple of weeks out, but just wanted to let you know. And then I don't know that anybody from Iroha is here, but if they do listen to the recording, it looked like there's was on that list as well. If I could ask Steven a question. I originally had these lumped together to make it easier. Is this harder? Would you rather do those out? It doesn't matter. It's fine. It's all good. Okay. So for discussion today, thank you, Steven for letting me know that we were supposed to continue the documentation task force update. I did miss that last week. So we do have that on the agenda. And then we also have the badging lifecycle task force, which was due to report out today as well. So I guess with that, Bobby, I will hand it off to you. You're the right one to take this off board. I believe I am. Thank you so much. So let me share my screen. I have to apologize. My computer's been acting funny. This may or may not go well. We're just gonna have to see. So for our recommendations, we decided to actually show them to you instead of just talk about them. So hopefully you're seeing my screen. Yep. We can see a screen. Okay. So this is an environment. It's a metaverse environment. It's a private metaverse environment that my company leases. I create events for people for learning experiences. So this is the space I've set up for the Hyperledger library. That is one of our recommendations. So this is the space. I just want to, if you have ever attended a Ledger Academy event and have downloaded Ledger Academy's hub and have the Agora software already on your computer, you can join me in this space using the code HFL for Hyperledger Foundation Library. So if you have Agora, or if you wanna go to agoraviora.world and download it and enter the room, Hyperledger Foundation Library with the initials HFL, you can join me here. And if you do, I encourage you to come over to here and click so that we know where in the world you're coming from. So I'm in Princeton, New Jersey. So you see, I just tagged myself. So hopefully by the end of this demo, there'll be a lot of different people having tagged themselves up. There's Dupour. Thank you. She's gonna come in and tag herself too. Again, we're all different avatars. I'll show you with a selfie what mine looks like. So this is me. So if you come into here, you'll see me walking around with my Agora hat on. So basically we set this up. We're gonna just go real quick. This is the directory of what's inside the library and then a little mention as to one of my favorite Hyperledger marketing things is a collaborative doocracy because it again, Hyperledger is all about doing stuff, not just sitting there and watching. So we're gonna come in here and in a minute we're gonna go over these Hyperledger task force recommendations. But I just wanted to go over real quick and let you know where the information. So there's two parts we're recommending. One part is the existing Hyperledger documentation. And that's what we showed you last week and we're just gonna show you where that stuff is stored. And then the other is our overall AI included documentation and we're gonna go through that today too. So yes, last week we went over the GitHub templates. So there right here are recommendations where that there's token and badging as you move through the lifecycle, user guides for the maintainers so that they know exactly with checklists what they need to do at which stage and dashboards to show them exactly what's going on. The next was the repos and I do have a lot of feedback on this. I do have a section upstairs in the maintainers lounge where we're gonna talk about what everyone's using. I was attempting to do a pie chart but I never got finished and have a discussion with some feedback on which of these to use. And I'll show you that. We did show you some AI tools. So there's links. If you click here, you will open whimsical and here's another link to the gamma product we showed you. Moving along, we did the templates. Here is a link to or actually inside the creation station. There's a link to all these templates and then we showed you jam bot using the Figma tool and there's a link for that as well. We also recommended dashboards depending on who your users are and we'll show you where they come in in a minute. And then the creation station, what do you wanna build today? So basically if you want to recap the presentation from last week, it's all right here but now let's talk real quickly about our overall recommendations. So obviously we're recommending a library that's there 24 seven globally accessible to the world. Here it is, enjoy it. All you have to do is download the code. It is available through websites. It's on the Ledger Academy website. It is not working. I have to talk to the people over at Agora world so that you would just be able to go to a website and jump right into this environment. We do strongly recommend and I'll show you where the checklist come in. Checklist for everybody because again, one of the feedback we got from, again, I'm gonna throw Nico in here from Firefly was that when he was moving through the life cycle, he didn't know what the next steps were. So we wanna be able to make that kind of experience for maintainers and community contributors easy so they know what they have to do and not have to search for what they have to do so they can just get into doing it. Also the content creation hub which I'm gonna show you right now. I might as well show you that right now. So in here is if you wanna create documents and again, this is just beta. We're working on getting this rock solid. You would come in here and you would go to, what do you wanna start building? Do you wanna start building with AI or do you have an outline? Either way, here's another AI tech link to chat GBT-4 where you take your outline or your idea and you ask it to be improved or ask what am I missing? What do you think could improve this outline? So many ways you can use chat GBT to improve on any type of thing that you're doing. And then again, once you have that outline, you can use the other products, the AI tools highlighted on the outside wall, gamma or whimsical to further enhance your presentations. Hydroport, come over to here and we have what do you wanna build today? You can click on any of these or you will be able to click on any of these and get into that information. There's a clickable link here to get you to all of the templates whether they're white paper templates, use cases so that if you wanna create any of these things in the community, the outline or the template is there for you and suggestions on what needs to be in each section so that you can get to the job of creating and not worrying about formatting. Again, this is, oh, sorry, I jumped, getting excited. These are a link to the presentation templates. These are all coming from the marketing department of things you can use in your presentations, very helpful. So that's samples for that. I always find those useful. Hi, Runima. And then you come over to here and it is a link to logos and guidelines and here's an example of the project logos and here's an example of the best practice badges. What am I forgetting? So this is basically where you would come in to create anything. Again, it's not finished yet. There'll be the templates for blogs, suggestions on how to do blogs, where to do, how to submit a blog. Anything you want to create in hyperlegic community you would come into this inner circle to learn how to create it. So that was just another one of our suggestions. Let me get back over to, sorry if I'm making any of you dizzy and I jumped again because I'm so excited. Okay, so now the rest of our recommendations that's the content hub. And then we also, if you remember, Jen Luca did the FAQ AI chatbot. We actually want to create a lab for that. So I'm gonna go up to the library lab section. So this up here is if you're thinking of creating a lab how would you go about doing that? So here's a link to the repository you would need to fork and instructions on how to fill that out. There'll be checklist for you every step of the way. You can click here to learn how to propose a lab. Step one fork this repository. So it walks you through it. We are proposing a lab, a creation of a lab which we're gonna be getting spot. Oh, Jen Luca is here, Slim. For the new lab that Jen Luca proposed which is laid out here in this section. So if you wanted to see about the AI lab or if you wanted to join us, pioneers are wanted for this one because it's just starting. Our first meeting is gonna be November 6th during the TOC documentation task force. So if you want to help us create a lab for this improvement, future improvements on the demo that Jen Luca showed us, please show up for that. Just to wrap up the tour of the library because again, we want a task force for AI tools is another one of our recommendations and a task force for updating the metaverse and keeping the metaverse library going so that it is available to show you a little bit more about what a metaverse space offers. Back here is the maintainer's lounge. So here are your checklist if you're a maintainer on how to get out of incubation status. We also have your life cycle here. Here's an example of when a maintainer's dashboard if you're a maintainer, you can come up to the couch you can type in your username and your dashboard would show up again with all of the relevant badging user documentation profile cards and statuses for your representations would all be percolated, I'm looking for a word I'm not gonna find but I'll be put there for you to access. And then also I intended this space to be for maintainers to hang out. So you know, after the meeting the maintainers want to talk about get book or make the docs, let's hear your experiences before we vote on which one or actually just have it's not gonna be a vote, it could more recommendation to the community as to which one you should use. Again, I'm gonna have a graph as to what the community is using now. I was almost finished with it and that will be on the wall over here. And then we can just set up a time to meet here and chat about what the maintainers feel the best way to represent user guides for the different personas would be. So that's the maintainers lounge and the lab incubator space. And then down here around the outside we have all the different project pages. You'll have a quick guide AI created on how to install each one of the projects, latest information. And again, each product can maintain this learning station for their product. And then if you have your best practice badge it would be displayed on the table. Again, each project would have that same space to explore. Again, here's the directory. So around the outside here we have the hyper ledger staff and we already saw it around the outside here. We had the presentation from last week if you wanted to grab any of those links. And for those coming into the space we wanna be able for end users or contributors to know exactly where to go. So for end users usually they are looking at consortium based solutions. So we put the special interest groups here so that each of the special interest groups have a description of what they're doing and a link to their Wiki page so that you can join the group and they go all the way around. So each one has a spot with their information so that if you wanted to join or learn about them you could do that. And then wrapping around the other side we have for contributors looking to get involved. So how to do a best first issue, how to obtain a Linux foundation ID, an overview. This is the white paper so they can understand better what the whole hyper ledger foundation is about. Here is a video on configuring your GitHub and your first pull request. This is contributing how to contribute video to hyper ledger projects. And then in here we have meet the staff. So then there's some hyper ledger meet the staff so that you can reach out if you need to discuss anything with some of the staff members. So that's basically inside the library but we do have and if everybody wants to join me over at the boat real quick let's see if anybody else tapped themselves. Don't see any new flags. So over here and I'm gonna hit my shift key so I can run. Again, this is based on Unity. I am a Unity educator. So if you have any questions on the product this is based on please do not hesitate to ask me. And again, this template is editable. I could add things to it using that Unity software. So this is what I call the meet up boat. So for the meetups this gives information on where meetups are where they are located, how many groups we have. And then again, I can put more screens up here but if you come up here you can click here and watch. If you click, I don't know if my computer is gonna do this for me. I don't think so. You can watch the latest recall. I'm not gonna ask it too because it might fry everything else but in this marquee, this media slot then that YouTube video, whether it's a recording would play or a live video would be displayed there. So the meetups could all hang out here on the boat and watch the meetup recording or watch the live presentation. And then finally, the last thing I'm gonna show you is when we're all done with all this wonderful work it's time to have some fun in the metaverse. So I set up a race track for us. And this weekend, again, I'm just teasing the race track isn't operable yet. I haven't put the gaming stuff in but it has functionality, I just haven't configured it yet. So for the race track, Fabric versus Firefly on Friday, Basu versus Cactus and then the winners of those will play in a tournament. And in here is our little race track where we have our little race cars that we can put our names on and race around the track. We'll put our, oh, hydroport, I mean to run into you there. And it does have functionality, it does work, I just haven't programmed it right. Again, and you can put your sponsors names, I can put the members names up around the track. So that's just a little fun for us. Hopefully this gave you an idea of what we envision a space to store all of this wonderful information we're gathering in a logical way in a directory so that people can find it and access it whenever they want. So that is the demo with our two recommendations or three recommendations for, four, if you count the library itself, a task force for AI tools in the community, a task force to maintain the library and also a lab for that frequently asked questions of Jan Luca that he proposed. So that's it for us. If anybody has any questions, I'll be willing to answer them or actually, and this is not my work, this is our work that the mentees, Jan Luca, Arunama, Shapur just stepped up Kajal and did an amazing, amazing job. So kudos to you. And I think that Tracy either has a question. Yeah, I have a question. So these items that are on the walls, are they links to existing webpages or are they kind of hard coded into the environment? They are links to existing webpages or can be hard coded in. You can put a regular link to an external URL. You can do a web link, which if it's like a YouTube video would play in the marquee. Okay, I'm thinking about, with the documentation being in GitHub, is there a way to link to those pages directly? Yes, absolutely. Okay, cool. You can link to any page. So if you like when we, let me see if I can do this real quick. So for instance, when we were up in the labs, running backwards for some reason, and you click this, there it goes in a separate web, in a separate browser, that would load. And again, I'm asking my computer to do a whole lot here with Zoom and Agora. But in that white box that you see should be loading that GitHub repository. Okay, great. And again, it's usually a lot faster. It's just my computer. So I apologize. It's not responding, shocking. But it would, if my computer wasn't doing so much, it would, eventually it will load in there. And again, this is like for e-commerce. We do a lot of NFT art shows and you can click right on the artwork and buy it in OpenSea. So that's really handy for Metaverse e-commerce. So again, we're gonna keep working on making some formal recommendations to the TOC. Tripur, go ahead. Hi, Bobby. Sorry, Tendra. I am saying that we are forgetting one more slide that we discussed upon for the recommendations. Which one? The ETH India one. Oh, Darnie, you're right, ETH India. Yeah, so we also have a recommendation and I forgot to put the slide up for ETH India. I'm gonna send out something in Discord to let everybody know. But one of our recommendation is Outreach and our first outreach is we really, really want to display this stuff at that ETH India event. I don't have the information handy, but during the rest of the meeting, I will find it and put a link for it into the chat. I can share the screen if you want. That would be wonderful. So, yeah, this is what we are talking about. This is one of the biggest event that is happening in India and it is happening in Bangalore from 8th through 10th of December, right, 23. And it will be the world's biggest ETH EM hackathon and ETH Global organizes this every, like keeps on organizing in every month in different cities, countries. Like last time it happened in Paris and then multiple events are going on in this. So yeah, we wanted to ask TOC members to support us and let us be a part of ETH India event and so that we can represent Hyperledger and our projects there. And if allowed, then we can encourage many good ETH based projects to apply for Hyperledger labs so that more projects can be incubated and reach to their graduation. So yeah, this is what we had in mind. Thank you. Any more questions? Tracy's got another one or is your hand still up? No, I have another one. So last week, we were talking about make the docs versus get books and there was some misinformation about make the docs in the recommendations and so I know I had commented last week in the TOC chat but I think that it would be worthwhile to speak further about that. I'm not convinced get books is the right option. I don't know if there's a cost that's associated with get books. I don't know a whole lot about get books but I do know that there was some incorrect information about make the docs in the comparison so I wanted to just bring that up as a point for us to work on in the future with some additional information. Yeah, and I know Roy had a comment too. Again, that's up in the maintainers lounge. That's why we set up a whole section for that discussion because we know that a lot more needs to be talked about but a lot of the projects used make the docs and like it and there's no reason for them to change if they have used that. We just thought that the get book solution was easy and something to just look at seriously because I don't believe there and I guess Tripura Kujal could correct me but I don't believe there's a cost to use that but I'm not sure about that. But again, that's... Sorry, Gopabi, to... No, go ahead. Yeah, there is a cost if we go for the whole organization then there is a cost but if you want to work as an individual in that then there is a limited amount of tools available but yeah, we can work with that. So that is a problem if we are looking at that. You know, so basically as a task force what we want to do is we want to still have that conversation now with the maintainers now that we know what's out there and what everyone's using. So we did the analysis on what's being used and again, we showed that a while ago we're going to update that and put out a survey to the maintainers to see out of what we've discovered do you like what you're using? What can we do to help you? And again, we're going to arrange for those calls in the next few weeks. That's it. I'll turn it back over to Tracy for the next part of the meeting. All right, thanks Bobby and thanks to everybody who's worked on this so far. I think there's a lot of interesting ideas and information that have come out of the past week's presentation and today. So I think the next item on our agenda is for Rama to talk about the Badging Project Lifecycle Task Force. So I know we've been doing a lot of work there and I'm sure there's some updates that Rama has to provide for us. Thanks Tracy, can you show me the screen? All right, can everybody see it? It's coming up. Can anybody else see it? I haven't been able to see it yet. No, I just see a blank screen. I think your screen share is loading. Let me try. Still nothing, right? Still loading. Okay. Let me just drop the link there but Tracy you can share it. You don't have to navigate to it. Okay, I'll put it on this call. Tracy, can you try sharing? Yeah, I will give it a shot here. All right, thanks. Yep. Okay. Okay. All right, so actually before we go into this, I just want to ask the right question. There was a meeting on September 29th but I tried to find the recording on YouTube but couldn't. Can you look that up? And I'm not sure what happened. I'll try to look. I'll drop the date on the discord. Okay, so thanks to Tracy and Aaron for brainstorming with me on this topic. We had a short update about I think almost a month ago and since then we have kind of crystallized the set of badges and what, how we associate them with the project lifecycle and I just want to show you what it is I've decided on. I don't think I should take only more than 10 minutes to cover this and then we can have some discussions and if everybody is agreed on the badges, the criteria, I can make a more complete documentary draft that let's solve the criteria and everything. Because right now that's the form of links and notes. So what we tried to do here, just as a reminder to everyone is we want to list a set of badges that can be awarded to any Hyperlegia project and displayed on the website and the GitHub repository. And we also want to list the promotion and the motion criteria for projects that is moving from one station to another in the project lifecycle, based on whether or not they've fulfilled the criteria for the badge or if they have slipped up on maintaining the criteria needed to retain a badge. So the, you can see here, there's a section called mandatory badges, the section called option badges. Mandatory badges are those badges that we identified as necessary for some kind of project lifecycle decision, either to move to a particular stage or if that badge criteria has not been fulfilled recently then the project will be demoted. Optional badges are those that are somewhat softer. They are not going to necessarily be used for the project lifecycle decision, though they may in the future, depending on what the TLC decide. And those badges, but those badges, if the project possesses them, they indicate something good about the project. The fact that the project is mature and it's well maintained and people can have confidence in using them or also they feel good about contributing to the project. So those badges is just good to have. How are they going to be evaluated? I think at this point we have generally agreed that the projects are going to be, I mean the badges are going to be evaluated and re-evaluated at the annual review cycle. Though I think we also kind of agreed that if project maintainers asked for a particular badge, then the TLC could consider that in the next TLC meeting and make decisions. So yeah, that's the high level overview. And yeah, thanks TLC for navigating down here. I try to associate the, I just made a list of all the badges that were in the above list and attach them to these are just mandatory badges and attach them to the different project lifecycle stages. So if a project has to, if a proposal has to accept it, it needs to pass the legal criteria that is the code needs to be Apache 2 certified and carry the appropriate license declarations. It needs to be decentralized to some extent that is it needs to have at least two independent organizations contributing maintenance to the project and also those maintainers, the contributions should not be heavily skewed which is somewhat more of a subjective decision, but at least the count is something that we can verify in a straightforward way. The badge, the top level is part of a badge indicating that the project is top level badge is a top level project that the full hyper-legion project versus a lab project. So if you're qualified for a hyper-legion full, a full hyper-legion project, you'll get a top level badge. And if you're a lab, you'll get a lab badge. But that's sort of just, it's not a basic criteria, but we thought it would be good to have. Security refers to the project meeting the basic security guidelines requirements that is attaching the security template, making sure that there are security spots and so on. This is the following criteria laid down by the security task force. So that's a proposal stage. You have to move the incubation stage, there are a few more criteria you'll have to fulfill. You need some kind of a testing framework and this is some amount of documentation. It's not a spot because we couldn't really, we thought that we could give a pass to projects that were kind of mature on code, but not necessarily completely fulfilling all the testing documentation criteria as we have defined. But if something is necessary for a project to move from proposal to incubation stage, further it needs to have some CITD in place and also structure. Structure refers to the typical, the minimal hyper-legion project structure that all hyper-legion projects are supposed to follow. That is needs to have a particular files like maintain order 10D, security 10D and maybe folders like for documentation, for specifications, RSTs and yeah, for source code and others. So as long as the project has the minimum list of files and folders that hyper-legion project needs to have, then it will get a structured batch. If you go down to graduated, you'll see there are more criteria and I think everybody's kind of familiar with these criteria since we had a couple of graduation applications just one month ago. This also includes beyond what criteria are required for incubation. It includes, it requires an open step, best practices, the batch passing grade and it also needs to have at least one demonstrated use, demonstrated production use and at least three organizations that maintain the project that's the decentralization batch. So those are one thing green because these are badges that qualify projects for promotion. Now, the boxes in red indicate when the project will be maybe demoted. So if you can see, I added an arrow from graduated incubation. You won't find that arrow in the official diagram I just added here because we, when we were discussing this in the task force meeting, we thought based on particular non-properment criteria, graduate project project could be demoted to incubation rather than going to government or dedicated or UL. So a graduate project in point of incubation if let's say it's a number of organizations that are maintaining a drop from to lesson three and if the project maintainers are not following the release guidelines or they're not, the testing is not adequate to maintain maybe they've slipped up. Again, these are criteria that have to be manually affected and we expect that this could be done during the annual review cycle. And if the project is being not to pass some of these qualifications for those particular badges then we will demote it from graduated incubation. A project can go from graduated dormant if for somewhat more specific reasons that the releases are very infrequent that say a project has not put out a release over a year maybe it's not be actively maintained. The security criteria or the security box are also maybe not responsive or if the project is not actively fixing security bugs that are filing against it. And if there have been no new, Russian use pages demonstrated over a particular period of time the project can, for duplication you will just won't actively identify this. If the project is not, if the graduate project is not following the state security guidelines then it should be first move to the deprecated and if it still can use not to follow the guidelines then it will move to end of life. Yeah, that kind of covers what we felt would be with minimal set of badges and the criteria required for a grade or downgraded project. I'll stop there and take the next question. Any reactions? Looks like everybody said that. Of course, I mean please, this is fundamental information just review this at leisure, drop comments on the other page and if you can have a chat, you can also have a follow-up discussion in a future view. Does anybody like it? Anybody hate it? No reaction is it's hard to know whether or not people have a feeling here. I like it, I think it makes good sense. I think, yeah, having the definitions the underlying components that indicate what incubation means, what graduated means is good and being able to display it and badge it is a good idea. It would be good to see on the different pages. Thanks, people. Let's hear a thumbs up from Marcus. I saw a celebrate or something from Bobby. So these look like good reactions. Any, like, oh my gosh, what are we doing? Sort of reactions that people are having? I think, if nobody else has any comments, maybe informalize this into a better looking document that complements the list and I suppose then we put it up for adoption. Yep, I think that would be the next steps. All right, yeah, just give me one more cycle and I'll make second document. Okay, that's fine, no worries, Rama. All right, if there's no other further comments or questions on what we have here, definitely do have a look at this. If there are comments, specific things that you think weren't covered appropriately, there is a bunch of discussion down here about what each of these means, kind of the penalty for non-compliance. Any notes that Rama took during the discussions that we had? Please do have a look and see if there's anything that jumps out at you as, oh, that's not how I understood this to be. And just leave a comment and the task force can take that forward. If there's no other questions on this, are there any other topics that anybody would like to cover today? So if there's not, then I think that the next discussion that we have for task forces would be the continuous integration. I'll ping Peter and let him know that he would be next up on the agenda. And then obviously if there's anything else that comes up, definitely let me know where the agenda. We can add that for next week. And I guess with that, if there's nothing else, I will put in another reminder that if you haven't put in your nomination and you wish to run for the TOC next year, or yeah, I guess next year, then please do add your nomination before end of day on the 31st, since we won't be meeting before that. And we will, yeah, I guess close today's meeting and talk to you all again next week.