Open Telemetry Uncategorized, 9 Oct 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2019-10-09 Monthly Community Meeting

Description

monthly open telemetry community meeting

A

A

A

A

Hello, everybody, hey, hey, hey, well, hey until four or five after so we actually get started.

A

A

B

C

Hello Morgan.

A

Hello, we're just waiting another two minutes before we get started for other people join Morgan.

C

Invite because the calendar invite has a Google meeting.

B

A

B

It doesn't it but Morgan's we're computing. Actually, you know which.

A

I see I'll just delete it twenties in him awesome and.

A

Let me make sure that's fixed for next month's as well.

A

Yeah next months is already fun: okay,.

A

All right, two more minutes before we check this up.

A

Okay, all right: well, everyone I'm your host Morgan, a product manager at Google. This is the monthly open, Salama tree community meeting, where we go over the status of all of these special interest groups and open Salama tree and discuss recent items of note and news document. Our notes documents well, first off these meetings are recorded and the recordings will be posted online. Secondly, the notes document is shared in the community calendar link and that's where we post the agenda and take notes on everything that was discussed during the meeting.

A

I think Ted and I have already filled in some of the items in the notes for today's agenda, but ad thinks the conversation please just.

A

So the first item for today is git er. As you noticed, the main git er chat room for the open. Celebrity community disappeared this morning. We quickly recreated it I reached out to git er they're gonna, try and read all the members who weren't reacted to the new group and they're gonna see if they can capture the old chat history.

A

It appears that someone accidentally deleted the chat room, Gator has a very interesting security model or literally any one of the chat room can just delete the entire chatter, which is definitely not the best they've had a feature request that they said they will improve on that. They have a feature request to fix this, to create an actual admin role, but it's been open for three years so.

D

It's not nearly as important as gifts tell them. Gibson yeah.

A

D

Give support to.

A

The fire for the priority queue anyways.

D

They're gonna try and restore.

A

Things lesson learned: don't press the delete button, no matter who you are and yeah that's the update on Gator next I think Ted. You had a topic on improvement rules. Oh yeah,.

D

So this is instigated for me around trying to get more like a triage role put in and got into a conversation with Sergey and it kind of came back around the current approver role as well. So I kind of wanted to talk about both just a thing. We're noticing.

E

D

Who, including myself and also I, know you know you Morgan Gigi are other people Midori who's, not on this call, who are sort of like we're like project managers and we're often kind of around helping our engineers on the project and there's just some like annoying in ministry OVA around being able to set labels, and things like that that you actually need a tiny amount of github access in order to do it seem kind of annoying to have to go around to every single repo after gets created, think it this access added, so I was requesting that we do.

D

This is just like an org wide setting of being able to have some gardeners or whatever, whatever damina tizen role we want to use to employ. This person is not like in charge of the backlog, but nevertheless to have this access.

D

Your gaze question was that we actually lower the requirements to being an approver and I felt like that might maybe be except for, like you know, repo explosion, if that happens, having a lower requirement for pruners might also be fine. If we want to just say approvers, are anyone that maintainer czar fine with there's already seems to be some language in there about saying approvers can be project managers or tree huggers, but the requirements right now are that you actually have to do a whole bunch of kokum.

D

It's like, like the literal letter of the law, lists how many like reviews and code commits and other things you have to do to become an approver and I was also hearing from some people, maybe like that was just too onerous. Seeing people get rejected for a prove your status. You are code committers and it's just kind of slowing things down.

E

D

What do people think about this issue by.

C

The way, how do you see somebody coming and triaging issues if they don't know about the work? So now it's kind of following, what's really suggested, I, think you have to have a bit of context of what's happening in that ripple. You know to be able to to triage the issues in that vehicle. Correct, I, I,.

D

Think I think that's fair. If one approach is like going to like, say, Python and be like hey everyone, we've got two engineers on Python we'd, also like our engineering manager to have a prove our access, so they can just help, manage the backlog and if people are like yeah sure I think that's like an easy way to do the approval I'm just noting that right now our only option is approver an approver right now just says you. You.

B

D

To actually be a code contributor in terms of the requirements, I think.

C

I think it would be good for people to say other opinions and the governance should meet and in the decide on this, but I I think good, only filing with more input and why it's important, I think it's yeah.

D

