Cloud Native Computing Foundation TAG Observability, 30 May 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: 2023-05-30 WG: Query Standardization Meeting

Description

Agenda

* Introductions
* Summary of the WG Charter and goals
* Select initial DSLs to research
* Review and contribute to DSL Designer In-Depth Interview questions. (stub PR)
* Discuss End User survey questions. (stub PR)
* Review and contribute to the use cases documentation schema. (stub PR)
* Review and contribute to the telemetry model schemas. (stub PR)
* Review and contribute to the DSL documentation schema. (stub PR)

Slides
https://docs.google.com/presentation/d/1kmIR5TKuHIDGMphYhFlZKHozLiQjTb8BaUFa_POCLMI/edit#slide=id.g72e417d42c_27_0

Tweet Announcement:
https://twitter.com/alolita/status/1663577162451128321

Notes:

* YAML format seems ok to proceed with for documentation
* Look at adding validation for the schema for PRs to help folks
* Break the schema review due dates up so that we review the telemetry schema first then the use case and DSL schemas next.
* Extend due dates to June 30th as folks are pretty busy.
* Chat on Slack for primary communication in #obs-query-standard-wg. Major milestones/announcements in other slack channels and email.

A

Oliver edelmann: hi.

B

Chris larsen: hello!: how are you oliver edelmann: and you?

B

chris larsen:, I'm awake. chris larsen:, so it's a good start.

B

Chris larsen: I'm going to try to share a screen, and I'll see?.

B

Chris larsen:, that's true.. It's.

B

Chris larsen: see. does my audio still work?

B

oliver edelmann: yes. chris larsen: oh, great. okay.

C

Henrik rexed: no.

D

Oliver edelmann: hello. cool.

B

Chris larsen: hello. chris larsen: a. a. j. henrik.

A

Vijay samuel: so.

B

Chris larsen: go ahead. sign on in the or sign in on the.

B

Chris larsen: meeting notes., if you', not mine.,.

B

Chris larsen:, everybody should have access.

A

Vijay samuel: in the interest of time.. Maybe we can get started. thank you., everyone for.

A

Vijay samuel: joining this kick off session for the query, standardization working group, which is part of tag observability.. My name is julie samuel.. I am the observability architect.

A

Vijay samuel: what ebay? vijay samuel: and we also have. chris larson,, who is part of the ability at netflix.

A

Vijay samuel: and has also worked on the.

A

Vijay samuel: so today. we'll talk through what?. What's the logistic we'll talk through what this working group entails?.

A

Vijay samuel: what we have planned: goals,, non goals and then, briefly, talk about how we want to go about.

A

Vijay samuel: doing all the analysis, documentation, and then see if we.

A

Vijay samuel:, we can come up with the recommendations., so the tag observability co-chairs are not here yet,, but they are all in the chamma from apple m matt,, young from apple again, and richard hartman, from grafana.

A

Vijay samuel:, so the.

A

Vijay samuel:: can you go back to the previous slide?

A

vijay samuel: yeah.? So we have the minutes and the planning doc in the in the slides.. Please feel free to go in and add your names as part of the attendees, but the cadence that we are going for starting from this week on.

A

Vijay samuel: is to be able to meet the second and 4 3.

A

Vijay samuel: specific to 9 am., which are the weeks that tag observability, do not meet.

A

Vijay samuel: and the first and third week we intend to meet the at in the a back friendly, time., 9, pm, psd., so we'll meet every week.

A

Vijay samuel: on tuesdays, vijay samuel:, so that we can first go through the planning aspects of it, and then start making progress on things that we want to achieve.

A

Vijay samuel: next next week. yeah., vijay samuel:, so the goals of vijay samuel:. This working group are threefold: to research, analyze and to recommend.. We wanna gather as many observable use cases as possible. do research on all existing query, languages and telemetry models that are there. and as part of this, we wanna do 2 sets of interviews.. The first one is.

A

Vijay samuel: cater towards the creators.. This can be either open source projects or popular commercial products that are out there, which have a very well thought of languages, talk to their creators or the belief. engineers of the of those initiatives understand what prompted their thought process.

A

Vijay samuel: and also talk to vijay samuel:, a variety of end users that are there depending on size and complexity of installations. Various and users may have different needs that are there., so we want to.

A

Vijay samuel: do a survey, and vijay samuel: collect all the information we can from end users as well. Once we have all these surveys., we wanna build out a rubric to evaluate.

A

Vijay samuel:, each and every language. and how it suits the end user needs that were collected as well.

