OK, so I think we're all settled now. I'll start my presentation. Hi, welcome to the session on Android Common Kernels. My name is Amit. I work for Lennaro. In this session, I'll talk about Android Common Kernels and it's out of three Petset. We'll see how the Petset has evolved over the years, started from 2009 now. It's been almost nine years. Then we'll take a look at the Android Petset in Android 4.14 Tree. I'll not be covering what is in Android 4.4, but I'll compare the Petset, as you'll see in the next slides. Then I'll talk about the upstream story of those patches if people have tried upstreaming those patches and whatever success they've got. Next up, I'll talk about Android Mainline Tracking Tree. It is something new, which has started a couple of months back. I'll talk about why do we do this. And I will wrap up the session with the Android Petset Delta, how much we are carrying, and a call to action if something which, as a community, we can do about that. OK, so I'll start with Android Common Kernels. So Android Common Kernels is, OK, Android Common Kernels is respective LTS version plus a handful of upstream, a handful of out of three patches. So I have listed down these patches based on why they got rejected upstream when they were pushed for RFC. So broadly, you can classify them as the features which are specifically tailored for Android. For example, Qtag ID and interactive governor, which is a good example. It is no longer there, but it was mostly Android specific. Then there are a few features which got rejected upstream because they were not implemented the way upstream wanted them to be. For example, paranoid networking and few USB gadgets. And Android developers use this Android Common Kernels as a testbed of the patches which they are experimenting with, which they are trying to get useful, trying to make them more useful, and like a testbed before pushing them upstream. OK, so this one is quite interesting. There are a few features which got implemented at that time because there were no mainline equivalent of them. But for example, this PPP patches, when these patches got implemented, there were no equivalent functionality in upstream kernel. But at that time, they implemented these patches and they kept using it. They did not switch to upstream implementation until recently. Then there are a few features which Android Common Kernel is carrying because it is something which is more useful from community point of view. The patches which they have got from their OEM partners, for example, SD card FS. Now Android Common Kernels, it acts as a channel for downstream OEM partners to get LTS fixes, security fixes, and new Android features. So this is the Android Common Kernel tree URL. You will go through the URL. You will find all the release branches which are currently active. I'll briefly talk about the kernel branch hierarchy here as well. If you see that this Android Common Kernel is forked from LTS and then out of, I mean, for example, here you can see the example of 4.4. It doesn't make any sense here because 4.4 is mostly on Android O. I'm not sure if it is on any of the Android entries. It is mostly on Android O. So you'll see that Android 4.3, the Common Kernel, it was forked from LTS tree. Then you see Android 4.4-n, which is desert-specific release, and those are desert-specific release. Then Android again forked those particular releases for their OEM partners, which are not really interested in taking the LTS fixes as such. And you will see these release-specific trees, they get patched with Android security fixes. And those Android security bulletin-specific fixes. So the good practice here is to start, to pull from the upstream trees, for example, to pull from Android Common, not from Android Release Trees as such. You can get a more detailed information at this URL where they talk about Android Common Kernel and what are the best practices you can follow. Now so this slide is a last-minute addition to this talk.  At that time, these trees were more like a patch-set dump. They never used to compile and forget about booting them on a real device or any of the, even on QMU. But now if you see that they are, I mean, they are continuously being tested, build tested on Kernel CI. I've posted the link here. And we test these common kernels on, as a Linux Kernel Functional Testing Project. So Tom gave this talk yesterday, so if you're interested in learning more about the Linux Kernel Functional Testing, you can check out the slides, and hopefully videos will be available soon. So as part of Kernel CI, as I talked about, they do this build tests and basic boot tests. The next Kernel Functional Testing, we run VTS, ETS tests, and upstream LTP and KSELF tests. But those, we run mostly on open embedded builds, not on ASP builds. Now the Android Patch Set Evolution. So this is the talk which John Sturz gave in 2011, ELC. So this is what he said, OK, so these are the patch sets which we are carrying in Android Common. So all the usual suspects there, Ashman, Binder, Wakelocks, if you're familiar with Android Common kernel. Now fast forward to 2016. So this is the talk I gave two years back. So you will see that all these red lines, all these patch sets are dropped. So we no longer use them in Android Kernel. And all the green lines are the patches which actually got upstream. And yellow was Ashman moved to staging tree. But with 4.4, we saw that, OK, so we don't have this delta, but we have this additional atomic display framework. We have verified boot. We have SD card affairs. We have interactive governor. And energy of a scheduler was new at that time. So now that we have seen how the patches have evolved, I'll talk about Android 4.14. I mean, from now on, all the patches I'll be talking about, all the status I'll be talking about, are related to Android 4.14 Common Kernel. So this is the GitDiff delta. So majority of the code is SD card affairs. Then we have got net filter changes, energy of a scheduler, USB gadgets, input devices, FIQD burger, and other things. So I've put another slide for comparison. So this is the slide which I just talked about a few minutes back. So this is the 4.4 GitDiff status. And this is where we are today. So you'll see that apart from the networking, because at that time, networking used to be the bigger set. It used to have this UID-based routing and PPP patches, which I talked about, and other things. USB gadgets had MTB PTP. Now, all the red lines is that all these frameworks or all these patches, we are not getting anymore. So UID-based routing, it got upstreamed. PPP is something which we have moved to a upstream interface. So we are not getting those patches in 4.14. MTB PTP patches got dropped because we have a user space dimmer now, which takes care of MTB PTP functionality. Atomic display framework got dropped in favor of DRM KMS support, hardware composer support. Infective governor again, we are no longer using it because we have moved to energy of a scheduler now. So if you see the shift here, so earlier the networking used to be the bigger set. The big chunk of code sitting outside of mail line tree. Now it is SD card FS. Mostly because we have dropped so many things from networking. Same thing with USB gadgets. It's just dropped from third place to now fourth or fifth place. The rest is pretty much the same because nothing much has happened on those patch set yet. So to give a broader view of out of three patch set, I just dig it more. So you'll find some useful information here. So I'll try to touch most of these patches and most of these features and talk about the upstream status if we have tried anything, if someone is actually working on these things or not. So we'll see. So we'll start with SD card FS. SD card FS is a fuse replacement. For a long time, we used user space fuse dimmin, which takes care of this emulated storage in ASP. So Samsung came up with this SD card FS. So they say that, OK, it is working much better than using a user space dimmin. Let's have an internal implementation of emulated storage, which can emulate all these permissions and case sensitivity. So it was tried and tested because Samsung was shipping this driver in their devices for a long time anyway. So upstream, sorry, ASP just pulled out these patches and they pushed into 4.4. I mean, it started with 4.4, I think. I'm not sure about 3.18. I might be wrong there. So Daniel Rosenberg gave this talk about upstreaming SD card FS in plumbers last year. So if you are interested in getting us know what is happening from upstream point of view, you can check out his talk and some very useful information there. So a couple of months back, I think, ASP dropped fuse support at all. So first it was you can either use fuse or you can use SD card FS. So now they have removed the fuse support, and we are using SD card FS only. So what happened because of that is that a few people in NROV run mainline kernels on development devices, high-key DB410C, and we run into this breakage. So it's not something which we cannot live with, but it is something which is clearly broken, and we have to do something about it. Maybe get the fuse support back or speed up the streaming process, because if it stays like this, then it's going to be difficult to run mainline kernels on supported devices. I mean, if your device supports that. So last is, Huawei's SD card FS implementation. So if you track NROID, get it, you'll see that with 4.14, I mean, Huawei has their own SD card FS implementation. And if you go by the commit messages and the replies which you see on that message, they claim that it is much faster than using the SD card FS which they have currently. So I just put these two lines just like that, if you're interested in this. Right, so the next is F2FS. There is no out of tree delta here. I just put it because there are a few chunks of code which is there, but it is all upstream, so nothing to really worry about it. Squash FS is, yes, there are a few patches which the claim is an optimization, and if you should do this, it's a, I won't say recent changes, but yeah, it's fairly new. It's fairly new, and I have not seen any upstream activity on these patches. Right, so the next big chunk of code was networking. If you have any questions, you can just interrupt and ask. So networking. So there are a few net filter module specific changes, for example, Quota 2 and QTag ID, where they track the usage, where they track the, which mostly use for socket accounting, right, based on a UID, that this particular user, this particular process, used this much of data. So this is why this QTag ID and Quota 2 is mostly used for. The good news on this particular module or on this particular patch set is that they are moving to EBF now. So they are saying that, OK, for now, you can use QTag ID matching module, but going forward, I mean, they are very positive that by the time OEMs will move to 4.14, we won't be using QTag ID. So we will be using this EBF implementation to track the socket accounting and everything. And there is a very small change in idle timer notifications, where, right, so current driver supports sending new events that, OK, I'm in idle state, or I just came out of idle state. So instead of that, user space expects net link messages. So there were just few lines of change of code in this one. So upstream, when it got upstream for submission, the maintainers did not have much objections to that. They said, OK, if you are sending new events, if you want to send another set of messages to notify user space, they were OK with that. But no one followed on that particular patch set. And when I talked to one of the Android developers, they say that even they are not really worried about this patch, and they say that let's move this particular functionality to user space instead. So hopefully, next Android release won't be having this particular patch. And then there are few patches which implement this paranoid networking. Paranoid networking is restricting the use of network to a particular user or group ID. So if a process, if a user is a part of this particular group, then only it can access network. It's a very small chunk of code, just a couple of header files with user IDs which are mapped corresponding to the user space Android IDs. Now, that is a problem, because upstream developers do not want hard-coded user IDs. So it got rejected because of that. And there have been a few suggestions that maybe you can use namespaces to implement this much better. But we were told that it requires a fair bit of userland changes. And it is unlikely to happen just to save a few lines of out-of-tree code. But even user space, if you follow the changes, you will see that now you can restrict or you can allow particular services or particular processes if they have upstream compatible capabilities. For example, CapNet draw and CapNet admin. So upstream capability support is slowly growing in at the user space. So hopefully, the checks which we do at the kernel side, that if this particular ID is there, if a user is of this particular group ID, then do this or don't do this, will. And I mean, I am hopeful that we might be able to get rid of this feature quite soon. Not soon, but eventually maybe. Energy-aware scheduler, I'm pretty sure that most of us here are aware of this. It's a hot topic. So it's, again, a big chunk of code which is sitting outside of mainline tree. But ARM and linear developers are actively working on it. And you can track the discussions on mailing lists. You can track the discussions on ARM GitHub, who have provided the links here if you want to see the current patch set. So there were a few patches. I already talked about MTP and PTP. Those patches are no longer in 4.14. You will find it in 4.4. But at least pixel devices are not using those drivers. They are all moved to user space. But few devices, for example, all the 3.18-based devices, I think they are still using those MTP-PTP devices, but not config.fs-based gadgets. They're still on the composite gadget thing, the Android gadget, which was years old now. So the existing set of USB gadgets which are there are what they provide UEvent notifications to user space. So config.fs has a hook that if a USB is plugged in or plugged out, you will just send a UEvent, that, OK, I'm disconnected. I'm connected. So for these gadgets, I mean, developers have implemented a custom class. This custom class, again, is something which is, sorry, it is a legacy implementation. I'm not sure if you're using config.fs-based gadgets, you need that. But this is still there. Now, this patch got rejected upstream because upstream wanted to track the UEvent from UDC core. So instead of putting this particular UEvent notifications from config.fs-layer, they wanted to have it to be sent from UDC core instead. So no one followed up on that because there is a small hack, which we do at the kernel space side, which should be moved to user space before we actually move to using this particular code from UDC core. So that was our device state changes. Then we have accessory drivers. I'm not sure. I mean, I have never seen any Android accessory in use if anyone is even using that. But we still have those drivers, accessory drivers, audio source drivers. And if you go through the documentation on Android official pages, you will see that this accessory mode audio is not widely adopted and currently not recommended for new designs. So I think it's on its way out. But the packages, but these drivers are still there. Then there are two additional drivers, this dual roll USB ccfs interface. Provide a user space interface if you want to switch from host to device or vice versa mode. OTG wake lock is to grab a wake lock if you are connected to a power source, if you have a V bus interface. Common use case is that when you plug in your USB charger, then it just grabs the wake lock and your screen will lit up. So OTG wake lock driver is used for that. I'm not aware of any upstream submissions for these two patches. Android verified boot is the Android's verified boot implementation. So the DM Android variety is completely out of tree. It's not submitted upstream. Mostly because it has some few AB hooks, seamless update hooks, so it will be difficult to see how it will go upstream. Then there are a few changes in forward error correction code. It's not a that OK. So let me take this opportunity to tell you that most of these patches which we carry, they're mostly, I mean, if you will see that trend, that OK, so this particular patch is only to provide stats to user space, right? So I think, yeah, for example, we saw that USB get this thing, right? It was just you and notifications, sending something to upstream. Same thing is here with forward error correction code. It provides a set of CSS attributes to track how many errors we have corrected or other particular stats. So these are the few out of tree changes in DM subsystem. So input devices. So if you have key card and key reset drivers, which when you press certain combination of buttons on your phone or an Android device, then it does something, right? So these input drivers take care of that. Chunk of it got upstreamed in SysRQ driver, but still a lot of code is there which sits outside of this. Then there is this generic GPIO input support which supports different GPIO based input devices. I've not seen any, but yeah, they still have these drivers and support in Android Common currently. Then we have FIQ debugger patches, which is mostly used for kernel debugging for ARM. So the plan is to use FIQ interface for debugging. FIQ is an NMI-like feature which you see on X86 now. So if you're not able to grab or use FIQ, you can fall back to using normal IRQ to get the CPU back traces. Daniel Thompson from Ninaro worked on it for some time. Few of the functionalities got integrated with upstream KDB, but still, I mean, a majority of FIQ debugger code is still out of tree. So few items which people are still working on are KDB extensions, FIQ debugger for AMV8 devices, AMV8-like devices, because it says we are using FIQ debugger, but recently, people figured out that we are not actually using FIQ. We are still using a normal IRQ. So these are the major subsets which I've covered so far, right? Networking, SD card fs, your input devices, FIQ debugger, and other things. So these are small, small patches. The small, small fixes, if you remember that big chart which I showed you. So there are a few patches in memory subsystem which tag memories so that it's easier for user space applications to tag their memory usage. So this one is sitting outside of, I mean, all of these patches are sitting outside of main line tree. Then there are a few C group changes when you move a task from one particular, when you start putting applications based on their usage. So Android has these four classes. It's a top app, it's a background app, or it's a system app, or something like that. So they use C groups, C group changes to do these transitions. And recently, there are a few, recently, the upstream, OK, not upstream, the AOSP supports moving the tasks if you have capsis, nice capability. So it is similar to what we saw in case of Android networking that, if you support a particular upstream capability, you can do that. So this is a positive change. Then there are a few goldfish changes. Goldfish is the Android emulator. So recently in the last few days itself, I see a lot of goldfish changes. I have not covered those changes. So maybe if you look at these changes now, you'll see that, OK, these particular changes are nothing compared to what got included just last week. So this is that. There are a few art specific changes. For example, appended DTB support. And you build, I mean, sorry, when you can just append your DTB at the end of your kernel image, and your bootloader will just support it and boot from it. There are a few patches which dump memory around a few registers in case of failures or in case of a panic. So this support is something which no one tried to upstream yet, as far as I can tell. There are a few changes in tracing subsystem to trace GPU usage, CPU frequency usage, and other memory specific changes. OK, so there are a few changes in MMC subsystem to support embedded SDIO support and other SDIO specific fixes. Additionally, it relies on SD card detection and all those small, small fixes. OK, so this one is new. Sorry. So this memory state, driver is new. It tracks the time spent in different DDR frequencies, memory frequencies. So this got added recently. Well, by recently, I mean last one year or so, there is one security patch which prohibits any user to just don't probe for any kind of events. It got shot. It was pushed upstream for RFC, but no one was interested in that. So it got rejected. Then there are a few small networking fixes, like providing knobs to control the TCP window size or initial congestion window.  Then there is one in it, in a time-office change, so nothing interesting there. There are a few NFC changes which looked interesting. I tried to push them upstream. But at that time, meltdown and inspector were kind of hot property, so I will try to see if I can resend a new version of this. Or this wake-up reason patch. So what it does is it logs the wake-up source and the time it spends in suspense state. So this got traction, a lot of traction in between. And as I said, so there are a few patches which exist only to give or only to relay certain information to the user space. So you have this wake-up reason source and UID status. UID status does the same thing. It provides stats to the user space. So our next topic is Android mainline tracking. We recently started working on it. So if you track Android common kernels, Android common kernels are mostly LTS releases. So we base Android patches on top of LTS releases. But Android mainline tracking, what it does is it tracks upstream implementation. It tracks upstream kernel. So we keep rebasing Android patches on top of Linux master and we tag it as experimental Android 4.15 or whatever is the next version. So why do we need this? Because it helps us catch mainline regressions much earlier in the development cycle. So instead of just fixing all these breakages, if it is something which is broken and upstream, we can just report it. So this particular upstream patch broke this particular Android functionality or we can report certain ABI. We have reported ABI breakages before while following this particular tree. Again, if you are trying to push something upstream, this particular tree can be used to rebase your changes and work on top of it. Sometimes these trees can be used as a reference or experimental preview tree. For example, let's say we are on 4.13 and you know that 4.14 is going to be the next LTS. But the implementation which you have is Android 4.9. So in that case, if you have a tree like this, where you know that the next kernel version is most likely to be the next LTS version, so you start preparing your SoC BSP based on 4.13 and stick closer to next LTS version as much as possible. So this is why we have Android mainline tracking tree. So this is Android 4.10. So this we did with this Git diff stat is in comparison with 4.15. No new changes here. If you will see that pretty much the same set of changes which we saw with 4.14. So Android patched Delta. So this is the trend with every, sorry. So these are the number of lines added per Android common kernel version. You see that there is a downward trend, but it is not as good as it looks like. Because by that time, the Android 4.9 will go into production as a production kernel. You will see that the functionality, I mean, the developers will keep adding more functionalities based on the newer Android releases or Android features they are trying to get into, let's say, P. So as I said, the trend is there, but we always end up rebasing about 38, 40K lines of code on next LTS releases. And though a lot of changes we dropped in between 4.9, 4.4, and 4.9, and then 4.9, and 4.14. But on the other hand, Android developers keep adding new features based on the next release they're working on. So it's like a never-ending cycle here. So if you are aware of any upstream alternatives which you talked about, these are the patches which sit outside of tree. And if you think that there is a upstream functionality which can replace a particular out-of-tree patch set, then please do suggest or get in touch. Because that's how we got rid of a lot of things, right? For example, PPP, we already had PPP OLTP, I think, is the upstream equivalent of OPNS and what Android already had, but we convinced them that, OK, we already have upstream implementation. So just move away from what you are getting for last so many years now. So that was my presentation. Do you have any questions? So it's a combination of both. So the question is who is actually working on upstreaming these out-of-tree patches, right? So it's a combination of both, right? Google developers, I mean, John Sturz did a lot of streaming and red patches of streaming. And we keep on picking a certain set of patches and we feel that, OK, this is something which can go upstream easily. It's like a low-hanging fruit. So we just take it and try to push it upstream. So we got success there. And while going through this presentation and preparing this presentation, I figured out, OK, these are the patches which looks like are reasonable enough to send them. So we keep doing that. Yes, please? OK, so the question is that when a particular functionality which is implemented in, yes, they have been moved to, yeah. I don't think anyone is formally tracking it. Maybe USB developers are tracking it. But from our perspective, which we looked from outside, right, that, OK, I mean, I don't think there is any, is there any particular process which anyone follows? So we found out about stuff like this when we actually ask them, OK, for example, with 4.14 coming up, when we were revising for 4.14, we asked them, OK, this particular functionality, right? No one is using this particular interface anymore, right? So do we still need it internal? Or they say, OK, we have already replaced it with something else. But how do you do that? Yes, please? There are a few examples, right? For example, OK, so we did not fix it, but we just got rid of it. For example, mtpptp, we tried to push it twice, thrice. We said, OK, so many people, right? Billions of devices are using that particular driver. I at least put it in staging. But there was clearly objections. No, we are not doing it. And they said, no, move to user space, move to user space. And they did. And then we got rid of drivers. And similarly, I mean, John might be having much better examples on this. Another example I can think of is UI Debates Trouting, right? Lorenzo spent a lot of time on it. And eventually, he got it upstreamed. It's a big chunk of code which moved from 4.4. Yes, please? So we've been rebasing from one particular LTS release to the next one. So we used to do this Android Mainline Tracking Tree I talked about, right? So we used to do this activity within Linaro before we started doing it for Google. So we already had, no, instead of doing it from 4.9 to 4.14, we were gradually doing it for 4.10, 11, 12. So I mean, RC ones are always hard. It's like one week, I would say, to keep things in check. So but with Android Mainline Tracking Tree, where you eventually gradually keep rebasing your patches for every RC or release things, it gets easier. So just the basic feature sets, right? So I mean, for example, I use DB410C, right? So 4.14 boots with your Wi-Fi, Bluetooth, with DRM hardware composer and everything. So it makes our life easier. We don't have to do anything. And we know that 4.14 boots, right? So when we rebase and write patches on top of it, right? We just make sure that that particular functionality which we tested with vanilla 4.14 is not broken anymore, right? And then we enable QTAG ID to see if data usage tracking is happening or not. And we enable UID status, right, which provide all these status services. So we do it, I mean, I do it manually. I mean, since I know that these particular patches do all these things, so at least these things should be working. Oh yes, I mean, now we do, now we track all these and write Mainline Tracking Tree as in LKFT as well, which tests out all these, and VTS tests, CDS tests, and no extended set of LTP, KSELF tests, and everything. OK, thanks for coming, everyone.