I'm Terry, actually just maybe backing away from just triage, errs like people who are working on the very cigs did people feel like getting approvers has been difficult or do you feel like you've had to sort of bend the rules in order to get people to become approvers in any way, or is that, like mostly been been okay for people to kind of make actually hit the requirements.

F

Spline for us it's.

D

Been fine, okay, yeah.

G

I just want to know that became an approver should be very well balanced between being easy, so people will feel welcome and easy to get. At the same time, it should be like structure structure in such a way that there is no I, don't like your kind of reason, not to get an approval approval into the very poor Xury and the same time you shouldn't be able to bring like whole bunch of your friends just like YC around and, like then it'll become unmanageable.

G

So there is like both of requirements to balance and we've been looking at how kubernetes is doing it when we build a membership document, so I mean I. Think this request with the asha role is very interesting, and we need to do something with that and make sure it doesn't like it balance all the requirements very well. Yeah.

D

In the PR thread you mentioned, maybe relaxing the approver requirements or making it more oriented towards, like the sig maintain errs having just like, maybe a more direct, say, I think that would be fine. I do agree with you, though.

D

The more you go that direction the less the easier it becomes to be some form of like favoritism or something, though honestly I feel like the best solution, for that is all of us just trying to be good citizens I, don't know how much you can like legislate people into being good citizens, but if, if we do relax the approver role to the point that we could have project managers taking on that role, assuming you know they can convince the sig that trustworthy, I, think that would solve my problem.

D

But the other act option to consider is like the level of access. We're talking about is fairly small. Assuming we've got people who are involved with the project in a long-term sense, so they're generally considered trustworthy. You know. Could there be? Could that be like an alternate way to implement this? But I would only suggest that if we decide we want to keep some like coding and committed requirements on the approver role, which I don't think is necessarily the wrong way to go.

D

It just wouldn't solve my actual problem of getting like my engineering managers access to be able to do things on behalf of their engineers to.

H

Reiterate a point I made in that thread on issue thread: there's a significant investment from various corporate interests in this project and just bowing to the realities of how engineering management works in most places. It feels like having some sort of easy on ramp for the managers of the engineers whose time is predominantly dedicated to this project. It would be useful. You know, I, understand that we don't want to take power away from maintainer x', but I also feel like.

H

There are cross-cutting concerns that having some dedicated gardening staff so to speak, they can go around and is empowered to create milestones, and you know, help out would be useful, I think it's something we could least try and if it doesn't work out hey we stopped doing it. You know like we can change things, then we can change them back. I tend.

A

To agree like, certainly in our case I, don't know jiggers on the call use our TPM I, think that would be like a status that would work really well for him and I'm sure that's a lie: Stephan Microsoft in other firms and it's an important role. Frankly, like project management.

C

But between between the TPMS who decide what.

A

Is the governance board that.

I

Comes down to rock quarries, isn't one that's a universal way of solving anything.

A

It's it's listen. Everybody who's. Contributing here, wants to actually contribute and I think that valuable goes plan. I.

C

Think I think there are interesting points into management and and and how how management are are in open source. I would also want to talk to Sarah. Sarah has a lot of experience into this because I I don't know exactly usually open source communities are driven by engineers. There are not too many managers employed in this and I think this is an interesting request to have engineers in pried into into into the open telemetry project, which I, don't think, is bad or anything but I'm. Just saying, I would like to hear other opinions.

C

How do we handle this because definitely in a corporation management manager has in the end, has the full power for a lot of things, which is not necessarily the case in case of a source project, so I think I. Think I would like to understand better how we can structure it is, but I do understand the need of management to be employed into this, so it.

A

Sounds like I agree. Sorry Sarah would it's like probably one of the world's experts on this and we are lucky to have her in the governance board. So Bogdan. Do you want to take this up with her either in a separate meeting with maybe like Ted and other interested parties? Yeah.

C

We'll talk we were talking to with her Sergey, probably should be there Ted. We should. We should probably talk a bit about this again. Okay,.

A

That sounds like a good next step. Great.

D

Okay could use a bunch of ways to solve this, just be great to get it unblocked. So thank you. Ted.

A

Will you take action on it just set up the thing yeah.

D

I can do that no problem.

A

um Next governance, elections, I added this to the agenda. While we were talking about the last thing and Sergey since you wrote the blog posts about it, I figured you can help me out and talk to everybody about it, but the the elections are on for the open, celebritrees governance board, I, think there's or additional seats being added.

A