A

Vijay samuel: so adoption. how friendly the tool is!.

A

Vijay samuel: does it have any cross, telemetry capabilities that exist so on and so forth. and finally,. We want to see if we are at a place where we can recommend models., semantics,, schemas, any api and then finally, syntax.

A

Vijay samuel:, so these are goals, and as far as things that we don't intend to.

A

Vijay samuel: do as part of this working group.. There will be no formal standard that we intend to put out, because,. It's been rightly pointed out that we'll have to have implemented the prototypes or actual first get implementations that we need to put into the hands of end users and.

A

Vijay samuel: project product owners like to fear, do a a round of testing and validation to make sure that a formal standard can actually be put out.

A

Vijay samuel: and we don't intend to have any implementation per se. We intend to recommend that any future working group or project can feel free to pick up the recommendations, and then kick off a specific initiative outside of outside of the scope of this working.

A

Vijay samuel: yes. so, chris,, you wanna, take it from here.

B

Chris larsen: sure. hi!, my name is chris larson.. I work at netflix and we want to go over here kind of just at the top level.

B

Chris larsen:, what we're asking for help with,, because we're going to be doing a ton of research.. So we need a lot of folks to jump in and try to help out here.. So.

B

Chris larsen: one of the first things we'll do today. I'll copy and paste and share the talk about what initial dsl's we can go after we have some listed in the query, dot or the charter document?.

B

Chris larsen:, we can discuss on the call pretty quickly, which ones we think we should target.. I think we have a pretty good idea. and then next up, we've started kind of listing some designer interview, questions. carter's. Actually, there had suggested that as a good idea.

B

Chris larsen: to define a well document that includes all the questions when we want to designers the answer, and then kind of share that with the different groups, and then the designers,. And then the designers can review it, and then you come back,. And then we could kind of do. A quick interview. after folks have folded out and get any clarifying questions answered that we need.

B

Chris larsen:, we also want to do a survey end user survey.. So we want to get some questions that will work for that.

B

Chris larsen: and then we want to talk about documentation of the dsls and the use cases and whatnot.

B

Chris larsen: review the schemas for all the use cases. Model dsl, and that, of course, have folks start helping out with that.

B

Chris larsen:, so the initial dsl's. of course.

B

Chris larsen: google just logging in one along, back in.

B

Chris larsen: sign in.

B

Chris larsen: I'm going to share a different tab.. Can everybody hear me? okay? still.

B

Chris larsen: hope.

D

B

Chris larsen: awesome.

B

chris larsen:, and when we scroll down here, this isn't,, we can modify this and put it in order,. So we have. prom. ql, of course,, is the.

B

Chris larsen: most popular language in the metric space with prometheus., so that's probably at the top.. Anybody have objections to working on that one.

B

Chris larsen:, including it.

D

Alolita sharma: no,, I think that's a great start, chris,, because since it's a well-defined and you know well used language., so therefore.

D

Alolita sharma:, it's a good good start. Now.. Was there a specific order that you.

D

Alolita sharma:, given that this list is not in alphabetical order?, was there a specific order that you had itemized here.

B

Chris larsen: not yet., that's kind of what I wanted to to check with everybody here. on the call to see if.

B

Chris larsen:, there are any changes that we should make.. I know we have folks from light stuff, and dino trace here,, so we can bump those to the top.

B

Alolita sharma: I think, though, that.

D

Alolita sharma: I mean we could do that., but also,. Would it be worth thinking about how we could take some of the ad hoc, you know. popular standard languages, first, and then.

D

Alolita sharma: go into.

D

Alolita sharma: a list accordingly, or or I mean,, I'm just thinking about in terms of just you know, maintaining momentum as well as.

D

Alolita sharma: you know,, trying to kind of evaluate, based on.

D

Alolita sharma: popular languages first and then going into vendor specific languages. and again, this,, I'm just thinking out: loud, yeah, no,, that's a good point,, and I know that.

B

Alolita sharma: is pretty well used.. Anybody else have,, I mean, elastic. ql, might be.

B

Chris larsen:, let's see where that I have.

D

Alolita sharma: might be another very popular language.

B

Chris larsen: right?.

C

Alolita sharma: yeah,, I I I was initially thinking that we were going to do to list like it, and sort of eventually of the existing language,, even if it's popular or not., so we can understand the possible, what?. What is actually possible, as of now.

C

Alolita sharma: so then, so then,. It will allow us to to match the right standard.

C

