CHAOSS Common Metrics Working Group, 8 Jun 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: CHAOSS Common Working Group Meeting June 8 2023

Description

Meeting summary can be found here: https://chaoss.discourse.group/t/common-metrics-working-group-meeting-summary-june-8/165/1

A

Ready uh yep uh hi everyone welcome to uh the June 8th, 2023 common metrics meeting. uh We have a uh actually a rather long agenda today. uh Most of it was pulled from uh the last meeting which we we didn't make it completely through the uh the agenda uh last last meeting. So a lot of new metrics to discuss and consider uh so, uh but we'll start with an action item from uh last week, which was uh make a new document how to create a metric and the uh the action item for that was.

A

uh The nod was going to take a look at this.

B

Can you move my action items a little later because I'm commuting I've done work but I'll be able to like when I reach, to the PC in 10 minutes and then I'll be able to.

A

Will do I'm going to move that to the end, Zen and we'll uh we'll go ahead and jump to uh race action item, which was the uh numetric self-merge rate.

C

You get a badge for that on GitHub.

C

It's called the YOLO badge. You only live once.

D

But anyhow, yeah I, just uh I mean created a doc I think last week, um so I think I got the first section started I mean you should all have like edit rights, I I think I made it public so uh filled out. I think the first three sections question description and objectives: I can edit it so uh yeah. You.

A

D

Give you a go ahead. Sorry.

A

I was gonna say: do we want to take some time and uh edit this together.

E

Yeah I mean maybe Ray just give your overview of it real fast right.

D

And I think like Sean, you were in on the call a couple of weeks ago. I think most everybody else was uh I mean this. The Genesis of this is that uh I mean. Unfortunately, you see this happen like in whether it's like a small, open source project store. There are companies that claim to be open source, but they don't really behave that way they may have like a you know.

D

Apache tour MIT license, but you see like ctOS like submit something in that like five minutes later, it's like it's March uh by the same person um so.

F

D

Mean in in the early days of the project, that's understandable, like if they're only two or three people working on it, you, you can kind of understand it, um but if that's still happening two three years later, I think that's obviously problematic right and then a lot of times.

D

uh It's kind of obvious that the work is being done in private somewhere like a private GitHub repo and they just dump the code and and against marriage right. So obviously, that's not something you want to see um so want to make sure that there are, if somebody submits a PR, there's actually a culture of people, doing reviews, and- um and uh you know, even if it's like a simple Emoji, we want somebody else's sort of looking.

D

You know looking over their work and- and uh you have like somebody else like doing the actual merge like a real reviewer, uh because I mean this is like something that you can Implement, whether it's in gitlab or GitHub. You can just disallow like self-emerges right or not allow mergers at all unless there's a review.

D

um So um so you know over a period of time you want to see like has there been a decrease in self-emerge, for example, to see if the Project's actually starting to mature and and growing um in a right way so uh yeah? So that's sort of the high level overview, um I, think I covered most of what's in the description and I. Think uh the people who will be interested in this is I mean particularly Community managers. If you want to make sure that Community is, is maturing in in the right direction.

D

They'll be interested in seeing this and and whether it's potential users or somebody that's looking for a new community to contribute to uh contribute to. You want to make sure that there is a good culture of reviews and and good hygiene behind the projects as if, if there isn't a good uh track record of that being done, then why would you use the software or join the community.

C

Yeah I I I agree with that. I've I've done it sometimes in myself, but I do it less and less.

B

G

Important um for for companies or osbos as they um you know, look at what open source projects they're going to incorporate into their products or infrastructure.

B

G

Understanding that this is happening would be super important, I think.

F

D

I mean there could be some exceptions, like somebody found a quick typo on on dogs, I mean, maybe you can make an exception for that, but even that, like how difficult is it to ask your colleague to merge your PR right? I mean it can't be that hard? So if you want to be absolutely curious about it, you shouldn't like allow it, but you could certainly make exceptions as as needed right so.

C

Yeah yeah, we only. We only do it when something slips through our testing process and doesn't work, but.

G

I think it's pretty rare exception.

C

G

Your rate is going to be really low right.

C

Yeah exactly almost.

G

None of them unless you're doing it on a regular basis, right.

C

Yeah but like in the early days of auger, she has, we were doing all the time.

D

Right I mean so hopefully you'll be able to see that, like the early days of auger I'm making this up, it was 55, but last two years, yeah yeah.

F

C

D