The cutoff for candidates to apply was today. There were several emails, blog posts and messages about this most basic game and everybody.

E

Who has a sufficient.

A

Number of get commits, there's an official numbers somewhere. I simply don't know what it's off. My head is automatically enrolled. As a voter, there's also a form you can use to register if you've made contributions that aren't captured through get connects, huh for example, I think.

E

B

Had enough, but.

A

I perform preemptively in the same spot. Yes,.

G

It is at least in github post, and this list contains all people who you forget. There is a commission and emails associated with this commit. Some people have contributed a lot and we have them on the list, but you don't have any camis from them. So there is a separate list of like I. Think four people in this category on the top of my head is Tigran in this no Thomas I think no. There is not.

C

Are we gonna regenerate the least when no.

G

I think I think we we generated when we announced the election. So I think at this point, if you northern this is just that register yourself yeah, there is a form to register and it's like three questions so.

C

Even if you did more commit since that, let's say in the last couple of weeks, you should register via the forum and say why you should be a voter yeah.

G

I mean, if you or is it a lot of come, is just your github account will be sufficient enough. Okay, yeah, we will be watching in October and I need to be bring updates, but there is a vote and it will be hold over three days so people in all time zones. You have a chance to hear about it, and would you also accept late registrations for waters? If you only found out at these three days that you eligible to vote, and you really want to cost you what you can still do that?

G

But please don't ask for like if you want to register a juster now, because it will get easier on us to send you invite possible change anyway. Yeah I'm really excited. We have so many good nominee, nominations and whole idea of this governance. That we elected in the beginning is that we will bootstrap with five members, and then we want to have continuation.

G

So these five members who stay for a while, while new members will come and then they will replace original members eventually like 2021 I, think when all the original members are gone and like on the new people stay there.

J

To clarify, if you were not eligible due to the number of commits you had on the date that the elections were announced, but since then you made more commits and now you're eligible, you are supposed to register using the form right, yeah.

G

The only emails we have is what we positive and get github post I can dig it up. Yeah, sorry, children. Maybe you didn't.

C

We double checked, if any of you are in the list of, we do not have your email list at.

E

C

Make sure you also register at the forum and say I am that person so that way, because the vote, the vote link will be sent by email and the email that we have and by the way for 40 grand for you, we have your old emails, but that should be fine or the emails that you had at the moment when we query in github so make sure you have access to do. I.

C

Think by the way, Sergei are we gonna plan to announce the people who applied on a page or something in advance. Yeah.

G

We planning to do it in two days, I believe again: I really need to pull up the document and operate these days, Israel, not skater. So all the nominations got accepted, and now we have yeah October 14th discrimination and nominees will be published. So merely we took a couple days for ourselves just to clear out the lease and Ansan like put it like in nicely format and ask additional questions if needed, and then we'll post it October 14. So it's Monday I believe.

A

Okay, any other questions or comments about the election process. Oh one.

C

One comment: I want to make about the election process. If you know somebody who applied just tell them that we will, unless they tell us not to right now, we'll publish their appeal. I think Tigran asked us about this separately and we responded to him, but anyone who applied if they put something in their Bo, that they don't wanna, be shared. Please make sure and update otherwise we'll publish that on our list of candidates, yeah.

G

I believe he will contact everybody misinformation, okay,.

A

Okay, the next topic I had added this as well just an update on Cube Khan and the observability summit. We talked about this last month, so there's not a lot of updates. Today. I know of at least two talks that have been accepted for opens lemon tree. Possibly more and we've also been granted some done during the keynote, though I don't know, if we've actually planned what we're gonna do with it quite yet Ted did you want to speak a little bit about the observability summit that you're hosting the day before you come? Oh.

D

Yeah I, just just a shout out since this is an audience that I'm sure is interested in it if you are going to keep Khan on day zero. Just the day before the start of cube Khan we're gonna have an observability conference, some really cool talks. It's just a single track for a single day and I think it's 250 bucks on top of your keuken registration.

D

So if you're already gonna be down there, you should come hang out with us yeah if you have a platinum credit card and want to buy a cute, calm registration just to come to observability summit. That's also great.

A

Austin I see a topic underneath yes recording spot, which I think based off some notes or comments. This morning doesn't seem like it's possible yeah.

H

It looks like it might be dead unless someone knows some magic implications to get the CNC F tool.

H

