Hiero TSC Meeting - 2026/08/18

Hello everybody in engineer. How can you be before me in that meeting when I left the other meeting we came from before you? How fast are you? Um I'm some people tell me I have ninja fingers. I think it's because I spend all my time typing on the computer and I'm unfortunately where I'm I think my phone is bouncing off the internet connections in my area. So I think one of them is a little faster than the other. So I think it's working in my favor. [laughter] >> Okay. Uh okay. I was like how how can that be? Yeah, the the enterprise Java uh repository is going off great. Um no new updates and everything seems to be moving quite along. >> That was that was just the ending of that meeting. >> That what I missed. That's good. >> Okay. [laughter] So, let me send a ping to all the different groups. Hey everyone, good morning Um, no, we don't have Diane. Actually, I hope that we have Chrome today because I would at least uh do a vote on the um project proposal we have um because the corners work didn't go through. I think this is just because of vacation time but let's see I just pinged in all the channels. Um I know Eric cannot join today. I know somebody else from the TSC said Omigan said he will not be able to to join. Let's let's see if all the other people come up. Let's wait two more minutes. Okay, maybe I already start with the introduction or you're not seeing me, right? Let me share my video. So, welcome to the TSC call this week. Um this is the technical steering committee of the um hyro project of the Linux foundation decentralized trust and like every call we are doing within the hyro project. This is a public call which means um everybody can attend this meeting. It's not only for the members of the TSC. Everybody is free to join this meeting and not only join this meeting but even bring in topics uh join our discussions and so on. And next to this meeting we have some other meetings in the Hyro project. We have a public calendar. You can find the link here in our meeting notes. And I'm happy to share the agenda for this week with you in the chat. Um, and in the calendar, you can find invites and appointments for all meetings we do. And for a lot of past meetings, you have even links to the minutes and or to recordings of the call. This one, for example, is is recorded. So if you miss it um or if you want to check something that has been discussed in the TSC, you can easily go back and watch the recording of it by finding it in the in our public calendar. And since we try to do all those meetings as I said as public as possible and integrate as many people and and voice as possible. We have some basic roots here which is the antitrust policy of the Venox Foundation and the code of conduct of the Venox Foundation. And with that, welcome to this call and hope um to have great topics and discussions with all of you today. So let's move forward to the agenda. Um let's start with the short overview of the gas tierc call and in the gas tierc call we had an overview about the upcoming election um where the nominations will start in a week. Um we have three seats of the TSC um that um on on that we will vote for for new people um for that seats and nomination for that will start within a week and then we had a presentation of a project proposal last week that was a project proposal coming from the so team. um that would like to have more repositories. So, it's a totally new project. It's like extending the the repositories of the solar project. Um we made an Git vote an asynchronous vote out of it. I can already tell you the vote so far not went through. um because some people are from the TSC are just currently invocation and on the other hand some discussions of that um proposal happened um since last week and I think that are quite quite good discussions and and the people behind the proposal and I see Keith is here in the meeting because it's coming from from Keith and Jeremy um have updated the proposal and um added added some yeah updates to it. How it can be first of all done in a more easy way and and then based on that we can maybe move forward and and bring it to to a final form if we see that this is needed. Um actually my wish was that um because we have it here as point on the agenda that we can vote on that today but when looking at the um members of the call um I only see three TC members. Sadly, we do not have quorum in the meeting today, which means we cannot vote on um that one. Come on. Come on. Why is it not moving to it? Um okay, good. But if if you are interested in it, so there's a new project proposal that that gives an overview and makes first of all the creation a little bit easier. It just creates one new repository which is a solo build actions repository that add those specific actions to it instead of creating one and for every of those actions new repository. The other two the so charts and the so containers will stay. So those are two new repositories that is totally fine and even the relationship to the hyros action has been added here which I think is is quite good to to see how all that is is working together. Um that is that is quite nice. So um first of all Keith thanks for the additional work to to get all the input into it and update the um description of it. Um and yeah sadly we cannot vote on that today. Sorry sorry sorry for that. Um, but I will like the other two hip votes that we have which are both more or less in the same state as I assume. Let's have a look. But I have not seen that something. Yeah, same here. And does that one let me check and I see Keith here raise your hand. You can just already speak. Yeah. >> Yeah. I just had a quick question. I mean, I think all summer we've had a problem with getting votes and getting quorum at TSC. >> Just out of curiosity, does the TSC members have like their own communication channel where you guys can like I understand there's probably a lot of noise out there like is there a way that we can you can just ask, hey, there's an async vote happening. Can you guys please vote or something like that? >> It is. And I see some people here like Brendan is raising hand and I assume Brending is saying Hendrickk did. [laughter] Brandon, >> I was just going to say um as a TSC member, I've been trying to get um back in the channels. I know that a few other members like Milan have been trying to get me back into those channels. I don't have a Slack account of that anymore. >> So that's why I think you raised a really really important issue. I think that even internally when it's DSC there are problems. It's been a few weeks since I've been able to get in touch with TLC members and there's been quite a few requests. So, it is it definitely is an issue. >> Good. Good that that you bring that up because my assumption I've seen that you posted it or somebody posted it like a day or two before I went to vacation like four months for not four months, four weeks ago. And I see some people answer on it. So my assumption was it's solved. You know, for me it was not a to do anymore. Um let me get let me create a >> I don't know what gave the impression that it was that it was resolved like I'm just I'm not I'm literally not in the Slack channel. So and I think that Slack is probably not a good >> I I haven't checked it. I I agree with that. I haven't checked it. So So I was like I've seen there was some discussion about it. I have not checked what the state is. I was like, yeah, that is three weeks old. Somebody will have take care have took care about it. That was just my my assumption. Sorry for that. >> I would I would say probably too just I I would advise probably as well maybe we migrate the TSC out of Slack just because as >> um new members come in and we kind of want to expand this out to the broader open source community. I think that being in a Slack group requires you to have a paid Slack account, and I just don't know if that's feasible for for a lot of folks, especially um in kind of this economy. So, what I would recommend is maybe utilizing a platform like Telegram or something for those um official channels for TSC members. That would probably solve it instantly, I would say. Whereas, if it being in Slack, I don't know who would pay for my Slack account, but I just don't have one. So therefore, I'm not able to participate into TSC conversations right now. So that's a big >> Yeah, that that's a problem to totally agree on it. We have a Discord would be my favorite. Maybe Oh, I see Diane has sent up. Maybe she wants to do the say the same. >> That's exactly what I was saying. That's why Discord is there. That's why the TSC members should be monitoring it. And it's doesn't cost you anything. Um Brandon, so um please use Discord. I can't say it often enough. That is our communication channel. >> That's awesome. I was just gonna I was just referring to the kind of um uh TSC private. Is there Hendrickk? Is there is there like a because I know that the Slack channel with Lehman and all those folks like that's kind of the central member chat I would say. You're saying there's an equivalent on Discord. >> Not No, I'm not saying there's an equivalent. That's what I'm referring to Diane. >> Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. But um I assume Jesse Kisy in the call um that this would be possible to to create it and and I agree with what you said Brendan if like um it's a must to pay for to be part of the current TSC channel. Yeah. Yeah. That is that is absolutely not what what we want. And again um sorry for that for me. I said I read it in my vacation and I was assuming it's it's done. Um what I do not want to do is just now change it especially in a meeting where we don't have problem. So my suggestion would be we just me prepare it and next week we presented as hey that that could be the new solution to communicate and we in best case just say yes or if somebody complains about it do a voting within the TSC on that. I think that is the way how it makes sense which sorry for that President would mean uh it's it's another week what I can um tell you is um I don't know if we are disconnected on discord but I'm happy to forward everything um in the TSC channel to you manually to to you on on um on discord and that explains what I said earlier Right. So the is a the request I I think it was Diane about hey Hendrick can you maybe ping the TSC for those other Chronos. Yeah. Yeah I did but Brandon have not seen it because he's not in the channel anymore. So like Stoan has seen it. He votes on it and and and so on. Right. Um but but that makes it clear why others have not vote on it. Yeah. Um, >> so is your hands up still because you want to say something, Brandon, or have you not done hands down? >> Oh, sorry. I didn't know my hand was still up. Hold on. I'm on my I'm on my mobile phone. Apologies. I'll lower my hand. Thanks. Thanks, Hendrick. And no apology needed. >> Perfect. Good. So, I created an to-do item for me for that. Um, that's good. Um, okay. But so we looked at all three um as said um for none of them we had enough votes and um we still don't have chrome here have we one two three four five oh we are now five people here in the meeting um one two three four five which means if we want to um we could um go back to the uh project proposal and and do a vote here in the meeting about it if anybody from the TSC who's here in the meeting feels comfortable to do so because then we could move that proposal with the updated description about having one repo for all the action and then two repos for containers and charts forward. Ward. So the point is are there any questions from TSC members or anybody else here from from the meeting about that? If not, we could do a voting on it to approve it. One, two, three. That looks good. Okay. Um, with that we can do a voting on the build so build component actions repository and um, let me see. Story >> I vote yes. >> Um, uh, Brenda, >> I vote yes. >> Georgie, >> yes. Richard. >> Yes. >> And I vote yes too. Um that is great. So Keith please inform Jeremy that this one is approved. I will directly put it here. Um now we have the two hips. Um the let me open it. the sponsored feip and the ignore trading call data for system contract. So I know at at the um spawn fees there was this discussion going on. Um I see both here in the meeting uh Tai and and Richard. Um what is the state here? >> I think that is a Richard question. I sent you a DM a while ago before my vacation. Richard, sorry. >> Yeah. Yeah. It was before I went out of town last week. We haven't had a chance to sync back up on it yet. >> Okay. So, we move it to next week. That's that's totally fine. Boom. Boom. And then we have the um ignore training code data for system contract. um which have Dorian, Migan, Canto, Georgie and um AX already approved. Um does everybody here in the meeting feel comfortable to vote on that or should we um move that to next week too? Uh, who has yet to vote on it async? I think I'm in the list that hasn't done an async. Is there anybody else? >> You haven't done an async. I haven't done an async. Um, what >> uh can you stick the link in the >> Just send us the link and we can finish it. Yeah, I think we cannot just click on that and it's done because the vote was already closed. Um, so so it's either um >> we can do it we can do it here. Um, I was just checking to see if everybody here already voted on it or not >> other than you and me. >> Oh, you did. >> Every Brandon is missing. Um, everybody else here has has voted. So, we could easily do it here because then we do not need even 100%. Would be totally fine with us here voting. So, let's let's do it. Um, Stoya, you already voted on it, but c can you do it again? >> Yeah, I vote yes. >> Perfect. Thank you. Same for Georgie. >> I vote yes. >> Perfect. Thank you, Brandon. >> I vote yes. >> Richard, >> yes. >> And me, yes. Um, which means this is approved by TFC. Perfect. Okay. Soft, a lot of stuff. I like it. So, now we have some new topics. Um, Sophie, you would be next. >> Um, yeah, maybe I can talk about this just for two minutes. I actually wasn't sure if I can make this call, so I I wasn't able to um prepare all the things that I wanted. Um, but maybe I can just sort of quickly introduce what what's sort of going on. Um, yeah, one second. >> Do you want to share something or should I go somewhere? >> Yep, I can I can share but not while you're sharing. Thank you. Okay. So, um there is this Hyrohackers um GitHub organization which described here is a playground development community um around Hierro. This has grown quite quite well recently. Um there's a nice variety of projects, different um languages and things and um I've been trying to think in terms of how do we work to nurture these projects so that they are more ready to transition to hyro and um you know for the the TSC vote. So um in the governance repo I have started on sort of outlining um some rough sort of criteria um of of what that would look like. But this is this is a work in progress. It's the kind of thing I want to sort of discuss and sort of with with the TSSE in terms of when a project gets proposed to you guys sort of what sort of criteria would you like to look at and things like that. So yeah, I I think if I'm able to delay that until maybe not next week because I understand that then there's a lot of other things to discuss, but maybe the week after. >> Okay, >> thank you. >> Then let's do it in two weeks. Um share that one again. Um so the next thing is that is something um Jessica Sophie and I worked on and we did an update to our description of committers and maintainers based on discussions happened over the I don't know maybe last two months or or whatever um in the community and and even on the TSC Um and I said that for me it makes sense to inform the TSC about that. I think we don't need to vote here but just check in this meeting and we have Chrome that is very good. If those changes are fine for everybody. So what we did is um can I somehow Yeah. So we have this document that is called roads and groups and and that document describes what a contributor is, what a junior committer is, what a committer was a maintainer is and how to become one, how to remove somebody and so on. But what the document was highly missed is what are the responsible responsibilities of that kind of proof. So I think for yeah for the committer there was nothing at all. For the maintainer, there was one sentence. And what we did is we added for committers and for maintainers a section about how we so with we it was like Sophie, Jessica and I based on the feedback we got um see the responsibilities or of a committer. let's say like better how we understood that we as a community see it and we tried to to write it down here and my wish would be and maybe we take like three minutes to have a look at that and and see if that is fine for everybody or if we need to do some changes and I'm happy to send the p request here into the chat too Um so please have a look if you think that is a good description for for committers. If you think anything is missed for sure say two then we could create a new pull request an additional one. If you think something here is wrong we need to fix that. Please >> uh a while back I I wrote up a proposal for the TSC regarding security for committ. >> Yes. Yeah. >> Um is that part of this discussion or this is that's outside of this discussion? this is outside of this discussion and that is um something so especially one of the three you did I would say yeah yeah yeah we should create a pull request out of that so um maybe maybe you can do it for for next week so that we do more or less the same um next week with with what you had would that make sense to you >> yeah I mean how however you want to do it I don't care >> yeah yeah but I would say for sure Those are two different topics, [clears throat] right? Um because one is about security and this is about what we expect from you as contributors or committers or maintainers. Sophie, >> yeah, I I actually um I think this document would benefit later. uh as you say this is a responsibility declaration but I think this document doesn't detail too well what the requirements would be for a committer or the requirements would be for a maintainer I think currently the requirements are more time based um so Keith like if some of the requirements are to meet certain security requirements I think that that would also maybe be sort of in that scope but I I would view that has something additional that we need to do to this document. >> Yeah, make makes sense, too. I I like that and I think it it should be additional. Keith, you want to say something or is that still an old hand up? Okay, Diane, >> I I would like another week to comment on this before you bring it to a vote. um just so I could >> absolutely >> dive into it for how it compares to what the LFDT's current governance is and just make a few comments on that. Um there was a line in it and I can't find it about um sponsorship of um maintainers and I'm trying to find it in my three minute review and I can't. Um >> yeah, >> that someone needs to have a sponsorship and I'm not sure that align. >> No, no, no, no, no. That is not here. We don't. That is >> that's not >> absolutely not. No, no, no, no. >> Okay. I wanted >> No, no, no, no, no, no, no, no. Abs, absolutely not. You don't need a sponsorship. I think that is more where Keith had ideas about security for emergency stuff, but you you couldn't miss that's why I said I would like to see it >> independent of each other. Yeah. >> Yeah. I think I might be conflating the two. So, I just would appreciate another week to take a look at this and and make sure totally fine. It's in line and and with Jessica having done it, I'm sure she's already done all of that work, but I just would like one more week and >> yeah, that that's totally fine. And and we have more or less the same for maintainers, which start like everything a committer has fits for maintainer too. And then we added some additional topics here. Um, since you want to have it open for for a week, I think we don't need to do now a a 3minut week break for for that one. And I'm happy to to have it open for a week and correct um comments on it. I think what we should try to do is if you disagree with anything here um we say it because otherwise I would like to see all comments as yes that is a comment which could be done afterwards because what I don't want is to keep this PR open for two months with with endless discussions because exactly Those topics are the things you can discuss and close on, right? And as long as nobody has a real blocker here, I would like to have this initial version um merged and then move forward with with all the commands and um yeah, how to say it in English? Um partnership. Does that make sense to everybody? Yeah, Diane. So, I did did a search for what I was looking for and I did find it and let me see if I can read it out loud to you. I've got too many windows open right at the moment. But it's um under the additional roads roles for um supporting on boarding contribution that section um keep going, keep going, keep going. There you go. And there and that last paragraph after the bullets, these per project rules can be granted. based on community sponsorship or through a maintainer role blah blah blah. >> Um, as defined today, the roles can only be granted to people based on sponsorship from a company that is a member of decentralized trust. Um >> I can explain that that is um for for triage and and this is because some some people wanted that but the idea behind that role is oh we have some managers who will like so let's assume a company like in this project hashgraph or lime chain have several people who work on an open source project and then you a team manager or or project manager who's not technical at all, who's never committing, but who would like to keep track about the issues, maybe assign issues and so on. um with where we came from where we only had a contributor who's not allowed to do anything I mean like right access in in the project regarding that a committer and a maintainer nothing of that fitted into it. So what we said for those managers we need this specific role and then we came up with saying okay we need some kind of rule to define who is allowed to get it because our idea is it's project managers right and that's why we came up with that but in the time over time what has happened is we now have the so-called called junior committers and a junior committer is someone who has a triage role who is allowed to assign issues add and remove labels and and so on. So in theory I I need to take a deeper look into it but but I assume it's like that a junior committa and this super special um project triage contributor will have the same access rights. So what we could do is we could merge it. We could say like hey we have the junior committer role and for the junior committer role it's really more like hey you have created some issues you did some basic stuff then we invite you to become uh or to get that role and >> if you are a product manager you will create issues right so you will get that role quite easily so that is something we for sure could think about >> yeah and then you could then you could take out that line about having to the people based on a sponsorship of a company and that would make it more in line with um the standard governance the LFDT has. >> Yeah. >> So, I think that that was what jumped out at me. I'm sure there's probably a few other things that I'll do it, but I would suggest that since you have that junior role there and if that's everybody's understanding of how you know the project managers become junior contributors at the very least, >> um then then I'm okay with it. Yeah, I I think that that one makes sense. Yeah. And as you see, this is nothing that has changed, right? So, >> um, regarding those changes, we would like to bring in now that should not be a proa because it's a different topic, but I agree with you. We should have a look at it. And I see there's some hands up from Jesse. Hey. >> Hey. So, I have a question concerning that. So who do we do I have to like personally appoint myself to to become a junior developer? Sorry, junior commuter or someone specifically has to like raise a vote on that. >> Okay. Yeah. So um how it works similar to so for junior committer committer or maintainer what we need to do I I can happy happy to show it to everybody. What need to be done is we have um a file. It's this YAML file that contains all the different groups and information and what people are in what groups. So from a technical point of view to have somebody become a junior committer, someone needs to do a pull request against this config yl adding that account to the group of junior committers for the project and then all maintainers of the project need to vote on it um to get that person in. Um I think doing self-nomination about a junior committer is not what we normally want because um it should come out from the other committers and maintainers and I would even see it as that is part of the work of the maintainers because the maintainers should take care about the project including the community of the project. the project grows and the diversity of the community. So from my personal point of view, if somebody is working on a project and wants to become a junior committer for that project and the maintainers have not recognized that work so far and have not proactively um to ask you if you want to to become a a junior committer or created a pull request for it, the best case is ask in the related discord channel. So in in discord we have for each and every project a channel like let's say like if you talk about the hyro solo action there's a channel for it if you talk about the SDKs there's a channel for it and so on and you should ask in that channel hey I'm Jesse this is my GitHub account best put in your GitHub account there so that the people can see what you did on the project and said oh I did some work on that project and I want to know If I can become a junior committer on it, I would see that as as the second best as said best would be if the maintainers do it proactively. Um, does that make sense to everybody? I see hands up and I see a question from Sophie. >> Um, yeah, I think that that would be like the best case scenario, but we do have inactivity with some of the maintainers. Let me know. That's why I said the second one and not just mention the first one. Um I know that we have um um for some maintainers not enough activity and that is where maybe now the third one comes into place. So if you do that and get ignored like you ask it for two weeks or whatever nobody answers to you and not saying yeah I will do it or whatever then I think the TSC or community call would be a good thing to to mention that right so if if somebody is assuming there's a person who >> did work on on one of the projects and want to become a junior commit committ whatever. Um that for sure should not be blocked by um people not being being active because if we have people not being active, it's even more important to get other people to those projects. Um so yeah, please try what I said. Um if if you ask for you try what I said, write it in Discord and if you see that nothing comes back um bring it to any call um maybe to like the community call or directly to the TSC. Sophie, >> yeah, we um there's actually no easy way. Um I find not everyone's in Discord yet for example especially new contributors. Um it can be like a slow process to communicate to members in a repository that we are looking for commitments or we are looking for junior committers and this is the responsibility that we that we accept. So for example in Hierrohackers there's there's um you know lots of different repositories there and we're trying to grow the different community members but um some of them are doing some some good work and I would sort of like to communicate to them >> hey you know we're looking to get some people with more responsibilities and things but I actually have no direct way of contacting them. It would just be like one to one maybe if they have like an email tied to their GitHub commits. >> Yeah, that's um >> maybe like a discussion page or I mean there we don't really have like a Yeah, I think the current system isn't great in that sense. It's it's slow and it >> Yeah, I understand what you mean. You cannot just you know like ping and start chat with somebody on on GitHub. So somebody created something and you said, "Oh, you did like three very nice contributions in us four weeks. Um, >> would you be interesting in becoming part of our group here and become a junior promoter?" That that would be the easiest, right? So that is sadly not possible on on GitHub. Um what we could do is um we could create maybe a template like we already have templates for AI swap and stuff like that which is a very welcoming message about hey we have that um and based on your work you might be a good person to do so and here and here and here you find some information and what we can then do is we can post that message into a pull request done by that person and mention that person there. Um that would be a way how we could try to create contact but actually the only way um I see to be fair. So that could be something uh Jessica you and I put on our on our working list and and come up with such templates so that we can even easily put it into pull requests and and proactively suggest to people. Okay, I see from both names I said thumbs up. That's already good. Okay. Um any any other um concerns, questions on that topic regarding committers, maintainers, project roles and so on. >> Yeah, this this is Diane and I put it in the comments here and I'll put it in the comments on the issue too is I'd like to see some language explicitly encouraging organizational diversity among the maintainers. Um, so I'll add that in. And there's a little bit another there. So yeah, but yeah, I apologize. I didn't I didn't see this before the meeting, so I'm just weighing in late. M >> yeah we disc I can already say she so so when Jessica Sophie and I um wrote that we discussed how far we want to go like how extreme um we want to to be and say like hey it must be more diversity and and so on and so on and we decided we discussed more or less exactly the topic you wrote and I think all of us agree on it it's it's not something we need to discuss if we agree on it. Um we decided to start with something that is so basic that hopefully everybody easily agrees on it and then in the next iteration we can add something like that and then in the next iteration you know that that we do not one big bang that is discussed and discussed and discussed but do it more um on several iterations. >> Yeah. Well, I still I would uh I'll put the comment in and and I would could get this into the this this iteration because this is pretty lightweight. It's not saying mandatory or anything in it. It's just active actively encouraged and that was kind of where I was leaning is like >> don't we have written something like that even give even a second. I was thinking we said oh yeah we want to have it in a guideway way somewhere written down. >> Yeah. And this >> we had initially like if possible but then we removed the that wording. >> Maybe maybe >> yeah we never we never committed to that. We >> we edited the >> Yeah. >> Yeah. Yeah. >> This is this is not holding a a a fire under anybody. This is just putting it in there. >> Yeah. So that's what I'm >> trying to get into. >> I'm as said I'm totally happy with that. My idea was step by step and to start with where nobody discuss but I'm happy to to add that especially since nobody here in the meeting currently to hands up and says oh I would like to discuss it and I directly see two thumbs up on it. So to totally happy I'm I'm just copying it out of the um message chat and um happy to to throw it in. Yeah. >> All right. Cool. >> Okay. >> Thanks for doing this everybody. It's it looks really good. Um >> yeah, it's getting more detailed and and better with with every iteration. I agree. Yeah, >> cool. Um, with that, oh, I do not have the agenda open anymore, but can have it in a second. But I think that was the last topic for today. Let's see. >> I think I added a small one. >> Oh, Jessica did some additional work. So, Jessica, the stage is your >> Thank you. Thank you. Yeah. So this is just um an effort to make um uh Discord a little bit more likable for people. I know many people don't like it and I know that one of the uh concerns is that there's too many channels uh and it be it becomes confusing to follow up conversations. So we identify and this is not just uh me around hyro channels but um David and Ry are also doing this as a a global all channels. We're trying to identify channels that are uh could be pruned and could be archived or deleted depending on the conversations that are hosted in those channels. So I have identified uh one, two, three, four channels so far that have uh minimal to no discussion happening. So I just wanted to run it by you guys if it is okay that we uh we remove these channels. And additionally to that we probably should create the TSC channel that uh the TSC channel uh that is going to include all the TSC members. So uh those are the two changes that I'm trying to to run by you guys. >> Makes sense. Yep. >> Perfect. Thank you so much. And yeah, if you identify any other channel that could be archived or could be removed, just let me know and we'll take care of it. We'll try to make uh Discord a little bit more simple and easier for people to to to use. Thank you so much. >> Thank you. Okay, with that we have 10 minutes left. We come to any other business. Is there anything somebody of you would like to bring to the TSC? Ask maybe there are questions um you have in mind um uh I'm just curious about the um kind of uh process to become a contributor. you know since I in my case I I was contributing uh you know kind of earlier this year. >> Oh >> yeah yeah yeah just just you know what that that process is really helpful. >> Sure absolutely I I can help you first of all um great that that you are here and and thanks for your contribution. Um so you will find that information in our um roads and groups MD. Let me send it to you. I send it here in the in the chat so that you have a link and in the same folder there's even an FAQ that answers some questions. But in in general what it says um a contributor is everybody. Contributor is just somebody who has some kind of interaction with the repo which could be I create an issue. I create a pull request. I comment somewhere. That is that is what what a contributor does. So that is what you already are. Um from from a contributor the next levels are a junior committer and or a committer. So the the difference here is we created this junior committers especially for for young people who are still juniors in in software development maybe never did big work on on open source where they get some some first um you know like um authorities about and signing themsel to issues and and agreeable to issues and so on. So do some some first help in the project um with a clear goal to to make them to commit us where you then have the the rights to you know like um review PRS and and do all that stuff and how to become a committer. Um, there was a definition. [laughter] Oops. Give me a second. Um, here we go. Adding a committer. I think this is currently the definition what we have. You need to do quality contributions and reasonable time contributing to the project which don't mean like every day it's more about the time span or project dependent every project can decide that maybe three to six months um to to become a committer. So if you for example do that in in your free time and every second week you create a pull request and do that over two to three months that is from my point of view for sure um was becoming a committer of the project. I mean depending of the pull request right it is always just one character you you change maybe it's it's it's discussion able but um we don't want to have this written in a totally hard way like you need to do that many pull requests in that time and the um code diff must be that high. This is more like here are some guideweight routes that the maintainers of the individual projects can take and and check are there people who might fit into it that we can um give the the committer state because the clear goal of the project is and should be but but is to get more committers and not to hold people away from becoming committers. slide. So often um especially in the projects where a lot of stuff is happening um it's hard to keep track of new people how much they did who did that and that's why I can say here similar to to what I said to um the question from Jesse earlier don't know if you have already been there about if you think that you did reasonable work in in the project um just ping the people and and ask for it and in best they say oh we totally missed that. Yeah. Yeah. For sure we will nominate you as a committer. Or they say, "Yeah, you know that is great what you did, but those are really minimal changes. Can you maybe here we have two issues. Maybe you can work on one of them because there are like more deep code related. And if they again um do not um answer at all, then this meeting for example would be a good place to to bring it up. >> Yeah, that is how I would describe it. Sure, absolutely. And happy to see upcoming contributions from you. Where have you contributed to? >> Yeah, I think it was mostly in the uh PBJ, so protocol buffer Java and then the go. >> Oh, cool. >> The two things that I'm really thinking of, but yeah, it's been at least a few months. Uh kind of got started on a new job just now. >> Ah, cool. Okay. Oh, great. Thank Thank you for doing those contributions. Okay. Um, anything else from anybody here in the call? Good. Then we can stop four minutes early. Thank you all for your time and see you all next week on the next TSC call then. Bye. >> All right. Thank you. Bye. >> Thank you.