Good evening. This is a talk about Debian virtualization present in future by Jan Lübe Please if you want to make a question or an assertion ask for the microphone So everyone can hear you and if we're going through this camera that one Please crouch as in contrast like games Yeah, thank you. Thank you So I'm here to talk about what is possible with virtualization in Debian right now and how that will change in the near future So I want to thank every one of you to come for coming to my talk I've been Debian developer for only one year now and So maybe I don't know all the details of the other projects that we'll see first I'll talk about what virtualization is and how that compares for example to emulation Which different projects use which approaches So we can see Which approach in which project is best for each use case and at the end I want to talk about how that is Usable right now and then any for Debian and how that will change in the future So why do you want to virtualize a computer? There are very many different use cases for it At least in Debian for a developer. It's mostly useful for testing software networking For others it's more mostly useful for consolidation increasing availability and redundancy by Supporting the same software the same stack on several different machines so we can switch easily It is also used for example by Amazon and other big companies for the so-called cloud computing So we have Software stack that runs on any machine, but you don't really need to worry where it is running you can rent the computing time by the hour Something I haven't seen yet myself is the follow-the-sun module that is for for example global global corporations who need to have Really low latency in the part of the world where currently the working hours are But they don't want to shut down their service So they use virtualization to move them between the different shifts Without a big downtime to another location Yeah, something else What are you using virtualization for? anything interesting So for example the browser to keep it separate from the rest of the system So any internet fitting facing software if it is in a virtual machine you and which doesn't have anything real on it Then if you get broken into all they have had access to is your toy virtual minimal operation and we also use a sea Linux in our virtual containers So it is very hard to break out of it. Even though you compromise a patchy or something Okay, I really like to use snapshots on virtual machines Well, I can just say okay. I want to make an update of something so I can take a snapshot which is done in one second or something like that and Then I put this update there and if it works, then I can say drop this snapshot Otherwise I can go back. So I really like this feature Containing badly behaving applications So basically containing anything you don't want to have physical access to your hardware Yeah, there are a lot of different methods to reach this I go from the full virtualization over the more complex stuff to hardware emulation So with a full system virtualization I mean something like VM virtual box KVM whether Guest system doesn't need to know that it's being virtualized There is power virtualization that has been done by Xen August and even before by UML There's container virtualization something like Linux V server. Yeah, that are different terminologies But you use it for similar use cases so at least listed here and you have Virtuoso or VZ which supports that and on the basic level jails and change routes Then there's I API translation for example wine and System emulation We don't even need to have the hardware the guest software was written for There is just QMO PPC dustbox calculus. There are a lot more in Debian so for emulation the host has software which Replicates all the hardware that is necessary to run the software There's an advantage that you can any guest software on any hardware system But it's really slow so it's Mostly useful for testing not for running service or so But even with the emulation it's sometimes faster than any real hardware which it's available So for example arm built ease on really fast and B64 machines are faster or have more memory than the real machines The full system virtualization It's for the same goal, but you need this to have the same architecture than the guest except for AMD 64 and I 386 so you can run on many five guests, but it has higher complexity because The guest expects to have access to the hardware and you need to only emulate these parts of the system This really depends on the hardware you're running on because if you're in an architecture that's actually designed for Like the good old mainframes The complexity is not actually that high But even if you're an x86 as long as the actual emulated hardware you expect is low enough It's not significantly more complex very good example for that is a VM ver that Very carefully picked the hardware they emulated to avoid this complexity But it's still harder to get right than just emulating Then we have power virtualization which Xen is doing that is the first time we tell the guest that is running on virtual hardware So it can cooperate So we have lower overhead because we don't need to emulate things like disc controllers network devices and so on But of course the guest needs to be modified so we don't can't run any operating system Then we have container virtualization which may not be virtualization at all Because we run just one kernel, but the applications see different environments With a minimal overhead we have better resource sharing because we can share the page cache Can share the memory when one guest is using less memory But of course we can only run one kernel so all guests have to use the same kernel And at least with the current implementations The isolation is not as strict with as with power virtualization or full virtualization API translation We've seen wine this has taken a very long time To reach the current state so you need to reimplement for api which is really really complicated but You don't need to run that OS once you've re-implemented the API so it's low overhead So now we'll see what projects there are There's QMU which is An emulator Has been around for a long time emulates a lot of hardware for different architectures run some different architectures It uses something called dynamic binary translation Which is it looks at the code which is running and in the guest and translates it to native code And stores this native code somewhere else The device Library for is used for Xen KVM for virtual box also So it's some sort of base for some of the others That already can do snapshots it can do USB path through through the guests we can use all sorts of USB devices in your guests and there's an Additional kernel module which can accelerate the guest on x86 and mv64 hardware Then it's a lot faster than just emulating There's an basic management interface that's called QMU later. It's also available in Debian Then we have virtual box It was started by Endotech a German company and is now developed by Sun It's this the core of a commercial product There's this virtual box OSA for open source edition and They have a commercial edition which has more features for example, it was be passed through is only in the Commercial variant there's some interesting features. You can use the So-called seamless windowing module which support so you have windows for example windows on your Linux desktop Which you don't have a windows desktop only the windows And so it's all of virtual box earlier this year After they acquired it from Endotech Only this virtual box open source edition, which is the core and This is a commercial Yes, you can download it for free and try it, but you expected to buy it then and The commercial edition also has something like RDP Access to the virtual machine and so on yes so Xen Has also been around a long time was open source from the start currently supports x86 AMD 64 and the IA 64 titanium architecture they started Paravigilizing Linux and Probably started the Paravigilization trend in Linux and It also supports full system virtualization on modern CPUs, which have these Intel VT and I am AMD s VM support, which is on the current CPUs You have the small hypervisor Which starts before the kernel then loads the Linux kernel and runs that as the so-called domain zero which has access to all the hardware and Then use from there you start the guest systems, which are called the DOM U and they use virtual devices which run in DOM zero and Currently redhead is pushing For inclusion in mainline it's For the server space probably the most mature open source version variant of virtualization There are a lot of management tools available You have live migration that means if you have Two systems we can access to the same this devices you can Switch to the running machine from one to the other in less than half a second or so So it's not noticeable to use us which access these machines of the network You can pass through PCI devices So if you have special hardware that needs to be used in the guest you can pass through and The management tools for example Xenman Xen tools Xensher Garniti are all available in Debian There are currently some problems with using Xen There is no support for the DOM zero in the current mainline kernel and Only basic support for the DOM zero for the DOM U in mainline in The current cars they are merging mostly the DOM U in 2628 we hopefully have DOM zero support They are switching their Virtualization interface from the propriety one to the one that is used in mainline inox, which is part of it ops That is that's not ready yet The problem with using a separate hypervisor below the Linux kernel is that you don't have suspend You don't have power saving can't really use it on notebooks because you lose suspend There's The problem that 3d acceleration on the host is difficult because you also lose some direct access to the hardware and In general, there's a lot of code duplication They used some device drivers and ACPI stuff from Linux and copied it to the hypervisor Then more recently we have KVM Which is hypervisor completely based on Linux It's currently supporting x86 and indy64, but there are supports going on for IA64 power PC 440 which is an embedded power PC and also used in some large IBM boxes and It has support for s390 Which are not yet ready You need in contrast to Xen need these hardware support Even if you use the new power virtualization stuff Which is only used to speed up IO the guests run as User space processes on the host with some kernel support it of course uses co-emote who emulate all the hardware and Company who has sponsored this development is called one run it and it's now selling their first product solid ice which is some sort of desktop Virtualization stuff you run the Employees desktop on the servers and they just look at it over network And with the last release Ubuntu has chosen to use KVM as their default virtualization method And only use Xen if you have no hardware support The features are similar to QAMO so You have the snap shotting and so on with as with QAMO. You also have live migration as in Xen you can swap the guest pages because they're just normal user processes and There's a migration path for Xen users Which is an experimental project called Xenna, which can you run Xen guest kernels on KVM? And of course because you're just running normal Linux. It really works well on the laptop Also, it's compatible with the real-time extensions from Which are currently being merged so you can run a hard real-time Linux kernel and for example a Windows GUI on top Seeing people use that for controlling welding welding lasers Still some problems because it's under heavy development. They don't have stable releases so sometimes you have regressions the performance is not really predictable from version to version and There are no integrated management tools yet so If you don't want to run a whole system in the virtualization you can choose something like v-server or open vz where you only have the linux kernel and Several containers below that Linux v-server was a community project which has stalled in the last time a little bit Open vz was first a commercial product by parallels and is now open sourced They are pushing for mainnet integration and are with that further along than Linux versus v-server It isolates file systems users processes at works and devices per container from the other containers So we have schedule long scheduling inside the container and each container has limits on what sort of resources it can use They are shared among the containers using this approach has Some advantages compared to full virtualization because because you can just access the file system from the host you can see all the processes on the host Because it's just one file system page cache can be shared between virtual containers, so you don't need that much of memory Can you run more guests on the same hardware compared to okvm or xn and it also now supports checkpointing and live migration But it's not really as seamless as with the others Because first need to save the snapshot to disk transfer that and boot it on the other machine So that takes a lot longer than a half a second Yeah v-server Has until two days Not being ported to the current kernel of that now is a patch so that may Come into Lenny if it's stable enough no for managing the soul stuff there has been Initiative by Red Hat that is live word It is a abstraction layer over the different virtualization projects so thoughts Xen QMA KVM LXC which is Linux containers and OpenVZ We have a GUI interface for managing the guests creating guests which and virtual networks can attach them reboot them access their consoles This split in two parts the live word daemon which runs as a route of course and Use interface which can connect to the demon via various ways Locally via debas and policy kit over the network via SSH with different authentication methods Also announces the presence of service via avari Yeah, where do we stand with the daemon? We right now have no Xen dom zero kernel in Lenny or in unstable Which is problem for all the people who installed Xen with edge They have no clear update path It is possible that you can use the old edge kernel with the current user space and We hope that when Xen has been integrated upstream Maybe for Lenny and a half if that will happen we will then have a current kernel again, which can run Xen dom zero It's not yet There's no decision yet. Whether we want to have the old Edge kernel supported in Lenny or what should happen there then the v-server support Is supported of course in edge, but because until two days ago there was no patch It's not yet in Lenny, but it seems that it will be supported in Lenny There are open vz packages in unstable, which will probably migrate to Lenny. So we have support for that and And QEMO virtual box KVM open vz The bird are already in Lenny and are really easy to install and use Yeah, where will that go? Xen will be merged probably into 628 Open vz is currently being merged step by step to the large set of changes Then Xen then redhead will continue to develop lipvert So we have a consistent console to manage all of the virtualization stuff Then there's some Development in QEMO going on don't know what the roadmap is Perhaps somebody here knows more About QME there is there are a lot of change upstream currently They've switched from using GCC as the code generator to something called TCG tiny code generator So it will be able to we will be able to remove the dependent build dependencies on GCC 34 and Support more architecture. It's also a bit faster. And so the QMU has been in standby for a few months, but since the end of April actually there are a lot of new codes merged mainly from KVM So I hope we'll have for Lenny plus one support for Spark64 a guest support that will be useful given that the behind doesn't support Spark32 anymore and Maybe also the para virtualization para virtualized devices like our network card and our disk Thank you. And in the long term, which is maybe two or three years. We will see that most of the S's are available of a very virtualization so We will have common para virtualization interface Which can of course improve resource sharing performance you can have ballooning which means adding and removing memory from a running guest and Maybe hopefully pass through for 3d graphics But there's still a lot of research to do in that area Yeah, does somebody not have ideas what will happen beside this list Dom 0 on 2628 seems Very soon from my perspective as a kernel developer. Yeah, we've not seen any patches yet and given What bunch of crap all that consent code always was it will take a while to be didn't shape Open vz as is will not be in merch line Which actually have been merged main line is that the container folks which is a lot of the open vz folks a lot of IBM folks people like Eric Biederman who was not part of any of those projects a little bit of the V server folks but not much actually working on Basically doing everything from scratch or sometimes taking good parts of the existing solutions and do this and this has been ongoing for At least a year and a half if not you and it's not really gonna be finished any time soon That's the perspective from kernel land The number of two six twenty eight was from status report from extended a lot of us all that may be built by Gonna say no, but I'm gonna say I would be very surprised to someone But at least there is Development going on to get it better supported or at least based on the based the current patches The stuff that is currently main main line So hopefully we will have current sense apart on the kernels again. Yeah So that is a call for help We need probably to do some Improvement in Debian real in virtualization You have all the tools there, but you still need to install them tweak stuff manually Livered will have there, but I think we can still do something to make make it easier to use Debian as a platform for virtualization Currently most people probably use redhead for Xen maybe Ubuntu for KVM But It's not that way integrated in Debian yet So to make that happen we probably We really need to have more testers at least further for the power virtualization stuff stuff because it depends a lot on what hardware you have some bugs are only Visible on one processor with a specific guest So it's not really possible for One or two developers to test all the possible combinations combinations that would really like to Encourage every one of you who has some use case for that to try some of that stuff report bugs tried with different guests So we can get a lot more coverage that way Because I can't do that on the portal machines for different architectures. For example PPC It's not possible on the portal machines because you need root access you're restarting the machine you get kernel crashes They don't let like that on the Debian portal machines So if someone has access to that hardware can run those tests that will be really helpful Yeah There's I also I also want to make a call for help on for the QMU package There is currently a team, but it seems Currently I'm the only one working on that So I would like to find some comment on us. So if someone is interested, please come to look with me Any questions? Yeah, the current situation with Xen is basically that we only have the kernel Supported the yes supporting the edge kernel. Yes, so the next When we switch to Lenny hopefully soon Did the only the only way to keep running our Xen servers would be to use that kernel? Yes, and is there any Because of the the problems meant that I Don't remember his name mentioned. It's basically that the Allurement fork it too far from mainly in kernel and that's why Xen hasn't been Merged back in yeah They sent developers started Designing their own visualization interface and they are the only ones that use it and right now in the Linux kernel There's this paravirt ops interface Which the old Xen patches don't support? That didn't even add an interface But instead they claim they were new architecture supported by Linux think of like power pc x86 and then Xen Which was at that time, of course only Xen on x86 So this would have duplicated even more if they had more architectures and we kind of develop a set This is really not maintainable because I'm 90% of the code is copy and pasted from x86 anyway So we better have to find some interface and that's what part of what ops went and that's what Well, I'm KVM is running on that's what What the Xen dom I'm dumb you support right in now is working on that's what the strange VM ver of VMI binary blob runs on and that's what they finally after Ignoring it for a year have started porting their dom 0 to but the problem is that of course just porting to this interface alone It's not enough that might be parts not yet covered by that interface because no one has done as strange and drug induced things as the Xen developers did or Because it's of course not just that interface in the machine specific code But a lot of device drivers which are very different for dom 0 versus dom you so it's still a lot of work And the last time I saw the the redhead patches. They were peeing all over the kernel tree and that's something generally not looked upon very well Well from what I've seen well and reinforcing what you're saying Xen is Well was there the ray the great booze words some years ago But I think it's going to fade away because on one hand it's a lot of code duplication It's much dirtier and well you were asking what what should we do with our send hosts a after Lenny released I think the easiest way out will be to tell to advise our users when it's possible to migrate to a I mean when you're they're using full virtualization The best thing is to migrate to KVM other users may be me great to be server. Why? Because they in the end they are much cleaner in the end instead of adding An external operating system. Well, the hypervisor is just that Well, they the approach is quite saner in in in my opinion Of course, there there's many things that they send does offer that the that is not integrated in other solutions But I think that's that's what already happening by itself The way it's right now the switch At least for the linear release will be quite hard for other people using Xen Because KVM only runs on machines which have this hardware support and it's not as stable yet as the Xen on Edge was and If you need to run for example Windows then or Systems where power of virtualization is not easy Then Xen then KVM right now isn't really a full replacement for Xen I mean if if you have the Virtualization capable hardware actually is a pretty neat migration fart and that part that you already mentioned that's Xenner Which works very well, but about the stability. I don't know I've only heard that stability argument from people who are not actually using it So I use KVM on my development and traveling laptop All the time because that's where I have my virtual machines and where I do all the kernel testing file stem testing Distributions in and I never ever had a single KVM related incident in the last year and a half I mean stability wise from the Source code side because there's still a lot of change going on But even that is not a problem because the user space is backwards Compatible, so I still have a KVM user space from over a year ago And I just put the new mainline kernels on it. I just run one built yesterday, and it still works perfectly Yeah, so we probably need Xenna support and devian soon And the other part is like this is why me as back then in each times part of the kernel team Was very unhappy that it's released at all with Xen Because I was expecting exactly that that no one can be bothered to maintain it anymore It was shipped anyway And now we have the debacle and we'll see that same debacle with The v-server and open vz and whatever valley wants to push in because that's just not going to be maintained at some point anymore So everyone who's thinking about it. I would strongly recommend against starting to use it At least for a production system for playing around it's perfectly fine, of course Hello Right now. I'm in the process of updating the debian kernel handbook for Lenny And if people who know about this stuff would like to write a paragraph or a chapter for the handbook to document the current situation with Xen That would be a very good contribution Where can you be reached? That's Yuri at debian.org Yeah, something else. Oh Thanks for your attention


