I'll open it back up for discussion. So good afternoon. Welcome to the House of District Committee. We are back on H546 and act relating to racial justice statistics. We just had a walk through, well, before we went to the floor of draft 6.1 and we are joined the committee, committee discussion. We do have it scheduled committee discussion and possible vote. So why don't we open it up for questions? I don't see Eric here, but yeah, sure. I think I made myself clear as to where I stand with this bill. But no one has told me that, I mean, I think gathering these statistics and data is very important whether we're talking about racial justice statistics or any other minority group throughout the state of Vermont. We've talked about starting the division, a cost that goes with it and maybe the cost will go down later on down the road. Maybe it wasn't, but I don't want to start 10 different divisions for 10 different entities that we need to have the data and statistics on. So, and I don't see in this bill which I do want to support where it says down the road. Okay, after we finish the study of the racial justice and continue gathering those statistics, then we're not gonna start incorporating these other much needed statistics and data throughout the state that we need rather than starting eight, nine, 10 more divisions. If we go one start, is that what we're looking at here folks or because that's my concern here is one division clearinghouse for everybody. A few things. We can't, this legislature can't find another legislature like we can't tell a future legislature, you're gonna do this. You correct me if I'm wrong, but you know, I think that's what I was hearing from you. You know, we can talk about it and put it in the record that we, you know, that's the path we'd like to take, but in terms of anything we've passed, we can't find the future legislature. I'm gonna, while we're talking, I'm gonna go find a council state government's justice for investment to report because in making its recommendations and evaluating the legislature and justice for investment to one author for quite a while, they were justice for investment. One takeaway though, one of the recommendations was to look at racial disparities and data collection in Vermont. And so that's, you know, I don't know the side of that. And, you know, the same thing that came up with ceiling this morning, that, I mean, it's clear there are racial disparities or, you know, severe racial disparities in Vermont and that when we pass legislation that doesn't mention anything about racial disparities just by changing our laws like defilmization or ceiling records, it will begin to change. In other states, it has begun to change and mitigate those racial disparities. And again, going back to council state government that really is something that they recommended. So I do see this as a very important part of our work in this committee. And so if I could add a couple of things. So the Office of Racial Equity is charged with a broader mandate as far as collecting data. But this is a subset certainly of the data that that office should be collecting. But this is one of the priority areas that we need to collect the data in part because of what justice reinvestment has recommended. But it does not mean at all that what is learned in this process and what is put together as a database collecting this criminal justice data can't be essentially a roadmap for collecting other areas of data. That's one point. The other point is that we do talk a lot about racial, the racial justice components of it, but inherent in the data we're collecting we're gonna be finding out about for instance geographic disparities that we have in our state. I think that's very important as well. So the data we're gonna be collecting is going to be informing us broader, I think than just that one area of disparity. And it's gonna give us the start on being able to fulfill that obligation or mandate of the racial justice equity office. So in the justice reinvestment report, the final report January 6th, then we'll have page numbers so I can't tell you the page. Then we'll go to page 48 talks about Vermont facing ongoing challenges related to the collection analysis and use of racial disparity data. Among the things that they recommended is collecting analyzed sentencing data statewide as well as by judicial district, invest in staffing and system improvements necessary to increase future data collection and analysis capacity, identify opportunities to publish racial disparity data including an annual report to benchmark and monitor progress, engage impacted communities in the collection of quantitative and qualitative data as well as the development and implementation of racial disparity related policy changes. And then it also specifically says two additional efforts will help Vermont address disparities at other points in the system. And they named specifically the office of racial justice statistics proposed by the racial disparities in the criminal and juvenile justice system advisory panel, RDAF. In other words, the bill that we're dealing with here they essentially they have endorsed that as an important step. So and justice reinvestment is, I mean, yes, the council state governments was really helping and was behind that but any recommendations ultimately have to be proved by the justice reinvestment group which includes administration, includes the courts, state's attorneys, defenders, victims, advocates, et cetera, I tried legislators. So that's part of the why this seems like good idea. So the justice reinvestment is gonna be our not moving forward, it's our Bible, it's our instruction booklet, whatever they say is that what we're gonna be doing in the future. Oh, well, they made a number of recommendations and that was one of them. I knew probably can comment more or you were more involved in that whole process of actually. And whether it's our Bible, I don't know but certainly it's important guidance recommendations that the working group adopted and only heard the report one first week we were back on the Chief Justice chair, the justice reinvestment to working group spoke to our committee and then we heard from council state governments. So I do think it's very important work and that we should follow, we certainly can't do it all, it's a big list but this still really does play a big part of that in realizing that work. We haven't, I can't forget any exact field but I know that in terms of collecting other data and help me members, I don't know so there was the sexual assault there was there we had collection of data in other bills that we passed in different places. Hate crimes, right? Hate crimes bill, look for data but we do from time to time recognize what data is needed and task different agencies support and submissions with collecting that data so we can make best policy decisions. Anybody else? Thanks. Thank you. To get back to Bob's thought just as committee members to committee members having a discussion about the future in the best of all worlds, we would hope that our predecessors or the folks that follow after us would build on the work that we're doing because that makes the best sense. Now, we know things that make sense always don't happen but that being said, I would agree with you Bob. I mean, we've done some good work here we've taken some great testimony and this as a foundation is pretty monumental for Vermont because there's not a lot of states doing what we're going to attempt to do and this could be one of those pieces to the puzzle that helps bend the curve on Vermont being even more welcoming than it is today. And I really believe that, otherwise you couldn't get up in the morning if you couldn't hope that we're all working towards that same end. So that's just my thought. And we'll get there. Thank you. Sure. I guess going forward would certainly be my hope and Martin kind of touched on it that and I think coached it too that we ever did anything like this again around statistics and data gathering that we do follow a path because we had a path to follow, to start to follow from again, human services back a number of years ago and it didn't happen. And I think more by accident than anything we ended up doing some similar legislation. So I guess again going forward I would hope and there's no way to guarantee it again from legislature to legislature and you get 10 years apart doing something, 12 years apart, people are gone and people forget but that would be my hope that we can use this information gathering as a template of some kind. And if we do, it doesn't matter what committee I think committee does more similar legislation if we use it as a template. That wasn't as far as this bill to start for various reasons. And a lot of it had to do with how big the panels were in the boards and that type of thing. And I really think we did the right thing by knocking the board down from 20 to seven. Yeah, we were inclusive. I mean, we had everybody who was anybody potentially on the board, but if you think about it, I mean, we're a committee of 11 and that's a big committee in this building, 11. And if you go to things like judicial rules or nomination or retention and boards around the building that we have like that, they're five to seven, maybe a nine in there somewhere. But so I think seven is the right number to have a, you know, a good, robust conversation, you know, about the issues at hand. And I think with that list of liaisons, with who's on the board and that list of liaisons, I think all the information that we need to pass around is going to get to where it needs to go into our statistics database. So I just really think that's the right number. And as far as the other, I forget the name of the boards or commissions or whatever, but going from five to three, but if you look at things like a cannabis board or a liquor board and boards like that, there's three on there. And then I think the precedent has been set as far as a leadership, you know, a board goes for, you know, divisions or departments or whatever. And one thing I was really glad to see and maybe it happened before this and I didn't pick up on it. You know, it wasn't a big issue for me, but I know it was for some, is that this is back under the office of racial or not back under, it's now under the office of racial equity, you know, in the jurisdiction of Susanna. And I think that's a great thing. I think everybody needs somebody to oversee them, you know, especially if they don't make it. I don't think you can have boards or commissions and, you know, entities like that that don't have anybody to answer to. So, yeah, you know, along with knocking everything down, it's gonna cost us $260,000 less or something like that, which is kind of, I was gonna guess that's what it was gonna be by knocking off, you know, the two paid members of the board and a lot of the stipends. But again, I just think we did the right thing. I think it's gonna be a good streamlined product that we have and I think it's really gonna work better for efficiency. Well, I would entertain a motion to approve draft 6.1 of H546 and continue our discussion, but I was like, folks, are ready to vote? So? Give us a second. Okay. Thanks. Any more discussion? I guess from where I said, I just feel like we keep getting more and more information about the racial disparities that exist in our current system. And in my mind, this is a really important necessary step in order for us to be able to have a foundation of information that we can be working with so that we can build policy that can directly address the areas that we're experiencing the greatest disparities. And I feel like without something like what we have in front of us, we're just continuing to sort of stumble around in the dark and it's not working. So I'm excited about the bill that's in front of us and I look forward to voting in support of it. Yeah. And I remember council state governments saying, Vermont, you are a leader in doing this work. They are a leader and hope that other states would see this working and start doing the work in their states. Sure. So I mean, I'll reiterate that the racial data and disparity information is a critical part of this, but I don't want to lose the fact that this data is going to tell us a lot about our criminal justice system and not just with respect to racial disparities. By virtue of collecting this information, we're certainly going to find out about that, but we're going to find out how things are working in different courts throughout the state. We're going to find out how people are being diverted or not being diverted according to what kind of underlying offenses they are, in addition to the racial disparities that might be involved. And this is going to be a wealth of really important broad data for us to do our work, including critically, but any kind of disparities that the data will uncover. So we're very excited about the bill. Right. Yeah, I remember this morning when this is said, we live in a country that doesn't collect data. I was really, I don't know if other people heard that, but I think that was really interesting. And so Barbara. So for sure, over the years and recently, we have heard when we did the hearings to, it was a last biennium, we did hearings on this, a similar bill, right? And it's concerning and disturbing what's happening to people in our state. And so this bill is, you said so eloquently a moment ago, is going to be what we need to help sort of, help us to see how this is happening here because it's easy to not think it's happening here. And even in the meeting when CSG shared with us data, we had some of our colleagues in the Senate saying, oh, but like there is a mistake. Like you don't want to believe that this is happening. And yet this happening to our colleagues, our constituents. And so I'm really glad that our community is moving this. It's beyond time. And it's, it is what we need to help make change. Any, anybody else? Then the clerk shall commence to call the roll please. Colburn? Yes. Honolay? Yes. Postlat, yes. But I might change on the floor. LaLonde? Yes. Doppler? Yes. Norse? Yep. Noa? Yes. Rachelson? Yes. Christy? Yes. verdict? Yes. Brad? Yes. Thank you. Thank you. Thank you, everybody. Congratulations. Nice, nice work, everyone. Yeah, yeah. It's the end product. I can't even touch. Thank you. Thank you. All right. I did put the clerk's office on notice that we might have this reporter. Coach, sure. I'm not sure. For Martin. Martin, do you want to, do you want to share it? We can, we can do a, we can do a split script. Team. That sounds good, Cole. Yeah. I have some time because it'll go right to appropriations. Right. Correct? Yeah. Yeah. But I will, I think, so what, one of you will have to, I'll bring to, bring, you know, 6.1 to the, to the clerk's office. So Martin will do that since he's here, coach. And, great. Well, thank you. That was a lot, a lot of work. Appreciate it. Okay. One more thing. So do you have any news that's true? Should be on the community page as a forward email as well. Okay. Great. Yeah. So folks could, I think they'll be happy. I keep the numbers longer. 5.1 on today's committee. For sale? Well, yeah. Okay. Great. Yeah. Okay. 5.1. Okay. Great. 3.2, 5.1. Okay. So if folks could take a look at that, there are very few changes in there and we'll talk about it tomorrow, but I think most notable are the DUI went from 10 years to five years for the look back. There were some technical changes about removing the word, start putting the word in the ceiling. And I, yeah, so, so not much, but take a look at it. Amber has or we'll send it to the witnesses. But we do have it on our schedule for tomorrow afternoon. That's pretty physical copies for tomorrow morning. Great. Great. Sorry, where is the new draft? No, it's draft. Today's date under Michelle Child, I should say 5.1. Oh, yeah. Am I missing anything else? I'm gonna send you a draft later. Thank you. I appreciate it. Okay. Especially since we're done. Yeah, I can work on it. Okay. Great. Yeah. So, yeah. So we'll squeeze that in tomorrow as well. Selena, yes. Amber, did you say draft 5.1 for the ceiling bill? Yes. I'm just not seeing that on our page yet, but it could be just... I had to refresh. I'll meet you. What's that? I had to refresh. Yeah. I had to, I did refresh, but I'll try again. Okay. I'll go back to the link in the chat, telling you about the work. Well, we don't, yeah, let's not do it in the chat. Let's just keep refreshing and safely feel refreshed. Yeah, watch that. Yeah. Yeah. Yeah. Okay. Actually, if we could go up.


