 Oops. So, hi, I'm Helena. I work with the Open Infra Foundation and I work for the foundation on behalf, or I manage all the user groups on behalf of the foundation, one of those being the Canada user groups. I'm in Texas, so I manage those ones a lot more heavily by putting on meetups and stuff here. And then I assist with any other user groups who are trying to put on meetups or Open Infra Days in helping them find sponsorships, speakers, that kind of stuff, marketing promotion, whatnot. So for our agenda today, we're for a soft welcome message. Hi, I'm Helena. We've been there, done this already. And then after that, I'm gonna hand it over to Bruce from Wind River, who will do an introduction to the Starling X project. And then on to Bruno with Oncora, who will do a navigating Starling X, a practical guide to the community contributions and oops, sorry, I can't go back. Yes, so then I'll hand it to Bruno, sorry about that. The next thing is we're just four weeks away from the Open Infra Summit that's happening in Canada and Vancouver and registration is still on for that and the Starling X project will be heavily represented at the summit. We'll have representatives from Wind River, Oncora, and Austin and Brook University in Germany who all have sessions going on. On the right side of the screen, you can see the agenda that includes all the Starling X talks included in there is the Starling X hands-on workshop. So if you're new to the project and wanna learn how to get started in it, this is a good place to start. There is an RSVP list for that hands-on workshop. Just keep in mind to make sure you put your name on that list. However, it is included in your summit ticket. It's not a separate purchase or anything. And also the Starling X community will be meeting at the PTG, which will be onsite at the summit. As I mentioned, we will have Wind River present at the summit. So there are headline sponsors and you can go visit their booth and talk to some of the folks from there to learn more about the Starling X as well. The other thing going on is this year we will be featuring a hiring event. So if you're looking for a new career in open source technology, we have all these companies and more who will be there ready to talk to you about your career in open source technology. And that's all I had in terms of community updates. I'll drop a couple of links in the chat for some of the things I talked about if you're interested, including the link to the Starling X project website. And I'll hand it on over to Bruce. Thank you. Let me find the screen sharing button. So my name is Bruce Jones. I was one of the original founders of the Starling X project. I was project manager for the project before we even came up with the name of Starling X and worked on it for a while, had the privilege of serving the technical steering committee and then Intel's priorities changed and I can talk about that a little bit if there's interest in that and I moved on to other things. And as a perfect example of why you should never burn a bridge in the industry, I'm now back working on the Starling X community again and very glad to be here. We're here celebrating the fifth anniversary of the project this year, which is pretty cool. One of the questions, and this actually, this was a very urgent issue back in the day. Why is this called Starling X? Where did we get that name? And we had planned to call it something else and our plans changed drastically at the last minute and one of our executives said, well, Starlings do this cool thing called murmuration where the huge flock of birds moves as one without any communication, without any coordination between the birds. They just automatically somehow know where to go so the only birds that do that. So we decided to name the project after these cool birds and we put an X on the name because at the time all the cool edge-related projects had an X on their name. So we wanted to make sure people understood that we were edgy and cool. So what Starling X is, and I'll talk about a little bit how we got here, is a complete stack of everything you need to deploy systems at scale at the edge, manage those systems at the edge, manage the workloads at the edge. It comes with the Yachto kernel. A lot of our users today are using real-time operating systems for ultra-high performance. We have a set of our own services that run on the platform. We deploy Kubernetes and then we deploy containerized versions of OpenStack services should you decide that you'd like to run both Kubernetes and OpenStack workloads. The goals here are to keep the system easy to manage, although it is a big complex system so easy management is relative. We want to try to automate everything that happens. I'll talk about some examples of some of the automation in a minute. And we've taken the project from an open-source project to being deployed on major networks of major service providers in the world. If your phone is on Verizon, there's a pretty good chance that your call is being routed through nodes that are running Starling X. I just switched my phone to Verizon so I could say that I support our customer. We started the project in October of 2018. At the time, it was entirely OpenStack based on bare metal. The second release of the project, we moved to Kubernetes bare metal with containerized OpenStack on top. The following releases, we were doing two releases a year. We tried to follow the open infrastructure OpenStack release model, but we don't necessarily try to align with the cadence. So we just try to release twice a year to the community. And the folks at Wind River at the time were very focused on Telco Edge and on the Intel side where I was working at this time, we were talking to a number of big industrial customers. And what we found out was that Intel's not in the right business to service software to big industrial customers. So while Starling was very, very compelling as a solution and we have quotes from some of the executives at some of these big enormous companies that I'm sure you heard of, because Intel was not in the software business and could not and would not sign long-term support contracts, we found that our customers were adopting other solutions because over time, Intel chose to wind down their investments on the project. Now, there are still Intel people working on Starling X, but they're working down at the network level for the most part on network drivers and helping us adopt the Intel operators for high-performance networking and for our customer's use cases. I'm going to stop. Are there any questions from anybody here? It's all perfectly sensible. Bruno's nodding his head, so thank you, Bruno. So there's a lot of different ways to deploy Starling X today. It all starts by picking up a pre-built ISO image from the community, which they're all published, all the release images are out there and published and available. And you simply boot that up on the system that you want to be controller zero. And you tell that system then, well, I want to just run on this one system and then all of the control functions, all of the services, all of the storage, all of the workloads will all run in this configuration that we call all-in-one simplex. So it's one server, every single function of the entire stack is running. You can also, when you deploy on that first controller, you can say, well, I want to do a high availability deployment. I have two systems. So I'll have two controllers. I'll split the storage and the workers between them. However, the current architecture for the HA deployment is active standby. So really the high availability solution is when the desire is for high availability, a very high degree of availability and software and hardware redundancy and not because you want twice the amount of computing resources because you're only really running on one of the systems at a time. The third configuration is what we call a standard configuration. That is multiple control nodes, as many storage nodes as you would like to have and then as many worker nodes that work in computing resources can provide you. And this is a typical private cloud kind of environment. But the really interesting case and the one that we as the community work on the most is the distributed edge. So in the distributed edge deployment, you can have one central cloud which could be any kind of the three deployments. And then you can have hundreds and hundreds and hundreds of other distributed edge nodes that could also be any one of the other deployments. So if you wanted to deploy a thousand simplex systems to sit at the base of your cell phone towers, you can do that. And if you wanted to deploy all kinds of private clouds using a large standard configuration, you could do that as well. And you can manage all of those systems from one dashboard. You can push software updates to all of those systems from one dashboard. You can see alarms and logs from all of those systems. And the other interesting thing is since each of those edge nodes is itself a full deployment, if connectivity between the central cloud and the edge is lost, the work continues. So if you have Kubernetes, you still have your OpenStack services, all your other platform level services continue to run on the edge node, you can't manage or change anything from the central cloud until connectivity is restored. But this is a very robust solution and we find that a lot of our users are very interested in it. So I mentioned Verizon as a customer. These are commercial customers, but they are using 100% Starling X software in these deployments. And there's three of the biggest telephone companies on the planet right now have active production deployments of Starling X. There are other use cases we've looked at. In my time at Intel, I spent a lot of time talking to industrial teams. There's some capabilities of Starling that are very interesting there. In particular, the real-time kernel is very interesting. The other interesting thing about Starling is that the footprint on the nodes is very small. So all of the services, everything that needs to run to allow the platform to operate and manage can run today on two cores of a platform. And we're working very hard to get that down to one core. Now, the big, huge sapphire rapids core that are not cheap, but everything you need to operate your distributed edge nodes can run on one core of one sapphire rapids machine. So the overhead for the system at runtime is relatively small. So I didn't know this was a buildout slide. I'm just going to build the whole thing out. What we see right now is that the telcos are very far into their deployment of applications with containers and Kubernetes. And none of the current users, the big commercial users of Starling are running OpenStack at this time. However, they are scaling out to some pretty large numbers. So we are talking to users who are planning on deploying 50,000 RUs, which is a radio unit, something again, that sits at the bottom of the cell phone tower. And they'll be managing that with a number of central clouds. And as I mentioned earlier, everything you do needs to be completely automated. So all of the provisioning is zero touch. It all depends on connectivity over the IPMI or BMC bus. So we're really kind of leveraging server class hardware here. It is possible to run Starling on smaller platforms without BMC. We did that while we were at Intel. I don't know if that's still supported today. Bruno may know the answer to that. So a couple of the things happened in the past that I think I want to highlight here is really, really cool changes that happened. The original version of Starling that we released in 2018 was essentially a giant fork of CentOS. And the community worked really, really hard to get rid of the forks so that there's no more carried patches. There was a huge effort early in the community to get the patches down from 1400 to today, I think I can count the number of patches we carry on the fingers of one hand. And the other thing that happened was that we moved the software from a CentOS user space to a Debian user space. So we're using Debian for user space and the operating system. We're using Debian images in our containers. Of course, most of our containers we just take from upstream projects, but where we have to build containers, we just use Debian. Again, we're using a Yachto kernel because it has excellent support for the real-time kernel. And the transition from Debian is something we tried to do to Debian, we tried to do while we were at Intel. It was very, very challenging and my hats off to the team and kudos for them for managing the transition from CentOS, which is end-of-life a few years ago to Debian, you know, a fully-featured, fully-functional, well-supported operating system in just about two years. It's a huge accomplishment. So what we're doing next, we're working on planning for the next release. This is the link to the PTG, which has a link in it to the spreadsheet we're using to talk about all the features we're planning. As I mentioned earlier, we're following the open infrastructure slash open stack development methodology. We're not following the cadence. We didn't, you know, we wanted to make our own way, I guess, as a community. We declared milestone one for Starling X9 in April. We expect to declare milestone two in the next couple of weeks. And we invite anyone who's in Vancouver at the summit to come find us and talk to us. We'd love to hear from you all. And just a last page, if you want to communicate with us, we do have an IRC server and a presence there. I don't think there's a lot of people using that anymore. I think the best way to reach us on the Starling X project is through the mailing list, which we all in the community get. We also hold weekly Zoom calls for the overall project for the technical steering committee and for some of the sub projects. We'd love to hear from you all at any time. Any questions, please reach out to us. And that's all I had, Alina. Hey, Bruce. Hey, Steve. Yeah, I'm not going to chop that easy. So can we go back? You talked about Starling X and its intersection with Telco, right? And you had the one slide showing the other use cases. Is there anything preventing or are there insights into what it would take to adopt Starling X into any of those other boxes? What's the state of Starling X relative to those? And if anybody listening today or in the future has a video use case or a medical use case, what's the potential intersection of using Starling X for them? I think that, I mean, obviously there's a couple of things that I think, frankly, shouldn't be on this chart. Autonomous vehicles and drones in particular. If you're a Starling X worker node and you suddenly go off the network, we're just going to think you're down, right? We can't reach you then you're gone and we're sorry. So we rely on not only constant connectivity, but relatively high speed connectivity. The services, Kubernetes, OpenStack, our own services are all generating heartbeats and reaching out to each other. Are you still there? Yeah, I'm okay. I'm okay. All of that stuff. I think that for me, since I spent two years working with industrial customers, that that would be one of the ideal places to go. They're hungry for the kind of performance that we offer. They're an extremely conservative industry. So the telcos are moving very rapidly and modernizing their infrastructure. The industrial ecosystem, the companies that I talked to, realize that they needed to upgrade their infrastructure. They needed to move to a software-defined infrastructure world, but they weren't sure how to get there. And I think a solution like Starling that is fully integrated, contains an enormous number of features, could be a good way to start those conversations with those industrial customers. So then it would be fair that this matrix that we're looking at, probably is as much a thought, potential thought exercise as anything. But the big takeaway might be that there are use cases for Starling X outside of telco, and telco is kind of where it all started. Is that fair? I think it's safe to say that the telco industry has moved the most aggressively towards software-defined infrastructure, and they've created hundreds of standards and layers in their software. Some of these other industries haven't reached that point yet where they're really embracing software-defined infrastructure. Now everyone's using the cloud, but we're talking about edge computing here, and in particular high performance, highly deterministic edge computing, which again makes things like industrial or medical very interesting. What we're not talking about is tiny little devices with one small processor and eight kilobytes of memory. You would need a Core i5 with a decent amount of memory as a worker note here, for instance. Okay, Steve, anything else? No, other than looks like somebody else has a question for you. Oh, perfect. I'll turn over to Elena to moderate that. You have a question in the chat asking what's the difference between the Starling X project and the airship project? So I haven't looked at airship in a couple of years, but my understanding is that they are solving a very different problem, but I don't want to speak for the airship community. If someone else here is more familiar with airship, I do know that Starling uses components from airship, in particular the Armada component, but we're in the process of replacing that with Fluct CD. Okay, sorry, I can't answer the question. No worries. Well, are there any other questions for Bruce, or otherwise we can hand it on over to Bruno to ask anyone with his part presentation. Sure. How many windows? Which one do I want? It is. That's the one. What are you seeing exactly? Yep, we can see your first slide. Okay, that's good. Okay, so hello everybody. My name is Bruno. And on the other side of the scale. I've been working with Starling X for a little bit more than one month now. So very different from Bruce, which is here since the beginning. Okay. So yeah. Quite on the other side of the scale here and which is fun, I think. And I also think that what I planned for today will complement what Bruce was talking about. And the idea, even being a very new member to the community is, I kind of put together all the things that I think I wanted to hear on my first hour of Starling X, let's say, but it took me one month to get all those things together for various reasons, not only is not a lack of documentation or anything, but it takes time for you to get to the things and to the correct channels and to do the things that you should be doing when you join the community. So that's why I put this together. And this is the agenda for the presentations. Quite simple here. This one is the first slide here is just a set of links that I think should be your go to links whenever you need something from the community. And then I would talk about how to start as a contributor, as a developer. Then I will pause this a little bit and talk about navigating the community itself. I will talk about the channels that Bruce mentioned. Where you look for help and things like that. Then I will go back and talk again more about how to contribute with the community. And then briefly talk about the installation and the Tina that I'm working with. So I'm not alone. All the things that I'm doing here we are doing has a team of five currently. Okay. And by the way, don't hesitate to interrupt me if you need any clarification or if you want to ask a question. So we have a small audience. It's fine. Okay. So this is the product website. Obviously this should be here, but also more importantly, this is the documentation here. I think there is. There's everything is here. Everything is in the this documentation website. I'm I like very much that there is a team dedicated to the documentation. This is very important documentation is a form of communication and communicating is very important on a open source community like this one. Meetings. Okay, the community works around meetings. So here's a link for the meetings and we'll be talking about more about them. A couple slides down. There is a code of conduct. This is how the community expects everyone to, to behave. I think. And there is a bug tracker. It uses launchpad. Everyone is encouraged to open bugs, report bugs to the community. And, and even work on them. I will be showing how to do that very quickly. But I think. This is a place to, to report a problem that you found. If you have questions, there are other places I'm going to show you that. The storyboard is a nice place if you have to keep track of like a work that takes that have several tasks to be accomplished right now. My team, for example, is working on one story board, one story. That was, I think it's there since the beginning of the project night now that I know the timeline from Bruce presentation. By the way, if you put Bruce presentation with mine here, I think that's the, the great way to start here with the community. I'm enjoying this, this meetup here. And the repositories are at open dev.org slash starting acts. And there is the code submission guidelines. This is also lots of words. The code submission is built on top. The code submission guidelines is built on top of open stack code submission guidelines. And so it's going to take you right to that right at the beginning. But it's a very good read and a very important thing to read. If you plan to contribute with the community. Okay. How do you start as a contributor? If you are a developer like myself, you're going to go to the repositories. And what happens if I, if I saw that list of links that I showed you, I would click on the repositories, the first one. And then you would see a list of 60 repositories. It's four pages, 15 repositories each. So it's a lot. Where do you, where, where do you actually start after seeing that? Well, and this is a thing that I found two days ago. There is a neat, very neat little page here with the list of Starlin X projects. The link is up here. But what it's showing here, I would say projects slash teams. But this is a very, a very small list compared to the list of 60 repositories. Right. It's like 10 or 12 teams here. Which is way easier to, to navigate. And one thing that I even have a note here is, I think it's better to, to kind of make sense of the community around the teams that work in the community. And how the community organizes itself. So that's a very nice way of a very nice place to start. So here, for example, if I go to the first thing here, I start to find very interesting things. I start to see names. So now I know who is responsible for this thing. If I need to reach out to someone. And more importantly, now I know all the repositories that this team is responsible for, which is even better. I myself have interest in the Starlin X slash tools repository here. So what do I do? Do I, do I email Scott and say, Hey Scott, how are you? I need help. Come on, help me know. I don't think that's the way to go. So that's why I'm going to pause a little bit. And we are going to talk to talk about navigating the community itself and all the communication tools that are available for someone at the community. And starting with the weekly meetings, Bruce mentioned the weekly meetings briefly in his presentation. There's a lot again, but don't worry. You don't need to attend to all the meetings all the time. Of course, but it's important that they are there because every team has its own meeting. Sometimes it's weekly. Sometimes it's bi-weekly here. For example, the beauty that I was showing before. It's a bi-weekly meeting at 730 Pacific. Cool. Now I know where to go. If I need assistance, I don't need to email Scott. I can just go attend the meeting. And that's good. I'm going to know what this thing is working on right now. If I have a review that needs to be reviewed, I can just go there. And I think the most important meeting within the community is this weekly community call here that happens on Wednesdays. It's every Wednesday, but at the first Wednesday of every month is 12 hours later. So it's 2 p.m. UTC every Wednesday. And it's 2 a.m. UTC on every first Wednesday of the month to accommodate a packed region more easily. So yeah, that's all the meetings that you can attend to, but that's where you will be able to find people to talk to and they will be able to help you as soon as possible. It's the easiest way to get help, I think. But there's also the mailing list, like Bruce mentioned. It is encouraged that we use the list to discuss technical questions. I mean, the list is called starting X discuss. So discuss. It makes sense. Sorry, just. And has Bruce said. The mailing list is the best place to reach everybody on the community. So like I said, you don't need to attend every meeting. So the mailing list is the best place where you will be able to find everybody. Everybody will receive your message and be able to respond. There is also the IRC. I call it ARC. Sorry if I say that far in the middle of the presentation here. So, yeah, like Bruce said, I don't see many people there. These screenshots like from two days ago, probably, when I put this together and yeah, I was there talking to people, but I knew maybe that's why I was there. But yeah, I think everybody at some point is there. Maybe it's not as synchronous as I wish it was. But it is the place if you need help in a synchronous communication. And if you need synchronous communication, it's the best place to go right now. And I think that ether pads are also a communication tool in the community. And this table here that you see on the right is the same table that lists the meetings, but this is the right side of it. And here you can see the link for all the calls if you want to attend, but also all the links to the ether pads. It's a great tool for synchronous collaborations as well. And you have the history of the whole thing. I think you probably have the history of the five years ago in the ether pads of the community. So everything is there. Another great tool to communicate with everybody in the community. Okay. And I personally added this here because I think knowing how to ask for help is very important in the community. Knowing how to talk to people, even if English is not your first language, which is the case here, you need to be able to communicate with people. So asking for help, which is very common. I kind of put together a few hints that I like here to follow. First introduce the problem in detail. Sometimes it's important to say, I don't know, I have a problem in a controller, which is running on a virtual box machine that's, I don't know, on a Ubuntu server, whatever, all the details they matter for someone that needs, that wants to help you. And also proofread everything that you, all your explanation, because I do that all the time. I take, it takes, I'm a slow reader. It takes like 10 minutes for me to read something that I just wrote, but more often than not, I find the solution by proofreading what I just wrote. It's like rubber duck debugging. I read it and oh, that's, that might be the problem. Let me see before I send. And then I kind of end up solving my own problem. So introducing the problem in detail and then proofreading, reading what you just wrote helps a lot. And finally respond to feedback. If people want to help, people often wants to help. I love to help everybody to get things done. And I'm new to the community. So I'm all excited about everything that's related to Starling X. It's important to respond to feedback. Even if you don't know how to answer, acknowledge the question and maybe say, I don't know how to answer that. Maybe can you help me to answer the question? This will help people to understand the level of knowledge that you have and will help people to help you. And if this is familiar, it's because I kind of got it from the very famous stack of workflows. How do I ask a good question? So it's loosely based on that. And also this is a good time has any actually to remind of the code of conduct in the community. I took the six more important things there. Be friendly, patient and welcoming, be considerate, be respectful, collaborate openly. When we disagree, try to understand why and when we are unsure, we ask for help. So collaborate openly. I think it's very important. When you have a problem, it's probably going to be a problem for someone else two months from now. And if you collaborate, if you ask questions on the mail list, for example, there is an archive, people can go there and find the problem, but the problems, solve the problems by themselves. It helps a lot. Cool. I think we know how to get help now. We know where to find people. We know how to ask questions if we have. Let's finally dive into the repository. So it's recapping. I was here at the BUIT project taking a little look that Scott is the one to contact if I need. And he's responsible for his team. He and his team are responsible for the tools repository. I just go there and like any other tool like GitHub or GitLab, you just copy the URL, go to your machine and clone that repository. Boom. It's there. Right. Quite easy. Don't need passwords or anything. It's an open source project. Fine. If everything that you need is just maybe take a look at the code to make sure that, or maybe to validate that you have a bug, you want to take a look and understand what's happening. That's all you need. That's everything that you need to get access to the code. In this case, the tools repository. But if you are ready to contribute, if you are ready to like fix a bug that you just found, and you created that bug on Launchpad, like I mentioned before, you're going to need the Ubuntu one account. So you go to login.ubuntu.com. You create your own account. It's quite easy. Email, name, username and password. I think that's everything. And right after that, you're going to have an opportunity to upload your SSH key, the public part of your SSH key. This is important because this is going to authenticate you when you push changes to the repository, to Garrett, which is the tool used to do the code reviews. I'm going to be showing right now. Okay. You have your account now. You have the repository. Now I am on the repository here under tools. There's one more thing to do, which is basically install Git review. Git review is a sub command of Git, which will help you to submit your changes to Garrett, the code review tool. After installing, there is one very tiny little configuration that you need to do. I did it globally. So you have to set up your Git review.username property to the same username that you used on your account when you created in Ubuntu 1. And then finally, once per repository that you're going to set up, you run a, this command here, Git review dash s, I think it's dash dash setup. It's probably the same. This is going to basically create a new remote on your local repository to track the Garrett repository that's used for reviews. Okay. You were ready to rock? Oh, before that. I am a curious person. If you are, I put this link here. I don't know how Git review works. I don't know much of what it's doing behind under the hood. And I do like to know what it's doing, especially when it comes to Git. Git is fun. It's useful, but sometimes it's complicated. So I do like to, to understand everything that's happening under the hood. And that's why this, I do have a note here for physical posted somewhere on the mess that is my desk right now with this link here, because that's something I will be checking the coming weeks. Cool. If you're curious, you also now have the link for yourself. Okay. You are ready to develop. You do the same way you would do with any other Git repository. You create a feature branch. You work on it. You add new files and et cetera. And you push this files. You add the files. You create a commit on your branch. Dash, dash all. Yeah. Forget about that. I was being silly, I guess. When you do a Git commit, a very important thing here is the dash, dash sign off parameter here. What's going to happen is that this is going to add the line number four here that you see. This is basically saying that the code that you are submitting, that you agree that the code you are submitting is subject to the same licensing that the project uses. So that's why you have the sign off by here and this is using your name and email set up in Git to put this here for you. And the other important thing here, very important is this change ID here. This is when we install Git review in the last slide. This, I think it's when you set up, when you do Git review dash dash set up, it creates a Git hook for you. So every time that you create a new commit without a change ID, it's going to add an ID for you here. And this ID is going to be used to match, to tie together your change, this commit to a review. And then you run Git review. And it does the magic, like I said, I want to inspect the code and understand everything that's happening, but I didn't do that yet. But you get a review on Garrett. This is the code review too. And oh my God, there is a lot going on here. There is a lot of things. And I think the first time that might be the question that everybody coming from another tool like GitHub or GitLab might have is, what's going on here? So I did that for myself. And I kind of wanted to share with you here is, how do you see, a Garrett review here is just the same as a GitHub pull request or a GitLab merge request is pretty much the same. It's something that you want to submit to a repository and with your changes and information about it. It's basically it. It's sometimes complicated because you want to review. Can you review my review or something like that? So I've seen people call it GCRs, Garrett code reviews on some places that might be specific to some companies. I don't know, but that's what I have seen so far. And then one key difference is that commits in a pull request in Garrett are actually patch sets in a review. So if you see right here, I don't know if you can see my pointer. Okay, great. Thank you, Elena. You see here, this review in particular is on patch set five. That means that people committed to it five times. And then you can easily compare here any version of your review with the base branch or even among themselves. It's quite useful. It has all the tools that you expect. You can expand here to see the code side by side unified the way you prefer. There is a very neat little thing here, which is this change log down here. This is very, very useful because it's all the history. It's all in one place. Like I said, that first I was like, Oh, that's too much. But now I'm really comfortable with it. And I think it's honestly, I feel that's way better than then get her up at this point. Let's see if this stands. I don't know. For now it's like that. And yeah, another very important thing, approvals in GitHub. Here are plus ones and plus choose. Plus ones plus choose you only get from core reviewers from that repository. And you need to plus choose. I think it's hard review or review and two plus choose to get your review merged. Yeah, kind of funny to say, especially not being a native English speaker. But yeah, you need to plus choose to get your review submitted, merged, and going ahead. Yeah. And if, if someone says that you need to change something suggests a change or say this is wrong, please redo or add a comment, whatever the change you need to do. In GitHub, you would go to your local branch, create a new commit, and then submit like sync your local branch with the remote branch. And that's going to show up as a new commit in the remote branch in GitHub. Here you amend the existing commit. You don't change that change ID that I showed you before. That's very important. And when you submit to Garrett with review. It will create a new patch set with the difference with that new commit. And like I said, you can compare it in here, but you can kind of map commits to patch sets here when you are seeing a review. Cool. Oh yeah. What happens after I still don't know I don't. Oh, actually, I think one of our reviews were merged in the docs repository so far. But we have like four reviews opened right now. And what happens after is that this is the process that I just described, basically, and this is taken from the documentation. From with all the links that I gave you with the for the beginning of the presentation. You're going to be able to find this, this image somewhere. The process that I just described what happens after is that your change goes to a gate queue. And then it's tested and then it's finally on the master branch of the post are ready to be released ready to be used. When a new release come. Cool. Oh, interesting. I have a note for myself on this slide here say improvise. Here I put this here. Those are here you can see all the mass that me and my team mostly myself. We've been doing with the reviews, and that's why I put this together, because it takes some time for you to get used to it but once that's done. If you follow everything that I told you here you're not going to have the same problems but you see some abandoned abandoned changes here that's why we were getting to know the things so that's, I'm sorry community for that. I'm sorry, but yeah, there's four reviews right now opened I think that's a fifth from this week already underway. The important thing here is that you can see there is a metric for the size of reviews. Try to keep them small or median, keep them smaller meetings very important is easier for reviewers to get your code reviewed if they are very small when it's only one thing. Sometimes it's not possible and sorry again community. There is a very big one here X large extra large. It's because in this case we are enabling a link there for a whole Python module. So, and the code that we are touching is from 2019, and it hasn't been touched since so there is a lot code code rods. So there's a lot of things to, to, to kind of comment at comments and small fixes so it's a whole list of changes, but at least we kept focused on only activating piling to for that module. So, it's large, but it's simple changes and try to keep your changes small. Maybe median cool. Yeah, that's developing. Let me talk a little bit about the installation process which was the first thing that I did after reading the main website and a big portion of the documentation. If you look at the documentation website, quite easy to reach on the installation guides here currently release and then you go to this very first installation method here. The first mention is one of the, this is the all in one simplex meaning everything is running on one machine and simplex means that there is only one controller there's no high availability of any sort happening here. And go there is not very hard to follow. But there are many words that may be used to don't know at this point, which is, which is fine if you're starting with the community, and I'm okay with not knowing some of them. But back then I didn't know. And things like simplex controller storage virtual bare metal. Whatever everything that's mentioned in the documentation does a great job of pointing you to the right page where you need to configure some some things. But sometimes it's just too much for whoever for someone who is starting. So, basically what we did was bring back to life, something that was already on the on the project on the community, like I said it's code from 2019, which is an automation to bring a simplex all in one installation for you up in virtual box and we did all the fixes and reduce to five steps currently, those are the five steps, it's, it's going to be less than five. I finished this but with these five steps on any dbm box, dbm based operating system, you can get a fully working and running styling x, all in one simplex installation using virtual box so it's all copy and paste there is no need to, to, to adjust any of the comments, it's just copy paste to your terminal and the installation is going to do all the things this is a speed up video of me installing, you see a lot of windows popping up right there but that's because I was kind of explaining what was happening this was, I think I did for myself, but at some point I might share with the community as well. But at the end you get a fully working installation it takes a little bit of time it takes you know my computer for example it takes one hour. It's always one hour and a few seconds one hour one minute one hour 30 seconds something like that. But you don't have to touch anything windows will pop up sometimes your toolbox we are working on a headless version that doesn't bring up anything. But it's going to do all the things for you at the end you're going to have a solution fully working. So you get your hands dirty, right at the beginning. That's the whole idea. The whole idea is to, to see something working for yourself, where you have control, you can, you can then proceed to continue learning about the, the, the tool. We are what we are working on is pretty much all the other installation methods that are available. And this is me trying to make a joke but honestly this is not going to, to be very hard. There is a lot of code to review. There is a lot of code to, to, to kind of bring back to life. There is code to delete as well I hope to my hope is to have in three months like a metric that I deleted more code than I created. That's my goal. And at the same time of course bringing something to that's working in the community. There's a lot here but I don't think it's going to be that hard to make all those things work because they are variations of the same. Like Bruce showed they are other variations of the installation. If I remember correctly, I think the Kubernetes setup here, I think we already have something up. It's not up for review yet, but I remember seeing some code from Danielle on my team about this. So I think we are going to get Kubernetes also working on the AIO Simplex installation. That's why we have a lot of reviews open right now. But yeah, I'm the one talking but I'm part of a team of five. So Bruno, Danielle, Douglas, Lindley and Tomas. I do most of the talking they do most of the work that's how it works. Just kidding I do love to get my hands dirty like I said, but yeah they work harder than I do. Sorry. Thanks guys. And that was all good. Let's do a quick recap here. You have all the links now you have everything that you need to orient yourself within the community. So hopefully know where the code is you hopefully know how to reach people and when to reach people in the community. You hopefully know how to push your changes now in Garrett, which is different from what most developers are used to but I can guarantee it's kind of even better than what most developers are used to Hopefully in a few weeks you can quickly get a Starling X setup locally with the module script that we are working on. Right now you can go there to the reviews that we have open and download the patch set that we have and use it for yourself it is possible. I myself did this installation with the setup that we the script that we modified like, I don't know more than 10 times already and it's working, almost flawlessly. There's way more things to do but you already can get a starting X working quickly. And that's all I had. Thank you very much. You had one question the chat asking, do you know how many core reviewer active core reviewers are reachable at one time. How many come again for reviewers are reachable at one time. I don't know I do know that there is a simple way to know who are the car reviewers if you go here. Where am I. The core reviewers are on the east coast of the US. There's a couple in other places, but not there used to be more in Asia Pacific time zone. But right now most are on the east coast US. Thank you Bruce. So we've got the car reviews from browsing here on the groups and then finding a group that resembles the name of the repository you were working on working on it's going to show you all the car reviewers of that particular group. I can put a link in the chat that shows where the cores are actually stored in the infrastructure itself so if you go I'll put this link in the chat if you go to this link, and then look at a specific project then there's a link on that project page that says members. And that gets you the core reviewers for any other projects. Awesome. Perfect. Are there any other questions for Bruno or even for Bruce still. I actually have one question more for the audience. I'm curious because this is a pretty introductory like meet up to Starling X I'm curious to know for the folks who are listening and are you just Starling X are you already contributing to it are you just trying to learn more kind of where are people in their journey and Starling X. What a comment to unmute yourself would be interested to know we have one said new trying to learn more okay cool. Well I hope it was helpful I mean, I'm not a very technical person I'm more in the community marketing side and I found this very interesting to kind of learn more and what developers are doing so thank you guys I appreciate it. And I'll get this also uploaded and posted to the open and first foundations YouTube channel so I'll add all the links that were mentioned by Bruce and Bruno as well to the comment of that video to find those. Perfect. Well there's nothing else you can close out for the evening or the morning or wherever you are right now. If you have any questions you can reach out to me or Bruce or Bruno will be happy to answer them and hope to see you guys all soon. Thank you. Thank you. Thank you, Helena. Bye.