Sujatha is going to talk briefly about clinical trials. It may not be pertinent specific to kidney cancer. You have heard a lot of information, but one of the idea is we think clinical trials is such a valuable part of what we all do. And we just wanted to talk a little bit about what these are so that you get some comfort level. So again, thank you Sujatha for doing this. Good morning, everybody. So like Sandy just said, let me start off by just getting a show of hands. How many of you have ever participated in a clinical trial? So few. I can count four. How many of you are currently in a clinical trial? Two, three. How many of you have thought but then not participated in a trial? One. Wait, we all understand when you get diagnosed with cancer, it's one of the most confusing times in your life. You go to your doctor, medical language, here's your treatment option. Hey, I also have a clinical trial for you. So I know going through that decision tree, like you've already seen surgery, chemotherapy, do I wait, do I go on a drug now? So it's very confusing. And one of the options for every cancer or actually all the chronic diseases now is a clinical trial. So the aims that I set forth when I prepared this talk for you guys is just to talk about the basics of clinical trials, just to introduce you guys to what the concepts are, give you a little behind the scenes of what happens at our end when we start planning a clinical trial. And I actually want this talk to stay with you when you go into your doctor's office and this word is mentioned again and you're like, OK, I heard that talk. I know what you've done and I know what questions I need to think about and ask you now. So that's my primary aim for this. So it's going to be a very non-medical talk, if you will. I also want to introduce you to the resources that you can look up. The internet is loaded with information and we can just help you direct you to the right websites, if you will. And then just talk about the trials in RCC that are available at Stanford right now. I'm not going to discuss the results of any trials, but just introduce you to what we have ongoing here. So what is a clinical trial? So it's a research question and it can be anything. It can be just getting x-rays every six months, improve the detection of lung cancer. It can be if I walk up the stairs, that does help my cancer. It can be, it's better for my cancer. So it's a research question. And what a doctor or a researcher is trying to do is to tell, if I give you this intervention, is that going to alter the course of your disease and is that going to slow or stop the disease? So that's the basic premise behind any clinical trial that's done. And I said interventions and like I mentioned, it can be anything. It can be a diagnostic test. It could be a PET scan, a CT scan, a blood test. It could be a vitamin. It could be an exercise regimen. It could be a lifestyle change. And then again, it can be surgery, radiation, chemotherapy as interventions that are offered to you when you participate in a clinical trial. So what goes on behind the scenes before we plan on a clinical trial? So researchers, doctors, we see patients every day and we keep thinking of how can I improve the outcome? What can I do differently? So a lot of the times, a lot of pre-clinical studies are done. That comes up with the biological rationale behind the question we're trying to ask. So a lot of the times we have a lot of testing done in cell cultures and lab animals from which we get data and then we say, this is a biological pathway. I have an intervention. I'd like to test it in humans. So a lot of this pre-clinical testing is done, published, reproduced, replicated. And for us to give us a sound base before we actually propose a clinical trial. When we come up with a drug, the US Food and Drug Administration has to approve its testing in humans. No drug is ever introduced. Even a prior approved drug, if it say, I'm making this up, say accident today is being used for kidney cancer, tomorrow I say I'm gonna use it for breast cancer. So even if a drug has been in the market but I'm going to use it for a different indication, I have to get the blessing of the US FDA to do it. Because the foremost thing in clinical trials is safety. And so that's what we call the IND. We always file for an IND before we start any clinical trial. And also when you're planning a trial, the one thing we all do is write a standard operating procedure, a standard operating manual, it's called a protocol. It'll describe our rationale, how we're going to test this in volunteers, what tests we're going to do, how often we're going to do it, how we're gonna monitor you for safety. And while we do that, the first thing that comes into mind is ethics. Is it appropriate for me to test it in volunteers? And so that is a question, that's answered not by the researchers, but we come up with a panel of people that includes clinicians, researchers, and even people from the public that volunteer to serve on these committees, that actually determine the appropriateness of giving this intervention out to the public. So we write the protocol, but an external body sits and looks at it, looks at the ethics of it, looks at the safety of it, and then says, yes, I think your plan is good, I think you should all go ahead and offer this to other people. This board, I'm sorry, this is called the institutional review board. Many of you might have heard this term, but this is the body that actually is in every institution that actually any hospital, any academic center will have an IRB that goes over all these protocols and it will appropriately flag questions and say, have you thought about this? Have you thought about how this could harm your patient or not? And we are liable to respond back to them and say, this is my plan, this is how I'll do this. So once we've written our manual, once we've got everything approved by our IRB, we go ahead and start our trial. Now there are different phases of a trial. I talked to you briefly about what a preclinical study is. Say I came up with a drug X and this is the first time I'm going to give it to humans. I don't know what dose to give you. I don't know if it's five milligrams or 10 milligrams. We've done preclinical lab work in mice, monkeys, and we come up with a dose and we say, okay, this is the safest dose that a primate tolerated and we're going to give it to the next primate and let's start with the lowest dose. So when we do a phase one clinical trial, our main objective is to find the safest dose that can be tolerated by human volunteers. The secondary objective maybe, is this doing anything to the cancer or to any other disease that it's being tested on but the primary thing is going to be safety and finding the right dose. So that's a phase one clinical trial. Few number of people and we're just testing it to see what the safe dose is. Once we know, okay, 10 milligrams of drug X actually was safe, did not cause a lot of side effects, then we go on to a phase two trial and now my aim is going to be different. Now my aim is actually going to be, yes, I'm going to look at the side effects of this dose but I'm also going to look at how effective it is in your disease. So this time we choose a more robust population. We're going to test the effectiveness of this treatment and hopefully all these people have the same kind of cancer to begin with, ovarian, breast, kidney, or you know, heart disease, Alzheimer's disease, high blood pressure, anything. So we start them with treatment with a dose that we've identified and then we monitor them for side effects and then we also monitor and see what it does to their disease. And once we complete the phase two, we then compare. Now this goal can be predetermined before we start the study and here's when all the PFS and OS and all those numbers come in and we're going to compare and see. So I have drug X for kidney cancer, Pesopinib did this, what did drug X do? And that's how I compare both of them and see what is better. Then we move on to a phase three clinical trial. If a phase two successful in telling us that a drug is actually effective for a particular condition, we go on to a phase three. Phase three is again a bigger population, one particular disease and here we usually have a comparison arm because that's what's going to tell us if you're standard treatment that's currently existing for conditions better or my new interventions better. So that's a phase three trial and it's in a larger group of patients and has a longer follow up. I'm going to go to this slide before I come on to that. So that's the timeline that we've talked about. Here's basic research, drug discovery, preclinical studies, phase one, two, three, FDA review and one drug approved. From here to here, the average timeline is 10 years. But now it's shrinking and it's all thanks to patients who participate in trials. The trials are becoming larger, we're able to accrue more patients. It's come down to five in some situations but on average this is a 10 year timeline. Phase four trials are done after the drug is approved and here we ask more questions. Okay, drug X work for kidney cancer, can I give it to patients with bladder cancer? And even in kidney cancer, the patients have been taking this for five to 10 years. What are they doing now? Did their cancer come back or what side effects did they have? So those are the questions answered in phase four clinical trials. So this is just the behind the scenes for you guys. What happens, how we plan, how we conduct. This is a very great website that I found actually when I was browsing the internet and had great questions. It talked in a very simple language and explained everything. I just wanted to put it up there. It will be in the end of my slide set too. So in this website, it pointed me to good patient questions and so I wanted to talk about, so when you guys go and see the doctor and you're offered a clinical trial, you should ask yourself, why should I participate in a trial? So what benefits do you get from participating in a trial? Remember, I told you it takes a decade. So you have access to the new research treatments before they're widely available. So you get a treatment on the clinical trial to date, might not be publicly available for three to five years down the line. So that's a great advantage of being on a trial. You will receive very careful medical attention from the research team when you're in a clinical trial. It's not just you and your doctor and perhaps a nurse, but you also have a clinical team working with you that is monitoring you, asking you extra questions, writing down everything you have because we're trying to learn from you what the drug does to you. So you're looked at really very closely almost as if you're put in a microscope. So you get a lot of very, very close follow-up and attention. And of course, you're helping the community in general by participating in medical research. Remember for kidney cancer, the last decade would not have been so notable if it wasn't for clinical trials. So what are the risks? Giving you a new treatment could cause some side effects that we don't know about yet. And we are learning together, so that's a concern inside risk that you have. Again, taking this drug may actually not help your condition and we don't know that. It's something we're trying to learn. Going on experimental treatments sometimes also means more doctors visits, more blood tests, more scans. And so, and it requires a lot of time from your end. You have to take off work, travel to your doctor's office. So it requires a lot of time commitment and lifestyle changes. So what do you need to know? So, okay, you're considering going on a clinical trial. You've heard about it. What do you need to know? You need to know what is the science? So I think in this day and age when we have cancer, we all go back home. We browse the internet, we read articles.  So you need to know where does this drug come in? We all know about targeted therapies and such. Where does this drug come in the spectrum of treatment options that I have? How is it actually biologically affecting my disease? You also need to know about the protocol. This is the operating manual that your doctor wrote. You're not gonna see this, but you need to know what goes in it. In the protocol, we'll talk about who is eligible to participate. We screen patients very, very closely. We define things like, you know, you have to have no other chronic medical conditions that may actually harm your or affect your participation. You have to have good kidney function, good liver function.  Some studies or actually most studies will specify you have to be in really good cardiac health. So we go through all of that when we try to enroll patients in the study. The protocol also tells us about the test procedures, medications and dosages. So we will go through in detail about what medications you're taking. Are they going to interact with my study medication? What tests are you going to do? How often are you going to do it? How long will you be on the study? How is the investigator monitoring your disease and what are the expected effects and outcomes? So all this is in the protocol. This is a document that you don't see, but this is the document that you see. It's called the informed consent. It actually, Denise, correct me if I'm wrong, but almost a 20-page document that's given to you, 20-plus pages of all this information in the protocol condensed into this document that is given to you to read. And remember participation is voluntary. You can read, decide to participate and then decide, no, this is not for me. It's completely voluntary. What the informed consent does is it tells you about all what I talked about, the biological rationale, how we're going to do the study, what your expected side effects are going to be, how often you need to come in, what tests we're going to do, and how long we're going to treat you. So usually when you're in a clinical trial, we treat you as long as you want to be treated, as long as you don't have any unexpected or significant side effects, and as long as the drug is working for you. So those are the three scenarios where you are. So you're given this informed consent, you're encouraged to read it again, again and again, highlight your questions, write down your questions, ask a lot of questions. Believe me, we have to document the fact that we ask you to ask questions and we answer all of them, and that has to be an important process that happens between the doctor and the patient before you sign this. And only once you sign this is when the next step begins, which is we then start talking to you about, you know, let's get this test done, let's bring you in on this day. So none of it, no procedures are ever done without your consent. So this is a very key document that you all should be aware of as a part of a clinical trial. So what questions do you go in and ask your doctor? So what is the purpose of the study? I have kidney cancer, you're going to give me 10 milligrams of drug X. What is the purpose, what are you trying to achieve? So the doctor may say I'm trying to make your tumor not grow anymore, or I'm trying to shrink it, or I might just be trying to see if your quality of life gets better. Do you think it'll be effective? In other words, you're also asking, is this the right option for me? Being on this trial, do you think I should really take drug X rather than effinitor? How will you monitor me for safety? So this comes in, how do I reach out to you if I have something in the middle of the night? What symptoms am I supposed to look out for? Who do I call? And what tests are you going to see to make sure my heart is okay during this, my diabetes is okay during this, my blood pressure is controlled during this? How will you monitor my disease?  How are you going to look at that? How often are you going to do imaging tests to see if my disease is responding to this treatment? And how long will I be treated? Like I said before, as long as you want to, as long as you don't have bad side effects, and as long as the drug works for you. And what are my responsibilities? This means, what am I responsible for? I am responsible for coming to every doctor's visit. I'm responsible for doing the tests that you tell me are part of the study. I am responsible for telling you all the symptoms that I experienced during this treatment because we're finding out about this drug together. What are the possible short-term side effects? What are the possible long-term side effects? What are my other options?  What else can I do? Who will be in charge of a medical care? And now a lot of times people from the community come into Stanford because we have a trial here. And so it's confusing. So I had Dr. Jones in Walnut Creek who was my oncologist, but I'm with you on the trial. Who's in charge of my trial? As long as you're on a trial, the investigator doing the trial takes care of you, but you always have a relationship with your ongoing primary oncologist, and that's important for all of you to know. How will it affect my daily life? Am I going to be able to go to work? Should I take time off of work? Does somebody need to drive me into clinic? Does, do I have to apply for short-term disability? So on and so forth. And important, do I have to pay? So a lot of the times the trials are designed in such a way that a lot of treatments, tests and procedures will be standard of care. And when we say that, it means your insurance covers for it. Whatever the insurance doesn't cover, the company, the pharmaceutical company or the sponsor will cover for it. But you need to ask this question, how is this going to affect my finances? Am I going to be paying more? So on and so forth. There's some important terms. Every time we introduce clinical trials, some people really get, these are stopping points for people to stop and think. So what is a randomized study? So like I said, in phase three trials, we're always going to test the drug against the standard treatment options or sometimes a placebo, which I'll come to. And so what is a randomized study is that the study subject is randomly assigned to either your experimental drug X or you're going to get the standard of care treatment. So that is a randomized study. You will, a part of this is blinding. Sometimes you will not know what treatment you're receiving and that's scary for a lot of people. But here's why we do it. We do it to avoid bias because say you get Pizokinib, you know all about it, you get drug X, you know nothing about it. We need to randomize people to have, you know, study the biological effect of each drug. We need to blind people so that we don't bias the results of the study. So for example, if you knew what you were taking, you might come and say, you're absolutely right, my skin rash flared up or you're absolutely right, my diabetes got worse. So we don't want to bias the results. We actually want to know what impurity the drug is doing. So, and a lot of these times, in a lot of phase three studies, even the physician is blinded to the treatment option. So even I don't know what treatment you're assigned to and what drug you're receiving. So both of us are going to just look at the bird's eye view of it and we're not going to know what's going on there. And again, remember, this has gone through ethics. This has gone through planning. Nothing is going to be offered to volunteers that is going to be harmful. It's either going to be standard of care or the, you know, the drug in question, but the way that trial design happens is so that we don't bias the results. And placebo control studies. There's some studies where you will compare the drug with placebo. And like Sandy mentioned already, in this day and age, we have so many options. It's usually versus, go ahead. Time frame from the end of the study to getting back on. So that's a good question. And let me kind of back up and answer when you're in a randomized trial and their treatment arms. The way the studies designed also is that we keep comparing the results of both arms very periodically. And at any point in time, we notice a difference. Like one arm is doing much better. It is only ethical to stop study. And sometimes we cross over patients from that arm to the effective arm. Or if we see harm, we stop the study. Yes. Yeah. If it's working for you, you stay on the treatment and drug companies will allow for that. Say it was only for two years, but you've been on it, you've been doing great, your diseases are responding, you stay on it. So here's a slide. You're all very familiar, but this is our last great decade in kidney cancer. These are all the drugs that were approved, all because of patient participation, all because of clinical trials. We know so much more about how to treat. We have a lot of questions, but we know so much more about how to treat you guys because of these trials that were done in kidney cancer. These options have given us really effective options. We've been able to control the tumor growth. We've been, in some cases, even shrink tumors. And all this again happened because of patient participation. Where are we headed now with clinical trials in kidney cancer per se? There are a lot of pre-clinical studies again happening just to understand the biology of RCC. So there's researchers looking at this and trying to see what genomic pathways are underlying this disease and trying to come up with other suggestions and solutions about how to target them and treat us better. We are also clinically trying to identify biomarkers in patients, like, for example, who is the patient that's going to respond to an mTOR in an inhibitor better than a VEGF TKI or IL-2. So we're still trying to answer that question, which is the patient population that's going to benefit from treatment A versus treatment B. And you can call this personalized treatment and we're headed that way for sure. Like we've already looked at the slides that Sandy had, we're also trying to combine these agents and see if their efficacy is better. We're also trying to see when to give it to you after surgery, wait after surgery, so on and so forth. So we've already heard about those combinations too. And then immunotherapy. The immunotherapy in kidney cancer is the key player now. And how many of you have heard about this or not a lot, okay. So how our basic immune mechanism in the body works is that our body will not attack one of its own. It won't attack normal tissue because the tissues talk to the body and say, hey, I'm one of your own. Don't go ahead and attack me. And surprisingly cancer cells do that too. They tell immune system ways to evade their attack and say, no, I'm also one of you, don't attack me. So researchers have identified these communications that happen and they have come up with these drugs that break this communication. And that's what's the PD1 and the PDL1 blockade. This is just a communication between the tumor cell and the T cell. T cells are the key players of your immune system. So they've come up with drugs that break this communication.  So now the body taxes as a foreign particle starts attacking it. So this is like the basic mechanism how immunotherapy works. And the biggest player right now is Nevolumab. Like we talked about, data was just shown that it was effective, safely tolerated in patients with kidney cancer, clear cell. And their trials underway to get it approved. The phase three versus ever alignments that we talked about. And we're also testing Nevolumab and Ipilimumab. It is another immune checkpoint inhibitor in the first line setting. There are more. So Nevolumab is just one drug. There are other drugs that are also in clinical trials right now. The MK3475 and the MPDL drug. So what's available at Stanford? Actually, I thought I wouldn't go through this but I'm actually going to let you guys know what we have. We have a trial where we're looking at patients with early stage resected RCC and where it's a randomized study looking at giving them accident versus placebo. This is the trial we have here where in patients with metastatic RCC, first line treatment, sunitinib is standard of care. So we're comparing that to the combination of Nevolumab and Ipilimumab. In patients with advanced recurrent metastatic RCC, we are looking at the addition of this drug, delantercept and axitinib versus axitinib and placebo in this group of patients. We have a small trial which is looking at T-cell infusion in treating patients with metastatic RCC. We have some imaging studies. This is just one. I think three more that are looking at perfusion CTs or images, once you start a treatment, doing an early scan versus a later scan to see if the early scan actually is predictive of whether the TKI is working for you. And then we have a trial specific for papillary RCC subtype. We also have one for sarcomatite RCC. That's not up here. And this again is just imaging study that we have. Yes. I'll do. I'm not aware of that. And these are the resources I wanted you guys to kind of go back to or look up if you ever had a question. Clinicaltrials.gov, you all must have seen this. So this is the website where we all, whenever we run a clinical trial, we have to go on here and register our trial. It is actually good for you guys to go through because it will list all the inclusion and exclusion criteria that I talked to you about.  This is cancer trial specific to Stanford. Kidneycancer.org, this organization's website. I think it had great clinical resources. It actually also lists all the active ongoing kidney cancer trials worldwide and even specifically in the United States. So that's good to look up. And then this was the clinical trial basics website that I referred to earlier. Doctor, this is all pretty much national ideas but are there any international resources? So clinicaltrials.gov has international trials. So you guys might be familiar with it. So NIH is here. So you know, more international sources are more also based on guidelines that come or are set forth. So like for United States, we have the NCCN or the National Comprehensive Cancer Network. We have ASCO, those are the bodies that kind of help us develop guidelines here. When you go on to Europe where treatment options and modalities may be different, ESMO is a good site to look up for patients. They have a patient specific website where they talk about all this. And I can take questions. Yes. All the hospitals follow the same safety procedures while following the clinical trials or should we weigh Stanford or Anthem or Kaiser or whatever? So that's a great question. And yes, so there are international guidelines about ethics in human research. And we also follow something called good clinical practices. So doctors and all our research stuff, we actually have to sit in a training and get certified before we actually participate in any trials. And so these are standard procedures, standard education materials available to everybody. So everybody has to go through this training. And you know, like I said, the IRB has to review all your protocols in the way you're conducting a trial and approve it. The IRB will also have interim audits to see how you're doing. And if there has been any safety concern in the trial, like somebody experienced a side effect, they're actually going to have you come down and sit with them, explain what happened and how, if we are going to modify anything to monitor the safety of our patients. Again, when a trial is done, it's not only the institution, but there are also external bodies that are looking over our shoulders and seeing what's going on. One more question. So when does FDA involvement come into picture? Like is it before phase one or is it after phase one? So again, good question. So again, phase three mostly because that's when the data starts to emerge about. So we have more data about the side effects of the drug by the time it's in phase three. And we also have a comparison now. So say we had treated ovarian cancer with a drug for the last 10 years and now suddenly there's a new treatment. Now we can actually compare the two. And that's when the FDA comes in and weighs in and says, yes, you're right, your data actually shows that you can make a difference and giving the new drug versus the what was standard of care for the last decade is actually better. So it's usually phase three. And some trials may show promise even in the earlier phases and sometimes they're given an accelerated designation or approval where it's fast tracked to the FDA where they will ask for more data or earlier data. And if it's a high impact disease where you know survival matters for patients, especially with any kind of cancer, FDA will do that. They'll say, give me more data, give it to me fast. Cause if I approve this quicker it can actually make an impact. So actually you can be anywhere, we have patients who, because we have a trial available, we have patients who come here, fly out here for treatment. You don't have to be here. Again, you don't have to have a Stanford doctor, your community doctor can refer you to Stanford and we can take care of you for the duration that you're in the trial. Unfortunately, if we have the trial, we can have you go back and have it with your doctor.  Yes. What was the first direct? What is it? So fast track, like I showed in the set, so the FDA approval for a drug can take a year to two years, right? But if there's compelling data, which is showing that people are benefiting from it, it has been a safe treatment and we're actually improving survival and it's a high impact disease. For example, metastatic kidney disease or metastatic colon cancer where the faster it's publicly available, the faster it's going to save lives. At that time, people will push FDA and FDA will say, yes, let's give this a fast track designation where we are going to go through the review process even more quickly and get this drug out approved into the market quicker. All right, thank you.