I'm talking about I'm getting all the way sparked up to the left all the way from up to the right front back side I'm talking about I'm getting all the way sparked up everywhere or the number one was sam's club 6.6 mile for 1472 what it do. I just want to say this Oh, yeah, guess what? We also got some incentives. I'm gonna just stay through to the full video That's all I want you to do and you want to subscribe make sure you subscribe button Give me a thumbs up and do not skip those ads. Also, if you want a chance to win some of the free merch Oh, yeah, do us email me at brohamshouse.com or gmail.com Send me a picture so you subscribe to the channel and are your chance to win. It's time to get it in. Let's go Thank you very much. You have a good one. Do I say? So if it's all the way sparked up order to get an order, I don't know where to go or what to do Or anything all I know is That's probably Excuse me I don't know this extra dot there too. I saw a lot of cars up there though. So I don't know but there's no one right here It says leave by door, but Turn out and pull Excuse me. It's kind of creepy. I ain't gonna love I'm leaving right here. Yes. I'm leaving right here. Then with the photo smack. We're gone. How are you doing this morning? Yeah, that's all we getting on this auto vault. You guys have a good one order number two What to do this one? I don't know what's going on. I'm telling you guys this look it was all the way sparked up one order 4.9 miles for 21 25 After I accept that order in the middle it switched to Two orders 4.9 miles for 14 25 But I did just pick up the order and it's only one order. So I don't know what's going on Hopefully we get that 21 25 stay alive that drives. I keep you guys updated. I'll be out there getting to this money That's what we doing. Let's go. We are here to drop this all the way sparked up order to get an order I think this is going to be for 14 25. Good. Look man. That's only some chips Anybody still got the munchies from yesterday? Oh, no, yes the chips your chips in this here This in this In some milk. I think it's the half half any photo. Sorry. No, no smack with the photo back with the doorbell Let's go you guys would not believe what happened. Guess what spark has opened up the floodgates, baby They are now opening up sparking all the warmers in my area So it's one two three. It's like four or five warmers in my area So we're gonna get busy and on top of that they give me now the sentence for a complete trip This is going to be from um the 19th through the 25th. What's today the 21st? So we got four more days to get busy and if you complete four trips You get an extra 20 dollars and if you complete eight trips, you get an extra 40 dollars And if you can be 12 trips, you're going to get an extra 80 dollars. Guess what? We already completed four trips So we got an extra 20 dollars and it's all all this is going to drop on the 25th So I've I'm man. I'm happy, baby. They open up the floodgates. It's time for us to get busy I hope you guys are with me also. Guess what else? We also got order number three get with me, baby All the way Spurred up two orders 5.6 miles for 1563 get with me, baby. Let's go Uh car are you how you know, you see this cars and crib That's what I'm telling about that's what you supposed to be doing You know, I've been having a little trouble with the Walmart and gurney man They've been something I got to ask to record them and all that stuff. You got your phone. I put it in for you Oh, yes, she got me. That's what I'm saying. They got turkeys in them You be you still be watching the videos I'm dropping every day That's the blueprint a lot of people don't know that's the blueprint All right, I'll probably be seeing y'all soon again Appreciate you. All right y'all stay up How are you doing sir Yeah, yes, sir, this man has a little weight to it Need for me, baby. They got that brain It's okay. All right, you guys have a great day That's order number two, baby. Hey, guess what? It's feeling beautiful.  That's what I do know This weather I'm trying to pull out the best team when it's getting warmer side Y'all gotta stay too because y'all will see some legendary stuff Go on, baby Step back hit it with the photos Let's go order number four. We are here running up this dough, baby One more 27 items 6.6 miles for 11 dollars. We are holla playing. We are bucky down How you doing, sir Oh Barbara This is a live screen Alrighty, thank you. Have a great day, ma'am Just like that. We are here to drop off order number two What it did to get you on your crew? This actually was a too easy deliveries, man. Lucky the lady goes downstairs for the last delivery because I don't have to go up to the elevator She's right there waiting for me, baby I'm gonna put these right here just in case someone's gonna knock them over by the door Step back hit it with the photos. Mac with the photo Let's go Guess what that last order didn't leave me leave us a tip, man We only got three dollars and fifty cents for that order. Maybe the way it goes. We about to get an order We got order number five is all point five miles for 28 66. We back in the mix Oh, yeah, what you be doing under door dash instant cars spark real estate cars and everything How many do you get? Um, well, it depends on the video. I got like just almost 2,200 subscribers Yeah, I just Yeah, I've been switching. I've been doing it for like three years though. It's funny. You just something to hit. You know what I'm saying? How do you like your partial passion? It's really to help the people man because a lot of people think that you can't do this You can't do that, but you can just got to be as put the hard work in You can get anything you want in life Because maybe see them, you know, I got properties and I got a corvette and all that stuff So people think that it ain't achievable when it is Yeah, I like what you're doing through.  Now you negative so That's what it's gonna say the girl about go ahead and check it out. It's uh cars and careers Now I forgot the girl native working here. She's she's seen this from a long time ago. Somebody said yeah Yeah, that's it right there. Yeah, make sure you get that subscribe button so you can lock in I drop every day at like seven seven forty. Yes, sir. I appreciate you boss. You stay up So guys, we have another issue with the all the way sparked up and I don't know what's going on But they need to get it together. Let me turn around this cheddar. We got order number five I get there to walmart and they tell me that one of the orders has been dispensed already This is the second thing that happened today with the all the way sparked up at first They told me the order's gonna be 21 25 And I then they switched it to 14 25 in the middle of it. Then now this I don't know what's going on They need to get together. We about to continue to get to this channel. Let's go So what guys you guys wouldn't believe this we gotta take go up all these stairs to the third floor I'm taking you all with me.   Guess what I gotta do tomorrow for exercise I had exercise and then do a hundred burpees I'm talking about the lead the lead the weapon 18 We right here and keep on going, baby And I got two bags in the back here with the photo smack Let's get to take two photos this time smack Don't She That was a critical one my legs hurt man Look, so the reason why we had to take two photos one photo was for spark and one photo was for us to send to spark So this is what happened my business partner cars all the way sparked up They said the the reason why we have to send them a picture of the owner being delivered So they can take off the other orders because I push uh start delivery before I left walmart Which I don't see why I wouldn't because I'm starting to get all the way sparked up again Order number six. We getting paid in full no money Mitch all the way sparked up two orders 4.7 miles for 1815 We about to get that green guess what Both of these orders are going to an apartment and not only not only that One of the orders the second order actually is going to the same exact apartment I just came from and I had to climb those two by the stair that was critical But this time I'm only going to climb one either way go. We about to get it done. Let's go Just like that. We are here to drop off order number one.  I'm apartment one on one It's like jump I don't know what Just say zero oh, that's 101 say zero Okay, so one on one Hello, how you doing, man? I'm doing great. I can't complain. I'm still living It's the truth. Here you go. That's two of them Thank you very much. I really appreciate you have a good one. I just need a quick signature. I forgot about that Thank you.   It's time to get in the mix Hey, how you doing the nigga? This is Jerome. I'm here with your walmart order Okay, I'm coming down now. All righty. See you soon. All right Step back in with photos We go we are here to drop off order number two. What it do Yes, sir. So this is this what y'all don't know this like on the set for those of you who's familiar with air You know what's going on?   It doesn't ever stay the same And I think that if you're not growing You're eventually dead that you get to grow get a growing girl, baby We end up drop them at the top Drop them at the top They get this last open John right here tissue stuff like it's hot Step back. You already know what's happening. It's photo. Ah, it's a photo. So real pop. Let's go though Order number eight. We about to get this money and I hope it ain't too big all the way That's 5.1 miles for 34 34.  They said deliver inside of the porch I'm glad that they gave us some instructions, man. They said it's okay to put it on the floor So I'm going to put it like right by the door. So it's easy for them to grab that that bread Nice Now here open those windows get some cards for the educator here Or how about you on the side of the photo you already know to smack with the photo Order number two, we're gonna have to take a few trips, but it's not gonna be bad Hello, you want me to leave him right here? All righty Oh, okay You're welcome Get busy.  That's what she let me just leave him right there Oh I'm done. You have a great one, ma'am You're welcome Last one y'all know it's time to get it done, baby. Walmart 13 out of 5.3 miles for 1150 get with me Excuse me Um, I have a delivery for Tracy What I have a delivery a Walmart delivery for Tracy What address 1316 floor 2 maybe upstairs 1316 upstairs. Yeah, okay Okay, so go up these stairs right here that's going straight here. Yeah, you can go this one. Okay All righty. Thank you I ain't see the second four things like later. I just saw it like right now I'm gonna take this All righty. Yeah, he's talking just sitting right here.  Here or in? It's all right Getting together. I think we actually did a video in this house before To you on it I'm quite sure I'm pretty pretty sure I'll be remembering stuff like this All the time, baby I wouldn't have put this stuff separately from the water I don't want to put on top of the water because it's probably the first thing he's gonna grab That's the first thing I would grab at least You know what I'm doing? I ain't press all these buttons Hit them with that photo smack with the photo we go And just like that it is the end of the video. I hope you guys enjoyed the content And guess what? We made 208 71. We came and got a deal. Look at the time It's 140 shortly we came we saw we caught up when we were in Barkers Also, this is this is day number two of me doing dash by myself So again, I'm sure you guys there's no excuse or no reason why you can't get this money You can't get this 200 plus a day and get these haters away All you gotta do is apply yourself and keep on grinding so you keep on shining I hope you guys enjoyed the video also If you want to chance to win something a free merch or you have to do is email me at rome If yous at gmail.com send me a picture so you subscribe to the channel and earn your chance to win It's time to get it in. I see you guys on next one. We're going we're going we're flowing You already know it is DDK and I'm on my way