Alolita sharma:, because if we focus on the on from ql, we'll limit for 2 on the on metrics.

D

Alolita sharma: again.. I think this was chris.. You did do an attempt of kind of capturing, at least as many as we were.

D

Alolita sharma: familiar with that initial initial time. but, hendrik,. If you see any that are missing again,, we can discontinue to add right.

C

Henrik rexed: I. I had a discussion with the folks from victoria metrics, because they also have their own language.. I think it would be great that every vendor is describing at least how they are.

C

Henrik rexed: the data. so then, we at this we have a.

C

Henrik rexed: a significant list of way of querying data.

D

Alolita sharma:, yeah. and- and I think that what I mean again, this is just my take. here- is that first taking the languages which are non vendor specific or more project specific. and then looking at vendors, specific implementations, because the objective is.

D

Alolita sharma: not really,, to. alolita sharma:, you know, focus in on vendor specific implementations,, but rather that you know, from the ad hoc standards that have developed from the open source. Projects. then, you know, kind of going towards more vendors,, specific languages, and then looking at perhaps a standard.

D

Alolita sharma:, based on that vijay and chris,. What do you guys think?.

B

Chris larsen: yeah,, I think a lot of the.

B

Alolita sharma: popular languages are kind of tied into., then there's someone they start open source and flux. In one great, I mean again,. Obviously, we've been lending to it very soon., but all, all,. All my thinking was that it's like,, if we at least start from the.

D

Alolita sharma: project, specific alolita sharma: languages that have emerged right,, which are again cross vendor.

D

Alolita sharma: and then move towards when the specific languages, then that might give us.

E

Vijay samuel: and I think, like the way that the list is moving towards. The talk is more of like folks, who are already.

A

Vijay samuel: having some awareness, who are willing to contribute those., so I think like,, let's knock those off first, and then identify people whom we can get help from the latter.. I know if you for your folks from gravon., I have participated in this document, and they should be able to help with rescue and lock your.

A

Vijay samuel: and so anything that we can get help immediately. like,. If I I think it's okay to make progress on those and then keep collecting stuff off of them.

D

Alolita sharma: okay,, I mean a. a again,. I think we'll lend it the same.

D

Alolita sharma: same conclusions. nonetheless,, it's like,, again,, action?, totally.,.

B

Chris larsen: yeah., so any other ql's that we should add. and, of course we can add more as we go along.

B

Chris larsen:, I did want to put in somebody. You mentioned the.

D

Alolita sharma: elastic. ql,, yeah., alolita sharma:, you know.

D

alolita sharma: and we have victorian metrics covered. hendrik.. Is there anything else that you're seeing which is not covered?.

A

Vijay samuel: we should,, probably at cql. as well,, because a bunch of people who are using it for a globally these days.

A

Alolita sharma: yeah.

B

Chris larsen: that in here. great.

B

Chris larsen: alright., then let's switch back here.

B

Chris larsen: so back to carter's idea about the, you know, designer interview, questions.

B

Chris larsen:, we have some folks already identified from data docs, blanc, dime choice, of course, and.

B

Chris larsen: light step as well as brian here with asl. I can do open tsv. of course. as far as language, designers.

B

Chris larsen:, then we started the or I started document there with some questions, though, just to stub it out,. I could use help, or we could all use, help around questions regarding tracing and logging,, particularly.

B

Chris larsen: those time time, series.

B

chris larsen:, that's also a profiling.

B

Chris larsen: and potentially events as well., we'll try to add some,, but we want to get those going. there's a pr link in here.. We want to make sure to capture all of the implicit and kind of non-obvious.

B

Chris larsen: design decisions that went into the language that, even though there may be documents around a specific dsl., we want to get behind the scenes and figure out why choices were made and.

B

Chris larsen: how we can understand, and better come up with something that is able to standardize across the industry.. So what we're asking for is folks to go to the pr. link, drop comments on that,. Add questions that you think are relevant.

B

Chris larsen: and review any of the existing questions. chop them off a fixed text, whatever you like, and we'd like to try to have that done by june, thirteenth here., so a couple of weeks, and then start sharing those out across the.

B

Chris larsen: designers and vendors.

D

Alolita sharma: that that's a good good good, start., so, chris,.

D

Alolita sharma:: are we going to do that in a dock which is attached to this pr, or just on markdown.

D

Alolita sharma:, just just on the mark, down. right?,.

B

Chris larsen: well, then, the same thing pretty much with end user survey questions we had a brain dump,, a quick one that I put in the pr. there.