Now that you've practiced making a basic truth table and know the difference between and and or connectors in compound statements, I want to solve a more complex truth table. We will fill in the truth values below P and Q in the standard way. So again, the first statement is always true, true, false, false. The second statement is always true, false, true, false. Now for the negation of P whatever value P has, not P has the exact opposite value. So the first P is true, so not P would be false. Same here. The last two values for P are false, so the opposite of that will be true. Now to find the truth value of the compound statement, I'm going to use only not P and Q. So looking at those two columns, I notice my connector is an and. So with and when I have a true and a false, my conclusion for and is false. When I have false and false, my conclusion is false. When I have true and true, my conclusion is true because they're both true and you need both statements to be true and again with false and true, my conclusion is false. I have now completed the truth table for the compound statement not P and Q.


From the Aria Resort in Las Vegas, it's theCUBE.  Hey, welcome back everybody. Jeff Frick here with theCUBE. We're at AWS re-invent 2018. I don't know how many people are here. 60,000, 70,000, your guess is good as mine. I'm sure we'll get an official number shortly. We're kicking things off here of three days of coverage. Monday, Tuesday, Wednesday, Thursday, actually I guess four days. We're at the AWS Marketplace and Service Catalog Experience here at the Aria, and we're excited to be kicking stuff off with Rajiv Dutt. He is making AI that makes AI. We're going to get into it. He is the CEO, president, and co-founder of Dimensional Mechanics. Rajiv, great to see you. That's great to meet you. So first impression, how many re-invents have you been to? This would actually be my second. Your second? My second, yeah. I always feel really energized after coming here. It's like, last year was like heavy AI centered. It was just really, all these sessions in AI was really exciting. So let's get into it for the folks that aren't familiar with Dimensional Mechanics. What are you guys all about? So Dimensional Mechanics is about lowering the bar for entry to most people. So that's kind of our first focus. Our second focus is to make sure that deployment strategies allow you to deploy across any end device. So it's basically intended to be a complete end-to-end capability. Around AI. Around AI. Yes, of course. The artificial intelligence, the most important part. So it's about reducing the bar for entry for artificial intelligence so that anybody without even a machine learning background can build very sophisticated models on our platform. In sometimes as little as 14 lines of code, it's just incredibly easy. We've had high school students use us. We've had university professors who have nothing to do with AI use us without any problems. And it's really the way we do that is that we have an AI that we call the Oracle. We are all Matrix fans. And so what this, the Oracle does is it has a vast knowledge base, has a lot of additional machine learning components and things like that, that essentially allow it to adapt and learn based on the kind of problem you're trying to solve. So every time it solves the same problem, it gets better and better at what it's doing. So, is it libraries, is it preconfigured? Are there specific type of application that it works better on? Which kind of year go to market? So basically think about AI Studio as a full server application. So what you essentially do, we created our own language called the Neopause Modeling Language. And the Neopause Modeling Language, think about it as sort of the sequel for artificial intelligence. It does a lot of very complicated things in just a couple of lines. So essentially what you do is you compile it on the machine. So when you write the NML code, the Neopause Modeling Language code, you compile it on the machine, it looks at your data which is sitting in an S3 bucket. It starts training the model once the model is ready. You can export the model as a PIM object, so affordable inference model object which is one of our creations. And that allows you then to deploy it on to any end target as long as it's running our runtime. And our runtime can be basically sitting in the cloud or on a device. Sometimes we're also looking at write down to FPGA kind of device levels as well. So extremely low power devices as well as cloud computing. But it gives you that flexibility but it also, which is really important, it makes AI accessible. So anybody without any background in it, my wife is a radiologist and she's actually looking at using it for her own internal research projects. But how much do you have to learn? You have to learn the Neopulse language, right? The NML language is really easy to learn. So we had a high school student who spent about a week learning it and so a week later she was ready to start coding and she had built her first models using that. And the way it does that is that you actually, we have a keyword auto inside NML, which is context aware. And so when the compiler sees auto, it goes out to the Oracle and says, hey, I've seen this person needs help building an architecture or figuring out what function to use or hyper parameters to use and so on and so on. And the Oracle will come back and say, hey, use this architecture, use these hyper parameters, use these settings or functions or these optimizations in your model. And- So is that doing that when I'm setting up the model in the first place to give me direction? Or is it looking at the model once I've spun it a couple of times and saying, wait, this looks like one of these, maybe you should do some of this? So what it will look at is your data. So it will actually look at your data, the type of data, how much data you have, the kind of problem you're trying to solve, how many, for example, if it's a classification problem, how many classes you have. And all of that basically determines the kind of model that it will use. You can also specify the level of complexity that you're interested in. Like, are you interested in a very simple model or complex model? Is overfitting a risk? It'll determine all of these things behind the scenes. Right, right. Based on the kind of problem you're trying to solve. And the first time it solves it, it will give you a pretty good answer. Usually, it's usually very good. But then the second time you solve it or the third time you solve it, it gets better and better and better because it's able to learn from its mistakes. So, and eventually it gets really good at its job. But it's still a model that I built for that application. You're not drawing kind of pre-configured models down from the Oracle. No, no. You're basically training it from scratch. It's entirely intended for custom models. So companies that have highly customized data like radiology or, for example, looking at wing stress patterns like in polarized light and stuff like that. So things that are not normally covered by the standard image recognition. And so using things like transfer learning or fine-tuning doesn't help in this particular case because if you've trained a model on dogs and cats, then like training it to recognize stress patterns in a hull is just not going to work. It's not going to work. Preparing for the interview, I was looking through your website and you list a really dramatic example of where using your guys' technology was like, I don't know, a tenth of the price and I think one month versus six or something along. I wonder if you could share some custom examples that people are putting this to you. Oh yeah, so we have actually a few. So one of them is with a company. They're focused on kind of resume matching. So we built them. They were initially quoted by another company at around 450,000 and they were warned that they would not be able to exceed 40% accuracy given the data that they had. We managed to get to about 83, 84% accuracy for about under 10,000. So that was like a huge, huge reduction. Then the second one was just recently another company had been spending quite a bit of time and resources on building out a technology to measure heart rate. We were able to look at that and produce, instead of spending like their 20,000 a month or so, we could bring it down to 4,000 in total. So these are the kind of sort of dramatic reductions and costs that our platform can offer. We, Stanford University, another great example, these are physicians that we're working with. None of them have any engineering background. For them, it's like Linux is in itself. They can't even operate the outlet probably half the time. That was the hardest thing for them to do is to get used to Linux. And so once they started building on our platform, it was like they actually built a model that was good enough that they were able to publish at the RSNA, which is like one of the biggest radiology conferences in the world. In this case, it was for PET CT, which is a three-dimensional model, so it's a three-dimensional image, if you will, of the human body. And so it was able to determine whether somebody had a tumor or not. And I think they managed to get with a very limited data set, about 74, 75% accuracy. And this was actually at Stanford, so it's a pretty, pretty big name. Right. So Rajiv, we're here at the AWS Marketplace Experience.  I think you said you had a good-sized seed round, getting ready to go out and get a decent A round. Right. What does it mean to work with a company like Amazon? I mean, as a small company, just to get an approved vendor set up at Stanford, probably not an easy thing, right? They're risk averse. You know, there's all kinds of legal T's and C's. Exactly. As a startup, they're always worried about whether you're going to be around tomorrow. Exactly. So you're partnering with AWS. So how's that been working with AWS and the Marketplace team? Well, firstly, A, it's definitely given us the Amazon backing, in a way. So when people see you're on AWS, they see that connected to you, that it automatically gives them a little bit more confidence. Like they vetted you so it must be good. Exactly. And the second is that it gives us access to a market that we otherwise wouldn't have had. Like, if I'm thinking about producing software that you have to download on our website, that's a very, very limited market. You have to attract people to your website and so on and so on. Now it's like we're on the Amazon, there's a machine learning hub on AWS. We're on that, so which means that when people search for machine learning, our name does come up. So it means it's very easy to launch. You don't have to worry about setting up a machine, worrying about how to configure it. Everything is done automatically. It makes life really easy. So and on top of that, the AWS team has been, the Marketplace team has been really extremely helpful connecting us with end customers. So very often they will refer people to us. In fact, one of our largest customers came through an AWS referral. So for us it's been nothing but a win-win for... What about the potential downside? Not the rate on the parade, but the old joke used to be if you're a startup making widgets, you just got your first order with Walmart to goodness. Bad news is you just got your first order with Walmart. I mean, that's opening up a huge global distribution opportunity. I mean, in theory, say you got 1,000 customers tomorrow that might be a little bit of a challenge. Yeah, so we actually are starting to hit that. So our version two was really our go-to market version and which came out earlier this year. And so we've been trying to like wrap and pop the sales on that side. And literally in the last three months, we've had a deluge. It's like, I have not been home for six weeks now because I've been in the Far East and traveling and it's like because of this heavy customer interaction at this point. So we have a very good story to tell the investors now. Like this has also helped with the investment rounds that we're actually looking at. So we have a very good story to tell the investors that our invoice list and so on is huge at this point. So we need help now. It's actually more about raising, like building up a team now than it is about, can we get orders? Right, it's really delivering more than sales. Exactly, yeah. And so we need to build up a delivery team. We need to, I mean, it's fairly intuitive, but at the same time it's a new technology, which means as with any platform play, you're building up a team of evangelists, support individuals and so on. And there's going to be a marketing component as well. So we haven't really driven marketing that much. AWS has been great in kind of doing some of that for us, but we need to of course very actively go out and market and we haven't had that capacity yet. All right, we look forward to watching the story unfold and thanks for spending a few minutes with us. My pleasure. All right, thanks a lot. Thank you very much. All right, he's Regif. I'm Jeff, you're watching theCUBE. We're at the AWS Marketplace and Service Catalog Experience at the ARIA, come on by. Thanks for watching.


