Now, Nigeria and Zambia were deep in collaboration between the two countries, according to President Mohamedu Hari. The president's book confessed they are the state house in Abu Jawa receiving a special envoy of his Excellency, Edgar Changua Lungo. He said the two countries would explore further areas of collaboration for the good of the people and benefit of the African continent. The special envoy, Honorable Joseph Marlonji, who is Zambia's Minister of Foreign Affairs, felt Nigeria for her big brother role in ECOWAS and the African continent stressing that equity is when strong ones strengthen the weak ones.


The titles are doozy, it's very long, but what we're going to be talking about essentially is scaling and There's some lag, but basically there's two kinds of scaling vertical scaling, which is when you have a huge Machine and horizontal scaling when you spread the load between multiple machines So yeah scaling so basically I mean I can wing it without the slides by the time they come by so In this talk, well goals great. I want to conceptualize You know vertical and horizontal scaling I want to show you a cool new idea for a sharding scheme which has Atomic cross-shard transactions and we're going to explain exactly what that means and But more importantly what I want to do is demonstrate some research process or like hey, can we do this? There's a problem. There's a solution. Maybe it's at the dam that we need to go in our direction So can I restore the process and Generally what I want is to foster interest in this kind of research And I want I want people to collaborate with and and to work with me and with us optimism on this stuff because this is the kind of stuff We care about this is not something that's really on the roadmap It's a complete side quest and so like I said, this is a nerd snipe Like this is supposed to be brain candy super interesting stuff, but if you want to work on it, you should talk to me So like I said vertical scaling big machines horizontal scaling many machines spread the road and In terms of ethereum vertical scaling has been done by roll-ups right rope enable vertical scaling Because if you're valid here, you can validate the roll-up by validating the interim main chain There's only one extra assumption is that there is one honest L2 validators That can also supply data for the roll-up But the question is okay We can scale vertically and we can probably scale ethereum 10 times Maybe 100 times if we start pushing some buttons like scale database and things like that. What if we need extra scalability? And and there's multiple reasons we might want that so one is that Sure, we could like require a data center for L2 sequencers, but we want to have a healthy Validator network and not everybody can get a data center not even not even every company or every DAO So we might want to spread the road so that you can validate a subset really of the chain Our thing is that we might want many different roll-ups This might be roll-ups with different security assumptions and different parameters like different fee different pay tokens in a different Pay fees the different token increase the trial put change the value rules Maybe use a different VM all that stuff You might want to do but you might still want to have multiple roll-ups talking to one another Okay, so there's two main approaches to horizontal scalability one is prioritization and that approach You're gonna have a big blockchain lots of states and you can spread the road between machines Two options to do that Optimistic you just try to do things in parallel And you hope they don't touch the same state if they do you just throw away one of them and you start again if you do this the pitfall is that you can increase the throughput because Basically can't charge more for transactions are not parallelizable That's because you don't have a clear criteria of what is parallelizable and what is not Our option is to use what strict access list Some fancy people call this UTXO, but I think strict access list is clear and so basically That's shipping every transaction with a list of either all the contract date touches So you can have a lock on the contract or all the storage slots that touches so you can lock these specific storage slots the prioritization approach still assume that you have one entity that Validates everything Just now it's spreading things across cores and across machines So it's still a high cost and validators if you want to Reduce the load and validators you may want to do sharding and then values can value a single short So a short is basically a small sub blockchain The only thing with that that apps now need to think about On which short they want to deploy which might not be great But the great thing is that we can do it Eterogeneous roll-ups so like I said you can customize roll-ups to have different VMs different fee models and things like that And they can all talk to each other The problem with shortings that if there is no way for Shards to talk to one another in a way that is effective. This is a bad solution So I'll explain what you know an effective way means but as you guessed it from title. This is about atomic composability So this is an example I will use for a cross-shard transaction It's a transaction that swaps Bitcoin for either on chart a then bridges the ether to a short B And I'm sure be will buy an FT for either So this specifies a single transaction that you send either to a system or to short a depending on your architecture So one very desirable property is atomicity If any part of this reverts everything reverts and in this case in particular if you come by your NFT for either Then you also don't want to swap your Bitcoin for either Sometimes you can achieve this via application level atomicity but in this case it doesn't work because Sure, if you you know if you can't buy Your NFT for either you could swap back your either for Bitcoin But now you've paid to swap fees and you've been exposed to Bitcoin either volatility But there are sometimes cases where you can revert the action on chart a and if you can do that then you can do Okay, I Was standing in the wrong area so Yes, so in some case you can do application level atomicity if you can roll back the thing on chart a So what do we have today today? We don't have atomic composability, but between pretty much any pair of chains you can do Eventual delivery of messages. Okay, so imagine you have a chain a that chain be you can use systems like layer zero I think wormhole does this now mat to exchange messages between chains and What you you have is that the guarantee that if you do the action on chain a eventually you'll do the action on chain B Action on chain B can fail and there's nothing you can do about reversing the action on chain a That's what we have today. I just implemented ideally with lack lands and ZK proofs, but maybe you'll suck with all the multi-sig that happens so Getting to the fractal port of the talk we can do a little bit bearish roll-ups and especially with ZK roll-ups We can at least ensure a bound on this, right? This was eventual delivery could mean if I go back to a previous slide Could mean many blocks Sorry Didn't mean to do that. You could go back like many blocks in the future. Go forward my blocks What you could do is say well, we're gonna do this on the next block. Okay one scheme to do this use ZK roll-ups and so basically you have this architecture where You have a parent roll-up here ZK roll-up one and as child drops you keep up 11 and 12 and basically it's a fractal structure because the roll-up one rolls up to the layer one but the layer 11 and 12 they roll up to the to the roll-up one and If you assume that there is a ZK proof posted every single block then now what you can do is do Instant delivery transaction between Say this one 11 and one so for instance you could do your swap here and then buy your NFT here It's still not atomic because you can't reverse but now at least you know it's gonna be done like in the next block or one block apart That's good, but that's still not what we want So what about crush our atomicity? So I'm gonna propose a solution for this And then we're gonna assume that we're slicing our system into one blockchain block Which is gonna comprise one block for every chart so every chart advanced at the same rate and We want to have some form of atomic crush our transactions to enable this shard need to be able to send messages to other shards So let's just take the most nice possible idea which is eager interchart blocking So you just process all your transaction at some point you hit on to a transaction I want to send a message to our shard you just literally call that shard you wait for the answer and then you continue so This is Less crazy than it sounds and it's somewhat equivalent to what strict access list do because I do in the worst case You have the same throughput as a synchronous blockchain in theory But you can charge fees because you know exactly which transactions are crossing the shards The great thing is you don't need to specify the access list But the really really bad thing in practice not in theory is that you're assuming that all these shards are being validated by different Entities and so the latency to for one chart to talk to one other is really high And so in reality, there's not feasible because the latency will just kill any throughput that you might have Let's try to instead reduce the number of exchanges between shards Let's try to bound this very tightly And so the idea would be to divide the the block time into multiple slots in the first slot Every shard executes its own transactions and also collects messages to send to other shards In the second slot All the shards exchange the messages and then they run the messages that they receive Optionally, you can keep this going so you can have many many slots. You could say well messages can send our messages Etc etc. I think in practice, you don't really need this You can have a lot of expressivity with just like one hop just one short talking to one another short So this is still bounded message delivery though. You can't revert You can't revert part a if port B fails and that's because other Transaction rely on the result of the a part. Okay, so this is very unclear. So there's a graphic here So say I'm chain a I'm doing my local transactions I'm doing the a part of a cross-sharp transaction and let's say that's you know, that's a swap So both of these will be swapping and then on B. They will be buying an FT So this transaction here the a part depends on a part of the first one because the first one swapped Save it coin for either so it moved the price. So this one will use the price from from that was moved here So there is a dependency link and Because of this dependency link, you can just revert You can just revert this transaction if this one fails because this one uses the result so this is the problem that we're dealing with and The general property is that atomicity requires synchronicity basically Local transaction can still be processed separately, but we would like all the crushing transactions to be Executed as though it was a single person executing them right So we have a problem which is we don't want Chart to talk to each other too much so you shouldn't do that is to create a special shard I'm going to call it the atomic shard That will execute all the cross-sharp transactions And we have a second problem is that To execute all the cross-sharp transaction you need to state from all the shards, right? And this is this removes one of the big point of sharding which is that you can separate this the state between all the shards so The solution to that is to make the execution in the atomic shard stateless And that means you will supply all the state that's being accessed by the the transactions for that make sure So this sounds too good. So where's the poop? The poop is that you need to simulate transactions on on each shard in the early so In general in EVM given that you're not sure the state. It's impossible to collect all the storage slots accessed by a transaction You can approximate and the easiest way to approximate is just to run a Transaction against the current state and just assume that the transaction before it will not revert So, you know here It's easy. You just run the state of the first transaction against the state after all the local transactions for this one You just assume this wall this one will revert and execute and simulate But maybe it will revert. So maybe your simulation will be incorrect Our thing you can do is anything so you just Tell the shard well This transaction is gonna touch this slot or you can give him some logic to find all the slots are being touched And there's many ways to do this that can be explored it could just be some EVM code that just touches the slots It could be some kind of in protocol information or even out of protocol information That is not being validated, but that's being sent to the to the sequencers So I want to make things a little bit more clear. So here's a cross-shard transaction very abstract It computes things be on some state and the state might change, right? We're not exactly sure what is Then it's gonna send a message to short be and this message is gonna depend on the result of the computation That's message will have a result We're gonna compute something based on that result and we're also gonna send the results to start see and then do some more Computation, so this shows you like sort of the dependency we have right? We can depend on the results from one chart we can send to a short things that have been computed And so this will be important to understand there So to rephrase what I'm proposing Before we dig deeper into the problems like I've showed you only a small part of the poop a lot more poop coming up But the scheme is this phase one The short execute the local transaction and they simulate the cross-shard transaction When they do this, they will collect all the cross-shard messages and all the access storage slots in the face to we do the exchange and The short simulate the messages and similarly they collect all the storage slots in phase three all this In phase three all this stuff that we collected here and there we ship it to the atomic charge and This will atomically execute everything and normally it should have All the state needs and if it does and it will just basically fail to execute transactions So the big problem with this scheme is That the simulation restricts the expressivity Right, so we can only safely express Transaction where the simulation will be deterministic in some ways Because otherwise you you know the state might change and you might not be able to execute things So you might sometimes take the risk That transaction won't work say well, I'm gonna try if this says doesn't change is gonna succeed But if the state changes it's not gonna succeed We'll see that sometimes that doesn't work By the way, this is exactly the same problem as building strict access list or UTXO for slots Same thing you need to collect all the storage slots that have been accessed. So this problem is a pretty similar So the prime you know what it gets worse is that cross-shard messages may depend on uncertain states and We to derive all the messages during simulation and this way we want to be deterministic We can also Want an answer for a short and so we absolutely need to have a hint for the answer So let me illustrate because this is very abstract. So what I was saying was that this parameter here x Depends on the result of computation. So we need this to be always the same. Otherwise, we're just Asking the b-short to compute something that might not be what we want. So we absolutely need x to be to be known and You know that the message sends an answer and we're gonna send this answer actually directly to C So we absolutely need to know the answer already also I've actually illustrated this constraints. So Here we need the computation to be deterministic in the storage slots that accesses Here we actually need the computation to be deterministic. So they always return the same results Here if we use Y just in a computation We need to hint the results Approximately just to get a question, but if we send it to another chart, then we need to know exactly what Y is like no No guessing.  Is this a good idea? Are these restriction? Feasible, do they give us a powerful model that is useful in practice? Our question is can we statically guard against some some some cases of the non-deterministic execution that we want to avoid? Or do we just say well, it's a user responsibility and maybe some people will build some tools to detect some of these cases This is for sure a foot gun, right? Like if you're gonna make a crush our transaction and You don't expect it. You expect it to be deterministic, but isn't there's definitely there are lots of possibility to make bugs But is it worth the cost? Our question is what is the correct? Abstraction level for all this if we don't enshrine static checks We can simply add like a cross-short call opcode to the EVM and then just On the back end it will do what I explained But from the point of view of the EVM, there's just a new opcode This has been my presentation We have five minutes for questions. I'm sure some of you have burning questions You should have a lot of questions because this is very questionable And yeah, do you think sharding is maybe just fundamentally kind of impossible and like Kind of like when you're trying to do us like you have all these different systems It's almost like they shouldn't be able to interact in this way.  There's not a dumb question. Yeah in your model the Regarding the new opcode that is aware of sending message cross-sharding Does that mean like smart contracts need to be aware of calling another smart contract that is in another shard Yes, how do we envision those things and also in sharding without the new opcode our smart contracts being aware of Calling something that is in another shard because that brings Friction to smart contract developers So yeah, the model I've been assuming is the model of sharding as like small sub blockchains There are some proposals of sharding that I would classify under Paralelization you just pretend you have a big blockchain and then on the back end you just put things in shard and you move things around But for the user they don't see that here the model is explicitly you have multiple sub blockchains and they talk to each other This I think simplifies the implementation a lot, but not everybody agrees Actually my good colleague car does not entirely agree with that But that's at least my point of view and There are other advantages which is that you can have multiple roll-ups that do things slightly differently as I mentioned So that's an advantage Does it okay? So regarding the sharding in itself Is it possible for instance to imagine a system where the accounts would dynamically move across the shards to try to reduce as Much as can be the inter-shard Exchanges on so to simplify the whole process Or is it that completely different use? It's possible. I know there's research on this. I don't really know anything about it But yeah, I think this was more related to the models where you just like rebalance the shard and like you wouldn't necessarily be aware of the shards Yeah, it exists. It's definitely feasible. It wasn't really thought through here in this simple model Yeah, I think this sort of needs some like Like a balance chain where you have all your coins that will probably or at least have your balances be accessible by every shard I would support a simplified design a lot and in practice when we see Things like avalanche they have like a special like chain for like payments because it's so special and so important So that might be one part of the answer Hey, my other question was some could we use things such as like AI or sort of predictive behavior in Combination with this to sort of like just automatically optimize or is somebody working on on stuff like that to Sort of predict the interactions between the smart contracts and how to kind of optimize across charts I'm sure so people are working on it. I know I Know there's a bunch of research with that even on payment chains so things like Bitcoin and stuff I don't know why it was very hot academic like academics are like lagging behind the stuff We do a lot and they've been like very like I've been to a workshop this year And I'm very interested in exactly this problem, and I'm like does this change the smart contract or like no I'm like what's even the point like just put it on a big server and be done with it But yeah, you could do it sort of didn't assume that model here, but Okay, thank you very much