to be celebrating the outgoing fellows and the ATC residents and we're going to welcome the new class. The fellowship program and ATC program is considered among the most prestigious throughout the country. Hail and farewell, let's celebrate. On behalf of everybody I want to thank you for all the efforts and all the hard work you're putting to get the organization on the right trajectory so thank you very much. I think we should have a round of applause for Dr. Stemman. So Dr. Stemman always had the gift of surrounding himself with great people. We had a lot of fun together and they were a really great group but they were also very good young professionals and I'm very proud to congratulate you guys as you graduate and represent our alumni going out. Jimmy you're part of the family so thanks for all the great work you've done and for these great three years here. I'd like to thank everybody here. These three years have the best best time ever in my life. Now Kubla congratulations. Yeah I'm never gonna forget this so. Jess has done an outstanding job here and I can say that I would trust him completely to operate on me or any of my family. First off I want to thank God for getting me through all this. It all helped me out a tremendous amount. The Sports Medicine Fellowship allows fellows to rotate through practices within the Stemman Clinic. They work directly with five specific surgeons. And that's what we're all here for really is to take great care of our patients that we've learned from Dr. Stemman. This evening here is culminating 13 years of busting their butt to get to that next level and get to that next level and get to that next level. When they get here their diamonds already you know we just polish them up a little bit over this year and leave here as excellent ethical really elegant physicians not just surgeons. And so congratulations. What you don't know about Catherine is necessarily she has an MBA. She was also a certified physical therapist. I'd first like to thank Dr. Stemman who just you know created this legacy and he's the only reason why we are all here. You're gonna do amazing Wells. I'm proud that to say that you spend time with us and congratulations Brandon and welcome to the family. I want to start off first and foremost by thanking my wife Kim. 12 years ago we walked away from a well-established career and let me follow my passion. For Dan we're not one of the best we are the best sports fellowship so it's that's very clear okay. Connor congratulations for doing our standing job. I'm sure you'll do great when you go to Springfield, Massachusetts. I appreciate all the advice this year and you've been spectacular. I think he's an all-star in all regards. He's gonna have a great practice I know in Vermont. Everybody in the clinic from the teams the ATC's everybody that's been involved has been so welcoming just right from the first step when I got here. Alice and I are from New York so if you say hi to someone on the street probably the best thing you're gonna get is them just mumbling something at you and the worst is gonna be something much worse but everybody was super super super friendly and welcoming. My patients love them everybody loved them great manners always calm. First to the new fellows welcome this year goes by sexually fast so really don't blink try to take in everything you can be a sponge and before you know it you're gonna be up here doing this speech next year. He's one of the most kind of solid stable nicest guys we've had. Lauren's lovely wife. Wow I mean where to start it's pretty difficult this has been such an amazing year and everybody in the audience today I just like to say thank you. He's from Bloomington Minnesota he'll be the next best thing since I'm all of America you guys will see that. Dr. Phillipon I hope I make you proud with taking care of all of our seals that have really bad hips. And to all the support staff without the athletic trainers enthusiasm I think some of those they brighten our day and they keep us going. ATC support staff, PAs make sure we did a good job so thank you all. We want to thank you for the dedication that you showed to teaching us the patience that you showed to teaching us for all that you've done to us. I can universally say that we're all ready to go out and start our practice and we will continue and hope to make you proud throughout our careers.


