 Hi there, and welcome to another edition of Tuesdays with Corey. Today, we do not have laptops out in front of us today. Right. So we are going to be, this is a speaking show. And it's very awkward that you did not. Oh, you're waiting for me to say something. It's very awkward that you did not. Because it is a speaking show. This is a speaking show. Makes sense. And today, we're going to be talking with Baz. Hello. Or Baz. Baz. Baz. You got it. OK. Thanks, Corey. You're welcome. Yeah. We've been working together for years. And I just say we have, actually, that's kind of awesome. We are going to today be talking about the open sourcing. Yes. Of course, that's right. This is something that happened just a couple of weeks ago. Just a couple of weeks ago, yeah, on Pi Day. 3314. 33141. That was planned. 926535. Very good. Wow, that's impressive. I know. Yes. So yeah, we did open source on Pi Day. That was really popular. I can tell. So tell us what we've open sourced. OK. So we have open sourced. So we open sourced basically all of service fabric. About a year ago, we started kind of dabbling into open source a little bit with our programming models. We did service fabric explorer. But these are kind of the edges of the peripheral. The peripheral, yeah, exactly. But we've been planning during that time and during the last, maybe over two years, ever since we started Linux work, we've been planning on how can we actually open source the entire code base. So all three million lines or so source code. It's a lot of source code. And it's a lot of source code. So yeah, so a couple of weeks ago, all that went out open source under the MIT license. It equates to power. So that is how much power you can get from this. It is a lot of power. Yeah, that's right. You measure power by lines of code. That's how we do it. That's how we do it. You said open source with MIT license? Yeah, so it's under MIT license. Great, fantastic. And so it's kind of a starting point. We kind of have the code out there. We have kind of basic build and tests that we can do. And now we're kind of, this is sort of our starting points. Now we're kind of in step one. Yeah, this is step one. So now we're working towards getting to open development. That's the real important thing. So open source is one thing, but actually doing development out in the open. I see. Getting the entire team, like the core team, to be working out on GitHub and actually collaborating with people, that's kind of the ultimate goal that we're working on. And so this is super interesting, because it's one of these things that I think, especially for products that weren't built originally, products and teams that sort of weren't built around this concept. But then you shifted in strategy, but it takes quite a bit of time to sort of get people to work differently. Exactly, yeah. So this is one of the challenges that you're kind of raising here, is that we can get the source code out there, but to actually treat it like a full sort of community development project requires the entire engineering team to sort of work very differently than they used to work. Yeah, and not only the engineering team, but there are a lot of changes that we actually had to make to our build processes. Because, like you said, being a product that we developed internally at Microsoft for, I don't know, seven, eight years, something like that. Right, and originally even geared towards just being an internal phasing platform. And just being internal phasing. Precisely, right, right, right. And so we have a lot of, we have internal build processes and build systems that we use to kind of, I guess it's mainly to ensure some level of quality across everything we ship, but none of that serves as a very high level of quality. A very high level of quality, I might add, yes, thank you. Thank you. But of course, none of that serves as available outside of these walls, so you can't just throw that up out to the, out to get up, because then nobody can do anything with it. That's right. So you basically think there's a lot of, there were originally a lot of dependencies on other things that we're not planning to over source, it doesn't make sense to open source. It's not even necessarily dependencies on other things, but just the way the source code is built and tested. Oh, I see. Those tools aren't available outside. Of course, and they don't, they're home-brewed. And then it'll make sense. And then it wouldn't make sense for other things anyway, so it wouldn't really be, it wouldn't make any sense to do that. So it's a matter of moving everything to publicly available tools, CI systems, et cetera. And then also getting the entire team into this mode of, okay, we're now developing out of the open, we're actually working with people, we're collaborating with people outside of the company, inside of the company, it doesn't even really matter anymore. Right. This is an actual open source project. Yes. That's sort of the challenge that we're working towards and we're trying to be aggressive. But that is the plan. That is the plan, we're working on it now. Got it. Pretty aggressive about getting everything out there as fast as we can. Sure. And so this first wave, you said you sort of started now, you originally started with some of the top programming language models. Did you see, what did you see from the community in that first wave? I mean, was it a good involvement, or I saw it as a little bit slow, or what have you seen so far? It was good for what it was, because even at that time, we were still doing our own development internally, which isn't the right model. So you're taking drops basically. Yeah, we were basically doing code bombs. And it's not the right model, and we know that of course, but it's kind of, that was our starting point. We had to start somewhere. Sure. So we started there. And that's sort of what you'll do now until you get to this opening as well. Exactly, yeah, that's what we're doing now. It's the same thing .NET did initially, they were kind of doing code bombs for a little while, while they kind of got everything out in the open. So we're falling basically the same path. Got it. Yeah, so we're excited about it though. It's very good. So now this will allow people to take the basic sort of platform, not only run it anywhere, which was already supported, but now you can go and peruse the code, you can make changes, you can go tweak it to your own needs. You can fork it, you can change it, you can do whatever you want. It's under an MIT license, so you can run it however you like. It's pretty much, yeah. That's cool. It's totally open. It's free, yeah. Love it. Free as you can get. And so let me close on this last question for you. What do you feel like is the biggest thing that you've learned taking, and this is your first foray into open source, right? As part of this team. It's our team's first major foray into it, yeah. And you personally as well. What do you feel like? Yeah, it's definitely my biggest. It's the first time I've run a big open source project like this. Yeah, so what's maybe the one thing that you were surprised about doing this whole project? The most interesting thing was there's a lot of emphasis on setting up how you actually govern a project like this, which is actually kind of fascinating to learn how other projects do this, what the right way to govern our own project is, given that it's kind of a mature code base and there's already a large team around it. How do you take that and then form kind of a governance model that makes sense. You're not starting from scratch and letting people build on it. You're basically like, we've actually got something, not only do we have something, but we take major dependencies inside the platform. So how do you govern that? That's a challenge. It's interesting, yeah. We spend a lot of time kind of looking at how Apache Foundation does it, how the Eclipse Foundation does it. And just kind of learning from that and seeing what would work best for us and for the people that want to work with us on the project. That's awesome. And so a lot of excitement already. I know that we announced it and saw a lot of excitement out there from this. Yeah, it was pretty good. I mean, a lot of confusion as well. It's always always a challenge with any announcement, right? But yeah, yeah, yeah. But it wasn't bad though. We were training on GitHub at one point pretty fast. That's exciting. Yeah, it was good. More than we expected. More than it was good. So let's see, we'll follow up. We'll probably put a link here of sort of how people can find this sort of code. Yeah, absolutely. And Paus, I really appreciate you talking about this. This is super cool and it'll be interesting to see as you get to this next phase, what you learn in the process there. Yeah, yeah, see how it goes. All right, thank you. Right on. Thank you. And thank you for joining us. This is Azure Tuesdays with Corey or Azure TWC, hashtag in front of that. And are you on the Twitter sphere? I am not on the Twitter sphere. I'm not on Twitter. Okay, so if you have questions, I should have asked him maybe before. But I am on GitHub. We'll edit this. We'll clean that out. He's on GitHub. You can find him on GitHub. Or you can tweet at me and I will email him. You will email me. Send a carrier pigeon in school. Send me a written letter with any of your queries and we will get back to you within two to three weeks. I will lend you my fountain pen. I appreciate that. Fantastic. Thank you so much. Have a great Tuesday. That should be it. It'll be a quadreset. It'll be a quadreset. It's a little bad here. Nice. A quadreset. Is this, are you enjoying this? Yes, we're good. How are we feeling? Yes. We are talking about our muscular, our muscles. I'm stretching. I have to stretch before I do my kicks. I can't touch my toes. That was a pretty good, that was a pretty good. That was good. I can't touch my toes. That's a flexibility. You almost fell over. You know what it is? Because the cloud is for flexible deployments. Yeah. I'm incredibly agile.