This is the question that first sparked the journey that I took to Complete the novel. What is this question? Why why was a young unknown Scottish writer in poor health? Hiking this remote road above Carmel Valley, California in 1879 and this was a hike that almost killed Robert Louis Stevenson the author of Kidnapped Treasure Island Jekyll and Hyde and many others This is a modern picture of that road Robinson Canyon Road above mid-valley It's full of like live oak chaperrill and in 1879 it looked pretty much the same I believe from old photos What was Stevenson 26 years old doing there? 5,000 miles from his Edinburgh home his parents were quite wealthy Well, this person had something to do with why he was there and she graces the cover of the book Her name was Fanny Osborne. She was San Franciscan at the time they met She's about 35 in this picture and she was studying art in France When just happened to be canoeing by was Robert Louis Stevenson who is about 11 years younger than her She was very unhappily married to an upstanding San Francisco citizen named Sam Osborne and Sam was a very handsome guy, but somewhat of a philanderer Don't have time to go into that at any rate. She got her children. She was a tough lady She got her children on a steamer in a roundabout way got herself to France in the mid 1870s to study art with the early Impressionists Stevenson described her look that she was about five feet tall When she looked at you he said it was like someone's citing down a pistol She was a tough tough woman and this was Stevenson and That's an actual sketch that Fanny made of him This one thing I like and I wanted to use this especially in talking about writing historical fiction I love images Fanny did that sketch shortly after she met Stevenson and I think it's a very affectionate sketch Here's the real guy You know and it's I mean it's it's close that's a photo but He was again young and so I turned this into the first scene of my book The two of them had met fallen in love. She was still married Had a husband in San Francisco all kinds of complications why this shouldn't work Okay, but nonetheless She decided to go back after falling in love with Stevenson to her family and try to make a go of it Partly for economic pressures and because of the kids, okay So I imagined that she did this sketch on the day that she was going to tell him She had to go home and this one minute reading here goes like this They walked out into the forest in the fountain blow and she sat down her easel She formed a rectangle with her fingers and considered Lewis through this frame Trying not to be distracted by the meadow behind them His face was oblong like a long stone hanging from an earring slight trifling almost but with unusual length from the eyebrows down to The chin long thin nose and beneath it the right grin that would be charming except the teeth were stained And a little bit crooked she would draw him with a lips closed a gentle mouth The boys really except for the thin mustache above it the nose a classic shape slender like the rest of him and the eyes Sensuous and unlike her husband's utterly without guile Are you certain that you are all right Fanny Lewis asked you look so sad She swallowed don't talk it distracts me She took up a pencil and quickly sketched his face and its features in rough proportion to what she observed Then she worked on the rest of him the big coat with its wide lapels that dwarfed his shoulders pleased her She added shading to suggest bulk until satisfied that her drawing captured the way He looked like a boy who had put on his father's coat The humor provided by the coat might counterbalance the haunting Strangeness of the thin face now to the hands he had propped one of them on a knee so that the fingers dangled downward Long lean and delicate. They were the fingers of a pianist or perhaps a monsieur Sinful fingers he smiled playfully. I saw that look Fanny Osborne What look just for an instant the grim look you've had all day gave way to a naughty grin Nonsense she dug in her purse for a cigarette paper and tobacco Lewis relaxed from his pose and they each rolled a cigarette Fanny realized that her hands were trembling So she held them to her sides while Lewis struck a match She wondered if the children were busy packing for the long trip home as she had asked Tell him now Lewis blew smoke to the wind and smiled. What are you thinking Fanny? She swallowed. I'm thinking we should finish the sketch So shortly after this sketch then in my fictionalized version of history She tells him and she takes the children gets on a boat and goes back to California Lewis spent a miserable year Living with the parents like a lot of 20-somethings do in Edinburgh And just scheming about how he was going to get to California and rekindle things with Fanny To do Write the book. I did some research a lot of research actually Luckily a lot of the sources are near us This was the Stevenson Museum in St. Helena where you know you can get vetted and as a scholar you can put on little white gloves and and Be allowed in to see Fanny scrapbook is there her photographs her letters You can look at her handwriting or the stationery she used I got a lot of insights into her character And also her kids and Lewis that way also Lewis published or Yale has published eight volumes of Lewis's Letters he was a beautiful letter writer and slap-dash handwriting. You can hardly understand his Hers is very neat. He also drew and doodled cartoons all over his letters, which I thought was really neat And that's my writing process Okay, so this journey took me to the Stevenson's home in Edinburgh 17 Harriet row. It's still a very Smart neighborhood. This was a view out of his parents bedroom So I have a scene that I wrote in his father's bedroom where very formally the father said What's the matter with you and he's confessed that he's fallen in love and he tells her it's with Mrs. Osborne and she lives in California and And so the father was adamantly opposed obviously, you know and But so Lewis had to sneak off when he made his escape and and spend a year in California And this is what he came to a downtown Monterey looked like this. It's quite a switch from Edinburgh In the 1870s it got a lot of great old photos at the California State Library in Sacramento and this is the Cottage that he Rented a room up around the upper right and this is about the way it looked like then now It's beautiful with boogan veal is and all kinds of things growing in the garden and the state parks runs the runs tours through there He camped out in Monterey, and I'll just complete the story right now because I'm gonna run out of time in a minute, but He stayed in that little unheeded room for about three months and He almost immediately went tapped on Fanny's door and proposed marriage and he looked like heck He had been on a steamer and then the transcontinental railroad and then a narrow gauge railroad and a wagon to get to her And he was very sick had sores on his face dirt on his clothes and will you marry me? And she said are you out of your mind? So She said actually she said something like Louis, you know you got to give me some time This is kind of a big one yeah, because he just showed up right and And so he said as long as it takes you and he stayed nearby He went to the Bohemia saloon in Monterey Which is a place where he told stories for a Nicholas story in order to support himself And then she moved back from Monterey where she had was with the kids again To San Francisco. This was the ferry building at around that time just a beehive I mean you couldn't drive over a bridge to get to San Francisco then So it was busier than it then it is now and those are omnibus's Horsepower to I don't believe their steam or cable powered, but That's what it would have looked like so several scenes are set there Bush Street where he spent the winter in a little tiny Apartment this is a you know the plaque on the current door, but the original house came down with the 06 earthquake That's 1906 Not to be a story wrecker, but the couple eventually about a year later honeymoon near an abandoned mine in Calistoga how romantic yeah in a miners cabin and that Little hole up there on the hill is the mineshaft where Lewis took it over and made it into his wine cellar and The two of them the cabin was right about there very remote and rugged But but they were happy then he took his blended family home to meet the parents And this is Braymar Scotland in the Highlands where my wife Esta and I Spend a week at the cottage Where to enter? entertain his stepson He started telling a continued story over tea and that story was about a Wooden-legged pirate long John Silver and and he just spooled this stuff out at night It came very easily to him He had been an essayist before then but to tell this 11-year-old boy a story was the easiest writing He did and that became of course treasure Island huge classic This was the home in which he worked This was a window to the room in which he sat it was off limits to where we were staying Downstairs because the owner lives in there, so he rented it out. He's an Aberdeen oil man now Treasure map This is actually my process. This is a Plotting board for my new novel about Jack London the top blue line is is Jack's Timeline and the bottom one coated in red is his second wife Charmaine So there's some really great parallels to this story, but in this case Jack was very unhappily married and had to find a way out of that Situation to marry the person he should have married in the first place whose name was Charmaine and So anyway, I worked on this in Vermont and Plotted it all out, and I'm slogging away, and I've gotten through a first draft. My time is up. This is an iconic picture of Jack in his favorite writing studio in Glen Allen Under the trees on a boulder and he is this is about the time he wrote Call of the Wild very hunky looking guy Fascinating person very different than Stevens and of course and this was Charmaine and Jack Now they were they're rich and famous living their dream and yachting around the world stopping in Waikiki And that's the way the way they looked in about 1907 And that's all my time. I've got some questions to pose, but oh my website if you want to see it That is a John Singer sergeant Mary knows something about him a portrait of Stevens and very famous portrait So thank you for listening and I'll turn it over to the next