Basically, it doesn't appear that any of the CNC f zoom counts, have API access, so no web hooks no off BOTS, no, nothing! It yells about account admin access, so I'm, mostly putting this on here as a generic plea. If anyone knows people at CMC F that can alleviate this, because it seems bonkers to me that that would be the case because I believe kubernetes uses CN, CF, zooms and I can't.

I

Imagine that they.

H

Handle archiving manually always.

I

Gonna say: I'm include con co-chair, so I'm working closely with Dan and Chris. So if you want, we can talk offline and I can at least get us more direct access to CN, CF, okay,.

H

G

Take a light step.

H

G

Just go: I can create the support ticket. Typically, if they ask to just go through out twice and support you, then yeah.

H

Apparently, through who is it, you told me to talk to you: okay, mommy, yeah,.

G

H

Put him on through her and she they can't apparently came back and said: hey. You know this. This is another thing we can do, but I feel like we're not asking what I question or something so.

B

H

Problem is: is that the zoom accounts don't have the level of access they need to use the developer API, so I can't create a web hook. For you know, a meeting being over I can't create like a integration on the account that.

E

H

Oauth or anything, it just seems like that permission isn't available to these hotel zum accounts.

D

The intended goal of posting the videos to like yes.

H

The the eventual goal is to automate the process. I think Sergey has been doing it right now of taking these recordings and push them to YouTube, and so we have all the pieces, except for the most important one, which is talking to.

A

Zoom programmatically look some constants I. Think you mentioned, you knew some people to see. Ncfd been rejected, yeah.

I

So uh um yeah I could talk to Chris or Dan, because they're definitely want to get more involved in hotels, so yeah great.

H

Thanks ed Austin, at least at them, yep Brad. Thank you. Everybody all.

E

A

G

In seconds I mean, while if anybody wants to take this job, to get missing, click warning from zoom and post it on YouTube you're, welcome to ask and you'll get the keys are.

A

We doing it just for the monthly community meeting or for every Sigma T 15.

G

Meetings a week.

D

H

Have the keys to this right now and so I will see what I can do about helping the.

A

Alternative is we just have the host of each meeting be responsible for it, like I'm, happy to do it for the community meetings, but you know 15 a month, probably shouldn't be assigned to any one person. Oh yeah 15 a week 15 a week. Sorry, and do we want to shift to a policy where the the one person from each meeting is responsible for it? Just.

G

Too many people to share our counties: okay,.

H

A

H

How finicky the settings are for the auto record and everything? Okay.

A

Sounds like constants you're. Our only hope. That's.

I

A lot of pressure, I assume, is.

E

I

H

No way to actually come to the website sig tomorrow, oh yeah, actually, that's that should be a note to decide. Sig starts meeting tomorrow. It's.

A

Over you're down in the signal de section, okay, yep, okay, Sergei I- can help share the load with you. If you would like.

G

A

Progress on metrics API, tears, yeah.

K

So I just wanted to open this type of real quick.

K

It's been about a month and a half, or at least so a little over a month since we met in San Francisco to discuss the metrics API, we had our working sessions and I think the peers are still open and the way I said during my interactions with the same leads I find that you know this is a metrics work that they're they're, blocked off and I just wanted to ask: do we need another session that will help accelerate sort of whatever is blocking the work on the PR, or it's going at a good cadence and there's valid reasons why you know it's it's still open since it seemed like we had ironed out what we needed to do for the metrics work.

K

Hopefully, Bogdan can speak and if Josh there or Ted or whoever but I'm just trying to if it asks a, is there a problem B. If there is do we need to do something about it rather than this all waiting? Okay. So what's the problem tell me.

C

No I met I met with Josh a couple of times this week a lot of things. We are just ready to merge the first like 70% 60% of the PR, it's approved, he's gonna get merged, and then we so what we decided to in order to make progress. Everything that we agreed on is gonna be merged.

C

Probably, today, I just left two minor comments on that thing and then the rest of the work is going to be a bit rewritten and we're gonna try to make progress, though the advantage will be that now it's becoming way smaller and way easier to review and stuff, so yeah well, I think I think it was a combination of things like last week. I was in New, York I didn't have time to look at this, but I think I'm doing a good job with Josh right now and his is very responsive. Okay,.

K

So what I'm hearing is that things are back on track. There were some other reasons why it might have been a little bit delayed, but we don't need to meet again or anything like that. Not.

C