Welcome it's April the 8th, 2022. And this is Jenkins documentation office hours agenda we've got news she could Africa contribute on Google summer of code and I had something on weekly change large process but I don't think we need anything on that. Make any other topics you want to put on the list that does it for me sounds good. Okay, so by way of news. Oh, a good one. She code Africa has started started April 5. We're in the two week period. For community bonding. We're trying to know each other understanding the project, talking about how we'll deal with each other, preparing blog posts, those kind of things. And that's new this year we did not have that last year. Correct last year we did four weeks started and stopped and boom. And this year we're making sure that they're configured ready to do the work that they're introduced to the team that they've had some introductory training, those kind of things well before we actually did the official work. Excellent. So, so preparation right now and then. Then we will, we will start the actual work in. It's about two weeks from now so figure April 15 or 18. And that'll only go for four weeks and then they have a two week end of project period so it's a good match. Yes, sounds good. Now there are our detailed notes in the meeting notes from our meeting earlier. So the meeting that was yesterday in calendar time has a bunch of notes on things that we described took them through a tour. Two of the contributor to the Chicot Africa women that were there. We talked about the steps they do to download and run Jenkins create a GitHub account. Create an account on get pod.io so that they can do video they can do website development. And there's this tutorial that shows how. We discussed how to divide the work between us. This is one actually make where it probably help if I show you what what we've decided to do is let me show you the idea. The idea looks like a word I put the sheet is this it. Nope. These are the people. Nope. I closed the sheet. Maybe I hit it away. So what I've got is a worksheet that lists every plug in sorted by installation count. And then I assigned 15 of them to the first person. And then I set up a four and 15 to the second Catherine to and hero, and then we alternate back and forth. And what I was just doing was doing some sanity checking searches looking for inclusive naming failures in those and in each two or three blocks of 15 that I checked I found at least some in every case. And these are very popular plugins so when I say the high popularity these are the top 30 or 50 plugins, which means averaging more than 200,000 installations each. So those are those are good things and many of them have been solved right many of them are there. There's no reference to slave or no reference to master, and so that's good that's a win. But having just found a few that says this exercise of having them go through it is valuable, it will help us weed out those last few remaining things, even in those high volume plugins. Yep. Excellent. The idea is we'll use that sheet as the, as the arbitration point to decide who's going to work on which, which things and how, and we'll let it run from there. Terrific. So, that's really the topic I had there then and for Google Summer of Code we've got ongoing reviews of projects are needed. A lot of plans are needed of proposals are needed and do by April nine, so that the candidates can refine and submit in time for the deadline, which is April 19. I recall correctly. So do you have a lot of proposals ready for review. We have, we have three or four or maybe five that are all being actively reviewed on different, different topics to that are very active on the get get idea to that are very active to or three that are active on another one and then the plug in health topic we've got one very serious one so it's it's looking okay. Yeah. Those are the topics that really I had. Are there other topics you wanted to bring Nick. Dare I bring up my old favorite any movement on that. So, good question let's put open PR is there I think that's what you're talking about right. So Mark still has not negotiated has not made the trade with the security team. So I'll talk with them for some of their time so I'll, I'll talk with them. It may not be tomorrow but I hope to talk with them before, before we meet next week. Yeah well let's not burn you out I mean if it waits another right. I was just curious. What I mean to me is I'm, I'm admittedly accepting that I'm going to fail on some of my action items just so I can keep the other ones, get the other one. So, if this gives if this makes you comfortable that you failed on this one this is a good one. You know, I mean some, some of them are more serious if you fail on them, let's face it. Right. Exactly. Some of them are much more pressing have a have a hard deadline or yeah, exactly. I just kind of want to make sure this doesn't fall off the edge of the earth. That's all I care about. Right. And, and that is wholehearted agreement we're going to we're going to get that thing through all the way to the end yet. It kills us. Right. Seems like such a good idea at the time. It was a good idea and it still is. So any other topics we should discuss today. I don't think there's anything else urgent I think the GSAC stuff is probably calling. Okay, then let's call tonight done. Thanks Meg have a great evening. Thank you. We'll talk. Bye.