Can you please turn on the microphones? I believe I'm on. Thank you and Have we confirmed that we have a quorum? Yes, we are supposed to have Virtual faces Hi, everyone. All right since you guys seem to be queued up here We will call the February 8th meeting of the architecture review board Intercession and if we can start with a roll call, please Steve Joe Clark here Marcus Savaglio Jerry Jones Richard Lindy Richard Lindy Pam Langen was going to be missing today Robert Heimerl also called in and indicated that he was not going to be here Charlie Wig Charlie Wig, so right now we have three and we need four for Anyone online that I missed as we put things on pause for a minute So it would come down to Charlie Charlie or dick Thank you, we do need to go to a commercial time out after all yes, is someone else joined the call Charlie hi Charlie excellent, and I believe that brings us to a quorum excellent. Thanks for calling in Charlie No, no problem no problem and with that we can get things rolling So I would ask everyone to please stand for the pledge of allegiance Indivisible It's always fun with the delay Item 1.3 is identification of any potential conflicts of interest with today's items anything from board members Hearing none. We will move on to item 1.4 approval of the minutes from Way back September 28th, and Steve can we just do that as a Thank you, do we need roll call for this or can we just do a voice vote we can do a voice vote All right, so we have a motion and a second if we got who Marcus and Charlie great. Thank you any further discussion Hearing none all those in favor signify by saying aye aye aye Opposed Minutes are approved. Thank you very much Brings us to item 3.1 the proposed construction of the new warehouse and salt shed by the Shepoegan area school district at the Horace man site And if you want to bring your team up and give a Quick introduction if you can use the podium mic just so that goes out to everyone We're on now Excellent. All right. Good afternoon. I'm at Wilfrid with Bray architects Joel Wulmer Shepoegan school district And then mark Miller is joining from Bray as well on the screen share a virtual option So good to see everybody today the proposal the proposal is to Construct it in approximately 9,000 square foot a storage warehouse with a detached salt shed This is replacing One to two buildings within the the district in the city as well So replacing one existing structure some rented space really consolidating maintenance and storage operations for the school district To one far more central location and definitely in a newer structure to where they're currently operating out of The location is really a relatively invisible Spot within the Horace man property Grade is about 15 16 feet lower where we'll be constructing the building from the closest Jason roadway of Georgia Avenue And really the the proposal is split-faced CMU base in the color roughly as Joe is holding up the darker brown color here The metal panel upper metal structure in more of a tan and then the accent trim color in the darker or gray to black Which is really generally in alignment with existing Horace man colors Don't have exact until we go through the process of acquiring the metal building but the general earth tone neutrals to blend into the landscape and I wouldn't say be complimentary but be similar in in tone and aesthetic to the Horace man middle school So again, we feel it's a good project through a variety of lenses and probably the biggest one is Freeing up a site which is in a dilapidating building that the district needs to move away from and We feel like this site and location was specifically selected to have the least visual impact possible on the neighbors to the property So we welcome any questions or thoughts you may have Great. Thank you. I Guess these are pretty simple straightforward Utilitarian buildings is the biggest questions. I had were on the actual materials and colors and how those Fit you you've verbally described that I guess I would ask that once those are set that you submit actual colored elevations with the materials To to staff just to confirm that everything looks good then Other than that, I guess to clarify for the rest of the board that there are some variances Being requested as part of this project, but that's not our purview plan. Commission will be dealing with those So we're really just looking at the aesthetics of the building in the proposed the location proposed And I do have a question Yes, please proceed between the building and the Tennis court is a major walkway to the back soccer field and During the season that area is constantly wet. Are you putting a sidewalk between that area? And where's the watershed from the building planning to go? the the existing Sidewalk that you're talking about is on the south side of the tennis courts. This building is going on the north side of the tennis courts. I Agree with you, but the major walkway The parents and the children always walk on the grass on the opposite side. They don't actually use the black top walkway that was Put in for the backfield Yeah, there will be sufficient room between the south face of the new building and the north face of the tennis courts to allow that Pedestrian float to work in general the storm water moves if I remember correctly from I'll say north to northeast Around to the west and southwest of the building and that drainage pattern will be Maintained with obviously some minor grade revisions to support the project, but that general movement of storm water will remain Looks like that's a about 20. It's about 20 feet Yep They're still going to be sufficient room for not only pedestrian movement But the district needs to maintain movement for lawn mowing equipment and other things through that location Charlie did that answer your question. There's no plan for a sidewalk or another Drainage to where the water flows between the trees in the new building There is a natural plan There is not a sidewalk planned, correct the drainage will be revised But it's not being done to specifically address the issue you referenced It's being done to make sure we can move storm water sufficiently around the new building It's not going to hold up my vote. I think it's a great project I just think it's something you guys could consider because it is the major traffic flow path for that field and Most parents usually walk away with my feet during the spring because of the excess water in the drainage ditch behind your building We'll mention tennis courts. It's sorry Charlie We'll mention that to the civil engineer make sure they've taken that into account and as always we've got the sidewalk and slightly the wrong Place should have been north instead of south. It sounds like Yeah 9,000 square feet of building that's a lot of water drainage So, you know, that was the one dry field that the younger children played on all the time because Soccer fields are always wet. There's always a drainage from there's always a worry about ruining the turf hence why you guys put in a big turf field, which is amazing But it's the one dry field that they continue to play on and now it's going to be gone So I just curious about the drains Issues that are in that area. Yeah, well just just to be clear We're not affecting any existing fields with this project. We're building over the top of what used to be sand volleyball courts Fair open green space, there's a bit of that affected agreed Because it was dry Thank you appreciate your insights Charlie, you know the site way better than the rest of us it sounds like Other questions or comments from the board This is Terry Jones I live one block over from the existing site that they store the sand and Assault that so I'm glad to see that I sort though The sooner the better and I live not too far from horsemen by consulate So I would make a motion to approve as presented subject to staff recommendations Second We have a motion and sec was that Marcus seconding Thank you. Any further discussion Hearing none, I think we probably need the roll call vote sounds good Joe Clark I Arcus of Aglio Jerry Jones and Charlie wake great that is approved Thanks, you good luck with playing Commission that brings us to item 3.2 The resubmittal of the exterior remodel proposed at a million dreams 1423 North 29 Gavin if you and your team could please give introductions and Tell us what's changing and why? I'm Angel Berry. I'm executive director and co-founder of a million dreams Gavin Dorsch with abacus architects, and I'll let her explain the reason for some of the resubmittal and then I will take any questions concerning materials and other building components So along with everybody else on the planet it seems like we had some hiccups with COVID At some of our funding it turned out to be not as deep as we had hoped So we went back to architecture and made some adjustments to the plan to cut those costs down So that we're not buried in in fundraising and we can move closer to getting this open faster Basically, we've taken out exterior wise. We've taken out some of the windows on 29th Street And we've changed the siding so we're we took out the steel siding and we're putting in vinyl Fiber cement whatever that is But the colors are all staying the same we've also eliminated at the kitchen edition which would be in our backyard on the backside And we've eliminated one of the the door overhangs in the back In about the same section that you're in right now and Move that extended one to the southern back door That's about it. I think okay Unfortunately, I think we can all relate with the issues that you're talking about Shame to see it not taken to quite the level that that it was previously But it still looks as if it's tidying up the property nicely putting it to good use So I really didn't have anything from my end any other questions or comments from the rest of the board We have a motion from Marcus and a second from Jerry, I believe Any further discussion? Hearing none Steve if you could do the roll call vote, please. That's good Joe Clark. Hi Marcus of Aglio Jerry Jones and Charlie Wigg It's like we are approved. Thank you very much. Congratulations. Thank you very much. Thank you. Good luck with the project Sounds good Thanks, Kevin Brings us to item 3.3 the proposed exterior renovation at Petro Center at 905 Indiana Avenue leave that applicant must be joining us remotely Yeah, I'm yes. I'm here Hey there, if you wouldn't mind giving a brief introduction and tell us a little bit about what you're proposing for the project Be happy to so this is a renovation of the existing building at 905 Indiana Avenue and the owner currently has a Kind of a abandoned Car wash at the rear of the building which you can see in the site plan there What he's looking at doing is converting that into a small restaurant space and As part of that doing a little bit of renovation to the exterior of the building So obviously putting in new windows and doors in the back car wash space, but then also looking at Adding to the exterior of paint scheme just to sort of unify that entire property There's opportunity along the street furniture to create some green space. So we're taking advantage of that as part of this But we think this will really clean up and make that site nice again Great. This is a another fairly straightforward one I think it was just the addition of a few windows that sort of kicked it from just a staff level approval to the board so Steve so everyone knows Again, what they're talking about is there was an old car wash portion. That's what they're taking a look at You can kind of see in Rendering that it shows the tables and the kitchen That it's presently vacant looks like they're going to do some improvements and quite a bit of painting too you can kind of see photos of the existing facility and There are some improvements that are taking place and Adam would you be Adam James is from vision architects He's who's presenting today. Could you just kind of indicate? What you're doing with the storefront and the paint scheme and the mansard and what's all actually taking place Yeah, sure can so the the exterior as you can see in the rendering there's We're the rear part of the building that used to be the car wash We're taking the overhead doors out and then we're adding in some storefront there And then there's a couple small windows on one side of the building that would be the I guess it would be the southwest side We've got a couple windows shown there The main access into the space to be both on the north and the south side again They're existing garage door open openings. We're just putting new storefront in there All of the existing mansards on the buildings for the architecture of the building all stays the same We're not proposing to change any of that What you're seeing in those renderings is really just an updated paint scheme So we've got a couple different shades of gray on there and then maintaining that red Accent along the top of the building the the existing buildings obviously a little tired I think what what you've done is Fairly simply just given it a new life Introducing a horizontal banding provides a nice ordering system for the building So nice to see it to get spruced up a little bit. I really didn't have any other questions or concerns other board members Questions comments from your end Mr. Chair, I've got one question. Are we really attached to that color at the top? It's it's a corporate branding color So we we just kind of stuck with what was there enough and What's going to be served in the restaurant? I'm excited to know Then in contact with the owner Jeff is with Sierra structures He could probably comment a little more on on what the food service is going to look like Good question, Marcus. You want to take that one? There we go. Yeah, it's going to be a restaurant grab and go Which is fish fry deep-fried appetizers And And I'm trying to remember if you're a little talked about the mechanicals and any changes to visibility of mechanical equipment We don't anticipate any They'd be on the roof and We're anticipating locating that far enough away from the parapets. It's not visible from the ground I guess with the dimension of the kitchen one thing that often comes up is that Exhaust requirement and whether that ends up being visible on an exterior wall or if that's also going up through the roof We would go through the roof on that.  I'd make a motion to approve at this point Right, we have a motion. Do we have a second? That was Jerry We have a motion and a second any further discussion Hearing none Steve if you could do the roll call, please Joe Clark I older person savaglio Jerry Jones and Charlie wigg super we are approved for item 3.3. Thank you very much And is it you? Same team presenting for 3.4 Yes The proposed new convenience store and service station at North 26 and Superior So again Adam. Are you? able to give us a brief description of that project, please I Sure can Again, this is another same same owner on this one, but this is a new service station fronting on superior You know with a new service station obviously there's a lot more flexibility and materials colors and things so We're excited about what we're presenting here. I think it'll be a nice addition To this this main kind of thoroughfare fronting If you look at the site plan, we've got 3,000 square foot building We've got a small trash enclosure on the east side kind of tucked back behind the building Jason to that. There's a spot for some stormwater management. So we're covering that on the site play out and then we've got a canopy a fuel canopy out in the center of the Site area with basically three pump islands on it We've got access shown off of Superior and then also the side street Jason to which I think is 26 And then we are also providing a pedestrian connection from that public sidewalk To the front door of the building The floor plan just an interior layout of this pretty typical of what you see maybe one Little nuance to this as we are proposing a small restaurant use in this as well so that's on the On the west side of the building and from an elevation standpoint We're showing something here. That's got a real contemporary modern look. I don't have anything for the red color. So I'm not trying to get all ready in the city of Sheboygan this Accent color on this one may change Depending on his partnership or the branding of the the service station. So depending on where that lands That that could potentially change but on this project this particular project. We're showing just a small amount of that As much as the last one You know, we've got a base of masonry on this building a good solid ground And then we've got some some paneling and things up on the upper facade portion of it Trying to keep it really crisp and really bright make it look clean and and and again very modern great that that will certainly be a change along superior So the the canopy and pumps I believe are a future submittal and really not part of what we're looking at today is outright Steve Correct. That's correct I think the drawings that you have before you in terms of the perspective give you an idea or a concept and I think I think there would be the ability if the board wanted to say hey You're headed in the right direction if you brought something in similar to that. I think that's something we would consider I do think that the pulse With the brickwork that matches our things that we've tried to see in other recent service station proposals and the colors matching so I think they're headed in the right direction, but They would need to bring that back at such time as they have a definitive answer on what direction they're heading Thank you for that clarification And yes, I would agree that what's shown in the renderings Seems to be that the right sort of direction of what we've been asking for on other similar projects So if that were to come back as shown That Probably good, but if there are any other thoughts or concerns from board members, please feel free to weigh in on that too But as we focus on the building there were just a few things that jumped out to me So I'll hop in on those first one was the the alignment of the tower in plan It's shown with that glass top piece wrapping the whole way around But then when you go to the plan That doesn't align with the wall layout for the division of the restaurant to the the rest of the space So it looks as if there must be something happening with a an interior soffit offset Between the wall and the glass up above And I'm is that something you can speak to Hi, it's probably just a Last-minute floor plan change that didn't work its way through the elevations. I think we would try to align those for simplicity okay that The transition there Could make for some kind of funky architecture inside But if the intent had been to have a display shelf or something that that would make sense But yes, it would be ideal if if you can't align it just that's losing space out of the sales area Second question was on that red band. I Personally don't have a problem with the color But the thickness shown it looks fairly thin like it's maybe an 8 to 10 inch tall band I'm just curious on the canopy projection part of it What you anticipate the structure being for that Being able to support it and shed water And remain that thin Yeah, more than likely what we would do there would be And I don't know that this has been completely decided yet But it would either be a sunshade so that it's not carrying Water or it would be something that was very minimal like, you know, a steel deck type canopy Okay, we've just seen in the past similar Items on submittals that then as you get through the detailing you realize that it has to be a lot thicker or it introduces Downspouts or other elements that just change the look a little bit So if anything does change from that that would need to come back as a resubmittal And then I think the last thing on my list was Without having a building section Not sure what the parapet height is around the perimeter that I believe you're using for screening the mechanicals What kind of parapet height are you looking at? I don't know that I have those on here, but we'd probably be in the neighborhood of two to three feet so I guess without that and sort of the Presumably some rooftop units in there to know what the line of sight would be Just wanting to make sure that those those units are sufficiently hidden from the street elevations Okay And as far as I'm concerned if that can be included on additional drawings to come back for staff To check at that level. I don't know that that would need to hold up the approval at this point But okay open for further discussion from the rest of the board What are you guys thinking other thoughts from your rent? Why are we separating the canopy from the building if you're proposing to build a gas station? You repeat the question Charlie You want me I can answer that Because US venture US oil Does the canopy and gas pump portion? For actual approval on the building and then the canopy is a separate company and a separate contract Need to feel like it should be a separate submit Just to clarify Charlie you're you're asking why it's a separate submittal rather than physically attached to the building Through the next the middle because the building for the Parcel is already done. It just seems like it should have been submitted at the same time Yeah, that was something we definitely talked about it. It sounds like it's two different contractors And that's why they put it in the perspective. You're right in terms of Coming in that was one of the reasons why I said that there's no question that before there's any type of Affirmate issuance that that needs to be in here so we can confirm that it is consistent with the Main building so you're right It would be nice to have it come in at the same time But based on what the applicants indicated to us. I said this is how they could proceed and how we would handle that They won't get building permits until both are approved That's correct. That's what you're saying That's at this point in time now now gentlemen Did you guys I'm assuming that the canopy is going to be coming in at about the same time Do you have any comments with regards to that? construction standpoint What we're presenting here is accurate But as far as the Timing of the canopy It should it should align With with whatever else we need to send in All right with that information I will be grudgingly second that even though there is a red line on it All right, we have a motion in a second any further discussion I would I would imagine you guys would not have any issues with the aspect of the applicant submitting the final drawings with the Specifics that were Addressed and that staff could review those and if there were any issues I could bring those back Is everyone in agreement with that amendment to the motion? Is that sufficiently recorded for the minutes that? Agreement that that does make sense so we are Going to vote on the the motion to approve With the final package of colors and materials coming back to staff for approval So with that if we could go to the roll call, please Joe Clark. Hi older person savaglio Jerry Jones Charlie wig Perfect, I think that gets us our approval so congratulations. Thank you very much for What looks as if it should be a nice building on that part of the superior Is plain Yes, and still yeah, I can come one of the things that I would just kind of For warn you guys is to you may want to take a look at some of the conditions and the staff report for tomorrow the owner Mr. Adakari does have some Miscellaneous items signage and different things that will be discussed at tomorrow's meeting so it may not be a bad idea to Read through that ahead of time because there will be discussion. All right. Thank you very much Any other items from the board to discuss before we adjourn? We could I have one Steve we would well be meeting there are items and we will be meeting and February 22nd Super And if I could get a motion for adjournment And a second and Just a voice call all those in favor aye Any opposed Then we are adjourned thank you very much everyone appreciate your time. Thanks you guys