Year, it's been like less than two percent and obviously you're seeing the trend in the right door, you're trending in the right direction right so.

C

E

So I will I. I will say this. We talked a little bit about the name of the metric last time. If you recall that yeah, when the name came up just as a like a data point, Sean knew immediately what it was.

C

But I'm, not the I, don't think I'm the no I'm, not the typical newcomer but I, don't think I'm unusual in open source, but.

E

That's to me that was a good indicator that.

C

E

C

What it was right away well, GitHub gives you a badge for it, but it's kind of an ironic badge right.

F

C

Called yellow I think I said: yeah yeah.

E

And I and I do think this came up last time too it I'm trying to think if there's any other metrics like this one definitely has a negative connotation like definitely I, don't know that we really have any others, Kevin or Elizabeth.

C

Think of any other elephant, Factor bus factor I think those have negative connotations in the same way that self-made does.

A

Now, uh in this one we're we're actually we're measuring an action that we don't want. I think this is actually the only I think it is actually the only chaos metric where you're measuring an action that is undesirable.

A

uh But I think that's fine, I, I, agree, I think the self-merge rate. Everyone knows what that is, uh even though there's a negative connotation to it. The negative connotation is because of what we're measuring and not necessarily what uh the name of the metric I.

C

I think um both GitHub and gitlab um make a we'll make a note of in the in the logs if you're the same person that opened it like it's easy data to get.

E

So do you, could you try to get it with agar Sean, not like right now, but.

C

Is it something we we have the data that would be necessary to answer this question, because we know the creator of the pull request in their case, and we know um the person who merged it and that's that's actually, um even in the commit log there's a distinction between uh commit committer and author, so the committer is the person who merged it.

C

And the author is the person who wrote it and when they're the same person in the commit log, you can see it there, as well as in the pull request data, and that goes all the way back to Brian Warner's facade project, which is buried inside of auger. Now.

E

There was a comment from Jen in the chat about yeah, including with our reviews. Yes,.

C

That's the point: I was gonna, make they if, if there's a review recorded, even if there's no text in it, if somebody approves the pull request so but that's a slightly different process, because you could merge it well like on most of the projects that I work on nothing can be merged by anyone. Unless it's been reviewed.

C

So I think that might be a different metric. But it's very very close to what this one's trying to get at.

E

What do you think of the title change that I just put in there based on that kind of it? We have self-merge without review.

A

Are we interested in both points there? Do we want to know the cell merge rate and the self merge mate right without review, or are we just interested in the one.

C

You could call it a ratio of merges with and without reviews, if, if you wanted to neutralize the title a little bit.

G

I just think the the without review would be a filter, I think some people, some people, would care about that and I think other people wouldn't I mean some people just don't want um the person merging their own pull requests, even if somebody else has done a review um because it's not great practice. uh Definitely if they're without reviews- that's that's even worse, um but I'm, not sure. If everyone cares about that or not.

H

I think it would also be applicable to look at the lines of code changed I think you mentioned that earlier Ray, but if it's just a typo like maybe that would maybe that's another filter, I guess is lines of code change. So if there's one tiny change, then it might, you might want to filter that stuff out. You might want to only look at those.

E

um What character change yeah.

H

I think we have that as a metric right lines of code change.

C

Yeah we have lines of code um files, changed, um I, think files change might be a filter on pull requests.

E

Then do you think that would address your comment if we included the self-emerge without review as a filter, yeah.

I

I think that the only reason I brought it up is because, when I looked at, this I immediately started arguing with it like well I had people review it, that's what I'm supposed to do. So, that's the only reason. Okay.

D

Right on I mean isn't lines of code like somewhat it's a little difficult one, because if somebody changed a key variable in one line, that's a big deal right. I mean that could be a big deal depending on the code, and that needs to be really discussed amongst a lot of other developers. So.

D

I wonder if there's something besides like lines of code, yeah.

C

Lines of code is something that, if you count it it it's going to be. Oh first of all, it doesn't really, as you said, right account, for what damage could potentially be done. I mean changing. One line can ruin everything.

C

um I think the metric also encourages people to use more lines of code um to get more credit right.

E

So I just put in the chat that I still think it's a good filter. It just.

I

E

Know kind of it doesn't answer your question to your point right, but it yeah I told you a little bit more about it like if I and maybe where to look.

D

Yeah no I mean, if you need to view it in the right context, right so right.

E

D

Yeah I mean the other thing. I was thinking. We were talking about dogs like some projects, have docks in a separate like folder Repository.