Tip on how to impress business clients as a business English teacher, needs analysis. One of the first dilemmas that in company business English teachers face, is that classes can consist of students from different departments, and at a different level in the company hierarchy. If class participants come to form different company departments, the group will likely have mixed needs, and there may even be conflicting views among different stakeholders. It is important to receive a list of clearly defined needs and objectives from the hiring manager, to know exactly what measure of success they are looking for. In addition to the directives provided by the hiring manager, distribute a needs analysis to each student before the course commences. Design a syllabus that meets the goals set out by the hiring manager, and addresses the needs of the students as analyzed from the needs analysis data. Thanks so much for watching. We are ITTT the leading provider for TEFL and TSAL training courses. If you liked this video, please subscribe by clicking that button down here and click on any of the videos here on the left for more interesting teaching tips for getting certified to teach English abroad and online.


Everybody forced here rip in two boxes for 22 23 hoops hobby two boxes here for Chad B. Thanks Chad best of luck Let's see what you got man. Let's see a palo auto Still haven't pulled one.   Gianna Sons at a Kubo to 2022. Oh, yeah, Niners Cowboys is like the NFL's dream playoff matchup Kennedy Chandler Andrew Nemhardt Jalen Williams Paul George Redback This is right. I mean Brady has a right where he wants him. I think He's got he's got him as cross airs Wendell Moore jr. And everybody was dunking on Brady and Chad Kendall Brown Purple Josh Christopher. I would love for any of these teams to beat the 49ers, honestly Jaden Hardy rookie I root against the Niners and build so hard in these playoffs. I mean Niners build Super Bowl. I probably won't even watch it I'll probably just go go to the movie theaters that day So it would be dead at the movie theaters be great. I say I'm mobile.  Isn't that weird? J. Nivee Got foil jammer ants. There isn't some peel here. I'm gonna send a box and wrapper Send a box and wrapper with the uh break here I think I think I'm rolling with the birds. I'll let Uzi know Johnny Davis Go birds question mark My brother-in-law's are Eagles fans I think I am gonna do it Chet Holmgren a purple rookie Vince Williams jr. The Doug Peterson revenge Super Bowl is gonna happen. I think Paloban caro rookie Xavier Rhodes Florida State legends Benedict Mathurin rookie and a green foil daren fox 81 of 99 Who do I want to lose more the bills or the Niners? That's a tough one. That's a tough one H. A griffin Dang Holmgren On the uh What does it call a rookie uh special christian brown jabari smith jr. Jamtastic lebron james Sorry smarton It seems like everyone in the nfc is afraid of each other same with the afc. I mean, it's it's that's fair though There's some there's some really good teams. I mean, it's a pretty stacked playoff class on both sides. Yeah, it is So that's good for the nfl purple jammy grants Not a whole lot separates niners eagles and cowboys. I mean We'll see what the giants can do they looked good against that weak defense We'll see what happens when they have to go to the link Yabate we got next paloban caro. One thing's for sure is that coaching staff will have them ready? I think Let's see if they make their extra point go over to vince williams jr I mean they should go for two So 999 road to the finals dorian finney smith Julio jones Chet holmgren rookie It's like the old man bowl right here. Peyton watson shade on sharp They better run a play before they review it throwback clay thompson Williams Tyree eason And a scotty pippin jr on the rookie ink sparkplug jalen green nfl shrug riders What 18 now still three scores. So cowboys Not a whole lot change there. I guess big picture Just go run the ball gets in first downs Hey, that's how it starts though right there. That's how it starts So he does it jaden jaden hardy everybody uh, oh All the cowboy spans Stomach shrinking a bit here Them butterflies isaam mobley to 2022 road to the finals jalen brunson What's up, the best four cards? knots jabari walker jade nivy rookie pj tucker redback johnny davis Remember everybody's personals are full for tonight So anything ordered now, uh, pretty much we'll go tomorrow that mark williams chat holmgren purple cameron johnson roland's keegan murray rookie rookie mark williams 2 of 199 on the foil agbaji jazz rookie Ben caro tribute sohan Tyree eason we got next Foyle john marantz another peel on this one. Same thing is that last box. He's already sending a box Extra points might become important, huh? tie tie washington purple rookie luke travers Kendall brown purple kelly ubray who doesn't like jaw Oh, yeah, the foils I got. Yeah palaban caro rookie base I mean he does have his own insert set mathoran rookie Road to the finals to 999 is bam out of bio aj griffin foosman yang christian brown jibari smith kairi urving spark plugs tyrese martin Remember guys 10 bucks Tuesdays tomorrow with sam. Just kaleb houston a justin lewis rookie ink highlights mitchell robinson Uh, 10 a.m. Eastern starts time with mad on the baseball channel tomorrow personal resume tomorrow night And monster triple release day on wednesday I'm act basketball impeccable football flawless baseball I have not I don't think we've anyone here has pulled a palo auto out of hoops yet Green was it the abate rookie at 99 It's two numbered rookies and two boxes is good Kennedy chandler andrew nemard kairi urving uh throwback That's gonna do it Appreciate the order chat. We'll get these cards out to you shortly