Just one more time, okay? Mal, mal. It was to... I'm going to try again. I'm going to try again. I can't speak anymore. I can't speak any more. We wish... Again. One moment, one moment.


Thank you for speaking around after lunch. It's very rare to see a crowd after t-shirts have been given and food has been distributed. So it's a real pleasure, and I think it's a testament to what a successful day this is. We're now going to kick off a panel of what I deem an interesting kind. So we put this panel together with the intent of explaining to a lot of folks what the contributor experience is like. And we wanted to do it through a couple of lenses. So one of the things was to focus on people who have experience contributing to open source through their organizations. Experienced people, people who are new in the workforce, so new talent. And we also wanted to do a panel in response to some of the comments that we've seen in earlier sessions in the focus areas and the spotlight that was shined on the number of contributors in India rising and also a large fraction of these contributors being women contributors. And so we put together an all women panel. Of course, I am the open source sort of moderator voice, so I guess we made an exception. But that's our panel today for you. In terms of introductions, the world has known many women to come forward and be leaders at times of crisis. We know of stories globally. We know of stories from home about queens coming forward and taking the reins at times of crisis for their kingdoms. And closer to home in the technology realm, a lot of the first programming languages were developed by a lady named Ada Lovelace. A lot of other technologies like spread spectrum technology came from women innovators. And so it's not very common to have women at the helm of technology. And I guess with this whole wave of containerization and Kubernetes and things like that, it's all the more apparent recently. And so welcome everybody to today's panel. I will shut my mouth for a while now and allow our esteemed panelists to introduce themselves. Priyanka, you want to go first? Hey, everyone. My name is Priyanka Sagu. I work at SUSE as a Kubernetes integration engineer. And I do a few things in upstream Kubernetes project as well. Currently, I am the release lead for Kubernetes 1.29 cycle. And we are planning to release it on December 13 after a bit of delay. I'm also the technical lead for special interest group contributor experience. I'm also a GitHub admin for Kubernetes and sub-project organizations. And thank you for inviting me to the panel. Amruta? Hey, everyone. I am Amruta. I am a product engineer at InfraCloud Technologies. What I usually do is write custom controllers for different Kubernetes resources and play around with Kubernetes in that way. Apart from that, I've been contributing to a few open source projects, especially in the data protection space and storage. Hi, Ika. Yeah, hi, everyone. First of all, thanks a lot, Ram, for inviting me to this panel. And I'm Faiqan Sari. I'm currently a third year undergraduate student. I'm graduating in 2024. And I am a contributor to Kubernetes, apart from which I am a part of the release V1.29 of Kubernetes. I'm also a CNCF intern at Istio. And I am also one of the contributors for ETCD. And I contribute in various areas of Kubernetes, from being one of the summit staff lead for Kubernetes contributor summit to also being one of the maintainers for last week in Kubernetes development publications. So yeah, there are several areas that I contribute into Kubernetes. So as you can tell, there's people from different areas of contributions and things like that. And what I'd love to do for the next 20 odd minutes is dig into various aspects of what the contributor experience is like, what it has been like for you individually, and finally end with some takeaways for the folks that are here about how to get on board as a contributor in future. So Priyanka, talk to us a little bit about what exactly it means to be part of the Kubernetes 1.29 release in the capacity that you're in. So again, I'm the release lead for Kubernetes 129. But before I say anything else, nothing is possible in any release cycle without the amazing release team we have. So I have a team of 40 people, which in my capacity, I lead them. And apart from those 40 people, we have thousands and thousands of contributors who actually work on the actual release. So great shout out to every one of them. What I do is make sure we release on time or make sure we hit all the milestones. And this is my first time being in a leadership position of this kind, where I'm doing both project management and people management role. So that's what I do in my role. So when you say you have a team of 40, is this a team of 40 in SUSE that you manage, or is this like a Kubernetes? When I say I'm a Kubernetes release lead, that means the Kubernetes upstream release. So what do people, one of them is already on the stage, one of them is in the audience. I think I have a few more here. So 40 people are from around the globe. The team is divided into me as a release lead. I have four lead shadows. One of them was supposed to be a member of this panel as well. I have five role leads who in turn have shadows under them. So that's how we make this 40 people team. And all are from different parts of Kubernetes project itself. So Fahika, you want to add your perspective to this process? Yeah, definitely. So basically, like Priyanka is a release lead for the program that we are talking about. And my perspective to this is that this is a program which is your go-to point if you are looking forward to become a part of Kubernetes and looking for mentorship to contribute into Kubernetes. Since release shadow program is an itself a program that is made in order to let new contributors come in and learn the process of contributing. So like Priyanka is a lead, she also have been a shadow at some point like I am. And that is how you climb the ladder to becoming a core part of the Kubernetes releases. And so is there something specific that you contribute to the release process? Yeah, so Kubernetes release, there are several areas. I contributed to the nodes areas that is creating release nodes. But that's not the only area that we focus on. Since every release has lots of responsibility from doing code, release nodes, managing enhancements, and managing the communication between these different teams. So all of these areas comes up with their own responsibility. And there are mentors in all these areas and their mentees. These mentees are basically the shadows who work for the team. And the mentors guide them also to work towards a successful release. Speaking of consuming the work that you do, Amrita, you consume Kubernetes releases. But you also have contributions to your name. But to other projects, could you explain a little bit about what areas do you work on and what contributions do you? So I have been contributing to projects that are related to data protection. One of them is Canister. I've given a few talks on that as well. So it's a backup and restore solution for Kubernetes resources. So we deal with writing custom resources in Kubernetes, write controllers around it, how to do backup of these resources, and restore it. So we started off with a team of a couple of engineers which built it at the starting firm. They were one of the few engineers who started contributing to that project. And then later on, it's a big project that recently turned into a CNCF Sandbox project. So that is one of it. Other projects that I have contributed in my early stages of when I was onboarded to Kubernetes was Open Policy Agent, which is in security area for Kubernetes. So we write rego policies, which is a different language, again, to write different types of security policies on the different Kubernetes resources. So I contributed there as well. I played around with it first, that how it works and how I can try to find out issues over there. And then once I kind of hold off what it does, I look for some issues to start contributing to it, and then I picked up. So in terms of contributions itself, I'm sure that there's a lot of people who come forward, who start, but sort of fall off suddenly. And I'm not saying there's some magic special secret source somewhere, or it could be just personal hard work and dedication levels that you have. But could you share a little insight about what it is that helped you sustain, I mean helped you start and sustain as a contributor? And I'll start with you, Priyanka. So I also have my failure story. I started with Kubernetes. I think in 2020, late, I tried, did not work out, and I went back to whatever I was doing that time, because it was very overwhelming. I think it was a time when I was working on the project with people who were contributing to Kubernetes in all different capacities, like node, storage. And I, as a consumer of Kubernetes at that point of time, could not understand how storage worked outside of Kubernetes cluster. For me, it was a black box. This is a Kubernetes cluster, and that's it. I don't know how to take out node and work on it separately or storage. So when all these people used to talk about all these things in the room where I was sitting, well, it was extremely overwhelming, and I just gave up that time. But I realized that it's not just Kubernetes project, any open source project of this size. There is always a learning curve, and when you realize that is there, I think that's an enlightening moment. You know that it's not going to work out in day one or week one, or maybe month one as well, but spending that time is actually one of the requirements. You have to do some hard homework to even start reaching out to people in the project on what do you exactly want out of them. So that's what I did after six months. I think what helped me to come back to the Kubernetes project was my job. I switched to a company which was working more closer on Kubernetes kind of flavor of code. I would read those code, and then I came back to the project.  I went to him and I shared my interest, okay, I have worked on this, this, this thing. Do you think I can help you in some way? That was good. So I gave him exactly what I knew at that point of time, and he had some problems that he wanted help on, and I picked those things, and that's how I started. I can give another example. I was, I think one of the few things, first few things I did in Kubernetes project was contributing to the Python Kubernetes client. I joined one of their meeting for the very first time. I introduced myself as somebody who is sitting there trying to learn what the group is talking about, and I'm like, okay, I can pick up some beginner issue, and they gave me one issue which I could not understand, even though they had marked it as easy to understand or beginners. Okay, what I did, I think, I started looking at the documentation of the project and the examples they have in their repo. I started playing around what is working, what is not working, and I myself in that process realized there is so many other things that are not working, maybe I can start from there. So I took like a back turn, maybe a few steps back, just did minor documentation updates, minor example fixes of usage of Python client, and then went back to maybe retrying what I was actually assigned in the first place, and that's how I started. So there's always a learning curve to anything we are starting new with. Realizing that is the first thing that I would maybe share with anyone, just give some time. It is, if it is hard, or if it is looking like hard, actually maybe, not maybe, most times that is the case that it is hard. So, and that is hard for everyone, not just for that one person. So just understanding the technical perspective, for some people it might be like maybe few weeks, for some it might be a month, you have to understand the background from where they are coming. We really can't compare ourselves with people in the same room, because somebody maybe they are working on so many other things that right away helps them to get started with this other new project. So it really matters the background from where you are coming from, and also doing some homework before reaching out to people, because it helps you to narrow down your questions, what exactly you are looking for. One of the things I as a person who have spent some time in the Kubernetes project, I see people reach out to me with questions like, I want to start with Kubernetes project, can you help me? I really want to help them, but honestly speaking I don't know what are they really looking for. So it ends up being my work to actually talk to them and narrow down the scope of what exactly they are looking for, or sometimes it ends up me putting my opinions on them. So I really don't want to do that, most times I want people to find out what do they really want, because sometimes if I am working on something, maybe they do not like it, and they ask the blanket question and I really pointed them to that side and that was not the thing for them. So it's okay to try error and fail, but yeah, just doing some homework helps to narrow down those questions, and then you can reach out to anyone for help. Open source projects is the places where you will definitely find out these helps in many different ways. There's a lot to unpack in that answer. I'll come back to you about some specific questions. If you don't mind me interrupting. Amrita, do you want to share your first contribution story as well? Yeah. So when I started off, I had around six years of experience in different domain. So when I started off in Kubernetes, I was already, I already had a mindset, I already had an expertise in different domain. So to shift that mindset to how Kubernetes works. So when I started off Kubernetes, okay, I have to learn Cloud. Okay, then what do I have to learn more? Okay, I have to learn Docker. So it was like starting from scratch, like I'm a, like fresh out of college that I have to start on the things. So that was a difficult, I would say transition, that initially, okay, I need to start learning and there are younger people than me who know more about it. So that was a different, you can say fear, okay, they know more. I need to study, I need to be at a pace that I can converse with them as well. So I initially struggled, but later on when I got hold of things, when I started things, then yeah, I was a bit confident over there. Fika, your first contribution story might be somewhat different from theirs. Could you share that with us, please? Yeah, unlike Priyanka and Amrita, I started as a student. That was the most fun part of it because I was not liable to contribute to Kubernetes. I was not asked by my employers that you need to learn Kubernetes or anything. It was just a fun thing because I've already been a part of a lot of upstream community programs and initiatives like GitHub Campus Export, which are pretty exclusive. So I was a part of similar programs and that is where I knew the importance of contributing to open source and the visibility that it gets to you. So I always wanted to contribute to open source but starting into an open source project which took years to build is super overwhelming and for students though it is more overwhelming and anyone can sense that. So I started particularly, I had a lot of noise about Kubernetes and so I just started with a simple SIG which did not require a lot of technical skills. That was how I started. Now anyone when someone comes to me and asks how to contribute to Kubernetes, that is the answer that I give. Nobody has already figured it out or anything. You start doing things and that is how you figure out stuff. So in my case as well, I started contributing to non-technical aspects of thing that not like localization or anything, it was simply documentations and also contributing to the meetings. When people are discussing something, put your views in it. Ask people what is happening, simply ask them out. So that is what I used to do. I used to join regular calls at Contributor, Experience, Com, Steam and I used to take up the issues and areas that I know I can work or at least I can ask them or even if I think it is a little difficult for me to figure out, I know I will figure out a way by asking them. So that is how I was a little confident in myself that even if I'm giving a challenge, I'll take it up. So that was the confidence I held in myself. As a woman, if you speak, contributing to an area where there are lots of people and generally you see women in tech is a little low, the number is a little low. So that is one thing even I was having when I was contributing to kites but I had to keep my voice held high so that I am heard. That was one thing I always kept in my mind and I'm not below anyone. Even though I am a beginner, everyone was a beginner at some point. So that's how I started with kites. I started contributing to the weekly meetings. I joined the Slack channel. I used to read all the chats. I used to read all the documentation. I used to read a lot. So if you want to get started with contributing, read a lot, get a habit of reading. Read the Slack chat, read the keynotes from the meetings. So every open source project have their own weekly meetings decided. So all these weekly meetings have their own documents as well that they maintain, like weekly meeting notes. You just go through those notes, read what discussions are happening in these notes and if you find some area which is very confusing, ask that to one of the sub-project lead or something. That's what I did. So I went into those things. I read a lot of weekly meeting notes. I read the Slack chats. I read what the GitHub read me issues. Like Kubernetes, the best part of Kubernetes is the documentation. This is also one thing I highlighted at KubeCon Talk that though Kubernetes is overwhelming, but it has the best documentation any open source project can ever have. So documentation, reading the documents on GitHub of Kubernetes 6 is very important. So just go on GitHub, check Kubernetes, GitHub organization, read the documentation. You'll also figure out that it is very simple to contribute. But reading is important. You can't just go to someone on DM and say how to contribute. Don't do that. First, read yourself. Figure out a thing. If something is very, very specific, then you can definitely put it out to DMs. And if a question is good, you will definitely get your answer. But that's what happened with me. I got my answers after I figured out things. And that's how I became a regular contributor. Wonderful. So in everybody's contributor story, there's a lot of work done through self-initiative. Is there also a mentorship or a sponsorship angle to your story? Is there somebody who really helped you along this path, either at the beginning or in the middle or throughout, et cetera? Would you like to highlight some of that? It's very lucky if you find a mentor in the very initial phase, like someone who just gives you the path. But in general, if I say you find mentors, in my case, I found a mentor after becoming a very core part of the team. I contributed and that is where my mentors realized, oh, this is the person I should guide because I know this person is going very high. And that's how I found my mentor. So that was not a mentor initially, but with time, I did find lots of mentors who are so ready to guide me. And what kind of difference did that make to your contributor? Yeah, so when I have a mentor, now I am taking more structured approach to what I'm doing. Initially, things were not very clear for me. I was contributing to almost all the projects or all the issues that I came along with. I'm like, okay, I'll take up this, I'll take up this, I'll take up everything that I can do. She didn't a candy store. Yeah. But now I'm like, no, I'll only take up the, I'll only contribute in areas which I know I'm going to contribute to the larger aspects as well in the future. So now I pick up things which I know is going to help me and that is how mentors help me. That's nice. Priyanka, I know you've expressed a lot of interest in this topic too and you alluded to some mentorship experience before in your answer. Can you speak to that please? I, well yes, I had a lot of mentors along my journey and I actually want to add a bit, one more step to it, mentors and sponsors. So like FICA said, when you get mentors, they can help you structure, provide you a structured path to what you really, or maybe they can show you path and you can do whatever you want to do with that mentorship. I had mentors, I think very early on, I have a mentor sitting in the audience who have helped me even before. I was part of Kubernetes project before, I was part of any open source project and thank you, Maru, Jason, for that. What actually helped me beyond mentorship was sponsorship. So when people mentor, that's good, they are mentoring you, they are giving you guidelines to this, to that, and they are also giving you opportunities, but when people sponsor you, like when people vouch for you, when there is a requirement, vouch for you where you can grow, I think that is also a very big requirement and that happens a lot in Kubernetes project nowadays, especially in India. I don't know if Nikita is here, but Nikita Raghunath, I'm talking about one of the ex-staring person, current TOC, she has been a sponsor to me in many stages of my journey at Kubernetes. Which helped me to take a lot of leadership position. So I was working, I was contributing on a lot of things, like any other contributor, but she actually looked at that work and she vouched for me where there were opportunities to lead as well, where I can pass that on. So as a mentor, she also opened the path for me to pay it forward as a lead, as a person who has this capability or this platform where I can share what I have learned. So mentorship and sponsorship work like very much hand in hand. Priyanka, can you help us make the distinction a little more clear as to what exactly you mean by mentorship and what exactly you mean by sponsorship? Mentorship could mean one-on-one, like I am talking to you right now and I can give you like a documentation, follow this, but if, when sponsorship enters, that means when you are sitting with somebody else and now you know that is this opportunity opening up, I can vouch for them or I can sponsor them. That's where like sponsorship comes in the picture. So if, for example, let's say Fika is a lead somewhere and she knows she has to maybe take on two more people under her who could be next leads. So if she knows I have been working with her or she knows somebody who has been working with her and she wants to now sponsor them and take her role, that's sponsorship. So mentorship is important and sponsorship is important, but if they are together both in the same place, I think that works wonders. Got it. Amrita, I'm going to take a slightly different approach in your case in that from your story, I heard that there's a different kind of balance that you had to strike between work that you were doing and starting on open source stuff. So what was that like? Can you share that with the audience? Yeah. So when I started off contributing to open source, I didn't know that it is going to take more time than the working hours, but later on, after a couple of weeks, I realized that okay, I'm not able to contribute to it much even though I am a lot interested because of project work, then then there was a push from my side that okay, I need to work overtime, I need to maybe, if I'm interested, I'm passionate about it, I have to contribute on the weekends as well. So that is how I prepared my mind that okay, I have to give more hours if I want to do both of the tasks together, which one of them is of course, you're going to get recognition and a different type of profile that you're going to build and others, of course, your project work. Also, the organization I'm working is all supportive. They always encourage people to contribute to open source. So there's a lot of support from them as well. So yeah, that is how I feel. Nice. Again, I'm going to switch tracks once more and now I'd love to focus on some actionable answers and insights for the audience. Now there might be people who are very experienced with certain projects. There might be people who are just starting out fresh out of college and there might be students watching this or in the audience or who might have questions about how to get started becoming an open source contributor. So any word of advice about here's a way to get started based on your experience and based on the context that you have. I'll start with you Priyanka. So there are projects which offer structured mentorship or structured paths for on-boarding. I would not say Kubernetes is the best test there. But we have... So we have things to say on Cube Day, India, but okay. Yeah, like I am part of Contributex and that particular sake is responsible for improving the contributor experience and we take feedback whenever somebody comes to us. For example, I think two days back only I read this comment somewhere. We have this onboarding course, a text-based onboarding course on kubernetes.io and somebody gave a feedback. Yes, this was not helpful because they were looking for something specific and now we know that part is missing. So what I want to say is look, if there are structured onboarding process, look for those. Those are always the best opportunities. If somebody's in the audience is looking to start with Kubernetes, yes, we have a lot of mentorship opportunities. Even I actually become a technical leader as part of one of the mentorship cohorts. There was a mentorship cohort for SIG Contributex leads. I think there is a mentorship cohort for other projects like being reviewers for that project, being maintainers for that project. We have entire SIG, which is very much focused on documentation. They have different roles where they invite or they welcome a lot of people who can help them triage issues. So our SIG Contributex, sorry, SIG documentation repositories, they have issues like 700 open issues at this time. So we need help to triage them. We need help from people to actually add labels so that somebody who is interested can come and see them. So those kind of roles, named roles, named mentorship opportunities, if you find them, best way to get started with them. Another thing, like if you already have figured out this is one part of the project that you want to start with, the best thing you can do is look for the documentation. There is always a documentation. Maybe it's not the best piece of documentation and you can right away start with contributing to the documentation itself. For example, you are looking for something specific. I think your first contribution could be go back to the channel and tell them, oh, this piece is missing, and maybe create an issue or maybe create a PR right away, add that information. So look for documentation, go through those follow and try to understand the process, like Fika said, get involved, start involving talk. Maybe if I was one of the people who, when I started joining these meetings, I had nothing to contribute back. Like the people were talking about all these big things that I was not able to understand. Maybe that's okay, still okay. If you can't contribute anything, just join, sit in those meetings, be a silent listener. That is also part of your learning process, but don't leave it at that, start talking.  Say hello, just introduce yourself so that people know. Why are you there? And tell them in maybe one or two lines, this is what you are looking out. Why are you sitting there? Maybe you are just sitting there to understand anything about this thing. So when they actually know that this is why you are sitting in that room, and if they come across those opportunities, they will give you those opportunities. So I think just osmosis is also a very big thing. Being surrounding yourself with the people where you want to be in at some point, or surrounding yourself with the processes or project that you want to contribute to, I think that is also a big learning in itself. You will start, if not the exact thing that you are trying to do right away, maybe you will start grasping terminologies, maybe you will start grasping processes that people follow to do a certain thing, and you will have, definitely you will have some questions to ask and ask them. So yeah, getting involved, making use of the structured programs, if there are any documentation reading, Fika. Yeah, Fika, I'm going to throw this question to you with a slightly different flavor. Any word of advice on doing non-tech contributions? And what's a good way to get started on that? Because I believe open source contributions do not necessarily have to be about code only. And so anything that you can quickly share about that area. Yeah, every contribution in open source is huge. We've seen people like Divya Mohan who is particularly contributing to the non-technical side of things, but still leading so many aspects and so many people know about her. So talking about how to start with non-technical contributions, any of us can do, even people who are in the first year of their college can start with it. So if you want to begin with it, it's very simple, I guess, just join a Slack chat and Contributor Experience is particularly a channel in Kubernetes, and several other projects have similar channels where you can contribute into. Documentation is one of the way to contribute non-technically. Plus there are also programs like Kubernetes Contributor Summit or B8 Community Initiatives, these are the programs and ways in which you can contribute to the non-code expects to things. And in release teams, particularly we have is enhancements, communications, and release nodes which are a little non-technical aspects of things. They do involve a little bit tech, but it's not very technical. So any folk can just come and contribute. Amrita, your take on advice for people who want to get started. Yeah. So there are different programs as well, which is one of them is Outreachy, if you know about it. It is more specifically for underrepresented people. So if someone can go and ask for a mentorship over there, people can just, they look out for your story and how passionate you are, and you can start contributing to open source over there and also it's paid. So that's also a good thing over there. Apart from that, of course, you have to first figure out what area or expertise do you want to get into in any open source project. Okay, I want to target this area. I have interest in this area. Look out for projects in that area for open source. Start with small issues or just playing around with that project and then you can get started. Awesome.  So first of all, thank you Divya Mohan. Hopefully you watch this recording. She helped put this panel together and identify these wonderful speakers. Thank you Nikita and Dimms. It's impossible to have a conversation about contributors and contributor experience without having your names come up. So if you do watch this, we're all rooting for you. Thanks for all the awesome work that you've done. Big thanks to the CNCF and the Linux Foundation for their focus on diversity and inclusion. A lot of this is possible, especially the focus on underrepresented groups and things like that. It's phenomenal the amount of work that they're doing and the amount of focus that they do. I work with them personally on a lot of different events and things and I know the kind of focus that they bring into all this. Thank you all for taking the time to come here and share all of these insights and thank you all for listening to us. I hope you have a great day. Thank you.