D

So if you're managing that project, maybe in Doc's retail, you allow self merges or simple typo fixes, but on the code like you know, you don't but I don't know if we need to specifically address it. Yeah file type changes that that's a good one.

D

E

When I was asking, if auger could do this, it was with respect visualizations tools yeah that trick, because we're.

C

Trying to so we can. We could build that um because then make it relatively easily if we are clearly bounding this under the merge request umbrella, so we're only looking at merge requests we're not looking at commits or other things, so yeah.

E

um And the reviews are we're trying to get away from just like listing. You know some of the metrics or like tools providing the metric, we're just like we're more lab. It's just super vague in general yeah. So read a visual that.

C

Would be cool all right. um I will add that to my list.

E

I, don't know how you know I just say: can you just do that that.

C

E

Seven hours of work sure.

C

Well, I mean the way I look at this in all cases is everything that we build for somebody. Somebody else needs like so, and I do have some folks, this Summer that could work on that.

F

E

C

E

E

Ray I've been kind of making edits throughout no.

F

E

D

D

So I forget: what kind of information do we add into the implementation section.

E

Well, that's where the kind of what I was asking Sean about.

F

E

Like here's kind of one of them, look like okay, it's usually pretty broad. We used to actually provide in the olden days like SQL statements, yeah.

C

There were Jupiter notebooks.

E

For a long time, great idea, so it's become a lot more vague. Okay.

E

So if there's anything that you're working on Ray say like with insights, you know what I mean yeah.

F

E

This kind of stuff that that can show up in here as well.

F

E

And then her like data collection strategies in there as well, that's often used for things that are like more qualitative in nature, so like here, are some surveys or interview questions that you could ask.

D

Right, yeah I, don't know if it fits in here or not like.

D

How do we distinguish like because I think I mentioned it just looking at non-bots doing reviews because, like a boss, can provide like a simple like review type of comments right if you're missing something, but from non-bots like do we like? How do we I guess it's part like implementation is part data collection? What do we regard as a valid review like there was a reviewer sort of doing a thumbs up? Is that is that sufficient or do they need to provide like a specific comments via text a.

C

Lot of reviews say: lgtm yeah.

F

D

Don't know I mean which, which is which is fine like if it's a simple change and it's all that's needed second pair of eyes right.

C

Yeah yeah and a lot of times, I see people making, GitHub and gitlab are both nice and they let you make um wine by line comments that get included in the review right like. Why did you do that? Maybe you should change it to this all right and that's actually extremely helpful to the developer right, because it's all in context, but the actual like written part at the top might be LG GM, except for what I said.

A

The level of measurement that we're at is, at the change request level right. We're measuring the number of change requests that emerged without review, or are we looking at commits.

C

I, don't think we should look at commits I, think I think it commits effectively are just um a more a more granular look at. What's in the pull request. That would be my view. I think the colonel team would disagree with me. Okay, so.

A

The so for the the.

C

B

A

C

Ahead, like commits versus pull requests, I think pull requests gives us the right level of detail.

G

I think we were talking about self-merge, I, think pull requests.

C

G

That's the way to look at it: okay,.

A

That's what I was thinking as well, so the for the description of this metric. This is very specifically the number or the ratio of change requests that are merged without review.

G

C

Yeah- and there has like I, said on most repositories these days there has to be a review to go into Main, um I, won't, say Alex, most projects that have traction and users and contributors launched.

A

What's the what's that term for the contributor, do we have a? Is there a chaos term for the person that submits a a change request, contributor, I, think.

C

F

Too I don't know, though,.

D

Do we have the term author or.

A

Author, thank you yeah.

D

A

That I think that's what we've used in the past yeah, okay,.

I

E

Maybe Ray you want to take some of these comments and try to tighten this up a little bit.

D

F

All right cool, but.

E

Now you look like you're back.

J

Yes, I am back. My bus got deleted, so I was like normally I reach here, but 10 or 5 mags today, I mean so.

A

Okay, shall we go ahead and uh move on to yeah, okay uh Bernard did you want to uh did.

J

You want to talk about your your action item yeah, so there were two things: one was updated, template uh metric template which I updated it and I guess Matt, you already merged it. So it's good. The template is good.

J

uh As far as merging this uh uh release and revise metric together, I have done it, but I have not created a PR for this. The only hitch I was that uh the proposal was to move it to the contributor folder rather than a resource. Folder I was thinking on it that, whether uh any newcomer who is trying to contribute does it does they need that template or the one who is already familiar and has done some work. Then they need those resources.