B

Chris larsen:, we want to send out some questions that I know. this one gets a little iffy, because we don't want vendor specific.. We don't want to knock any vendors or anything like that or particularly technologies,, but we do kind of want to glean some insights from the users.

B

Chris larsen: about what chris larsen: features, they like, about various query, languages, and then also what they are looking for,, what their design desire?.

B

Chris larsen:, so we want some questions or kind of just trying to be fairly neutral but accurate about what dsl's are doing correctly, and what pain points they're facing and what they would like to see in the future.

B

Chris larsen: so again, same format: here, link, we'd like to have this one done by june 27.

B

Chris larsen: that date could be a little functionable,, but I think it will take a little more time and then follow up work on that. one is,. Of course, we have to. we'll be able to go through the cn., cf. pr. department, to send out a survey.

B

Chris larsen: and we'll have to work with them to edit questions., make sure it follows c and cf. guidelines, and as proper and whatnot.

B

Chris larsen: so after that goes out, and we get some respondents, we'd like to schedule some end user listening sessions as well. vj,, and I talked about that a while back.

B

Chris larsen: and kind of use some of these questions.. We don't necessarily have to wait for the results., but once we have this question set,, then we could do some end-user listening, sessions.

B

Chris larsen: and then once we get the results, we can analyze and publish.

B

Chris larsen: see questions on that one.

D

Alolita sharma: is that too short a period? chris?.

B

Chris larsen:, I don't know., we could extend it.

D

Alolita sharma:, or maybe we can do multiple iterations.. That might be better.

D

Alolita sharma: because we can. yeah,, we could turn through., you know what we get and then.

D

Alolita sharma: iterate on it again.

B

Chris larsen: and yeah, all of this depends, of course, on folks participating.. So if we get some questions,, if we don't.

B

Chris larsen: have much activity on the pr., then.

B

Chris larsen:, we can extend the deadline and poke more people.

B

Chris larsen: all right, then. chris larsen: in the pr. also, I've provided examples. brian helped me with the atlas query, language of documenting query, languages, use cases, and I kind of started on some of the models as well.. So for this I picked the yaml in get, because we can put it in the tag. observability get repo, share, it., it's open source.. Anybody can contribute, and we also get the benefits of attribution.

B

Chris larsen: for the folks who have contributed. it's easy to.

B

Chris larsen: just pop open a text editor and edit a yaml file,. Even though there are some space issues, there.

B

Chris larsen: and it's can be well structured. and we can have a fairly well-defined schema that we can then use to create a website or an interactive database in the future.

B

Chris larsen:, so I did want folks on the call.. If you have any thoughts as to a better type of, or a means of capturing this kind of data., just shout it out, or if you have any concerns with the yaml and get nothing.

B

Chris larsen: any other ideas, folks, have.

D

Alolita sharma: chris,. Do you have an example of what this would look like, this?, scheme!.

B

Chris larsen:, let me pull up chris larsen: here here in this tab.

B

Chris larsen: switch over pick one of these.

B

chris larsen:, so let's say, for this atlas stack language.. I've put also.

B

Chris larsen: in the chris larsen: readmes and each of these directories within the pr. kind of an overview of the scheme, itself, the fields that are available. and then, for an example,. You can see, it's pretty, basically of a title., the abbreviation for language, copyright, license,, open source paradigms.

B

Chris larsen: and then the supported, met or models, telemetry models., and I have a lot of call outs here.. These are things that we can populate.

B

Chris larsen:, with chris larsen:, implicit, behavior or non-obvious behavior for a dsl as well as eventually the results of designer interview, questions.

B

Chris larsen: and then just lots of description.. I wanted to support mark down in all these fields,, so we could drive a website with it. and then I was thinking for the actual operators or grammars,. We can start breaking out.

B

Chris larsen: into individual terms, with descriptions and what not. there.

B

Chris larsen: and then, for use cases.

B

Chris larsen:, I was thinking,, we pick a a use case., so like, for example, grouping in and aggregating data in metrics is a very common use. Case. almost everybody does it.

B

Chris larsen:, so we have a basic description,, a type of telemetry. That's inputting.

B

Chris larsen: or coming into the use case, the type of outputs what we use it for alerting, visualization descriptions there and then kind of create examples in the various languages that we're going to be analyzing..

B

Chris larsen: and then there's a similar one for the telemetry model.

B

Chris larsen:, so does anybody have suggestions, concerns comments.

B

