 Great pleasure to have you here. Brennan Durantso, here we go. Awesome. Thanks, Mariah. Yeah, and we're really excited to be back to start second year participating. Unfortunately, we've never been able to be in person. So looking forward to that opportunity, but for now we're here. We actually have kind of two back to back sessions. So this one will be kind of a little focused on our experience getting here ultimately. And then Darwin and Carlos on my team as well, they're kind of talking next and go into deeper details on some of the tools that we've built around open tap and the things that you can really do with it. So it'll get a little bit more of a story and background from me and then some deeper technical stuff from Darwin and Carlos. But one of the things that we kind of really wanted to share, because I would say, within Keysight, we're not a traditional open source company. And so it was kind of a unique journey, I guess, that we went on to get to this point. I kind of wanted to share our story a little bit. And some of the learnings that we've found and things that we, we ran into some problems that we had as well kind of kind of getting here, you know, in the hopes that I can potentially inspire some other people. I know, obviously everyone here is very familiar with open source in general, but, you know, there's oftentimes some challenges, particularly, you know, within larger organizations and enterprises where that's not necessarily the key focus. And that's kind of what we have really pushed for a lot is to get those types of companies to move into the open source space. And the way we ended up doing it was really starting at from the inner source side of things and moving out. And so kind of wanted to share our journey there and some of the learning. So feel free to ask questions. I'll try to monitor the chat as well. But like I said, we have Darwin and Carlos on my team are here as well, but we'll be talking more right after this. So first, just kind of a quick background on what open tap is. I'm sure many of you have not heard of it, maybe a few of you have, but just to give you an idea of what it is and kind of what the, what it's meant to do. And then we'll kind of go into the details of things. So really, kind of at the core it's a it's a cross platform open source test sequencer. We really focused around a lot of the hardware and software test automation. I like was mentioned that we are from Keysight Technologies. And so if you're familiar with that company where we're really kind of a hardware test company in the end. So we work with industries, kind of all across the world and all different areas. And we are able to basically connect and work with them and control various different aspects. We are not necessarily traditionally in this space. And so we kind of had to break into the market essentially and take somewhat a unique approach compared to competitors that have been in here for a long time. And one of the ways that we sought to do that was, was kind of coming from an open source angle and kind of moving away from proprietary code and proprietary tools, and really becoming open source. And so the focus that we have is basically one around simplicity, making the tool really easy to use, making it really easy to adopt and for people to connect into focusing on scalability. So we don't try to have open tab be a tool that can solve every problem for everyone out of the box. It's kind of designed to be extended and built around people contribute what we call plugins into it. That's for controlling devices, handling data, anything like that. And, and then in the end we're optimized for speed. This is a tool that gets used kind of all over the place. So whether you're doing kind of simple automation stuff on your on your desk all the way out to high volume manufacturing. We, we've kind of leveraged a couple of existing things in the area so we're built around net and Python. Like I said, there's hundreds of different companies and users in various different areas kind of all across the product life cycle for today. But step into what the architecture actually looks like at the center is kind of what we call our sequencing engine. And then we have these various different interfaces that we allow for extending out into so on the upper left. DUTs so devices under test so whatever the component is that you actually are testing. And then that is actually allowing for you to connect into, you know, whether it's a cell phone or base station or 10 handset PC, some other software anything like that. You can define your interfaces around to control. On the other side is kind of what we call instrument plugins. So these are traditionally things that he said makes, you know, power supplies signal analyzers signal generators. Things in that space that those are also kind of the plugins or drivers you can think of them as to control those test steps are kind of the smaller components that actually are part of your sequence. And so those are things to do specific measurements to handle data, do limit checks, all of that type of information is kind of containing what we call test step. And then the other kind of components are the front end interfaces so whether it's no simple command line interfaces, what we call the editor which is actually a tool from key site. So some UI is built around it anything in that space. And then also what we call result listeners which is more focused around handling of the data so when you're building out your test, the result listeners will then handle storing the data in CSV or a database format anything that you can customize. And one of the things that we've tried to emphasize with the architecture is that these truly are kind of all individually developed and componentized in that way. So anyone in the community can build a device plugin or test that plugin, and that can connect to someone else's result listener on the data formatting. They don't have to build entire solutions that are all architected together. And that's kind of one of the areas that we've really seen benefits in the end is that it promotes a lot more of the reuse aspects and code sharing and, and all of that are around the various tools. So like I said, we'll take kind of a deeper dive into what all of this means in the next session in a much more kind of technical case but wanted to give you guys a quick background of what it is that we're talking about in the end. And kind of just some key highlight and areas around it. We were very windows focused but because we're built around net. We've also extended out into Linux. We, we've extended into kind of the Python space as well as we see that as a big growing area in our space we kind of traditionally our customers and and consumers are much more in the the window side of things and so we're moving more into what I would say is more kind of the common software path of things with various different tools on the cloud side of things and in all of that and so these are kind of key areas where we see different people start their interfacing with us ultimately. And as mentioned it ends up being used in kind of all different markets in all different areas, you know aerospace and defense automotive semiconductor internet infrastructure wireless and general purpose kind of tools. And because of all these different things that's that's why we really wanted to focus on kind of creating this this open platform because you know there is no kind of one complete solution that address all of these needs right. So we wanted to get to the point where we can have this really open and extensible platform, but we started along that journey. We ran into a couple different issues and like I said kind of want just to share our path of getting there ultimately and really at the foundation of this what we're ultimately want to do is kind of become a de facto standard in the in the hardware test industry. And I think we we learned a valuable lesson early on prior to being open source that it's really hard to get there with commercial products. It's not that it's impossible but it makes it really difficult and so kind of to reach that goal we realized we had to take a different approach to things. And kind of where we're at that at that place now, all the different users and customers and tools but how did we actually get there. So going back to literally the very beginning of this so so Keysight Technologies is actually a branch off of the original HP kind of the birthplace of Silicon Valley right so dating all the way back to 1937. We evolved kind of partnered with other companies. Eventually we became Agilent Technologies and then in 2014 became Keysight so there's a very long history that exists here. And then kind of more specific on the open tap side of things this is a tool that was created for Keysight usage back in 2011 actually Agilent at the time and moving forward into very specific targeted areas for Silicon Valley with wireless device manufacturing. Then we sort of had a collaboration within Keysight because we were seeing all these different tools being used for the same reason. And that that was a big struggle that we were having was everything was doing. Everyone was doing things differently and independently and not none of the different tools work together everyone was doing their own thing and there was no kind of work with anyone else. Nothing could be reused anything like that. So we ultimately kind of had a selection of what's just called tap at the time, and move that into a formerly commercial product. And initially working with some of our customers and Nokia was one of kind of the key ones there they really said, you know all this is great but ultimately we need this to be open source for it to be something that we can take forward. And so, eventually through working with them and through lots of lots of trial and error, we're able to get there, but it took us kind of 82 years from the very beginning of HP to when we were finally able to open source this product. And so we're the only only open source project that has existed in that entire lineage of the company. So it's something that was not familiar to the company space at all. Not something that they were used to doing or had an experience around in any way. And so, we kind of took a step back to say, you know, what, what changed and what what did really need to do to get there. And, and what we what we kind of what ended up happening ultimately kind of along the way is that we, we actually created an inner source project and the kind of interesting thing is at the time we actually didn't even know that it was called inner source. And we've since kind of connected through the inner source commons and other areas and learn that that's what we did. But, but we really kind of took the simple step of just making the code available internally, you know, making all the issues accessible to everyone in the company, making all the source code available that was something that was not kind of traditional and standard we had this very kind of closed mindset I guess even within the company that every team should develop their own things. They didn't want to share stuff with others, even if other tools already existed, assumed that they weren't good and other, you know, they could develop better. And so by just taking that simple step of being extremely open in that space and letting everyone see what you were doing, we kind of saw that that created this sort of mindset shift of even, you know, simple, simply people would, you know, come in and submit an issue in at the beginning where there's, you know, a problem that they found or even with something as simple as documentation. And it was very easy for them to do and we sort of over time naturally saw the fact that because it was so easy for them to start and communicate with us and work with us that we had people that just naturally migrated to that space and in the end we ended up with literally thousands of people within the company working on this, contributing back to it, asking questions, building around it, building different tools. And so that was sort of a mindset that we wanted to take when we were moving forward ultimately. And so we were kind of thinking, you know, how do we, what do we do to do that, to move that forward. And what we, what we kind of ended up with and where we struggled within within our company for a while was that, you know, obviously we're a public company where we're around mainly around selling and making money. The aspect of saying let's take something that we're building and make it make it open source is something that was, you know, we were selling it and we said we want to give away for free now. And so that, that took some convincing and struggles I guess to, to, for people to understand that that was the right thing to do. And kind of what we, what we found was, you know, really getting to a business model that we could communicate was was really the foundation of things and so, and we found a quote from Martin Mikus and that was something that we really kind of resonated with, I guess, in his, you know, his way of positioning it was that, you know, you have different organizations that at different times essentially interact with you in different ways, right. Some of them have lots of time and are willing to use all that time to save money. And those are the ones that really kind of end up using a lot of those open source tools at the very beginning of things. On the other side of it, you have organizations that have a bunch of money now and would like to use that money to save them time. Right. So they are kind of people that move between those different areas and so what we want to do is build out a strategy that allowed us to, you know, have people start early on in a very easy way, but then allow them to build out into areas where a key site can ultimately benefit in a in a financial way as well. And, and really the focus there was kind of helping people move away from a lot of their their homegrown tools. That's what we saw so much of was people that have started down the path of, you know, this is an easy problem to solve we can just do it ourselves, and we'll start building it out but it ended up becoming this kind of un maintainable project in the end it's kind of their prioritized something that anyone else in their company really cared about. And so I basically positioning it as, you know, this is something that does a lot of the same things it's free to you, you have all the code available to you. You know that that kind of connected with a lot of people where they were able to more easily make that transition when they saw that they could contribute back to this project they can view all the source code there's no, you know, lock into it there's no risk of, you know, key site as a company deciding not to support this proprietary software anymore, because they had access to all the code. And then our goals, kind of from a key site perspective, were to build tools on top of this that acts that eventually had more and more value right and it became easier for us as well because now we're building on the same platform. And that's ultimately the connection that we wanted to make right is having kind of this shared platform that we're building off of our customers are building off of even our competitors are building off of that kind of allows us to move up one level in the type of work that we're doing so rather than focusing on, you know, very low level kind of sequencing and controlling the devices looking at the actual problem that you're trying to solve, building out test cases, you know, looking for issues within your designs, all of that type of stuff. So, this is ultimately kind of the model that we came up with kind of transitioning people along this path and I think this was really the foundational aspect to us kind of convincing people within our company that this was something that made sense was kind of proving that, you know, giving away stuff on the open source side of things doesn't mean that there's no kind of revenue path around it. And that was sort of a unique kind of realization for a lot of people I think within our company that that aren't really from that background they were from the background of patents and selling everything as proprietary and everything is a competitive advantage, and you would never want to share any code with people so that was, I guess, really our ultimate key learning in the space and what's ultimately driven a lot of the success that we've had since then is being able to leverage this model where within Keysight we can build these higher value solutions and then with our team we can kind of reach people at these lower levels and closer intersect points. And so ultimately we were able to kind of move in this direction. We actually jointly announced the open source version of the project with Nokia. Since then we've had various other kind of partners announced, you know, that them joining, you know, publicly. So it's been kind of cool to see it's not just someone, you know, contributes in the background but actually, you know, very publicly announces that they've joined into the community and have contributed back and so coming from an industry in general in the test measurement space where none of that was really a concept. That's been really cool to see that some of these different companies sort of recognizing that value and being able to, you know, step up and say that they see the value of it and kind of announce these different initiatives with us. And so kind of our next steps and what we're looking at from here, and one of the reasons that we're at Fosage and enjoy just participating and communicating with people is that, you know, we found just like on the inner source side, that the most valuable aspect kind of to move the open source piece forward is really not the code and the tools, but it's the community in the end, right, and being able to build those interactions with people and people that find value in the project and connecting to them and talking to them and figuring out, you know, where you can have these different intercept points ultimately I think in, you know, the broader kind of open source space that's one of the unique aspects is people are in general very willing to share what it is they're doing where they're trying to go, the goals that they have and what they're trying to build. And so we've done a lot, I would say, on our side to help foster this. We have, you know, a forum that we've created where we are interacting daily with different people. We have a package repository that we host that has all the different plugins that have been contributed. Obviously, we have all of our code available on GitHub and interact with people there. We also have kind of a news and blog page where we, we make announcements and reach out to our community. And then we've sort of built some internal tools as well with different metrics that we, we deem important to kind of ensure the health of the community so looking at, you know, usage of the platform interactions on the forum and on our YouTube channel in this to kind of give us a good idea of how things are growing and building and moving forward. And, and so that's kind of ultimately where we want to connect here and what we're, we're kind of kind of leaving open as a, as a kind of communication point is to reach out to us if you see kind of areas to connect. If there's, you know, tools that you have that you think make sense or, you know, reasons where you think the platform might make sense we want to, we want to build, build out kind of our relationships and partnerships in the space. Like I said, it's a, it's kind of a new journey for us and, and key set in general. But one of the things that we've kind of really enjoyed is being able to connect with all of the people that are so passionate about things and in the space. So, if you, if it's something that seems like, you know, either you have an existing product or an existing kind of use case that you reach out to me. I'm, I love to talk and, and see, you know, how we can connect, you can also go directly to our website. If they're, if that's easier for you as well, and kind of look at, we have simple things like a you know, the Contributory License Agreement to, to, to join. We have different tools in different ways where we can kind of help you as well with putting, you know, your local on the website and doing different announcements. And, and ultimately, like you said, that's, that's really what we're looking for. It's, I think from an open source perspective, it's important that, you know, even, you know, the open sourcing is one aspect, but getting other people to sort of have that diversity of thought and, and kind of different aspects of things is ultimately what makes, makes, makes the successful. So, having a tool that's kind of owned and maintained just by one company in his open source is not kind of ultimately the end goal. And so if you have different areas that you, you want to connect into, then that's, that's where we really want to reach out and communicate with you. So this kind of a few additional resources if any of this was interesting to you. We have our Git Hub page, like I said, where you can connect with us there. We have our newsletter and we have our forum. So kind of tools if you want to just stay in touch, if anything sounded interesting, just want to track things on GitHub just to see where we're going. And kind of a key different, different areas from there. And hopefully that was at least interesting enough to get you guys to stick around for the next session where we can go into some deeper technical details on how we, how we do all these different things and build out the plugins and the types of things we can do. I think that was more or less all I had from a presentation perspective, so I'll open up for questions from anyone. I said I would monitor the chat but I didn't do a good job of keeping up.