J

So it's more of a. Where should we place this particular template once I have merge these two documents together, my proposal was to keep them as the resources rather than uh for a new contributor or uh thing.

A

uh I, don't think it would go in the resources. I think uh like the a template would go in the resource, but a how-to document would go into the uh probably the how to contribute folder.

J

So so these two documents that needs to be merged together are more like checklist that we developed.

A

Yeah I think I think we I think we need to have a basically a how to contribute folder. That would uh that would have that.

A

Okay, because this would be a and the the name of this document would be how to how to uh create a metric or some such thing. Where would that be Kevin like in the community, repo, okay,.

E

Yeah and then this right here.

A

E

J

So this this is kind of a checklist that, once you create a metric or you revise a metric. These are the things that you have to uh ensure as a quality metric.

J

This is more of a how to get into the chaos rather than particular, resource of a template.

A

Yeah, so these the items that are in the how to contribute folder now, probably some of them need to be moved, and some of them will probably go away.

J

A

uh So the the how to contribute folder should explicitly tell it should explicitly tell the either the newcomer or the or the existing contributor how to do a task right. So the the document that you're creating is it is a checklist, but it's also a it's a road map on. This is how you create a metric, and these are all of the things that are involved so yeah.

B

A

If we're being very explicit in uh in our guidance on how to do these, things, that this document should be should be in the how to contribute, and it should have an explicit name that says something like how to define a metric.

J

A

uh And then the stuff I do realize that the stuff that's in there is uh probably a mismatch of uh of things and some some of it'll be maybe moved to different folders.

J

Yeah, that is where I while I was creating a peer I got I stopped it for a while, because I was looking at it and I felt some mismatch.

E

Actually I, like Kevin I, don't know if you meant that intentionally but like starting every document, name in here with how to yeah that that I mean I. Don't know if you, if you meant that on purpose, but that's a really good idea. I.

A

I did mean that on purpose, okay.

E

Right on, thank you.

F

E

Makes you then look at every one of these documents so just for example, like Community guidelines, like is this a how-to? You know what I mean, because.

F

E

Help I think specify that it's in this folder, okay, you know how to, for example, do a well. We probably don't want that one but like how to do a dco, yeah, yeah.

A

Something like that, how that one that one probably does stay, but we rename it how.

E

To do it yeah, so many of these need to be like.

E

Completely reduced anyway, but yeah I get I like that. I like that idea, okay,.

H

Can we take out that Community guidelines like I feel like that's? What a code of conduct is right.

F

J

Yeah, that just seems so, if, if I, think of in terms of how to be focused, how to be inclusive, how to be respectful that fits in that definition.

H

J

How-To yeah how to be welcoming how to be respectful, how to be collaborative how to be mindful. You know all the how to be fits in this list, how to be focused.

A

I was kind of I was kind of contemplating, maybe moving it into a different folder and uh maybe renaming it to like chaos, Community culture statement or something like that or.

B

H

I mean I could see that maybe a.

E

Little bit or like very specific, like how? Because.

H

Maybe maybe those guidelines are a little bit more nuanced than like a code of conduct, but yeah I think it should be in its own culture kind of thing: I agree with you: Kevin yeah.

A

So for those uh for those those two kind of folders that we've been discussing here, one is the.

F

A

Folder and the other one is the the how to contribute folder, uh so I think they're they're both really important, uh and we we also need to be careful that we don't get them confused right. So the the resources folder provides kind of the the tools and templates for you to do your work, however, the that how to contribute folder, that's the that's the the guide, the the explicit guidance on how to contribute to very specific parts of the projects and not not not in general, but like very specific parts of the project.

A

So how do I? How do I do something on the website? How do I contribute to uh uh how do I get started, contributing to Auger, or something like that, so uh very explicit and very specific in where we're pointing them.

J

Now I got the better idea, so what I'll do is I I'll go through these two folders again and then maybe uh advise the files to these folders. Accordingly,.

J

E

Excuse me, the other folder you're talking about Community.

J

Resources, yes, yeah.

E

Yes, yeah I agree like it's nice having our logos in here.

J

But then there is one third thing uh that also conflicts with this is on on the logos, especially or on the communication, that we have a communication group that defines the logos that defines the slide decks. You know all the media guidelines, so these things are over there also as a repeated.

E

Where are they this.

B

J

E

Well, let's, let's bring them all together would be my suggestion.

J