Member Statements, the Member for Whitby. Thank you Speaker and Chair providing $175 million to hospitals through the Health Infrastructure Renewal Fund and over $7.6 million to community health service providers through the Community Infrastructure Renewal Fund. Within the region of Durham, the Lakebridge Health Network will be receiving approximately $1,320,000 and the Korea Community Health Center $87,000. Speaker, this funding allows healthcare system partners Lakebridge Health to address urgent infrastructure renewal needs such as upgrades or replacement of roofs, windows, and security systems. Speaker, these are essential improvements that will in return deliver excellent care to patients on the front line in a safe and comfortable environment. Through the 2022 Ontario budget, Ontario's plan to budget and as part of its plan to build a stronger, more convenient and connected healthcare system, the government speaker is implementing the most ambitious plan for hospital expansion in Ontario's history. This includes speakers supporting more than 50 major hospital projects that would add 3,000 new beds over 10 years. Thank you Speaker. Member Statements, the Member for Humber River Black Creek. Morning Speaker, as I happen to rise on November 21st which is the day that commemorates St. Michael the Archangel and the old calendar I want to wish all those celebrating a happy St. Day, Sretchnoslava. Thank you. Speaker, the months-long shortage of basic children's pain and fever medication has impacted families across the province. For too long, most parents and caregivers have been unable to find any on shelves with or without a prescription. The little supply that can be found for sale online has been reported for sale as high as $300 by price gougers. The shortage has left many parents feeling desperate and panicked as we head into the height of cold and flu season. Matters have gotten so bad that the Ontario Poison Centre has been receiving calls about children who have been given incorrect doses of adult pain medication. The shortage has put additional stress on our hospitals as many parents have rushed their children to emergency departments because they were unable to manage fevers at home. Hospitals have had to postpone long-awaited surgeries and have also considered transferring patients to Buffalo for treatment because they're so overwhelmed. A shipment of this children's medication is finally on the way, but if you ask parents and guardians, it isn't coming fast enough. Plans have to be made now so that when the shipments arrive, medications are distributed fairly and the government must do everything in its power to prevent hoarding and price gouging. And finally, these shortages show why we must bring back manufacturing to Ontario. So we are not so self-reliant on the winds of international suppliers, whether it's medication or so many other things. Thank you. Member statements? Member for Rampanese. Thank you, Speaker. For the first time since 1986, the Canadian men's soccer team will be playing in the FIFA World Cup. Hosted in Qatar, not only is this a proud moment for Canadians as we enter the cup after 36 years, it's a proud moment for Bramptonians as well. Speaker, Brampton is a city with an immense amount of talent, and a week ago, Canada's roster for the FIFA World Cup was announced. And I'm so proud to hear that over a quarter, seven out of 26 players will be on the Canadian men's national team, will be from the great city of Brampton. Speaker, all seven of these players started their youth career in the city of Brampton. The dedication of these men have displayed throughout their careers is not only impressive, but is motivating for our youth and for our community. I would like to acknowledge the seven Bramptonians representing Team Canada and the FIFA World Cup. Kyle Lauren, Liam Miller, Jonathan Osorio, Ike Ugo, Teijon Buchanan, Junior Holiet, and Antiba Hutchinson. These players are homegrown heroes, and we appreciate, and as we prepare for the games to begin, we as a community are extremely excited to cheer them on, as well as all of Team Canada, as they head to their first game in Belgium on November 23rd. Thank you, Mr. Speaker. Members, statements? The member for University of Rosedale. Thank you, Speaker. Democracy is important. Humanities struggled for hundreds and hundreds of years to secure democracy. People went to war to uphold democracy. People have lost their lives to secure the right to vote. Bill 39 is an affront to representative democracy. It is not democratic. Do have eight out of 25 councillors decide matters that affect 2.9 million people. It is not democratic to have the Premier do away with an election and handpick regional chairs. This has nothing to do with solving the housing affordability crisis, and this has everything to do with taking power away from citizens and concentrating power in the hands of the Premier and the Mayor of Toronto. True leadership means governing for everyone, not just the few. True leadership means listening and collaborating with Ontarians, not just the ones that donated to your election campaign. This government has political power. It's true, but Ontarians have people power. We have people power, and people power always wins provided that we exercise it. Thank you to the many of you who have written letters, made phone calls, attended protests, joined advocacy groups, spoke out in the media, are going to court and who are persuading and encouraging your friends and neighbours to speak up and get active. In the face of a government that does not respect democratic norms, our involvement has never been more important. Thank you. Member for Oxford. Thank you very much, Mr. Speaker. Mr. Speaker, Ingersoll-Tilsenberg and Woodstock Chamber of Commerce have recently handed out their annual awards of excellence. These awards honour local businesses and entrepreneurs, their success, and recognise their contributions to our community, and I'd like to congratulate each of this year's winners. From Ingersoll Chamber, Ian E. McLaughlin Limited, Red Dragon Dairy, Kayla Hahn for Youth Citizen of the Year Award, Ian Robertson for the Mark Warnick Citizen of the Year Award, and Alice Shelton for the President's Award. From Tilsonberg Chamber of Commerce, Tilsonberg Garden Gate, Tilson Pizza, Fleetwood Metal Industries, Legend Fleet Solutions, Execulink Telecom, Margaria International, Rob Bilger for Entrepreneur of the Year Award, and Amy Rohr for the Esseltine Positive Change Award, and from the Woodstock Chamber of Commerce, VON House of Secure, Nodes Pasta, Oxford Energy Solutions, Paws Up-Obedience Training, The Womb, Jarful Local Refillery, Willow Grove Animal Welfare Centre, and Jack Street for the President's Award. Mr. Speaker, these winners demonstrate that Oxford Spirit and Hard Work Innovation and Community Giving is going strong in Ontario. Thank you very much, Mr. Speaker. Member Statements, the Member for St. Catherine. Mr. Speaker, I rise today to honour that at the end of this week on Friday, November 25th, the 60 Days of Activism Against Gender-Based Violence Campaign will begin. In this Chamber, we have an obligation to reach across the aisle and across communities to do everything in our power to end violence against women and girls. In this province, we have the roadmap to reduce, prevent and respond to gender-based violence. Over the summer, the Coroner's Office reported that the province's inquest into the triple homicide in rural Renford County resulted in 86 recommendations. 68 were directed at this provincial government. It has been six months, and this provincial government has not publicly responded to the inquest recommendations in any way, ranging from formally declaring intimate partner violence as an epidemic to the creation of a survivor advocate role to look into interpersonal disclosure laws like my PMB, Claire's Law. If we only use our voices to memorialise and honour those that we lost while being silent when asked to meet the moment with action, then we need to reflect deeply on our own values. These recommendations are responsible, reasonable, and it's our obligation as leaders in the province to make sure they see action. We all know that the vast majority of domestic homicides are both predictable and preventable. I hope all my colleagues will challenge gender-based violence with action. Thank you. Member Statements, the member for Etobicoke Lakeshore. Thank you, Mr. Speaker, and good morning, everyone. You know, I'm delighted to report that last week and writing of Etobicoke Lakeshore was packed with great news for my constituents. First, let me express to my colleague, the Honourable Minister of Seniors and Accessibility for the pending announcement of the recipients and my writing for the funding for this year's Seniors Community Grant Program, totaling nearly $130,000. Thank you, Minister. These grants are awarded to organisations that help seniors stay fit, active, and healthy. And they recognise the debt of service we owe our elders, those who built this province and served as the mainstays for our families. Second, I am thrilled to report that the fabled Dorothy Leigh Hospice will receive two additional beds as part of Ontario's government's plan to stay open, health systems stability, and recovery strategy. The hospice commemorates Dr. Dorothy Leigh who pioneered hospice care in Ontario during her career. Dorothy Leigh became an internationally respected oncologist before herself succumbing to cancer in 1994. This funding stands an additional tribute to her memory. Third, and finally, I'm pleased to share news of a significant funding for upgrades, repairs, and maintenance for hospitals and community health centres serving my region's residents. Trillium Health Partners received more than $4.2 million from the province's Health Infrastructure Renewal Fund and Unity Health-Tronable Benefit from $10 million over the same period for the same purpose. These investments will ensure patients can continue to access the care they need while providing our area's health system with the tools to improve health care for all Ontarians. Taken together, all of these share a common goal for helping to make Etobicoke Lakeshore one of the best places to live, work, and raise a family. Thank you. Thank you very much. Members' statements, the member for Don Valley West. Thank you, Mr. Speaker. I would like to address the pressing matter of Bill 23, the flawed Bill 23, and the Conservative government's broken promise to protect our green belt. Paving over farmland reduces local food production, which contributes to higher prices and makes it harder for Ontarians to put food on the table. Thousands of people are reaching out to this government through their MPPs, through petitions and rallies, asking them to reconsider. Is this government listening? Their own housing task force says, and I quote, a shortage of land isn't the cause of the problem. Land is available both inside the existing built-up areas and on undeveloped land outside green belts, end quote. The land in the green belt, meant to be permanently protected, provides our food, clean drinking water, and clean air. Proposing to replace it with different land, protected only until this government breaks that promise too, would be laughable if it were not so sad. Bill 23 threatens existing affordable rental housing. My constituents in Don Valley West and Thorncliffe Park, many of whom are new Canadians, are worried that the 50-year-old apartment buildings they live in are being worn down and can be torn down under this bill and not replaced, forcing them out of their community. They need affordable housing in their community, not houses in the green belt that line the pockets of conservative donors and green belt land speculators. With petitions of thousands opposing Bill 23, it's clear that Ontarians do not support this bill and want major amendments made. Is this government listening? Thank you. Thank you. Member statements. The member for Chatham-Kent, Leamington. Energy and optimism in Chatham-Kent right now. Recently, a small group of local business leaders purchased the Downtown Chatham Center, a large, outdated, under-occupied mall. In earnest, and at their own expense, these community partners developed a visionary concept for the future of the downtown, entitled Imagine CK. This bold plan proposes entertainment, education, culture, accessible resources, business, and a wide range of modern housing to the downtown core, all while preserving charm and historic features and facades. Most importantly, this was accomplished in collaboration with residents and officials. A modern, inclusive community hub will serve as the new library, art gallery, museum, and civic center. This new design replaces and centralizes several aging, inefficient municipal offices, requiring millions of dollars in repairs. Once complete, this hub will also showcase Chatham-Kent's rich agricultural roots and celebrate the area's important black and indigenous history. Anchored by a new state-of-the-art, family-focused entertainment complex, the second phase includes a modern, 4,000-seat multi-use arena, as well as space for farmers' markets, festivals, and concerts. With a focus on sustainable growth that embraces multi-generational residents and youth retention, Imagine CK offers people of all ages a reason to make Chatham-Kent their home and brings meaningful, well-paying employment and a multitude of lifestyle opportunities back to the area. Thank you, Speaker. Member Statements, a member for Brampton North. Thank you, Speaker. November 23rd, 2022, Speaker. That's the date when 26 players on Team Canada's men's rosters will make history. And Canadians from coast to coast to coast will stand witness. For the first time since 1986, and only for the second time ever, Canada's men's team is qualified for the FIFA World Cup. And Speaker, this World Cup cannot be more special to the great people of Brampton. As a certified Brampton boy, it fills me with tremendous pride to say seven of the 26 players on Canada's World Cup roster are from Brampton. Speaker, they would have had an eighth player from Brampton, but I told them that I was busy in this house fighting for taxpayers. Speaker, I've had the privilege to rise in this house on multiple occasions and speak on behalf of my constituents and the residents of Brampton. I know how hard they work for what they have. Brampton is home to people from all walks of life that chose to build their home here and make a life that they are proud of. The hard work, the sacrifice, the resilience, I see it every day in Brampton North. It makes me proud to be their voice here at Queens Park. I want to wish Tejon Buchanan, Kyle Lahren, Jonathan Osorio, Junior Hoylet, Liam Miller, Atiba Hutchison, Ike Ugbo, and the rest of the team, the best of luck. This is a historical moment. I encourage every member of this house to cheer on our Canadian boys as they take on the world and guitar. Thanks. Very much. That concludes our member statements for this morning. Introduction of visitors.