What is up everybody, Jason here for JaspysCaseBrakes.com. We just sold out our last and only filler to give away the last 11 teams in Sterling. Pick your team number five. Now again, guys, this filler is a 2022 Capstone's one-pack break number 185. It's pretty simple, guys. Like our normal fillers, we'll do the break. We'll randomize the customer names teams to distribute the hits out. And then at the end, we will randomize only the names and the top 11 get a team there from the Dodgers down to the Rays, guys. I know, I'm like, it's felt like we've done these forever, right? Think about it. I mean, there's probably like, what? Maybe 12 packs a box? We probably only used like one case worth of Capstones with all these packs. Two cases at best. But I don't even know if we have any more cases actually. I think we only have boxes left. But that's still plenty. All right, so here we go, guys. Let's do the break first, though. Quick dice roll, three times. One, two, three. Chris, done a Chris. Two, three. Astros on the Nationals. All right, again, guys, obviously it's just a quick little pack filler. Not the craziest product either. So I'll let you see your teams for like 30 seconds, but no trading. Today I've seen a lot of memes of that. One guy getting recorded that they used for like Lord Voldemort memes were like, he was the best guy around. What about all the people he murdered? What murder? So like, that's the one I've been seeing a lot today. Some people will love AJ, some people will hate him. That's the life he lived, basically. Especially after the whole, the whole murder situation. He allegedly killed people. Let's do this. Super crazy here. Now let's switch the scenes. And again, top 11, get a team, guys. There's all the names again, original list. So you can click Dice Row, lucky number seven. One, two, three, four, five, six, and seven. Seven times, seven, seven. As you can see, Chris snuck in right there. Christopher at 10, Chris Eugene, Zach Christopher. Edward, Zach, Chris, Chris, and Chris. There you go, man. So I'm gonna put the whole list in the randomizer list here just to show you guys, obviously. But only the top 11 are gonna get a team. And congratulations, Chris. And you've got pretty much all the top teams in this. Dodgers, Angels, Mariners, Zach with the Rangers, Edward with the Mets, Christopher with the Cardinals, Zach with the Nationals, Eugene with the White Sox, Chris with the Tigers, Christopher, E with the Twins, and then Chris with the Rays. So thank you guys for getting in. Coming up next is the break itself.