Chris larsen:, I think this is a good start., and, chris, I mean to make mods.. We are just going to take a template, and just,. You know, replicate it? right?.

B

Chris larsen: yeah., so my thinking is that we'll get chris larsen:. If everybody's happy, or when folks are satisfied with a format,. We can merge these as examples, and then folks can take the.

B

Chris larsen: copy pasta and start filling them out for different languages, models, and use cases.

F

Brian harrington:, how consistent do you want these to all be? It might be useful to have some sort of validation if you want.

F

Brian harrington: quite a bit of consistency, or need to be able to programmatically analyze these things., but.

B

Chris larsen: right? and that's a good point. We could. I'd like to get a few examples in,, because I think, as folks add.

B

Chris larsen: languages,, they might come up with a few new fields,, and then we could start adding the validation to make sure the schema. is it here?.

B

Chris larsen: forward that we use that as a pr build.

B

Chris larsen: yeah, good point.

B

Chris larsen:, so I'm hoping that folks would chime in with any comments by the thirteenth, just on the overall., I think nobody's complaining about it here,. So it's probably not very.

B

Chris larsen: controversial.

B

Chris larsen: so then, digging down into the individual components,. We have the use case, documentation schema., so I kind of walked over that briefly.. We've got the inputs, outputs, descriptions, examples and links so that pr, link is in this, and.

B

Chris larsen: I'd like to have folks try to chime in on that before june. Twentieth.

B

Chris larsen: and then, in the meantime, of course, folks are free to start populating. The data set issuing prs if they like, as well.

B

Chris larsen: and then same thing with a telemetry documentation. I've got some.. We have the schemas up there for that and the documentation around it,, where we want to capture the various models that the dsls work on,, because some of them are slightly different, eg.

B

Chris larsen: prometheus has a slightly different metrics model than many of the other metrics use cases, period.

B

Chris larsen: databases and processing systems.

B

chris larsen:. There are tons of different profile chris larsen: models out there, a number of different trace models.. So we want to capture the most common ones that are available. There. we'll probably need to start a list of those similar to the dsl list that we have.

B

Chris larsen: and maybe we'll merge that in somewhere as well.

B

Chris larsen: but, ditto,, we want to have the chris larsen: a schema reviewed around the twentieth, and then we'll start populating. that data set.

D

Alolita sharma: chris. The only concern I have. is, are we doing too many threads at the same time.. That is.

D

Alolita sharma:, because I I noticed the due date is overlapping.

D

Alolita sharma:, the sound is schema documentation.

B

Chris larsen: well,, I'm not sure., do you think it might get in the way,, because it's all kind of tied together in a way that the dsl's reference to telemetry and.

B

Chris larsen:, the use cases also reference dsls and telemetry a little bit,, but we could try and nail down telemetry first, and that's the underlying the model. yeah.

B

Chris larsen: and then try to put the.

B

Chris larsen: maybe use cases after that.

D

Alolita sharma: because we want,, I mean, you outline.. We need to do at least 3 areas at the same time.. You know it's like by fear of it.

D

Alolita sharma: a of alolita sharma: a bit too., it's too too much.

B

Chris larsen: yeah,, I can do that. and then, yeah,. That was really it for this kickoff session.. It's just those.

B

Chris larsen: documentation, scheme.

B

Henrik rexed: so I'll update those dates., but does anybody else have thoughts? questions?? I think the thirtieth of june is is a good deadline. for the rest,. I'm not sure,, because I don't know if, for.

C

Henrik rexed:, I mean there's not things coming up.

C

Henrik rexed:, for I mean for everyone., henrik rexed:, so I think if you have 2 tight deadlines, we may not be able to respect them.. I don't. we may maybe more flexible and deadline,. I think.

B

Chris larsen: okay,, that's a good point. yeah,. I can put those in the 30.

B

Chris larsen: yeah. and then there are a lot of conferences coming up: to. yes,, correct.

B

Chris larsen: we'll be going around, too.

D

Alolita sharma:, I mean at least the fall.. There are lots of conferences, right?, so I mean again,. If we want to. for coupon,, especially if you want to, you know. do a session,, then it might be good to achieve at least a couple of these goals and.

D

Alolita sharma: be able to dive deep at a,. You know user group user group session.

E

Chris larsen: yeah, again,, these deadlines were just kind of reviewing the yeah, schemas. and then.

B

Chris larsen: hopefully, folks can start populating that on their own.

B

Chris larsen: yeah, any other thoughts.

B

Chris larsen:, let's see,, did folks fill out great?.