Yet not good I would like you know, if that's the case. Okay,.

K

And the second piece was on a similar note: how are we doing on this back version for I think alpha-2, we're.

C

Going to talk about that in the second date, okay,.

B

A

Okay and speaking of which, it's time for sick of days, starting with the open salami tree collector, which I think Tigran usually speak to yeah yeah,.

J

So a couple updates, so, first of all, it's now called collector. No longer a service, we renamed that the name was causing a confusion. After discussing with the community, we decided to rename it to a collector. That is cheering yes, the github repository and all go package names are also renamed from open, telemetry Darsh service. Don't let me to director so if you're importing this, you will need to update your import path.

J

Number two. We released collector alpha 0.2 last week, which means that the configuration file format is now considered stable. We at least we aim not to make breaking changes to the format, but it's still alpha, but we aim for that. The next release 0.3 will aim to have stable public interfaces for packages that are intended for consumption.

J

This is important for people who create custom, builds of the collector and and also we decided to align the collector releases with spec releases number wise, so the alpha 0.3 will be released in November and if specs ik finalizes the open flame tree protocol early. That release will also include the open, telemetry collector sorry, protocol implementation in the collector, but.

C

Because the data model that you use internally are exposed by the interfaces, so you there is a there is a blocking thing that you have there. That's.

J

C

We are working on that and we are making progress, but that's something that you yeah.

J

So it's preferable that we actually release that or approve the protocol early as early as we can for 0.3 spec. You.

C

J

Ready whenever people are ready for the final round of discussion, we can start that ok.

C

We should then yeah, let's, let's make sure we start very soon. Thank you guys. Okay,.

J

Okay, okay! That's it from me.

A

G

A

A

Which is usually bargain awesome.

C

Because last week so I think they're we missed the deadline. We still have a couple of issues, open, I, think, sir, you better hold it. What's.

G

Yeah I can talk about specifications, as Bolden said we had a milestone set for ourselves as last Friday and today is ordered to signal Wednesday, and we still not there. So we have 19 open issues out of this 19 I believe about five is about ethics, so once matrix, P R will be merged.

G

You may get rid of five issues altogether, but assume leave us is 15 more like 14, and we have a lot of active peers, I think around 8 right now, few of them, if you fixing the issues, few of them just fixing issues of next milestone, so it it's not like this 10 TR coverton issues, so we're still looking for owners for this issues and people who will be working on specification I feel that there is like lots of people could seek and was out for some other business.

G

So I hope that situation will get better when we entered like this week and by the next week. So if you have energy to healthy specifications, please help us, as Jigar said specification, sometimes block other like broken limitations, because people were expecting to see what needs to be granted and how like how to handle questionable. Appreciations. Okay,.

D

Yeah and just a simple process in case people don't know, Sergey has been doing a great job of organizing everything by milestones so on both the specs repo and the Odette's repo. You can search by milestone and select point two, and you will see the open issues that are like specifically related to this release. I think.

C

D

Ones that need attention, I think.

C

The other thing that we should focus on, we should have a deadline, maybe Friday and everything that doesn't get to be. We do release and move everything over to v3. I am suggesting that in order to make progress, because otherwise yeah.

D

C

Want to have some some releases, what do you think Sergey everyone.

G

I'm fine is being aggressive. You just need to like even more grace if some issues needs to be closed and we can get back to discussions after 1.0 if this is about new feature, especially this way, but I'm all for being aggressive. At this stage, we very close to new year.

D

I would suggest it's really the metrics that are the thing we'd like to see in point two, because that's the one part of the API, it seems like SIG's ever looked and to put effort into like everything else. People already have something so soon as metrics gets done, I would recommend releasing point two and everything else can be point three yep.

C

A

Right next is Java Wow. Yes,.

C

Sir also behind, and mostly because of me again so for the moment we we do meet a lot of v02 issues.

C

Unfortunately, there are people on vacation. There are a lot of people on vacation on Java, but hopefully we can deliver it with the one week. So officially we should have done it on 14, but probably we should aim on 21 for the first release.

E

A

Dough, that's usually Rahul, sir, who wanna call her.

B

Go Clay's part is done for me to release. Metrics is still what being worked on a few changes that are, as Marvin mentioned, he and Josh talked about it, and those changes are gonna happen so again for in this probably not going to be possible for matrix world, probably 21 for go as well. I.

D