This 2013 Chevy Camaro 2SS is stock number 12111Z. We are here at Summit Automotive in Fond du Lac, Wisconsin, you're new and use sports car headquarters. This 2013 Chevy Camaro is super clean. It has a 6.2 liter V8 engine, which pumps out 400 horsepower when it's paired up with the automatic transmission. This one has been fully safe and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off. And this car is 100% ready to go. Black clear coat is the color. We shoot all of our videos in 1080p, 60 frames per second. So if you have HD capabilities on your computer tablet, smartphone or television, turn them on right now because it is definitely your best way to check out the quality and condition of the car before seeing it in person. If you want to subscribe to our YouTube channel and the lower right hand part of screen is a subscribe button if you like the video, click that and then click the bell notifications. You'll get updated every day we do videos here at Summit Auto. Comes with the factory polished aluminum rims. They are in excellent shape. I didn't see any scuffs or scrapes on that one. And it has Pirelli P024545ZR20 tires. These tires have, I'd say probably about 60 to 70% of the tread left, maybe a little bit more as the Brembo breaks. Front fender is absolutely perfect. Didn't see any dents or dings on there. Has the HID headlamps, the LED running lights, factory fog lights, and the front bumper is in excellent condition on this car. Didn't see any scuffs, scrapes or cracks. The hood is in excellent shape. I didn't see any dents or dings on there. And the passenger side front fender looks really good as well. Passenger side rim, no scuffs, no scrapes. Very nice condition as well. As you go down this side of the car, you can see just how clean the body is, how reflective and mirror-like that paint is. And we take these HD videos so if you are far away or even if you're close by, just can't make the trip down but you're still interested in purchasing the vehicle, you can see the car, hear the car, and have confidence in what you're looking at before you even get here. So when you do get here, there is absolutely no surprises and you can make a smart and informed buying decision from the comfort of your own home. Very clean down that side. The rear quarter is an all-rock chip which can happen on these Camaros. It looks really good. This back rim is in excellent shape as well. And you can see just how much tread is left on those back tires. Coming around to the back of the vehicle. Rear bumper, excellent shape. Does have the backup parking sensors, deck lid spoiler, trunk lid is in nice shape as well. Back storage area is very clean. And I'll show you where the RPO codes are on these Camaros. This body style, they're back here. Feel free to pause that, make sure that this one has all the options that you're looking for. This car also has remote start on the key fob here. As we come around the driver's side just as clean as that passenger's side. And for full disclosure, this back rim absolutely perfect as well. So all four rims on this car are very, very nice. Driver's side door looks really good as well. Didn't see any dents or dings on that. Heated power mirrors inside the 2SS package. Gives you the black leather interior. Both of these front seats are heated. No rips, no tears on the seats. Back seats are in excellent shape as well. You get the latch child safety system for any child car seats you may want to put back here. And the carpeting is very clean as well. So we'll put this convertible top up in just a second. You get the silver trim on the doors and dash. And you can see it's actually a metallic trim on there. Pretty cool. Power windows, power locks, power mirrors and Boston premium sound system. We will hop inside, turn the ignition on so you can check out the miles and then the radio. This one has the heads up display as well. So you get the speedometer compass outside temp in the windshield. This car has 12,915 miles. You do get a compass display up there as well. Digital speedometer there as well. Instrument cluster is very nice and clean. Comes with the leather wrapped steering wheel. Bluetooth and audio controls on the right. Cruise controls on the left. You get the paddle shifters since this one has the automatic transmission. And you do get the SS logo on the bottom of the steering wheel. This one comes with the Chevy MyLink system, AM, FM and Sirius XM radio capabilities. It also has the factory navigation system on it. You do get your climate controls right there. Heated seat buttons. You get an oil temp, oil pressure, volts and trans temp gauge. Stability control, automatic six speed transmission. Passenger side floor mat and seat are in excellent condition. This car smells very clean inside. I don't think it's ever been smoked in. Has on-star capabilities in the rear view mirror and we'll put that, also home link buttons for your garage door security systems and lane systems. We'll put that power soft top up. I'll show you that that's working nicely. So goes a certain way and then you just grab the handle and turn it and then that locks it in. So we'll start it up and we'll also check out that soft top. Make sure there's no rips or anything in it. No check engine lights, nothing like that. Check out that soft top and then we'll take a look under the hood. Soft top is in excellent shape as you might have expected. It's really good. And we'll take a look under the hood. I would personally like to thank you for checking out the video today and hopefully from this HD video. You will have been able to tell just how clean this car is all the way around. You get the strut tower brace on there. Engine bay is very, very clean. It runs very smooth. Once again, this car has been fully safety and inspected by our service shop has a fresh oil and filter change. All the fluids have been checked and topped off and this car is 100% ready to go. There is your emissions sticker.  There are those HID headlamps, LED running lights. And I would highly recommend this car from a quality and condition standpoint and to see more pictures of this car or one of our other 450 new and used cars, trucks, SUVs, minivans, wranglers, Camaros, Corvettes, challengers, Chargers, Mustangs, GT500s. You name it, we gotta go to that website right there, www.summitauto.com. Full pictures and descriptions of every single vehicle from two locations all at summitauto.com. And if you'd like to check out more HD videos, you can go to youtube.com slash summitauto. Remember to like, subscribe and share on this video and all the videos that you see there. In fact, in a second you will see a link to subscribe to our YouTube channel in the upper left. A link to more Camaro videos like this one in the upper right. A link to this vehicle on our website in the lower left and a link to one of our latest YouTube videos in the lower right. Click those, check us out. Remember to hit like, subscribe, share. Click those bell notifications to get updates daily. And we really look forward to helping you with this super clean 2013 Chevy Camaro 2SS black convertible. Thanks again for checking out the video.