Is it possible for DeFi to exist without KYC-AML? Yes, not only is it possible, Mike, it wouldn't be DeFi if it had KYC-AML. No doubt, some people are going to try to hijack the whole concept of decentralized finance in order to introduce KYC-AML. But of course, KYC-AML really doesn't really fit into decentralized finance. Let's think about it. Know your customer. Who's you? Who's your customer? In DeFi, I'm not anyone's customer. And I don't have any customers if I've built a DeFi platform. The platform has customers and it doesn't really need to know anything about them because the trust doesn't depend on knowing the customers. And anti-money laundering regulations require the platform to behave without neutrality, without neutrality to source destination purpose and amount. And without neutrality, you're starting to centralize the power dynamic again because those who decide which purposes are permissible for every jurisdiction, those who decide who is vetted and who isn't vetted to participate in the financial services environment act as centralizing forces in the system and accumulate power. Of course, that will result in fragmentation because in different jurisdictions, different things are legal and illegal, which means that the system can no longer be borderless. Because you have to vet participants, that means the system can no longer be open. And of course, because you have to not permit certain types of activities, the system can no longer be censorship resistant. And of course, at that point, it's no longer DeFi. It's C-Fi. You've just recreated the banking system using a very complex programming language that few people today understand on an immature infrastructure. And the worst part is that you've reduced the actual functions of democratic oversight that you would have within free countries. So is it possible for DeFi to exist without KYC, AML? I would argue that it is not possible for DeFi to exist as DeFi with KYC, AML. But I bet you that is definitely a controversial opinion. I think one of the biggest functions of DeFi, especially for unbanking all of us or banking the impact, if you like, is the ability to remove the legacy mechanisms of exclusion, such as KYC, AML, that ultimately do not functionally serve the purposes they claim to serve, but result in untold misery for billions of people who are pushed outside of the financial system in order to offer a vague sense of safety to the uninformed and an enormous amount of power to those who control the levers of finance. KYC, AML is worse than useless. And introducing it into DeFi makes DeFi worse than useless also.