So so these things will go to the resources.

E

Like resources to me that you can create yeah.

A

The brand style guide's definitely a resource yeah.

E

And then it would just be whatever the other folder was called like Media stuff, okay,.

J

J

So uh I don't know uh you move the folders around, should I create a PR as we were discussing first or should I just move the folders around and settle it down and bring it to the community.

E

Create a PR and merger yourself.

B

E

E

um Yeah I mean just go ahead and create a PR just to move it. Okay, okay, that.

J

Makes a lot of sense, because that will actually get rid of nicely a.

E

Whole folder, okay, great.

H

Okay, quick question for you Kevin. So when we're moving these things around.

F

H

Going to need to make the uh parallel changes on the website right to remap kind of everything, correct.

F

J

Yeah- and that brings my another point- is like I created a Excel sheet for the knowledge base to map these things where I've placed existing structure and the revised one. uh Maybe I can share that link and then we can finalize it. Thank you.

F

That's the biggest.

A

Do we have a uh so this work had a has a meeting assigned to it correct yes, when is when is that? Did we miss one or.

J

Did you buy this one? We missed the like in last one uh so yeah when.

A

Is the next one.

E

Next week, I think yes like on Wednesday, maybe Wednesday.

J

Or maybe we finalize it over there and then I start moving the changes or.

E

Yeah we can do that, but this is a nice conversation here as well, though. Okay, okay,.

A

F

Think one of the one of.

A

The high level things we wanted to talk about with that was uh uh which high level folders We need.

F

A

Right which which of them can go away right, uh which so, which high level folders We need uh and I know like the uh like I, don't know if mentorship programs is, is a high level. Folder I don't know if local chapters is a high level. Folder we've already kind of talked that that media outreach the stuff that's in there. It looks like it's being moved into the resources.

J

A

What's the newsletter MD in in that or the Outreach, what is what is that.

E

It's more like info about the newsletter. Okay.

A

So I would maybe we edit that to be a how-to, how to create the newsletter document, and maybe that one goes into the how to contribute this.

E

Is how to set up a chaoscon.

J

A

Right, yeah yeah so rename, so we rename those how to how.

E

To do a chaos cast okay,.

E

How to run a chaos meeting.

A

Oh I need to look at that.

A

B

A

And this one is actually a resource.

B

J

Yes, so this is what I have been facing when I was reviewing all these things.

E

This is helpful, though, for me the conversation, but then it also makes me think, like we um under resources, like templates like we, oh, so here is the slide deck just making sure we have all of like our actual resources that people could use.

H

Yeah isn't that stuff in Google and the Google Drive yeah.

F

Yeah, so would it be here also or I.

J

Think what we've.

F

Had oh, go ahead, yeah.

J

I was suggesting like we can, keep it in the Google Doc and just point a permanent link to the here, so that they can grab it from there, because it's a slide deck.

A

Yeah I was gonna, I was gonna, suggest the same thing so just create a create a markdown file that points to the uh to the drive where that stuff is at I. Think that's important for the uh like. This logos.

F

A

E

A

F

E

So still keep the Google Drive.

A

Yeah yeah github's not a great place to store uh that.

C

Kind of stuff images- and it's.

A

More complicated yeah barrier.

C

To entry is higher.

I

A

So then we want to do something similar with the the logos and images image folders as well.

C

B

C

About like Jen is a comment about how to be a good Community member.

I

C

F

E

Have do we Kevin Elizabeth? Do we have the.

E

Okay, so they're, not here anymore, remember how we used to have like the Media stuff.

F

E

A

uh No, that is not here: okay,.

E

Great I mean that's fine, because I was just gonna say. If we have it here, then we probably don't want to like.

A

Help it's that stuff is supposed to be in the uh in the knowledge base, so it was left. It was intentionally left off the uh gotcha holder, yeah.

E

Just double checking, okay, cool and then via the knowledge base. It would take you essentially to here It, ultimately get you to the GitHub folder. Is that correct?

E

The so like? Let's say, I came here and I was looking for the logos.

A

Oh yeah yeah, so you go to.

J

Resource Community yeah.

A

Community knowledge base yep and then you go to the resource, yeah Community Resources. So when you click on Community Resources, you would have you. Would you don't have templates here? You would actually.

J

Yeah, that's all.

A

That it's just all the resources would be right here. So you'd have a yes, a page that would be slide. Deck or chaos slide deck.

A

