 Hello everybody. Hey, hey, hey Hello Hey, until four or five after so we actually get started Hello Morgan Hello, we're just waiting another two minutes before we get started for other people join Morgan Calendar invite because the calendar invite has a Google meeting That's it does that's the lead that Morgan because it was confusing actually. I didn't know which oh, I see. Yeah, I'll just delete it That's easy in it. Uh-huh. Awesome and Done and let me make sure that's fixed for next month's Yeah, next month's is already fine. Okay, two more minutes before we take this out. Okay Hello everyone, I'm your host Morgan McLean Product manager at Google. This is the monthly open telemetry community meeting Where we go over the status of all of these special interest groups in open telemetry 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 I think Ted and I have already filled in some of the items in the notes for today's agenda But it adds things to the conversation. Please just to put the document And So the first item for it today is Gitter as you noticed the main Gitter chat room for the open slum review community disappeared this morning We quickly recreated it. I reached out to Gitter They're going to try and read all the members who Weren't re-added to the new group and they're going to see if they can capture the old chat history It appears that someone accidentally deleted the chat room Gitter has a very interesting security model where literally anyone in the chat room can just delete the entire chat room Which is definitely not the best they've had a feature request that they said they will improve on They have feature requests to fix this to create an actual admin role, but it's been open for three years So it's not nearly as important as gifts. Tell them gifts Yeah, adding gift support should be higher on the priority queue Anyways, they're gonna try and restore things Lesson learned don't press the delete button No matter who you are Yeah, that's the update on Gitter Next I think Ted you had a topic on approver and two other roles. Oh, yeah, so this is instigated for me around trying to get more like a triage a role put in and Got into a conversation with Sergei and it kind of came back around to the current approver role as well So I kind of wanted to talk about both Just a thing we're noticing is you have people who including myself And also, I know, you know you Morgan G gar 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 a minute Strava 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's been kind of annoying to have to go around to every single repo after gets created and get this access added So I was requesting that we do this is just like an org wide setting of being able to have some gardeners or whatever Whatever Diminitizing role we want to use to imply this person is not like in charge of the backlog But nevertheless to have this access I Their gaze suggestion 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 approvers might also be fine if we want to just say Approvers are anyone that? Maintainers are fine with There's already seems to be some language in there about saying approvers can be project managers or triagers but The requirements right now are that you actually have to do a whole bunch of Code commits like like the literal letter of the law List 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. We're seeing people Get rejected for a prover status. You are code committers and it's just kind of slowing things down Background, what do people think about this issue? By 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 Sergey suggested. I think you have to have a bit of context of what's happening in that rep or you know To triage the issues in that rep or correct? I 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 approver 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 and approver right now just says you You have to actually be a code contributor In terms of the requirements, I think I think it would be good for people to say other opinions the governor should meet and And the decide on this but I think good I mean filing with more input and why it's important. I think it's Yeah I'm curious actually just maybe backing away from just triage yours like people who are Working on the very six. Do 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 It's been fine for us. It's been fine okay Yeah, I just want to know that becoming 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 such a way that there is no I don't like you kind of a reason not to get an approval Approver into the repository and same time you shouldn't be able to bring like a whole bunch of your friends just to like party around and Like then it will become unmanageable. So there is like lots 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 as this Request for triage role is very interesting and we need to do something with that and make sure it doesn't like it balance all this Requirements very well Yeah in the PR thread you mentioned maybe relaxing the approver requirements are making it more oriented towards like the SIG maintainers having just like maybe a more direct say I Think that would be fine. I do agree with you though 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 But the other 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 It just wouldn't solve my actual problem of getting like my engineering manager's access to be able to do things on behalf of their engineers To 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 would be useful Yeah, I understand that we don't want to take power away from maintainers But I also feel like there are cross-cutting concerns that having Some dedicated gardening staff so to speak that can go around and is empowered to create milestones and you know help out Would be useful. I think it's something we could at 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 to agree like certainly in our case, I don't know jiggers on the call. He's he's our TPM I Think that would be like a status that would work really well for him I'm sure people wants to light step in Microsoft and other firms and it's an important role, frankly like project management but between between the TPMs who decide what? The governance board That comes down to rock paper scissors. That's the universal way of solving anything It's it's Listen, like everybody's contributing here wants to actually contribute and I think they have valuable roles play I think I think there are interesting points into Management and and and how how management are in open source I would also want to talk to Sarah Sarah has a lot of experience into this Because I don't know exactly usually open source communities are driven by engineers There are not too many managers implied in this and I think this is an interesting request to have engineers implied into into into the 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 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 the case of open source project So I think I think I would like to understand better how we can structure this But I do understand the need of management to be implied into this. So It sounds like I agree Sarah would it's like probably one of the world's experts on this and we are lucky to have her on the governance board So Bogdan, do you want to take this up with that with her either in a separate meeting with maybe like Ted and other interested parties? Yeah, we'll talk We'll talk into with her at Sergei probably should be there Ted. We should we should Probably talk a bit about this. Yeah. Okay. That sounds like a good next step. Great Okay, there's a bunch of ways to solve this Just be great to get it unblocked. So thank you Ted will you take action on it just set up the sink. Yeah, I can do that. No problem Next governance elections, I added this to the agenda while we were talking about the last thing and Sergei since he wrote the blog posts about it I Figured you could help me out and talk to everybody about it But the the elections are on for the open slum tree governance board. I think there's four additional seats being added The cutoff for candidates to apply was today. There were several emails and blog posts and messages about this And everybody who has a sufficient number of git commits, there's an official number somewhere I simply don't know what at the top of my head Is automatically enrolled as a voter There's also a form you can use to register if you feel you've made contributions that aren't captured through git commits for example, I Think I technically had enough but I've been at the forum preemptively and should other people in the same spot Yes, there is a list in GitHub post and this list contains all people who will Who get their visit commits and emails associated with this commits Some people have contributed a lot and we have them on the list, but we don't have any commits from them So there is a separate list of like I think four people in this category Of the top of my head is Tigran in this No, not Tigran Thomas. I think no, there is no top of my head Are we gonna regenerate the list When when no, I think I think we regenerated it when we announced the election So I think at this point if you not on this list just to register yourself Okay, there is a form to register and it's like three questions So even if you did more commit seems 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, I mean if you already did a lot of commits just your github account will be sufficient enough Okay Yeah We will be watching and 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 times also have a chance to hear about that and vote. We also will accept late registrations for voters if you only found out that these three days that you Eligible to vote and you really want to cast your what you can still Do that, but please don't Pass phone like if you want to register register now because it's to get easier on us to send you invite to for the voting Anyway, yeah, I'm very excited. We have so many good nominations and whole idea of this Governance that we elected in the beginning is that we will put strap with Five members and then we want to have continuation. So this five members will stay for a while Well, 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 only new people still there Just 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 are eligible. You are supposed to register using the form, right? Yeah, the only emails we have is What we posted in and get the guitar post I can dig it up. Yeah, sorry Tigran. Maybe you didn't know if I am No, no, no, I'm there. I'm on the least By the way, double check if any of you are in the least of we do not have your email list section of the bottom That list make sure you also register by 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 for Tigran 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 those Yep, I Think by the way, Sergi, are we gonna plan to announce the People who applied on a page or something in advance. Yeah, we Planning to do it in two days. I believe again. I really need to pull up the document and Operatives dates is real schedule. So all the nominations got accepted and now we have for Yeah, October 14th, these affirmations Namely, so we published so we we took a couple days for ourselves just to Clear out the lease and I'm saying like put it like a nicely form it and ask additional questions if needed and then we will post it October 14th. It's Monday. I believe Okay Any other questions or comments about the election process? Oh 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 will publish their bill. I think Tigran asked us about this Separately and we responded to him but anyone who applied if they put something in their bill that they don't want to be shared Please make sure An update because otherwise we'll publish that on our list of Candidates, yeah, I believe you'll contact everybody information Okay Okay The next topic I had added this as well Just an update on cube con 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 open telemetry possibly more And we've also been granted some time 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 cube con? Oh, 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 cube con on day zero just before the day before the start of cube con 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 cube con registration. 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 cube con registration just to come to observability summit That's also great I Austin I see a topic underneath Yes recording spot, which I think based off some notes or ours or comments this morning doesn't seem like it's possible Yeah, it looks like it might be dead unless someone knows some magic invocations to get the CNCF till Basically, it doesn't appear that any of the CNCF zoom accounts have API access. So no webhooks No, oh off bots know nothing. It yells about account admin access So I'm mostly putting this on here as a generic plea if anyone knows people at CNCF that can alleviate this because it seems bonkers to me that That would be the case because I believe Kubernetes uses CNCF zooms and I can't imagine that they handle archiving manually I'm actually I was gonna say I'm in coupon 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 at CNCF. Okay Yeah, I'll take that light step. I can just get them. I can create a support ticket They typically they ask to just go through at last and support ticket Apparently through Who is it you told me to talk to it's okay. I'm me Yeah, I put a one through her and she they apparently came back and said hey No, this this isn't a thing we can do, but I feel like we're not asking the right question or something So what was the problem? The 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 webhook for You know a meeting being over. I can't create like a Integration on the account that Using a lot or anything it just seems like that permission isn't available to these hotel zoom accounts intended goal of posting the videos to like Yes, the the eventual goal is to automate the process I think Sergei has been doing right now of taking these recordings and posting them to YouTube And so we have all the pieces except for the most important one which is Talking to zoom programmatically. So Constance. I think you mentioned you knew some people at the CNC if you could reach out to Yeah, so um, yeah, I can talk to Chris or Dan because they're definitely want to get more involved in hotels. So Yeah, great I said you can be Austin at light stuff and yeah Brad, thank you everybody Okay And I mean wait a second. So meanwhile if anybody wants to take this job to Get meeting recording from the room and post it on YouTube. You're welcome to ask and you'll get the keys Are we doing it just for the monthly community meeting or for every sick meeting? 15 meetings a week Not everyone volunteer at once I Have the keys to this right now and so I will see what I can do about Helping the 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 15 a week 15 a week. Sorry Do we want to shift to a policy where the the one person from each meeting is responsible for it? It's just too many people to share our counties, okay Especially giving up finicky the settings are for the auto record and everything Okay, sounds like Constance you're our only hope That's a lot of pressure as zoom is Our doctor's dead There's no way actually speak come to the website sick tomorrow Yeah, actually, that's that should be a note to website SIG starts meeting tomorrow Down in the sick update section. Okay. Yep Okay Sergey I can help share the load with you if you would like okay Jigger progress on metrics API peers. Yeah, so I just wanted to open this topic real quick It's been about a month and a half or at least 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 So during my interactions with the same leads I find that you know There's still some metrics work that they're they're blocked on 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 hopefully Bogdan can speak and and if Josh is there or Ted or whoever But I'm just trying to if you ask a is there a problem be if there is do we need to do something about it rather than this Okay, so what's the problem tell me No, so I met I met with Josh Couple of times this week. I guess a lot of things We are just ready to merge the first like 70 percent 60 percent of the PR It's approved and he's gonna get merged and there we so What we decided to in order to make progress everything that we agreed on is going to be merged 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 So the advantage would be that now it's becoming way smaller and way easier to review and stuff. So Yeah, we're I think I think It was a combination of things like next week I was in New York I didn't have time to look at this, but I think I'm doing good job with George right now And he's he's very responsive. Okay, 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 yet. Not yet I will let you know if that's the case. Okay, and the second piece was on a sort of similar note How are we doing on the spec version for I think alpha two We're gonna talk about that in the sig update. Okay, perfect Okay And speaking of which it's time for sig updates Starting with the open telemetry collector, which I think Tigran you usually speak to yeah, yeah So a couple updates. So first of all, it's now called collector No longer a service. We renamed that the name was causing confusion After discussing with the community we decided to rename it to collector That is cheering. Yes, the github repository and all go package names are also renamed From open telemetry dash service to open telemetry dash collector So if you're importing this you will need to update your input paths Number two, we released the 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 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 spec seek finalizes the open telemetry protocol early that release will also include the Open telemetry collector. So protocol implementation in the collector But you you do need parts of the protocol because the data model that you use internally Uh Are exposed by the interface. So you there is a there is a blocking thing that you have there That's correct. You know, we are working on that and we are making progress But that's something that may block you. Yeah, so it's preferable that we actually Release that or approve the protocol early as early as we can for 0.3 spec You know that it's on you. You have the last comment I'm ready whenever people are ready for the final round of discussion. We can start that. Okay, we should Then yeah, let's let's make sure we start very soon Take it doesn't Okay, okay Okay, sounds good. That's it for me. Okay. Nexus specs Which is usually bogged in awesome Um, because I was Out last week. So I think the we missed the deadline. We still have a couple of Issues open. I think sergi has better Better knowledge. What's Yeah, I can talk about the specifications as bogged on set. We had a milestone set for ourselves as Last friday And today is already Tuesday. No, wednesday and we're still not there. So we have 19 open issues out of this 19. I believe About five is about matrix. So once matrix pr will be merged. We may get rid of five Issues all together, but it still leave us with 15 Or like 14 and we have a lot of active prs I think around eight right now A few of them fixing the issues few of them just fixing issues of next milestone. So it's not like this 10 prs will cover 10 issues So we're still looking for owners for these issues and people who will be working on specification I feel that that is like Lots of people got sick and was out for Some other business. So I hope that the situation will get better when we enter like this week and maybe next week So if you have energy to help with specifications, please Help us there as jigger said Specifications sometimes block other like block implementations because people were expecting to See what needs to be implemented and how like how to handle questionable situations okay Yeah, and just a a simple point of process in case people don't know Uh, sir gay's been doing a great job of organizing everything by milestones So in both the specs repo and the otevs repo You can search by milestone and select point two Uh, and you'll see the open issues that are like specifically related to this release I think the ones that need attention. I think the other thing that we should Probably force us. Uh, we should have a deadline maybe Friday and everything that doesn't get to the two We do a new release and then we move everything over to the tree I I'm suggesting that in order to make progress because otherwise Yeah, we do want to have some some releases. What do you think sir gay everyone? I'm finally being aggressive. We just need to like even more aggressive some issues needs to be closed and We can get back to discussions after 1.0. This is about new feature, especially we can Handle it this way as well. Yeah, but I'm also being aggressive at this stage. We're very close to new year I would suggest uh It's really the metrics that are the the thing we'd like to see in point two because that's the one part of the api It seems like sigs are reluctant To put effort into like everything else people already have something So as soon as metrics gets done, I would recommend releasing point two and everything else can be point three. Yep Thank you All right, next is java well Yes, uh, sir We are also behind uh, and mostly because of me again um So, uh, for the moment we We we do miss a lot of v zero two issues. Uh, unfortunately Uh, there are people on vacation. There are a lot of people on vacation on java, but uh Hopefully we can deliver it with the one week So Officially we should have done it on 14, but probably we we should aim on 21 for the first release Okay And that's usually rahul is rule on the call Uh for go, uh trace part is done for we to release metrics is still work being worked on There are a few changes that are, um As bogdan mentioned He and and josh talked about it and there's those changes are going to happen. So Uh, again fourth in this probably not going to be possible for metrics work Um, probably 21 for go as well Yeah, I do know that uh, josh and kresmir have, uh, kind of metrics um Implementation waiting in the wing But they're waiting for the spec stuff to get finalized. So hopefully it won't be too long of a gap Yeah, so some work has already been done, but I think that work will change a little bit No, it's not everything is going to be thrown away, but So the api is done that will change slightly And I think josh is working on sdk right now Yeah, that's correct. And uh, I'm looking into the promitius exporter and the metrics data model Okay Uh, do we have mayor to speak to node? Yeah, okay mayor sir So, uh, we released a point one or uh version, uh with the apis and uh Nord and web sdk This also includes, uh Two exporters for the tracing zipkin and eager And sdp and grpc instrumentations Uh, so currently we are working on the metrics sdk and the promitius exporter Do you have a date for uh, 0.2? Probably two weeks from now Okay Okay Python I think that's usually chris. Yep. So we're largely in the same place as javascript Uh, we did the 0.1.0 release last week Um, and then we've got a bunch of work to be doing now for the o2 alpha release Uh, we we do have a problem like all the sigs have this problem now that We have milestones in the spec repo that 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 jash is working on the sdk, the sdk means a lot of things, right? It's not just the implementation of the api. It's also all of the stuff that we buried in the sdk Which includes the data model and exporters on aggregation And all of that is going to be More work than people Uh, imagine right now. Like I don't think it's realistic. The stuff is going to get done in the next two weeks Even if it's all we were working on And I don't think another meeting is going to help that. I just think it's you know We we haven't scoped this stuff. Well, we just We say sdk work, but sdk work actually means three different big projects Chris on the aggregation the aggregation is not defined and I don't think that's going to be there even for go So when I say the metrics will be there probably for the basic Counter engages that will be exported without aggregation Spec being defined that's that's going to be in v3. So v2 includes only the basic types But I thought the spec on the uh repo says aggregation part of v2 unless I mistread it We get milestones. Yeah, yeah I I think we're going to 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 everything. So I don't you know, it's I think as far as like messaging around the project goes um It's realistic for us to announce project-wide stuff around like the spec releases, but As far as like implementations go I feel like that's going to be all over the map, right? Like when go gets 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 I I've been interested in what people think about versioning metrics and tracing separately Because you know, if you imagine that we're going to have logging in the future too We're going to 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 of the packages in sync the first logging release will be one point early But my main issue with that Uh, because we've thought about that before I'm sure other people have opinions But the thing I've noticed is right now those different observability apis 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's 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 It's like a especially good reason for not having them in separate, you know, say repos or or packages or what have you But I think we're on the problem soon that we are ready to release tracing one point out and not metrics one point out And we're going to be holding up tracing on metrics We should we should discuss about If that's okay, I think I think we're a bit far from 1.0 that I think I still think we have features to to solve for 1.0 Aspects to define for 1.0 even for traces so Once we will get closer and this will become a problem we can Yeah, I think uh 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 could be taking python and exercising the tracing portion of it And writing like instrumentation and we could be getting perhaps some valuable feedback On that front. 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 going to be like another month for python to get out No, no, make sure it's make sure Thank you, cool okay next Sorry chris I said that was that was the python's like progress. We still have other six to go right? Yep. So we still have dot net uh ludemila I don't know if I saw her on the list of attendees Sergei's laptop crashed and he made he wanted to mention that it was a mac not a window I think we also lost austin who is who was uh part of that sig No, I'm here. Are you here? Hey, awesome. Even if they didn't I think we're much in the same place as other sigs. Um, we do have work going in Some stuff around benchmarking came in this week, which is good um more integration with the dot net ecosystem um 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 Okay, so it looks sounds like uh, we should be unblocked again Once the next metrics pr the one that contains I think 60 percent of the work is done That will not unblock the major decisions that will be in the next one Uh, I I'm aiming for end of this week promise Okay, though. I'm gonna go and spend time. I'm gonna go to Life step office and stay there until josh is Writing the the specs. It's very nice. You'll love it Just down the street from you buck. Uh, I think it's too black I don't know exactly what it is, but it's it's a it's in downtown here We await we await the results All right ruby Is there anyone from ruby on the call? Don't actually think so. All right. I will plus in the right people from ruby Uh, erlang. I don't think I saw tristan Uh, anyone from the new php sig Uh, I was on the php sig call this morning. So instead we can talk about it. Basically, they're just getting started um, they have one pr that uh copies a bunch of The tracing implementation from somebody's private repo Um, it looks good. They are probably going to be blocking on Coders, so if anybody's interested in php and wants to go contribute to that, I think they're looking for people perfect I don't think we have a rust sig. Do we well, I saw it on the the list from last week Uh, rasta just said she's meeting some is also just such she's meeting some developers. I'll get rid of it um C plus plus This sig was I was I was there this It was just the beginning the introduction meeting This monday. I think there were some decisions about some languages and stuff. I think Probably we should start having some kind of Hello world there Okay, we are at that moment, so Okay, and finally we have the website, uh, austin. Do you want to speak to that? Yeah, um, that'll be the first sig meeting tomorrow So if you're interested in working on the website or involve the website stuff, please show up Um, one thing I did notice is we need to get the meeting notes on the calendar invite We need to do that, um But yeah, and Constance, I think you mentioned documentation and the website is desperately looking for quick start guys I will probably do that in another round right now I'm already bombarded as to you guys probably laughing right now as you can tell I'm already bombarded writing documentation for collector Yeah, no, um, yeah, I'll get the other stuff another point a special shout out to the collector documentation. It's very good It's stuff in the repo already. I By the way, uh Morgan you may want to talk to joe. Uh, he he mentioned that he has a Tech writer that yes Started the conversation. So bring him maybe tomorrow to the meeting Uh, there is some stuff that is in progress. Uh, josh wrote a quick start guide for go that I'll be trying to repurpose into Um, that there's some C sharp quick start guides already. So I've just been Traveling and doing a lot of other writing and stuff this week. I 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 Okay, thank you And I had added notes at the bottom just for the conversation that we had with chris about doing version metrics and tracing separately Uh, are there any other topics that people want to discuss this week? Uh, one general thing on the uh, like for the election, there says it's going to be a governance meeting tomorrow But I don't see anywhere that it's mentioned or like Couldn't my calendar or something like that? Uh, it should be let me because I have the shared calendar open right now Oh, maybe you might you might not have resinked since we got all our things clobbered, but Uh, yeah, because it's on uh, it's the monthly community open telemetry governance community meeting at 10 a.m. Tomorrow It's been on the shared calendar for a while. You do you want to stop? Let me know if you see it Yeah, no, it's I think it's my calendar because like our calendar is in weird limbo because I'm changing I think I think Time as gold's tea so I don't think we want to change all my meetings are clobbering my other meetings. This is so sad Do you see it now constants? Yes, I do. I forced a resink and now it's happy Okay, let's happen that happens when you as exchange not my choice Don't worry, sir. He's not in the call anymore. I don't think I think we can Oh, it's I used to be I was a former Microsofty. I'm okay with I will own my shade thrown at Microsoft Um any other topics Okay, I think that's it. Um, I'll publish these notes up on the blog Probably some time tomorrow and I'll work with Sergei to get the recording uploaded to our youtube channel Thank you Thank you very much for attending and we'll see you next month