Rick, well, thanks for talking by the booth, if you could just maybe explain to us kind of your experience and your thoughts about our product and explain the background of your company a little bit and the size of your Wisp. Okay, well currently I'm with SOS Communications and we have probably 1,100 plus customers. We're sort of a small network expanding slowly.  And so with your new RF elements, the horns that we have here, I was able to take one sector and turn it into four sectors and offload a lot of extra customers off of one AP and spread them out over three different APs and tremendously gained a connection, signal strength, throughput and overall I've been very very satisfied with the product. What kind of ranges are you seeing with these horn antennas? Well with the 30 degree sector that we put up, I'm getting, I have customers that are at 8.4 miles, excellent size. What kind of CPEs? I'm using the Ubiquiti, Rocket, Nano Beams. Nano Beams, okay, cool cool cool. So as far as like the noise isolation and stuff, what kind of improvements are you seeing or not seeing with noise floor and stuff like this? Well before I pulled them up and was able to, and I used the Class A sectors from Ubiquiti, my noise floor was hitting around, it was good to see a 92 when I could see it but now that I've put these horns on, I'm seeing, I'm staying steady at 102 to 105 on the noise floor. It's been fantastic. Cool. And you've also used our carrier class sectors, right? I have. How are they working in conjunction with these horn antennas together? Well I've put up a new site after we did the testing with the horns and we were really excited about them. We put up another tower site and on that tower site I have two of the 90 degree sectors for close range inside for a high concentration of people and then I put the carrier class out in the country for where the people really far out. And I have customers hooked up at 10 miles away with it and I've already increased, that tower has been up for maybe a month and a half now and I've been able to move people around and I've already got 35 people on that tower and it's working, I have, here's the amazing thing about it, before I put the new equipment up I was having issues with the APs being overloaded and getting interference, latency, was trying to figure out what it was. And since I moved these customers over to the new tower and to the new APs, they don't have the drops, they don't have the latency, their speeds are what they're paying for and our service calls have actually gone down in that area. Right. So happy customers, huh? So we were having like maybe, we've dropped down to maybe two or three service calls a week or two weeks out of that area and right now I'm very impressed. And what do you think about our UltraDish? You have a point-to-point running with that. I do. I put my first UltraDish up as a point-to-point to feed this new tower and I have it at a, it's right at a six mile shot and I'm in the next fifties with that signal and doing my, looking at my charts and watching my traffic flow, it's easy to push 80 megs through that spot with 35 people on it. It's been awesome. Awesome. Cool. So if you were to kind of put it in a phrase or a couple of words, I mean what would you say, you know, is your thought of RF elements as a whole, you know, I mean, oh, what would you say? Well, I think it's the new design, it's been a long time coming. I'm sold on them. I gotta say this, I put stuff up on the towers myself, I do a lot of work. I can put three sectors up in the amount of time it takes me, it would take me to put one up of the other kind because I can put all three up at one time. Right. Awesome. Well, thanks for stopping by and using our product and we appreciate everything. Well, thank you for the opportunity, man, I look forward to doing business with you.