Do know that Josh and Chris Mir have kind of metrics implementation waiting in the wings but they're waiting to the spec stuff to get finalized. So hopefully it won't be too long of a gap. Yeah.

B

So some work has already been done, but though I think that work will change a little bit. No.

E

B

Not everything is not gonna be thrown away, but so the API is done, then. Will change slightly and I? Think josh is working on SDK right now, yeah.

E

That was correct and.

B

I'm, looking into the Prometheus exporter and the matrix data author, okay,.

A

Do we have mayor to speak to node yeah so.

L

We released a point 1o version with the APS and node and web SDK. These are includes to exporters for the tracing, zip, keen and eager and SAT PNG RPC instrumentations.

L

So currently we are working on the matrix SDK and a Prometheus exporter.

A

If it takes probably.

L

Two weeks from now.

A

Okay, Python I think it's usually Chris lip.

F

So, where largely in the same place as JavaScript, we did the code I wonder, release last week and then you've got I, went to work everything now for the two alpha release. We do have a problem like all the SIG's have this problem. Now that we have milestones in the spec repo. Let's say you know, for example, metrics exporters will be ready for the like the o2 alpha yeah, but none of this is written. Yet so when we said josh is working on the SDK, the SDK means a lot of things right.

F

It's not just the implementation with the API. It's also all of the stuff that we buried in the SDK, which includes the data model and exhalation, and all of that is going to be more work than people. Imagine right now, like I, don't think it's realistic! This stuff is gonna, get done in the next two weeks. Even if it's all we were working on and I, don't think. Another meeting is gonna help that I just think it's. You know we haven't scoped this stuff.

F

Well, we just we say SDK work, but SDK, or it actually means three different big projects.

B

Chris on the aggregation, the aggregation is not defined and I. Don't think. That's gonna be there.

B

So when I say the metrics will be there, probably for the basic count of gauges that will be exported without aggregation, spec being defined, but.

C

That's gonna be in v3, so v2 includes only the basic idea, but.

B

I thought respect on the reprocess aviation part of me too. Unless I misread it.

F

Yeah yeah I think we're gonna need to start distinguishing between spec milestones and implementation milestones, because right now you know, we've got a date for one, but if the spec, you know, let's say just barely- hits their milestone target date and they they have one day to spare. That means we have one day to implement them. So I, don't you know it's I.

D

Think, as far as like messaging around the project goes, it's realistic for us to announce project wide stuff around like this spec releases, but as far as like implementations go I feel like that's gonna, be all over the map. Right, like wind, go, get something out the door versus Python versus Ruby versus PHP, which just started last week like it probably won't be realistic to have some big official. This is the release of everything and all the languages kind of.

F

Interested know what people think about versioning, metrics and tracing acceptable, because you know, if you imagine, we're gonna, have logging into we're gonna be in this weird state, with logging, where let's say that we're at one point out, then, if we're trying to keep all the packages in sync, the first blog and release will be the release.

D

But my main issue with that, because we thought about that before it I'm sure that people have opinions by the thing I've noticed is right. Now those different observability api's tend to have some amount of shared surface area, so there's some concepts that are shared across them and particularly, we want to be like correlating these various kinds of observations, and so that made me feel like it would be like a step too far to at this point, be like they're all treating them like they're separate, independent verticals is like not necessarily.

F

Especially a good reason for not having them in separate, you know, say repos or packages or whatever, but I think problem soon, that we are ready to release tracing 1.0 and not metrics. One final and we're going to be holding a tracing of metrics.

C

We should we should discuss if there's a gate, I think I think we're a bit far from one. We know that until I still think we have features to solve for one. We know aspects to define for 1.0, even for traces. So once.

G

We will get closer and.

C

This will become a problem. We can yeah.

D

I think more directly than 1.0, there's just I think what Chris is saying is we could start getting user feedback on tracing at this time right, like people can be taking Python and exercising the tracing portion of it and writing like instrumentation, and we could be getting perhaps invaluable feedback.

D

We probably don't want to gate. We want to be able to make some amount of noise to encourage that kind of interest and not wait too long. If, like the metric stuff is gonna, be like another month, you're piping, it out no.

B

No make sure make sure.

B

F

Next Christmas.

A

F

Said that was that was the Python sync progress. We still have other things to go right, yep.

A

We still have done net Ludmila, I, don't know if I saw her on the list of attendees, so.

C