Welcome to Mainframe Matters, and today we have with us Louisa Sears, Chair of the Galassa Technical History Committee for Open Mainframe Project. Louisa, it's great to have you on the show. Thank you. Yeah, and as today, we are going to talk about Galassa Project. I want to understand, first of all, it's a new project. Talk a bit about what is this project about, what problem is trying to solve, and also if you can tell me what is the story behind the name. Okay, so the name is probably the easiest place to start. So Grace Hopper is, I believe, she's the kind of founder of Kobol, and she came up with the fact, the name The Bug, because she came up with the first bug, I believe. And so when they were putting together the Galassa name, I believe it's the latter name for a moth. It's, if you Google Galassa Moth, then some pictures will come up. And so at the time, the team were looking for a name that looked a bit weird, looked a bit different. And so there's a loose connection with Grace Hopper, which is quite cool. It's about four years old, but we are just releasing it, of course, into the Open Mainframe Project. So at a kind of a high level, the problem we're trying to solve is the manual testing that users and testers have to go through every day on the mainframe, because ZOS is quite a unique platform to kind of develop and push through changes. So at the moment, from my understanding, testers will have to go through many manual steps. So for instance, if they were creating a new banking account on the system, then you would have to log on to a web interface. You would then have to go into the back end, for example, Kix or IMS, and then into a database at the back. And at the moment, it's very difficult to make those changes through testing it end to end. So at the moment, a tester would go in and look at their spreadsheet of individual kind of keyboard inputs into a 3270. And they would record those screenshots. Test results would be everywhere. And it would kind of be organized chaos is how I would probably describe it. So Galassa is an attempt to automate that, make it seamless, and make it really easy for testers to kind of take back control of that ability to make changes. And so you're able to run that test that go from the web interface all the way to the back end and back to the web interface again in one automated kind of suite, which is really nice. And that's where Galassa kind of fits into the kind of new mainframe modernization agenda. And as you're saying, the project has been around for four years. So my question to you is that, was it an internal IBM project? And what made you folks release this into open source? And also if I'm not wrong, it will be officially announced at the open mainframe summit, which is co-hosted with the IBM exchange event. So it was originally developed to solve the testing conundrum within KIX, the customer information control system within IBM itself. So its own development problems. And they have their own testing facility. But the challenge they were having was exactly as I was describing. The ability to do the end-to-end integration tests were becoming much more difficult. And at the time, we have kind of yearly forums where customers can come and talk about their issues and talk about things that are going on. And one of the big questions that they always asked was, how do you test these mainframe applications? How do you do it internally? And we kind of would tell them what was going on and how we would fix it. And then they would say, great, can we have that solution? And that ended up being Galassa. So the way that it kind of evolved over time into the open source world, I think it's been open source for about two years. And the way that it kind of operates in terms of being able to extend Galassa, which is where the open source really comes into play, is that you have something called managers, which are these kind of plug-ins to Galassa, where you can plug in the KIX or the IMS or if there was something from another company, you would be able to create your own. For example, Azure would be a good example of that. You'd be able to plug in the ability to talk to Azure all within the same framework, within the same test. So the open mainframe project was a way for us to take it from its inception as an ability to do tests on internal IBM products. And then it branched that out into other cloud providers. And some users, some testers have very unique tools. And so Galassa is hoping to be able to accommodate to all of those different types of applications that you might need for an integration end-to-end test. When we look at open source project or open source communities, oftentimes it happens that there are projects which might overlap the functionality. And then sometimes there are gaps that you're trying to fill. If you look at open mainframe project, of course, they're not specifically for testing like cobalt check is there, test CI is there, which do the whole deployment, but it's also the testing. So when we look at this project, can you talk about where does it fit in, where it's like, we are kind of building the whole repository of the project, which complement each other very well? So there's a space, there's a couple of angles I could take here. The first one being that when I joined the mainframe community, I joined from kind of distributed world. I worked in cloud. I'd worked in open source previously, but it was all in the cloud forum. And so when I first came into Glassa, I thought, great, there's a way for me to test and access the mainframe without knowing the mainframe. And that was my major hook-in into the project, really. And that's what I love so much about it. And what I love is that Zoe takes very similar valleys and kind of vision for the mainframe. And I think Glassa and Zoe are definitely a potential roadmap item. I think because it holds the same type of mainframe modernization story, looking at how we can get... So for instance, if you were in the cloud team or you're a cloud tester and you wanted to be able to access the mainframe in order to run your integrated tests in your automated pipeline, then you don't have to know intimate details about how to use a 3270 in order to execute those tests. So I think there's a really close alignment with kind of the valleys of the open mainframe project through modernization and accessing from a space of little knowledge of the mainframe. The other project I mentioned would definitely be CableCheck. That's around specific testing of... I think it's unit testing of Cable. So Glassa can definitely look to extend that into CableCheck. So those managers that I talked about previously, that would be a good extension. So you would have a CableCheck manager that would be able to handle specific CableCheck tests. So really good integration points into the other projects in the open mainframe project, which we're really excited and it's hopefully on the roadmap for future implementation. What kind of community that is already here or what kind of community you are looking at building around this project? Of course, because we sort of had an open source variation of this before officially announcing this as part of the open mainframe project. We have garnered some interest already, which is great. We've had some users, some customers looking at POCs with Glassa. So as a baseline, we're in a really good position to kind of start building the rest of the community. At the moment, we have started, obviously I'm chair of the Technical Steering Committee, so we started that as a monthly meeting that we get together. There's currently four different companies that are involved in that, looking at the roadmap, looking at the blockers, kind of what a development doing day to day. We already have a development team running as part of IBM, and we've now open sourced that. So the scrum meetings three times a week, and then we have an iteration planning that we do every two weeks to look at storyboarding, look at what we're trying to aim for. And the, well, what's really exciting is that now that we're being announced, now that it's officially out there, we can publicize those links more effectively, hopefully through the open mainframe project website. So it's not just a closed room that only the IBMers can access. It is now a full official open source project. So I'm hoping to gain more of a conversation around testing. I think that's number one. I think the second is around, well, how can other companies, how can other users extend it? So I talked about Azure. We've got some users that have built an Azure manager. So how can we get that out into the public domain? And yeah, how do we get access to those people that don't necessarily want to play with a mainframe at its core at the nuts and bolts level? How can we get access to that from a kind of a higher level in the testing that they're doing? I think that's the main idea for us growing this community. It's around extending that platform with lots of tentacles. And earlier, you were also mentioning that there are other companies which are also involved. Can you talk about who are the other contributors who are contributing to this project? We run our public technical steering committee meetings at the moment and involved, we've got Broadcom. Macro4 have given some really great talks on Galassa through GSE Nordics and we're hoping that Michelle will come back and do another talk at GSE UK about their use of Galassa. And finally, Rabobank are on the technical steering committee. The project has been around for a while, but it's kind of new for the open management project and the committee. Can you also talk about what kind of release plan do you have for this project? We're currently, I believe, on version 0.29. So the team have been fairly kind of baby steps around making sure that when we do release our first version, official version one, that it's the right time. And I think we've been waiting for adoption by the open mainframe project to really get that going. So I said before that we have weekly scrums and we also have bi-weekly iteration meetings. That's probably fortnightly iteration meetings. And so that forms the basis of our road map. So in that, we've got, at the moment, our biggest work is around the CLI. So Galassa at its inception was accessed via Eclipse and that worked quite well for the first time being because the internal kicks team used Eclipse. However, now we're moving on to the CLI terminal-based move and that's partly based on some of the conversation we had earlier about mainframe modernization accessing the mainframe without knowing it. So being able to access Galassa through the CLI is one of the really big development points we're making at the moment. I think long-term we have some moves in terms of how we can interact with other managers. So making sure that that ecosystem of applications you can interact with are growing. But we do have a full road map between now and I think the end of 2024, we at least have items in that we're looking at doing. Authentication being one and looking at the Cable check in Zoe is something kind of for future that we're looking at. We do go into more detail in the technical steering committee meetings of course but at the moment they there are quite granular levels of roadmap items that I don't have to hand. Can you also talk about who would you like to see to get involved with this project and how they can get involved? So I would love to see some more testers involved. I'd love to see how we can really embrace the product, how we can, or project sorry, and how we can really include more usable features within the CLI. So for example at the moment we screen capture all the way through that test plan. So from the web interface all the way through to the 37270 we're able to make the screenshots of every time we make a change. So I think there's a really great test bed for all of the users of testing platforms, people that are currently using manual spreadsheets. I'd love to see them get involved and see how they can improve Galassa, see if they can find anything that would improve it from a usability perspective. I think the other great opportunity we have is around the cloud providers. There are lots and lots of different clouds out there. Digital Ocean, AWS, Azure, there's lots you can mention. And I'd like to see how other companies, other users are extending Galassa into those other applications. So they're the kind of main few that we could start with, but there are many more cases. For example, if you're a company that are doing internal testing, it's other ways that we could help with Galassa. So I think they're the kind of main things to start with. And then if you want to get involved, there are a couple of places you could do that. You could speak to one of the team directly on the Open Mainframe Project Slack channel. There's the Galassa website. So the website itself allows you to, it's got documentation to sign up to look at the CLI. You can download that. And then, of course, the GitHub page, Galassa-dev. And that's where you have all the code base to browse through, to have a look at, and contribute back if you feel like that's something you want to do. Louisa, thank you so much for taking time out today and talk about this project. And I would love to chat with you again whenever there is an update to the project. Thank you. Thank you so much.