Hello and welcome, everyone. Welcome to Cloud Native Live, where we dive into the code behind Cloud Native. I'm Taylor D'Ulazal, a senior developer advocate at HashiCorp where I focus on all things infrastructure, application delivery, and developer experience. Every week, we bring a new set of presenters to showcase how to work with Cloud Native technologies, and you might notice where this seems like a rerun, but don't worry about that.  It should be fun. These people will build things, they will break things, and they will answer your questions. Join us Wednesdays at 11 a.m. Eastern Time. Today is a little bit later, but the rules were meant to be broken. This week, we have Jason Morgan and Catherine Paganini here to talk with us about the Cloud Native Glossary. This is an official live stream of the CNCF, and as such, it is subject to the CNCF Code of Conduct. Please do not add anything to the chat or questions that would be in violation of the Code of Conduct. Basically, please be excellent to one another, and be respectful of all your fellow participants and presenters. With that, I'd love to turn it over to Jason and Catherine to kick off today's presentation. With that, the stage is all yours. Well, hey folks, thanks so much for joining us. We're here today to talk to you about actually not technology or I guess only obliquely about technology and a little bit about words and what they mean and how we define them. Catherine, do you want to add anything? Sure. We're going to talk about the Cloud Native Glossary, and so I think we should probably get started about telling you a little bit about what it is and why we created it. Basically, it all started a little bit over a year ago when Jason and I launched the CNCF Business Value Subcommittee. We're both co-chairs there. The goal of the committee is to create resources that explain why and how Cloud Native Technology has such a big impact on the business. We want to explain that not for people without a technical background. If you're wondering why, you probably noticed that Cloud Native has become really mainstream or is becoming more and more mainstream, more and more people are getting touched by it. Just think of a decision of a company whether to migrate an application to a microservices architecture. That's a huge decision. It can cost millions of dollars, and it's not a decision that is made in the C-suite, not in the IT department, the C-suite is also involved. You have business people now having to make those decisions, and they have to understand what the heck all this Cloud Native stuff is. They need to get up to speed. But if you look out there, most content is really targeted for technologists, and that makes it really difficult to understand if you don't have a tech background. That's the why for the Business Value Subcommittee. When we started, we were thinking before we can do any of that, we have to agree on how we want to talk about terms. If we're talking about service mesh, what does it mean? Also, we don't want to be explaining all these things all over again. If we're writing an article about containers, we don't want to be explaining what containers is, and then in the next one, it's all over again. We realized, we need a glossary we can refer to. Although this all started like this thing we wanted to do before we could do what we actually wanted to do, it became so much more. While we were working on it, we really realized how valuable this resource could be. Now to the glossary. The goal is really to explain Cloud Native concepts, technology, and approaches in very easy and simple terms. We're using no tech jargon, no buzzwords, trying to use real-life examples, something anyone can relate to, like anyone who uses a smartphone, who uses a laptop, Wi-Fi, all these concepts of something that you can understand. And it turns out that explaining complex concepts in simple words is really, really hard. So it's really easy to fall back to industry terms. Because that's how everyone talks about it. So it requires a lot of discipline, and it is really incredibly rewarding too. At least for me, like I had, or I have no technical background. So for me, when I started learning about this, I really, really struggled understanding it. So for me, like knowing that people now that are in that position have something that they can kind of read and is easily inaccessible, that makes me really, really proud. So I'm really glad we did this. And yeah, Jason, do you wanna add anything to that? No, not a ton, Catherine. Like, so Catherine nailed it, right? Like, we started this business value meeting and we probably had like 20 folks on.  Well, engineering may be the stretch, but I've been doing computer work for about 20 years. And, you know, we just didn't, we didn't agree, we were all using words in different ways.  So let's, let's define stuff. And yeah, I hope folks like check it out. So they posted the links now in the chat. Post some links in the chat. There's a website, and that website's powered by GetRepo, and we'll talk about all that as we go. But please check it out. Yeah, Taylor, I've been, I'm a button presser. Professional, you know, an expert. Please don't try this at home. Like George Jensen. Yeah, it's just, just hopefully not a big road button in most cases. Awesome, awesome. Thank you. It's really helpful to be able to have a glossary and to not gloss over the details and the finer points of these things, I must say. It's, I think that it'd be helpful too for when trying to describe to friends and family members kind of like what you do, you know, now there's a resource for some of those terms and some of those things. So thank you, thank you both so much for really kicking this off and for making this happen. With that, I'd love to ask both of you, can we take a little bit of a tour through the glossary? Oh yeah, yeah, I'd love that. Do you mind if I chair a screen? None at all. All right, so I've got my handy dandy laser pointer. Drothamel, I'm sorry, I don't know how to say that name. But for, and not just for you, but for anyone, right? Like come check it out, we desperately want help, right? So there's about 50 terms in here in English. And thank you, Daniel. There's about 50 terms in here today in English. And one, you know, we'd appreciate folks to just review individual definitions. And if you like it or don't like it, you know, leave us a comment, well, maybe don't leave an issue if you like it, but leave an issue or send a PR if there's things that you need, that you think need fixed. Or if you want to define a new term, create an issue coming in. And we'll talk about that in a minute, but we would absolutely love your help. So without all that talking, if you go to glossary.cncf.io, you'll see this page. So this is our little welcome. Tells you what's going on, how to contribute some acknowledgements about all the folks that have done, done work to get us to where we are. And yeah, a little bit else. You can see we've got a style guide, which we can link to at the top eventually. There we go. Style guide, a little how to contribute guide. And then on the left, there's definitions. So let's take cloud computing, right? Like this was, every time I look at a definition, I get like a little bit of like flashback to what it was like to try and define this in the first place. So for every definition, we go through and we talk about what type of thing it is, right? So is it a concept? Is it a technology? Is it, I think we have a couple of other things and I don't remember what all the terms are, but there's essentially a couple of categories which your definition may lie in. And then for each definition, right? So to hit that target of, I can explain to someone that is not currently, you know, it's not just for business folks, it's anyone that is not currently indoctrinated in the language of cloud native, right? So I will answer that and I absolutely can't wait to have you help us with this. But, you know, for each one, we basically drop it into three categories. What is the thing that we're talking about? What is the intended problem space or the intended problem that we're trying to deal with? And then how does it help? Right, really simple. What's the thing? What's the problem? What does it do about the problem, right? And with that, we also are in the midst of building out a bunch of different languages. But I think, Catherine, we're gonna talk about that in a bit, right? I don't wanna spoil our flow. So this is the essential path. And then you can link to every individual definition and then you can link to individual sections within the definition. So we all got a little clicky link thing if you wanna go to that. That's the technical term by the way, clicky link thing. And back to you, Taylor. Awesome, thank you so much. I really like that you have that ability to kind of capture feedback and kind of get a sense of, you know, is there something we can improve here or is there something that we can get added? One question I have for you is why is it open source? Can you talk a little bit more about that? Sure, I mean, like first of all, we all know that technology is changing really, really fast, right? So having like a few people in charge of updating it would be like a huge burden, first of all. And so by inviting community to help and that becomes a lot easier. So that's one reason, but more importantly, we really believe that the end result will be a lot better if people collaborate, right? So Jason and I wrote a lot of definitions here, but are these the best definitions? Probably not, right? I mean, we put a lot of thought into it and we're probably more attached to some than to others, right? As always, but I mean, there are a lot of people out there that may have a better definition or can help improve the current one, right? So we really want this to be a living thing, something that grows and improves over time. And that's only feasible if you open it up to the community. And so open sourcing it was really like the right approach. Besides, it's also a lot of fun, right? People, you get to work with people all around the world, which is really exciting. And yeah, our community is still small, but we hope we can change that maybe today. And we hope to see it grow and get lots of engaged contributors. So we really welcome everyone on the call today to join, right? Jason, anything you would like to add? Yeah, so sorry, I just want to say hi. Hi, Simon. No, I don't have it. I don't have a ton to add, right? Like the goal of the business, so we set this business value committee and we're like, man, there's a ton of resources that you kind of need as you begin to address your market, whether it's for a project or for a company, right? And what we'd love to do is we'd love to generate, like as a group around the CNC, I'd love to generate some content that's just reusable, right? And that changes based on what people want, right? So we've got observability in here, right? And like I was nervous to define observability, right? It's a property. And like, if you look at it, there's like a ton of, folks have a bunch of different definitions for what this is, right? And some people are really passionate. So what we need is we need to be able to welcome changes from folks in the community, right? Like everyone's gonna be sharp on different things. And this can only really be authoritative if the community agrees on the definitions. And as someone that's been in tech for a while, I was like, well, I think the best way to make, to get a community, you know, crowdsource set of definitions is put it in Git and go that way. Yeah, so that's all I have to add. Sorry, Taylor, go ahead. Awesome, no, that's fantastic. And I think that it is nice to kind of be able to have that oversight from everyone and just kind of like say, does this look good? I know that there was a lot of, I was at KubeCon just at the end of this year here in LA. And I know that that was something, I went to one of the day zero events and talking about GitOps and just kind of those concerns and GitOpsCon. And they were, a lot of people were thrilled at the fact that there was that formal definition of what is GitOps? Because I know that a lot of people had different ideas and when we're able to all kind of unify and agree on what something means, then we're at, you know, that gives it that much more meaning and then people are able to take that and build with that. So again, you know, the words, the pen is mightier than the sword, these words have a lot of power and it's helpful to kind of align on those things. So again, thank you. This is, it's really nice to have that ability to connect with people in that way, awesome. So with that, speaking about people and teams and kind of aligning on language in many cases, why should someone contribute to the glossary, would you say? Yeah, so just before I see like people asking about Bengali and Urdu and so on, so we're gonna go about that. So I'm really excited because I'm actually more excited about like those more smaller languages because I think that would be really, really cool to see that all translated. So we're gonna come back to that in a minute but going back to your questions, why someone should contribute. So first of all, I really think it's really fun and rewarding, right?  And as I mentioned before, you get to interact with people around the world and that is especially true for the people who are working on the localization team because we have like a Slack channel where all the teams can interact as well. It is also a really good way to get started with open source without having to code, right? Like you don't really need to code to do this and it's still open source. Of course you do need to understand the concept, right? But like, I don't have, I cannot code but still I'm part of this project, right? So if you wanted to do this, this is basically your chance. You also really learn a lot because as I mentioned, like explaining these things in simple words is really, really hard. So you're testing your own language, your own knowledge, right? Like sometimes you think you know something until you have to really break it down. So it's a great, great exercise. And I think there is like a, isn't there like a saying about like the ultimate test of verifying your knowledge is when you're able to explain it to a child or something like that. So basically that's very similar. Take a complex term and explain it to someone in a way that someone with zero technical knowledge can understand. If you can do that, you really got it, right? Like if you don't, you're probably still kind of missing some little thing. So it's a really, really good exercise to test if you actually know what you think you know. Yeah, and then to expand, oh, I'm sorry, Taylor. No, no, no, go ahead. I was gonna say to expand on that when we talk about creating localized content in the particular native language or the particular language that you are comfortable with, right? Like so much technical content is like bias towards English. And like it's gotta be, like it's hard in English, right? To operate if you don't have a good understanding of what these terms mean. And like if English isn't your first language, right? Like having terms in your language defined by native speakers, you know, who are doing it in a way that's like culturally relevant to you is super valuable. So it's a great way to help. You know, one, if you're contributing English, great. Do it, we would love it. And if you can help localize and build definitions for your own language, right? Like you're setting up so many other people for success by doing it. So it said, you're doing something good for your community by adding terms here. At least I believe you are. I think that's something that is kind of, you know, when it comes to localization and adding in all these languages, that's a great point, Jason, is the fact that it has to kind of mean the same thing too, I would imagine, right? It's not like a quick translation where you plug it in and oh, okay, all of the words are now in this native language. It needs to be kind of tuned to capture the essence and the meaning of what is this thing, whether it be a concept or something else. So I think that that's a mad respect to the team for being able to kind of think about that and work through that. And I think it's something that not a lot of people realize is that, you know, as you go through that, as you go through those language changes, you need to keep that in mind as well. So really, really interesting. Cool, cool. One thing I'd add before we go on, we got really lucky early on. Leonardo Murillo, is that how I say his last name, Catherine? So Leonardo Murillo helped us kind of just be like, yo, folks, you need to be sure that you are focused on making it accessible to other languages. And he just, he set the stage for our ability to have this site and have all of the glossary terms think about localization at the absolute start. And so we're really thankful for the early work that he did to set us on the right path. That's fantastic. There's nothing like measuring twice and being able to cut once in that aspect for sure. I did see one question come in from Almus, so is this cluster related to general knowledge in software development or mostly related to cloud native items? And then I can read the part B of that question as well in a sec. Yeah, we're folk, it's cloud native glossary, so we're shooting for cloud native terms, but there's some stuff in here that's not cloud native specific cluster is defined. I think we have, yeah, we have bare metal machine defined. So a lot of these things are general, but we're starting with the lexicon of cloud native terms. Awesome, awesome. The next question in the part B of that question was how friendly is it towards people who are familiar with software development but in different fields or stacks? Example being this person is a backend developer trying to learn DevOps, Kubernetes, et cetera. Yeah, I'd say it, hopefully it's really friendly and if it's not raise an issue, right? So if you get into a term and you're like, this doesn't make any darn sense, raise an issue and let us know because it ought to be really accessible to you. Yeah, the goal is that anyone can understand it, right? With no technical background, with different technical background, anyone, right? Cause it's like, I mean, it's, yeah, it's getting more and more and more people and companies are adopting it and more and more people are really kind of getting in touch with it. So that's the goal. So yeah, as Jason said, if you stumble about across something that is not, does not comply with that, which I'm sure there are a few, please, please do raise an issue or improve it. And with that kind of talking about contributions, I did see a comment that came in and said, would it be great if we showed a contribute to in native language on the stream? One of the things is kind of looking at that in a more general sense. One question I have for you is, how can people contribute and what kinds of contributions are you looking for for this project? Yeah, so I can, I can start. So one go here, there's like literally like a how to contribute button right at the top, which we'll talk through, talk through the process. The other second best place, and I don't know if you'd be happy to share the link, but if you could reshare the glossary link. So it's CNCF slash glossary on GitHub. So I can't make that, make that any bigger. But this is mentioned inclusive naming initiatives. Oh, sorry, I'm gonna finish what I'm saying. And then I'll look at the questions. So here is the Git repo. You can see, well, one, the readme talks about how you get started, right? Or how you get started with the actual project. And then the issues here, we've got like an issue template. So as you go in here, you wanna raise an issue and this works from here. So again, if I'm here and I wanna report an issue, it brings me to create a new issue right away. And it actually gives it to you on the term. But if you go to an issue and you create a new issue, we've got a bunch of issue templates that specifically talk about what language you're doing. And for all the folks that started talking about, how do I set it up for my particular language if it's not already in here? Well, we've got this one form to initiate a new localization team. And to be clear, audience members, if you want, a stream specifically on how to set up a localization team and how to get started with your language, we can set that up. We don't have the, so we have, we had a new person come on as a maintainer and they're amazing and they're helping us do a great job with localization. And I'm scared to say their name because I say it incorrectly too often, but it's Sioco, Sioco, is that right, Catherine? Yeah, I think so. Great, so he's been incredible and we can do one specifically on how to get set up. But essentially what we need is three folks per language, three folks that know and trust each other and are able to look over their definitions together, right? And set up approval and then go through the process of initiating a localization team for your language. If you have questions in the Slack, we have a localization channel where we can connect you with like-minded folks who speak the same language as you and start rolling to get you a localization team in your language. But sorry, I strayed a bit just because I'd seen so much about localization. In general, you're gonna open an issue or you're gonna look at the particular content. Here under the content tab, we have the various languages by language code. So assuming you're in English because that's the only one that I contribute to. So when I go in here, I go into English, I pick the particular thing and then if I wanted to make a change, I could just create my own branch and actually, I could create my own branch and then I could actually make the changes that I want, submit a PR. For every PR, you'll see. Right, so yeah. So for every PR, assuming that this one's a good one, you'll get your little Netlify link. So you can see the actual version of it as you go. So you can see your changes as you go. So it's a fairly low stress thing. No one's gonna yell at you if you do something wrong, right? We're excited to take any contributions you've got. And if you need help, go into the Slack. Thank you, Sal, for posting that. There's a Glossary localizations Slack channel on the CNCF Slack. There's a Glossary channel, right? If you need help, let us know. We're eager to work with you. And if you've never done anything in Git, we even have some guides to how to get started using Git so you can do a PR, so you can raise an issue, all that stuff. To answer your question, Taylor. Absolutely, and one thing I saw too, I kind of liked that it has that following structure where it's Glossary and I can see Glossary localizations and then Glossary localizations and then the actual languages that are being worked on. So that makes it easier and easier to find as well. Cool, awesome. Really like how you have things set up too with all of the Git have issues and just trying to, it's clear that you're trying to make that accessible and kind of straightforward in terms of figuring out how to route different requests and things and not only request things, but actually file tickets and get some things added as well. But awesome. Cool. And to everyone who's watching today, if you have any questions, please feel free to throw them in the chat where you're viewing this and we'll be happy to answer things on that front as well. I did have one other question for you. You're also looking into translating the Glossary. How does that work and how can people kind of join in the effort there? I know we talked a little bit about that, but curious as to if you have a little bit more of information on that front. Yeah. I mean, first of all, we're super excited to have people come and I'm also super excited to see people now in the chat as well, because it's like that is really, really dear to us and we really wanna get this effort going. And so, as Jason already mentioned, there is a lot of content on Cloud Native out there in English, but most of the people in this world are not native speakers, English native speakers, right? So it's like, I mean, imagine learning Cloud Native concept in a foreign language, especially if it's not like, you're not super familiar with it. It's twice or three times as hard, right? So really making a Glossary accessible to anyone, anywhere is really something that we really wanna help to, right? So we do have the Glossary set up to have multiple languages and we have teams you may have seen already a little bit in the GitHub. We have currently teams working on translating into Korean, Hindi, Portuguese, Italian and Spanish and actually German just, they just kind of had like a little group today. So that is really excited. We have two volunteers from Nepalese. If anyone interested in Nepalese here, please join. And five of these teams have committed to try to get the 10 first terms translated by a KubeCon NA in October and have, that would be like the first mini versions of the Glossary. So yeah, hopefully we can get that going. So yeah, if anyone here is interested and we saw like some interest here of joining a current Glossary localization team or creating a new one, hop on the channel, the Glossary localization channel, the channel that Sal shared before and yeah, just let us know. As Jason mentioned, we are looking for three volunteers per language at least, but if you don't have someone like, I mean, there may be three people separately like watching this now and wanting to hop on the channel and maybe you can find each other or we can try to connect you if we know anyone. So hop on that channel if you're interested and it doesn't really matter if your language is spoken by less than a million people or a billion, right? Like if you have three volunteers and if you're passionate about this, demystifying all these concepts in your native language, you qualify, right? So please join us and yeah, we're gonna share all the channels again. And I think like we also have, we published a blog post yesterday where you can find all the information as well with which channels to join and so on. Anything you would like to add, Jason, anything I forgot about? No, I think you hit the nail on the head, right? We need three folks per language, right? Like our goal is not to have Catherine myself be folks that gate contributions from other languages, right? We want everyone, every language group to self-govern, self-defined terms, set their own names for the terms. Like we don't want you to just, I don't want you to go translate abstraction into Italian, right? Like I want whatever the appropriate Italian view of abstraction is, right? Whatever their term is, right? I'm sure you have an Italian word. I was gonna make a joke there, but I decided no. But whatever it is, we want them to be able to use their own wording, right? Not just abstraction, the Italian version, right? But instead, you're set up for it. And in general, just stay out of your way as you get to do it. And Slack is the best place to get in the loop. Absolutely agree. I did see one thing come in that said from Sal, consider coordinating this with a CNCF KubeCon hackathon and could potentially get a bunch of valuable localization commits from a group of developers. I agree. And that's a fun thing about open source, right? Is being able to kind of say, hey, I think we could do, we could make this better. We could do this thing. And to just kind of throw that out there and see it come together or work towards making it happen. So I agree. I'd really enjoy seeing that. I wasn't aware of the glossary myself until January this year. So really excited to see that this exists. I did have a couple of questions as well kind of around the project and just like the consumption of some of these terms. Do you know if there's a way to download this to PDF or I could see it looks like there's fuzzy search on the site. Are there any thoughts around other things in terms of not just localization specifically but any other ways that might help with accessibility or sharing this around or kind of any thoughts on some of the technical components or pieces behind the site that you all have thought of or have any come up. Yeah. So our first version of the glossary. So we released this originally at KubeCon EU, right? And I think we had 25 terms or 10, whatever it was. And our initial version was a PDF and we dropped that as quickly as we possibly could because it was, it just, it goes sale fast. It doesn't auto update and stuff. If, listen, if folks, you know here there's actually a link to view and download the PDF version you want to get it. I'm not sure that it auto generates but if this is something, everything in this project if you have an interest in seeing it be a certain way please, please help us and get involved and we want to get it. As long as we can build something, you know like with PDFs, if we can build a thing that auto generates a PDF so that it's always current when someone clicks a link, great, right? We'd love to, we'd love to see something like that. And again, I haven't even dug into the PDF function enough to know whether it's a static one or it's a new one every time. But anyway, so It's static. So. There we go. And it's old. It still has the 25 first one, so. Yeah. So that's an area that could use some improvement, right? So if you have, if you have an interest in it then we'd love to get your help so that we can make it look the way you want it to look. I saw someone asked about, you know the inclusive naming initiative, right? And I actually just Googled it while we were sitting around. Like, it's another one. So because the definitions are open source, right? If you see, if you see some language that is not correct or not appropriate, right? Like, let us know. Well, it's, I can tell you personally in English, Catherine and I will prioritize and it's like, hey, can we please remove this term and replace it with this one because this one sucks or is bad for some reason. Damn, right? Like we'd love to, love to get those things fixed. And I saw my tool, the tool, essentially you need three folks who speak the same language who are interested in developing some terms. And honestly, if you have that, go over here, raise a new issue and build a new localization team. And when you do it, it gives you this handy-dandy checklist of all the stuff you need to do, right? So there's a bunch in there. Yeah, if you don't have three yet, join the Slack channel, well, join it anyways, right? But there may be someone there who also wants to join a team and doesn't have their three volunteers there yet. So I think like during the Slack channel, if you're interested for sure, and yeah, like once you have the three, then you do the issue. But we'll try, I don't know, we cannot promise to connect you with all three, but we're gonna do whatever we can. Like if we're in the next live stream, like with the Nepalese one, I know they have two. So we'll try to let people know. So other people can just join you. Excellent. I do like, again, how it's, you've made this really accessible to be able to add things and kind of ask for things and work through adding to this glossary. I think one selfishly, I'd love to see at some point in time and love to pitch that at some point is pronunciations for things and then in specific languages. So we could, and maybe for CUBE CTL, Cuddle, Control, we can have a randomizer to just say one of those at some point in time too. Yeah, we avoid politics, religion and pronunciation of CUBE CTL. You're welcome. I bought CUBE Cuddle.com. So at some point in time, we need to make that something fun. I'll talk with a couple people about that, but awesome. Awesome. Wonderful. Well, we'd love to open it up to anyone that has any questions. Otherwise, are there any other things that are good to kind of keep in consideration with the glossary or are there any things that y'all have your minds on accomplishing within this first quarter or kind of like any immediate concerns that you might wanna share or talk about before we start to close things out? I think the focus for us right now is we feel like we have like the basis there, the foundation right now, we really wanna find more contributors, right? So that's now, yeah, we want it to really kind of grow and improve. So that's our focus now. And then like now building as well like the localization teams, right? Like we have several teams getting started, but of course nothing is there yet because it's just started. And so I think the focus of the next half year is really getting those mini versions started. And I can't wait to see like the little drop down in the languages and seeing all that. That like, yeah, it's really looking forward to that for sure. Yeah, no doubt our priority from now until KubeCon is get as many languages as possible to have 10 terms so that up in here or somewhere, you can just change the language, right? And go to what's appropriate, you know, that being said, if you're out there and you have some definitions, I would love to get some new definitions or to get some of the existing ones updated, right? But our Catherine and I's main focus is helping the localization teams as much as possible. So, so, sure, sure we are. Geez, I'm so sorry, I said your name. I'm almost certainly I said your name wrong, but they're saying that we have three members. Now we need to form a team in Slack and then create an issue on GitHub. So what you do is come into the Slack and just talk about like talk, just make sure that everyone, everyone joins the Glossary channel and the Glossary localization channel in Slack. And then yeah, go into the Glossary and raise an issue to raise a new issue to initiate a new localization team and get started. Like we're to be clear, right? We're early days and we're building out the localization process. So we'll need help to get, you know, to get the, you know, don't expect the whole process to be entirely seamless, but we'll do everything we can to get you ready to start writing terms in your own language. Yeah, and actually there is, if you go into Slack channel, there is like the meeting notes, Seo Kwon who is our maintainer who manages the whole process. Like he's the person who has done like a lot of the docs localization for Kubernetes. And so he has created all the steps and the processes that we need for the Glossary. And so you can read all in there. We're also first, like he's trying to do everything for Korean right now, testing it. So a lot of things may not go through right away. So we're testing that. And once we confirm that it's all working, it's gonna be the process. As Jason said, like it's early on. So we're still like, we still have to do our first one. So Korean is our kind of guinea pig right now. And so yeah, there are a lot of things that can be done, but yeah, you find all that information in there. So it's all working. And don't let any of the process things stop you, right? Like if you grab a Google doc and you and the people that you're working with can begin defining terms in a way that makes sense. Ideally have that format in general for most of these definitions that includes what it is, problem addresses, how it helps. That would go a long way. Make sure that you check out the style guide and an appropriate style guide for your language would be great. But again, you can start doing these definitions yourself. And then as the process moves out, you've got a bunch of them ready to go that y'all can review and submit yourselves, right? As we get going. Yeah, and just talking to the style. So we haven't updated that for a while, the how to contribute in style guide. So that's my priority in the next two weeks or so to update that. So it's gonna be more, they're gonna be more detailed. So check that again. And yeah, just as a recommendation, I wouldn't start right away with GitHub, right? Cause it's like, ideally you're gonna collaborate and like tweak each other's thing. So the way we started, we worked on the terms before we added them on GitHub was a Google doc. It's just like a lot easier because you're gonna be changing and updating and that's like very cumbersome on Google and GitHub. And once you have something you're happy with, then you can put it on there. Cause it's a very collaborative process and back and forth in general. So I think GitHub is kind of good when you're ready to have a really good sense of what you wanna add. And then you can tweak it from there, but yeah. Excellent, awesome. I did see Jonathan mentioned YouTube video cube control, the definitive pronunciation guide, absolutely agree. I'm sure that we'll start to see things drop on that front and wonderful. Thank you both so much for really just educating us today on the glossary, how to get involved, some of the things that are coming up with it and really just exciting to see that it's going to continue to kind of change shapes and add definitions and really help people out with understanding and being able to unite and align on what these things mean. Cool, with that, I didn't see too many more questions if they do, I'll be sure to raise them up here as we start to close out, but really would like to turn it over to both of you. Do you have any parting words of wisdom or anything that you would like to say in terms of kind of closing things out here? Well, I mean, just get started. So for me, it's just like, we really, really want people to get involved. So join us. It's a lot of fun.  I think that's super exciting, right? Like, I don't know. So again, it's a lot of fun. It's really rewarding when you see it up and running. If you're localizing it, you're really doing a huge favor to the community and your country. So yeah, I hope to see you all on first on the Slack and then seeing all these GitHub PRs coming in. I'd add to that, right? If you like the glossary, if you've been to the landscape lately, the cloud-native landscape, and you've seen this landscape guide button now, so there's a little guide, if you like things like this where you start to explain some of these terms, you start to make an impact on cloud-native stuff, but without an exclusive focus on the tech or on coding, right? If these things are interesting to you, come check out the CNCF Business Value Committee. We do some neat stuff. If you have something you're passionate about or a project that you're interested in doing that isn't necessarily scoped to one thing in the CNCF or is maybe not so code or tech exclusively focused, we'd love to help you make your idea a reality. Awesome, thank you both so much. And thank you, everyone, for joining the latest episode of Cloud Native Live today. It was really great to hear from Jason and Catherine about the cloud-native glossary, and I'd started undefined, but now I feel a lot more defined in my understanding of what the glossary is looking to do, so thank you both very much. We really love the interaction and questions from everyone in the audience, so thank you so much on that front. Next week, we will be joined by Diego Braga, who will present on from zero to production in less than one hour with Cradeo Platform Ops. With that, thank you for joining us today, and we will see you soon. Thanks, everyone. See you around.


