 Good morning Doug. Hello, how's it going? It's going well. It's nice and warm on the West Coast. That's always good. Hold on a sec here. Gotta get myself organized. Hey Eric. Yo Tommy. Hi Tamer. Hi Doug, how are you? Good. And Ginger? Ginger, you there? I am. Can you hear me? Yes I can. Cool. You're in Texas right? Unfortunately. I was gonna say how are you doing with the weather and stuff? Now it's fine but the storm was intense. I don't even know how to describe it. I was lucky in the fact that I did have power the whole time. I lost water though on day three. So I was out of water for eight days and had one broken pipe but thankfully it was in the garage and so it flooded the garage a little bit but it was on the floor so it didn't mess anything up. Now I'm just super anxious about every sound I hear in the house and I check the meter four times a day. Yeah because leaky water can cause massive damage. It's amazing but yeah that's scary. Yeah so just trying to recover at this bigger point in time. All right Remy are you there? Yeah. Hi. Hello and how? Yep. Okay and Klaus? Yes. All right Kristoff. Hi. Hello. Let's see we have a fairly short agenda today. So if you have any topics go ahead and add it to the list. Every time you say that Doug it ends up going longer and longer. I know I just jinxed it and I am not eating breakfast yet so I am definitely not in the mood for a very long meeting today. Hey Jim. Morning. And Vlad. Good morning everybody. I was going to slide some Clemens joke in there but I figure maybe I should end this for being recorded. Do it. I'm going to jinx it. It's not recorded so you can put it there. Yeah aren't there? I'm being recorded by automatically hold on a minute. Yep upper left. Yes see I don't see that when I'm sharing the screen. I don't get to raise my hand and I don't see whether I'm being recorded or not so interesting. I think all the C and C have calls by default or being recorded. Yeah that's what I thought. Okay. I didn't think you had any control over that actually. Well technically I do have the host code so I could probably get in there and do something but I never log in with that so yeah. All right Lou are you there? Yes. Hi. Hey and there was someone else on the fly by oh Jesse. All right give him one more minute then we get started. Hamid are you there? I'm here. Excellent. And Simon are you there? Yes. Excellent. All right tell me what it's three after. Let's go ahead and get started. Only 16 people today. That's interesting. All right. Okay community time. Anything from the community people want to bring up? All right so just a reminder we do have an SDK call after this meeting. I'll double check but I'm pretty sure we actually have nothing on the agenda. Let's just do a quick scan there. Yeah nothing. So if you have a topic if you have a topic please go ahead and add to the agenda. Interop discussion last week. The only thing I think worth mentioning because I think most people were too busy to do a whole lot of work on their stuff. We are planning on doing a interop testing starting at the end of March with the hope of maybe being done by KubeCon and maybe do some sort of demo there we'll see how it plays out. But the big thing to know about that is we are planning and doing interop testing starting end of March so that people plenty of time to to bring about their coding efforts. Okay Tim or anything you want to mention from the workflow stuff. Since last time we completed the GRPC stuff we completed the expression language JQ and we're planning our version 06 release before KubeCon EU so just you know working around that to make sure everything is the way we want. That's that cool. All right any. I didn't want to remind you about the KubeCon bash. Yeah I was going to touch on that next. Yeah that's good. I appreciate you reminding me though I didn't forget. Okay any questions about workflow. All right moving on then. So I got a note from the KubeCon EU organizers saying that they're going to have a cloud native bug bash which is well you can read it here right it's talking about basically working on debugging code and banging on stuff and things like that. Now obviously that won't really apply for our spec work however if the SDK folks want to sign up for that just let me know. I'll send in a form for you guys or I'll send you guys a point to the form or whatever is necessary to make that happen. In fact I'll try to remember to mention that then our SDK call if we do have one today. I just wanted to bring that up and if someone wants to join in you know let me know but I didn't think it applied to us from a spec perspective unless someone could think of an aspect that I'm not thinking of. Okay I think there's no more comments on that. I'll try to remember to bring that up in the SDK call. Oh okay it's in where it says there's a bug bash slack channel in CNCF if you're interested in joining that. Okay all right so I have a question and this is more of a get slash get hub type question because I wasn't quite sure how to work here and I don't feel like I'm an expert on get to know for sure what the answer is here. But we got a PR for 1.0 for 1.01 basically just a typo type thing nothing big so that's not the issue. However they open the PR against the V101 branch so obviously I could merge that PR and that would work just fine however that's actually going to obviously change the 1.01 version of the spec at least from a branch perspective. Now I think you can technically have branches and tags have the same name but I think when you when you don't go out of your way to be clearly clear about which one you're actually talking about I think it defaults to the branch and you could only have one I'm sorry in get hub when you have the default thingy it's a default branch it's not a default tag so when someone first goes to the repo they're going to look at a particular branch and we're going to point them to the 1.01 branch which means they're going to see this PR this merged PR as part of that. Now obviously it's not a huge deal because it's just syntactical type things but it seems a little bit wrong from a process perspective that we don't sort of stack up these PRs and then eventually create a 1.02 right it seems weird that we're slipping this thing out of 1.01 because it seems to me once we actually cut a release that thing should be basically set in stone and static okay so I wasn't quite sure what people do in this type of situation I was thinking what they might do is something what I'm suggesting down here which is a create something like a V10 stream branch where that's where all the PRs are sent to and then we just create tags off of that or tags or branches off of that so we'll create a 1.01 branch or something but that way all PRs can go to a stream and we and then we just create the next patch release from that stream how do other people do this kind of stuff is anybody have any suggestions because I wasn't sure how to move forward here can I raise my hand yeah please go ahead um so I'm just I just want to mention the the xml 1.05 edition errata um meaning I think it's okay if you don't make any substantial changes and if you just just uh make um uh type if you fix typos that we're we're looking at the 101 branch since it is one is it a tag or is branch is it it's a branch right it is a branch correct yeah so that's that the one 101 branch is the 101 branch with errata we should merge we should merge the PR into both faces but um I think I think everything that is we want to type it to be fixed we want to type it to be fixed in the thing that people see I think that's that's what we so so you do errata for spec if you're finding embarrassing stuff that doesn't change the spec per se but that is just dumb stuff like typos or grammatic errors or something like this but the the spec with errata is still the same spec that's my that's my stance on that so you lost me there for a second because at some point in the beginning of what you said there you said you merge the PR into both places what is both um so so I think I think the the 101 is set in stone in that we don't really progress on it that's what I mean but but if there are there is something that is helping better for better understanding with 101 um where you are fixing an obvious errata then I think that's fair to put that into the 101 branch but it will also it will also have to exist a master yeah yeah I definitely agree with updating master and and I guess I just wasn't I just felt uncomfortable making a change the 101 branch um because like I said I think typically in my mind it's set in stone but then if we do that when would we ever create a 102 because typically patch releases are always just supposed to be typos type stuff right so when would we ever create a 102 yeah we have we have the question is how do we deal with errata right that's the question and and I think with if you if there's literally just a typo I don't have a problem with it because ultimately what there are still more people who don't know about cloud events than they who know about cloud events and we want them they will show up and we want on the default that we're showing them we want them to to see the right document I think that's the principle that I'm playing and and so therefore whether that document has been you know finalized four weeks ago and or um we we fixed the bug the text bug yesterday I yeah that might be a process objection here but I think I think that the product that the people who are coming to us see is the most important important one and we want them to be normatively correct reflecting what we've agreed to but then at the same time we also don't want to have embarrassing mistakes there right so so one option is to do what you're saying and I think which is basically merge everything into 101 and we basically in my opinion probably never create a 102 the other option is we could change the default branch on the repo to be the 10 stream branch yeah yeah okay so what do people think about clement suggestion basically merge it straight into 101 and what 101 becomes a bit of a moving target but it's always going to be just typo type fixes seems to me the question is whether you're actually changing the standard by fixing a typo and it seems fairly clear that the answer you know right this is more yeah as Clements said this is more a process and puristic perspective right is 101 technically set in stone or not and we're I think Clements is saying no it's not but we are limiting it to just patch fixes and I'm okay with that as long as the group is okay with that but it is it is a you know being a little bit wiggly about things anybody have any objection to that okay tell you what because we don't have everybody on the call here what I'll probably do is send out a note suggesting that and if we don't get any objections then we'll go ahead and do it um well yeah so Jennifer said it's not being wiggly as long as you're making part of the spec yeah well it's it's wiggly in the sense that I think most people assume that once you stamp something is complete you know as it was an official release title or tag it's it's set in stone at that point right and that that's the part that's wiggly to me is we're not keeping it set in stone we're at worst we're morphing it slightly over time so when you look at 101 a month ago versus a month from now I think most people would expect them to be the exact same and we're saying they're not going to be and that's okay as long as we're upfront about it I think that this is like a standard kind of thing is what I'm I'm kind of getting to like all kinds of specs um we'll have the like deal with this uh and in general my experience has been like uh it like typos fixing the typos that's just considered like part of the process and not considered uh versioning up the the spec it's not a change in the spec it's not it's not actually being wiggly but as long as that's like the agreed process is the key part yeah um yeah okay yeah it's funny our life would be so much easier if github had the ability to point to a tag instead of a branch that's the default thing when you go when you come into the repo so such as life okay so there's an ai for me to do that all right any other comments or whatever on that topic before we move on all right cool and thank you Clemens for the idea all right um jim were there any updates on your signature extension proposal I don't think there were but I just want to double check no there aren't um I failed in my attempt to um do the homework that was set to be my by Clemens last week uh don't get my homework I'm afraid okay that's fine um let's see Slinky is not on the call and let me just double check I'm pretty sure this one is still under development with comments and stuff that and therefore it's premature to think about merging let's double check yeah there's still some outstanding stuff yeah so okay I think we need to hold off a little more so just a nagging reminder for everybody please go ahead and review his pr when you get a chance um I think it'd be nice if we can get at least the rough draft of that in fairly soon just to get out of the pr stage and that will I think raise its visibility for people okay um now this one another slinky one now Clemens you said you were having a fit of uh old age and could not remember why you wanted to make a change on this one right um thank you thank you Doug it's yes um yeah I um so so I I know that I don't want to move it um but I'm sorry this I'm sorry I think I'm getting confused no never mind never mind I'm pauses keep going I'm sorry yeah one yeah that is yeah exactly um I have I literally have to go back to our recordings and and see what I said there but I haven't done that yet I have I have the last two weeks were um all of my cloud events time budget is being sucked up by uh working with cause and and his friends okay therefore um I have not had the time to go and take a look at that in detail this one yeah this is the one I was actually thinking of I apologize I was getting them confused I thought something was missing here yeah so yeah that one I looked over and uh like I literally couldn't remember why why I had an objection but then I read it again and that I did today and um that now that looks fine to me I don't know I don't know what I had maybe I had a bad day or something okay but we we had discussed something about this and I'm not sure whether it might just have been that I had no time to look at it and you said because nobody else here knows anything about it that I should go do a review that's probably more like it um but I can we can merge yeah okay well let's make sure Slinky's still not here and he's not okay um well he needs to do a rebase anyway so we'll I'll I'll I'll reach out to him and ask him to do a rebase and see if he remembers what you were thinking of um maybe that will jog your memory but if not we can then merge it however I do need to ask the question of the group does anybody else have any possible concerns with this meaning if everybody's okay with it I'll do an offline double check with Slinky and do a merge unless someone has an objection anybody have any comments concerns okay so let me do that where is it so okay that's this one okay cool and so that was that one this one distributed tracing what was the who were we waiting on you Clemens for this one just to I think we were right yes so that's why I was that's why I was a confused it confused her yes we were waiting on me um and then I have to go go back to because I don't know what so I am opposed to removing it but Slinky had removed some had raised some points and I had said something about this and then there was some homework that was assigned to me I believe based on this but I have to go back into the recording because I can't remember what that was yeah okay yep okay cool in that case I'm moving forward I don't see Lance on the call so I can't nag him and in your scheme registry you saw some I think PR changes to make there right yeah I have I have a few I have a few things to to change there still with the with these with these events I'm not completely completely done with that yet okay so I'm hoping I'm hoping that I can have have that all finalized in probably not next week but the week after okay cool thank you and just to remind you you still have these two up here yeah and and so and yeah the potential properties part that is um that's pretty essential also for the other one we need we need to take it we need to take more of a stance for these for all of those for the triple of new specs we need to take more of a stance in terms of what the author story will be because those are proper apis and not just the the message and we're we're already like we're having discussions with the calls team and our team about um you know how the relationship works between those two big big platforms and most time is being spent on rules and permissions and people and authorizations so you can already tell that that's a complicated story so I think I think we need to go and materialize that somehow in the specs because otherwise we can't get get into off working yeah okay cool um and that's it for the agenda um are there other topics you want to bring up very very short today no one has anything okay then just a quick reminder unless Eric you want to talk about this we do have Eric's issue out here that we said we're going to talk about offline I'm not sure anybody had a chance to do anything with it um but please go look at that and comment if you're so inclined and with that I will go ahead and do the last of the roll call so Manuel are you still there yes excellent uh Priyanka Priyanka you there yeah yeah there we go gotcha okay did I miss anybody for the agenda I think I got all 20 people 21 someone just joined Matt you there yep excellent you just made it because we're just about to adjourn all right anybody else for the agenda or the attendee list all right last chance any topic for either the primary call or the stk call otherwise we'll call it a day for stk as well so check all right in that case we are done really early thank you all for joining we'll talk again next week fabulous yeah enjoy your wonderful leadership again wonderful yes yes I get to go eat breakfast now yes or I start going by now yeah that's why you so rushed okay exactly food is very important you know it all right have a good one everybody