Jays laptop crashed and he made he wanted to mention that it was a Mac, not a window. I.

D

Think we also lost Austin, who is who was part of that sig I.

H

Think we're much in the same place as other SIG's. We do have work going in some stuff. Around benchmarking came in this week, which is good. More integration with the node ecosystem tracing has been in a good place for a while. So that's that's already out, but we're kind of in the same boat with everyone else on metrics.

H

A

It looks it sounds like we should be unblocked again. What's the next metrics PR, the one that contains to think 60% of the work is done.

C

That will not unblock the major decisions are being the next one. I'm aiming for end of this week. Promise okay, well I'm, gonna, go and spend time. I'm gonna go to my step office and stay there until Josh is writing the space. It's.

H

Very nice feel other.

A

We'll just down the street from you, but I.

C

Think I don't know exactly what it is, but it's it's a it didn't downtown here. We.

A

Irate we await the results, all right, Ruby.

A

Is there anyone from ruby on the call, don't actually think so. All right, I will plus in the right people from Ruby, Erlang I, don't think I saw it Tristan.

A

Anyone from the new PHP sig.

F

This morning, they're.

D

Just getting started, they.

F

Have one PR that copies a bunch of the tracing implementation from.

E

F

Private repo, it looks good, they are probably going to be blocking on coders. So if anybody's interested in cage B, he wants to go, contribute to that I. Think they're. Looking for people perfect.

C

I think we have a brass Sikh. Do.

A

We well I saw it on the the list from last week, roster just said: she's meeting some Isabel, so just such as me, accent developer, so I'll get rid of it. C++ this thing was I was.

C

I was there this? It was just the beginning. The introduction meeting this Monday I mean there were some decisions about some languages or stuff I. Think probably we should start having some kind of hello world there. So we have a dead moment, though.

A

Okay and finally, we have the website Austin. Did you want to pick that yeah.

H

It'll be the first cig meeting tomorrow. So if you're interested in working on the website or involve the website stuff, please show up. One thing: I did notice is we need to get the meeting notes on the calendar? Invite but yeah and Constance I think you mentioned documentation and the website is just really looking for quick start guys.

H

I

Owe probably that another round right now I'm we're ready bombarded it's too you guys really laughing right now, as you can tell I'm already been borrowed writing documentation for collector yeah.

H

I

There's stuff in other points, a special.

H

Shout out to the collector documentation, it's very good stuff in the repo already I, when.

C

Do we Morgan, you may want to talk to Joe? He mentioned that he has a dick writer that, yes, we started.

A

The conversation so.

C

Maybe, tomorrow into the meeting.

H

There is some stuff that is in progress. Josh wrote a QuickStart guide for go that I'll be trying to repurpose into that there's some c-sharp QuickStart guides already is so I've just been traveling and doing a lot of other writing and stuff this week and haven't had a chance to get to it but hoping by the end of the month. We've got all that fleshed out in terms of quick starts for tracing at least.

B

Okay, thank you and.

A

B

Had added notes.

A

At the bottom mister the conversation that we had with Chris about doing version, metrics and Tracy separately- are there any other topics that people want to discuss this week.

I

One general thing on the like: for the election: there says it's going to be a government's meeting tomorrow, but I don't see anywhere that it's mentioned or like couldn't my calendar or something like that.

A

It should be, let me because I have the shared calendar open right now. Maybe.

I

Mine might not have recent, since we got other things to collaborate, but uh yeah.

A

Cuz, it's on it's the monthly community, open, telemetry governance, community meeting at 10:00 a.m. tomorrow. It's been on the shirt calendar for a while. You want.

I

A

I

I know it's thing with my calendar because, like are accounted in a weird limbo, changing.

B

C

Think he's doing.

E

C

As gold speak, so you wanna change.

D

All my meetings are clobbering, my other meanings, so sad.

A

Do you see it now, Constance? Yes,.

I

I do I forced to resync and now it's happy.

C

That happens when you is exchange and on.

I

H

Don't worry so use that and I call anymore I, don't think I think we can. Oh it's.

I

Is me, I was a former Microsoft II I'm, okay, Louis I will own my shade to throw at Microsoft.

A

Any other talks.

A

Okay, I think that's it I'll publish these notes up on the blog, probably sometime tomorrow and I'll work with Sergey to get the recording uploaded to our YouTube channel.

A

Thank you very much for attending and we'll see you next month.

B