Hello, this is Professor Steven Neshaba, and I'm here to help you out with installing a Python notebook on your Windows 7 machine. So what you want to do is take your browser and go to the Anaconda download site, which as you can see up here, it's anaconda.com slash download and what we want to do is go down and we want to install Python 3.6 so you'll click that download and it will start this now it might take you know some time and we've already downloaded that so we're going to cancel cancel that download and But you'll want to watch that and when it is downloaded in your download folder You'll see a that that application and now we're going to click on that application. That's the that's the installer and You'll see various prompts come by you like this The default place to Install is called anaconda 3 now. This also takes a little bit of time and we've already done that So we're going to cancel out out of that right now But when you do that Normally what will happen is another screen will show up, which is the registrations screen, which you you might want to fill out But we're going to go straight to how to launch the anaconda navigator, which as you can see was here in the in that in that window they are the start menu and You can see the icon. It says anaconda navigator. So we're going to click on the anaconda navigator and It'll take a little bit of time to do its initializing and And what happens is a lot of different applications will come up but the one that we want is the Jupiter notebook so you're going to click launch there and that's going to open up a window and a browser and That's going to open it up into your home directory there now We've actually already created a folder in that home directory called my notebook So if you click on that and we've actually created a simple program a Python notebook Which just says hello world, which the usual procedure is you shift enter to execute it and so it works And that's all fine. Now normally what you'll want to do when you're done with writing on a program like this is you'll want to save using that save icon and then The clean way to get out of it is to go to file and say close and halt.