B

Chris larsen:, how about communication.? What does everybody prefer?, email blast to the tag? Channel,, tag,, email, list, or.

B

Chris larsen: direct emails to individuals?.

C

Henrik rexed:, I think slack- is based good.

C

Henrik rexed:, as the emails you can., you can fell into the.

C

Henrik rexed: into the junk jank folder easily., so I think it would be better.

B

Chris larsen: okay., alolita sharma:, we'll definitely populate slide. I'll, probably occasionally send down emails., but we'll do that. yeah,. I mean,, maybe for a major milestones. We should use all channels. but for but slack on a regular basis for every all.

D

Alolita sharma: discussions.

B

Chris larsen:, that sounds good.

D

Alolita sharma: are we, chris? using the same tag, observability channel?, or are we doing a different.

D

Alolita sharma: channel. yeah,. We have an obs query, standard working group, channel., now,, okay,, okay.

B

Chris larsen: I'll add you there.

D

Alolita sharma: yeah,. Can you please?.

B

Alolita sharma: and then,, just so,, folks. and now, vj is going to be on doton's podcast. The open observed.

A

Vijay samuel:, I think it's on the twelfth. alolita sharma: okay,. You have some time. all right?.

B

Chris larsen:, so yeah, that'll be nice. chris larsen: and then I'm just waiting on the ticket.. I filed the jira ticket to get on the community schedule as well., so okay. okay, yeah., I'm sure they'll just one.. It's just. I think things are just picking up this week back again.

A

Vijay samuel: actually,, it's on., it's on the eighth,, the second on the eighth next week. okay.

D

Alolita sharma:, so we can totally use this.. This presentation,, which.

D

Alolita sharma:, you guys put together.

A

Alolita sharma: spreading the world far and wait. yeah,, yeah,, absolutely. and, and we expect henrik and everybody else to do so.. So all good.

E

Chris larsen: and.

B

Chris larsen: and then hopefully, we'll have some more folks join next week as well.

D

Alolita sharma: yes., alolita sharma:, I mean again,. I think they. We should continue to reiterate.

D

Alolita sharma: and just, you know, broadcast,, so that more folks can get involved. also,. I think it might be useful.

D

Alolita sharma: for us to kind of.

D

Alolita sharma: you know, chat on slack and figure out.. You know a list of end users who can actually.

D

Alolita sharma: provide feedback. obviously,. All of us who are here can.

D

Alolita sharma:, but also alolita sharma:, extending out to other end users to be able to provide and get involved. Right.

B

Chris larsen: and I still have more folks to reach out to you, too., but anybody else who has ideas.

D

Alolita sharma: yeah,, totally kristen and me to help you.

B

Chris larsen: okay.

B

Chris larsen: all righty.

D

Alolita sharma: could be did that folks have other questions.

D

Alolita sharma: again. this is this is the group that has been familiar with all the details,, so I can assume that everybody is. it has intimately read through the.

D

Alolita sharma: chatter,, doc, and other. you know, docs, that we've added., but.

D

Alolita sharma:, I think., do you think it might be useful? I mean, obviously,. We will continue to reiterate on the mean tag meeting, also to tag all the meeting., but perhaps you know, also cross.

D

Alolita sharma: cross-sharing across other tags. for anyone who is interested on the slack channels? henrik,. Would you like to.

D

Alolita sharma: volunteer,, or can I volunteer you for just posting on the tags? slack channels?.

D

Alolita sharma: just,, you know, make yeah getting people to be aware. That this work group.-.

C

Alolita sharma: I mean, reaching the the meeting details and all the yeah, exactly. I mean, just the that, you know,. This is the.

D

Alolita sharma: and you were group.. This is what we are working on. and we typically meet on.. You know, these 2 tuesdays every month.. So please join.

D

Alolita sharma: really really appreciate. It., I mean again,, I think just broadcasting it across the tag.

D

Alolita sharma: other tags,, so that folks are aware just on just on slack. I mean.

B

Chris larsen:, that would be great. thank you.

D

Alolita sharma: is there anything else that folks wanted to call out oliver or pramsheu, or to qatar as a victor?.

D

Alolita sharma: anything we are missing here, which you feel we haven't looked at or.

B

Chris larsen: thanks, carter. alolita sharma:, thanks. cover.

D

Alolita sharma: okay, cool.

B

Chris larsen:, if that's good,, then get some time back and.

D

Alolita sharma: thanks everyone.

D

Chris larsen: bye, bye, bye, bye.