When you click on that page it'll point you to that slide deck and in the future, maybe we have multiple side Decks that are used for different purposes, so that page can point to three or four different slide. Decks that people may want to use. Okay makes sense. Thank you.

A

Okay, we are almost out of time, so I will.

B

A

H

A

Is there anything that we need to talk about today.

B

J

Just one thing that we can add on the I have shared a link where I've created the current structure of the knowledge base and the proposed that I'm experimenting it okay. Should we keep it here or move it somewhere uh yeah, so current structure tab is there which shows the existing structure of the knowledge base and the proposed where we make those changes and then move the files accordingly, this.

A

Is where you're moving this.

J

Is where the current structure is with the website link and the GitHub link right.

F

J

Pointing where this page is coming from and the proposes one is the one that we agreed upon and then I can move all the files accordingly. This is great, so proposed one is not yet final. I need a consent of uh Community, whether okay, this is the one. How we want it, then I can start moving the files accordingly. I think this discussion.

E

Will help a lot foreign structure? Yes,.

A

Yeah I think for the uh the next meeting. That's coming up. That's coming up this week. It's.

E

Next week next week, next.

J

E

A

Plan was to the plan was to talk through this structure. So uh banad had the action item of uh putting this together in this way, and then uh kind of the general action item for others was to kind of go and look at a few other uh open source projects and kind of see see what high level uh folders and headings they use in their knowledge bases and in their Community handbooks, uh to see. If there's uh something we can copy or bring in.

I

E

I like this, because this, like and I, think based on the conversation today, that should help a lot in terms of and and I'm I'm with Kevin. Like you know, things like that, like.

E

Or some of the things that might be in here, I'm, just picking things at random, but like remove as well like err on the side of class I always want.

A

And, uh and actually looking at this now, I am remembering that in that last meeting, where we were all together discussing this, we had decided we did want to have the community initiatives, the working groups and the local chapters folder, and the reason we wanted to have those three folders is because it aligns with that doc. uh The governance.

E

Document that was created so.

A

Yes, okay, uh so keeping keeping local chapters as a folder is uh is desirable. uh Yes, keeping software projects as a folder I believe is, is desirable as well. uh We just we may want to be. We want to make sure the language around those folders matches. What's in the governance document, though, but.

E

Like okay, that's fair and then maybe in this case kind of following like this, maybe we could just have a single document about local chapters, for example, yeah.

A

Yeah, we could do that. You.

E

Know? Yes, here's our chapters and here's.

J

This was more like uh in the governance document. We have a main thing: okay, like we have a local chapter, but more details go to this file. That's.

E

Fine yep but I'm, saying two markdown files. We could just have one that describes the entire right.

F

Yeah, where do would you find then the information about those chapters.

J

F

J

If you want to look at this at the same Excel sheet, if you go to the current structure tab, you have the website link and you have the GitHub link. Also so local chapters, chaos, Africa chaos, Asia the website link and the GitHub link. Is there.

F

So that's the link to the information, yes, that there won't be a page on their own, just a link for.

J

Each yeah there is a page of their own on the website and that link is I, have I've wanted in the access sheet for the restructuring. So.

A

These Pages do actually they need more information, so this is just uh it's. Basically, the starter information.

F

E

B

This is something I could ask.

E

You know how, like we have folks that are gonna work, some stuff in Latin.

D

America in.

E

The Balkans like this is something that I can ask them to take a look at because it would be nice is that if they created kind of consistent, narratives or a consistent document that described who the chapters are, um what the efforts are in the local chapters. You.

F

Know what I mean.

E

How they connect with.

F

Chaos um project tab, template for those communities to start creating yep, yep, okay,.

A

uh Well, I think we've run out of time, uh so I encourage if I encourage anyone who would like to continue having the conversation about the the community handbook and these documents from the knowledge base to uh come to the uh uh that knowledge base, meeting which is going to be on June uh 14th, uh and that is uh that meeting is dedicated to that is a working meeting. So it is dedicated to actually kind of editing and uh and working on the community handbook s.

A

uh Do we have any action items for the uh for the self merge rate uh metric? Did we uh Ray was gonna watch item Ray, take a peek at it again, yeah.

F

D

I think I made a few additional edits and accepted positive suggestions and changes. Let me know if you need anything else.

A

Okay, so we'll we'll pull that one back in uh for next week. uh Thank you all for coming uh and please uh feel free to uh add anything to the agenda for next week. If, uh if it comes to mind all.

F

Right thanks, everybody.

E

Thank you. Thank you.

F