Hi and welcome to our kitchen. I'm Camille and I'm Kristen and we're here with six sisters stuff today We're going to be sharing with you one of our family's favorite recipes our mom's potato salad. It's perfect for summer Barbecues for Pollux for any gathering you have coming up, especially with the 4th of July We're going to show you a fun version you can make with that Everybody makes their potato salad a little bit differently and we're going to share with you today How we make ours for this recipe we're going to start with some simple fresh ingredients You need about two pounds of potatoes, white vinegar, sour cream, a little bit of mayonnaise, yellow mustard, chopped red onion, chopped celery, chopped pickles, hard-boiled eggs, dillweed, parsley, Johnny's garlic spread, a little bit of season salt and to top it off some Johnny's salad and pasta elegance We're going to start today with these potatoes. The thing I like about these potatoes are their bright colors So they just will make any salad pop We've got your bright reds the bright purple and you can see the inside the golden yellow The other thing I like about these you don't have to peel them the skins are so thin And that's really where your vitamins and minerals are going to be so keep the skins on throw them in your salad The other thing I like to do with my potato salad For the potatoes now just a tiny bit more flavor is after they're done cooking I throw about a tablespoon of vinegar on top of them It just makes just a little bit extra flavor on there So Chris, I'm gonna have you dump that in the bowl and then we'll add the rest of the stuff So I hard-boiled some eggs you can do as many or as few as you want I like to do a lot of eggs because I think it tastes delicious So there's about six or seven hard-boiled eggs in there and then celery Chop it up really small and it adds just a tiny bit of crunch which tastes delicious to me in a salad But if you don't like celery, you don't have to add it you can do as much or as little as you want you whatever that much And then some chopped onion you can do any kind of onion I like the red onion because of the color and I also prefer that flavor chop it up really small No one will even know but it adds just a little bit more flavor So throw that in there nice and then the pickle debate whether you like dill or sweet either one's gonna work They both taste delicious. I prefer dill Sweet yeah, I prefer dill too, but we're going with dill. So sorry dad Okay, well, she's getting that all mixed. I'm gonna throw together a quick dressing The thing about my dressing is a little bit different is I like to do a little bit of sour cream So it's not such a mayo based dressing So throw your sour cream in a bowl and then you do me a little bit of mayo so I added just a little bit and Then mustard you can do as much or as little as you like I did about a tablespoon So throw that in there start mixing. Do you want to mix that? Yeah, I'll mix that. I'm gonna add some seasonings Today I'm going with fresh, but you can use dried whatever works for you I've got some fresh dill weed which smells amazing and goes awesome with the dill pickles So mix that in and then just a little bit of parsley just for some added flavor a little kick And then while you're doing that. I'm gonna add some Johnny's season salt That's just what I use that you can use whatever you have in your kitchen That'll work awesome just a little bit and then also some Johnny's garlic spread but garlic powder works perfect to whatever you've got It's gonna be awesome Okay, mix that all together It looks good. You want to throw it on and I'll Big finale Okay, give that a big stir Not gonna stir too hard because I don't want the skin to fall off the potatoes, but then you'd have mashed potatoes exactly Which isn't as pretty still tastes good, but Those colors look awesome. I agree. I just the colors just pop. So I'm gonna move everything out of the way And let's put it in a big serving bowl Okay, lift it up. I'll get it in sounds good. This is gonna be perfect for any potluck Dinner or I look so barbecue you have coming up.  I'm just gonna top it with some fresh seasoning I've got some fresh dill and some fresh parsley you can use dried that works perfect to the reason I'm doing it is just to add a little bit of pop of color The other thing my mom used to use on her potato salad was Johnny's salad and pasta elegance The reason is for that fun bright orange color and also the flavor that it adds It's just the perfect touch to any potato salad and with that I think we're finished this potato salad is ready to go for any barbecue or potluck Whatever you have going on. I'm Camille and I'm Kristen from six sisters stuff We're so happy to share this recipe with you for more recipes. Be sure to visit six sisters stuff calm happy cooking


Hello, everyone. Welcome to the pre-application webinar for a new NHGRI program called Molecular Phenotypes of Neural Realists and Cells for Morphic. I'm here. My name is Adam Felsenfeld. I'm a program director here. I'm here with my program colleagues, Colin Fletcher and Anjit Kilai. I also want to thank Sean Darren who will be helping with timekeeping and the slides today, and Gerald Simani and William May for their technical support. Sean, if we could go to the next slide. This slide is just for reference. This is relevant links that may be useful to you. I think you're probably familiar with all of them. The only one that you might not have seen is the one for the 2020 NHGRI Strategic Vision, which I think provides some higher level context for the kinds of programs NHGRI is interested in pursuing over the next five or seven years. Next slide. Some notes on the format. I will give a high level introduction to the program, and then I'll launch into a discussion of the first RFA, which is the Data Production Research and Development Centers, and then we'll stop for some questions. Next up will be Ajay, and he'll go through a brief presentation and then take questions for the data analysis and elevation centers, and then Colin will follow with a presentation on the data research and administrative coordinating center plus additional time for questions. To note, this call will be reported and posted to the NHGRI Morphic Web Pages. Your questions will be rendered into general FAQs with our answers, and those will be linked to the Morphic Web Pages. The chat is disabled. Please ask questions in the Q&A. You will have the option when you ask a question to ask anonymously, and you may do so. There is also an ability to upvote questions that appear in the Q&A. The next slide. On to the high level overview of the program. Next, please. We think it would be great to have a catalog of molecular and cellular phenotypes for gene knockouts of all human genes, especially together with the knockout cell lines as a resource. As an ideal, the data would be highly informative, that is, of multiple types and from multiple tissues. The data would be relatable to other kinds of data, so other alleles are anatomical physiological disease phenotypes. They would be consistent, high quality standardized, well characterized assays, and they would be complete, that is, for all genes, resource covering all genes. We don't think this is feasible yet. We don't know the best way to design an effort like this. There are a fair number of technical and scientific challenges or barriers, which I'll get to later. We don't understand scaling issues like costs and throughput. We don't understand the strategies to employ, the tools to be developed. We don't understand the trade-offs that will need to inevitably be made to best explore what's likely to be a very large experimental space, even though we've limited this to all of us, to one type of wheel. And of course, just getting the data is not enough. We need to understand how to use it with all that entails from data management, quality control to making the data interoperable with many other types of data generated elsewhere to demonstrating the scientific value of the data. We go to the next. Why is this interesting to do? So first, there's a positive idea on human knockouts, though of course there are resources like Nomad that do yield some good information. There are mouse knockouts from the knockout mouse project, but there's almost no molecular and cellular data for them. And while mice are an outstanding model for many reasons, they're still not humans. Knockout phenotypes are useful for interpreting other alleles. The data will complement a number of large efforts already under way to study gene regulatory variation. Such a catalog would be a resource for insight into biological pathways. And if the cells on which the assays are done can be saved, they may ultimately represent a collection of disease models for further study. Next, please. With the consideration that we don't yet know how to realize a long-term goal of a comprehensive morphic catalog, NHGRI is starting the program with a phase one. The purpose of phase one is to inform the feasibility value and design of the potential of phase two. Ideally, phase one will illuminate and start to address the main technical and other barriers to the long-term goal, such as how to select genes, how to optimize making millions, what cellular systems are the best, what molecular and cellular assays are the most generally informative, what's the potential for scale, what are the key scientific issues, and we can anticipate some, like specificity or priotropy or cell monotony or genetic compensation, experimental and biological variability, and I'm sure there are many others. And we don't know how to get the maximum value from the data, not least because we don't have a lot of this kind of data to play with yet. Phase one intends to do these things above by starting at a modest scale and at the same time giving room for some diversity of approach. It's fairly straightforward. Next slide. As I mentioned, up top there will be three components, data production, research and development, data analysis and validation, the data resource and administrative coordination center. Next slide. Switching gears now to some mundane but very important reminders that apply to all three FLA's. These are cooperative agreements. That means there will be substantial nature program management. There will be collaborative tasks, for example, across the consortium, for example, with regard to sample prioritization, quality control, data format discussions, data flow discussions, please read the FLA turns and conditions for how this will be managed. Another aspect, the consequence of having cooperative agreements is that NHGRI has a flexibility to set and adjust milestones, which is needed in a complex program. Finally, there will be a kickoff meeting after the grants are funded to establish the consortium and to start to outline some of the collaborative tasks. We ask that you please send in letters of intent. We cannot require them, but we do encourage them. The letter of intent date is September 15th. If you can't make that date, please send something in as soon after that as feasible for you. These are very helpful to us. We will call, we will contact everybody who intends to submit an application to talk to them. The other reason to send these in is that they really help our review branch recruit good reviewers, which always takes a lot of lead time. Next slide. Some more general advice. Please always read the review criteria section of these or indeed of any FLA that you are responding to. This is what reviewers must use to evaluate your application. Please read the instructions to applicants for the research plan sections. Each of these asks for a specific format to organize the research plan. The FOAs all have a separate resource sharing section. Usually when these are included, they are considered, but they are not included in the score. In this case, for all three of these, the resource sharing section will be considered in the overall score. Please read the section in the FOAs on review and selection. This section lists criteria that NHGRI may apply in selecting among well-scored applications. Please also read the budget section that provides guidance on minimum time commitments and also states that you should reserve some of your budget for work and social interactions. Finally, please choose letters of support judiciously. If you have too many of them that aren't directly relevant, it may put members of the community in conflict who could be good reviewers. But if there really is a collaboration, obviously you need one. I note about diversity in funding. NHGRI especially encourages applications from investigators from demographic groups or institutions that are generally underrepresented in genomic science. New investigators, experienced investigators who are new to genomic science, investigators that have not previously participated in NHGRI Consortium Program. Finally, please look out for the FAQs in the next few days on the website. These will be updated as we get more questions from folks over time. So please do check back with them. At this point, I'm going to go right into the discussion of the first RFA, HG21-029, with data production research and development centers. At a high level, what we're asking applicants to do is straightforward, conceptually, though definitely not biologically or experimentally. And that is to generate molecular and cellular phenotype data and informative cellular systems for mullo wheels of a thousand protein coding genes across the program in the initial five years. So straightforward, identify and prioritize the genes, make the alleles in the appropriate cellular systems, carry out informative assays in that system. The overall focus here and a point that I'll make over and over again is the overall focus should be on generalizability. How or what is done contributing to understanding how to do this across the whole genome and going forward in a potential phase too. Next slide, please. Following this data production research and development grantees, well as I said in the last slide, we did the consortium prioritization of genes and produce alleles in the chosen cellular systems. Diving into some of the others, the grantees will generate data from high throughput cellular modular assays and in vitro human systems. Multi-cellular complex systems such as organoids are preferred but not absolutely required. Molecular and cellular assays should be considered based on the utility of the information we know that and contribution to understanding how the best do this going forward. Grantees will ensure compatibility and reproducibility, develop metrics and quality standards, standardized allele and assay validations to enable assessment of advantages and limitations of different approaches. Grantees will share data, best practices, cells, protocols, methods, software and other products of research. Grantees will collaborate with other consortia or projects developing complementary data sets and generally develop an approach that will be informative for how we can eventually generalize and scale. So notes about responsiveness of application. Again, we're looking for generalizable approaches across multiple cell types and phenotypes in classes of genes. So not just one disease and not just one cell type. There's some discussion about that potentially in the FAQs. These are not grants to study gene regulatory variation. These are not technology development grants. They must work. What we propose must work at phase one scale. And each application must propose an integrated effort so gene selection for generation of molecular and cell or phenotype data and not just any single aspect that we've asked for. Next slide, please. You will see in the FOA that there's a list of what we call main barriers to understanding how to get to the long-term goals for Morphet. I have them in the slide, but I'm not really going to read them. I just want to say something about them. They're not necessarily cues for specific aims. They're mostly higher level than that. These are things that we want to come out of the initial five years as a whole and as such, they represent important motivations for phase one of the program. If we come out of phase one with a clear idea about these points, we'll consider it to be a success. This list is probably not comprehensive. If you can identify other barriers in your applications, I think it will be helpful. Next slide. I've already talked about a lot of this, but for emphasis, grantees will have responsibility both to their own aims and also consortium responsibilities. These are likely the key areas in which they'll arise. So developing gene priorities, developing quality metrics, data formats, policies, internal policies, sharing data plus other products, quality control. There's always a possibility here and an attraction to the idea potentially running the same genes through multiple grantees' assays. See if that's feasible. We won't know till we get there. Characterizing variability, both experimental and biological, and helping to develop use cases for the data. Next slide. I know I already said this in the general introduction, but I really do want to emphasize for this FOA. In particular, it asks for the research plan to be presented in four sections, so center overview and management, mutagenesis, biological sample systems and experimental assays, data management and analysis and then integration. And then as I mentioned before, there's a separate resource sharing section. Again, consent in the school. All right. I think at this point, we can start with the Q&A. I have some in the next two slides, some pre-loaded Q&A, but if we have some, a front-line student, we already have some. Okay. So this is first question is about whether we require stable null cell lines or is an approach that uses pooled knockout experiments. So it does not, it does, either of those are possibilities. If you look at how the FOA is worded and the review criteria, there's room for the second approach, but I think it really has to be carefully justified. There are some things about pooled experiments. There's some shortcomings of pooled experiments that I can think of in terms of reproducibility, for example, and I think that would have to be addressed. And you would also have to talk about how that's generalizable, again, against the other higher goals of the FOA. Let's see. So how defined does a null real have to be? I think that's, you're going to have to state, applicants are going to have to state how they have validated their alleles and how they will be reproducible and give consistent. So if you redo the experiments, you're going to get a consistent result. So I'll leave it there. There's another question about the deliverables. Okay. So it is not strictly correct that it is a requirement for a final deliverable to be individual criminal human IPS scenes, but I think that would be a great thing if this came out of the program. That's a close reading of the FOA. Okay. And then there's a very specific question about for IPS scene lines, how many vials of cells are needed to be frozen down for distribution. So you will have to propose, I think this is something for you to propose in the research, in the resource sharing plan. What you think is the white balance between cost versus what is a good deliverable? So I think you are going to have to figure out what the right balance is and propose it, and there's a few of us who will take a look at it. The next question here is a question that is I would say is a frequently asked question. How many individual genes should each application propose? So the way that we stated it is a thousand total over the whole program over the whole five years. And given that we intend to make four-ish awards, that's 250-ish a piece, but please leave some room for overlap. I think that it would be great if there's enough compatibility between what centers are doing, because I think that would help with QC and validation and extending the results. And then there's finally another question about an added dimension to this, which shows up in another FAQ that I already have, which is everything in every dimension we add adds a lot of work and requirement for resources. That's absolutely correct. The one asked about here is, generically, is sample diversity. We do not have, I don't think that there's any way any way that there are enough resources to, it's unlikely that there are enough resources for, to really test sample diversity and to get, you know, to get well-validated results. But I do think that this program needs to come out of the first five years with a much more solid idea of what the variability is between, between cells taken from different genders, from different life state, people from different life stages of life, and from people from different ancestry. And again, I don't expect that this can be thoroughly explored, but I do think that the program as a whole does need to explore this. And this is something that's explicitly discussed in the, in the instructions to applicants and also in the review criteria. So please take a look at the FOA. Okay. And I think I've answered the next, the next question. So the appropriate, I want to be clear about this again, because maybe this question is about what are the appropriate organoid systems and cell lines that would be responsive. So, so the ones that, that strike the best balance between informativeness and, and all the other and generalizability and all the other and specificity and all the other things that, that your plans are going to have to balance to, to in five years contribute to telling us about how feasible it is and how you would design a phase two. So you're going to have to propose that and strike that balance and justify what we choose in terms of the, the, the sometimes the goals where there are tradeoffs between, you know, how informative something a system is and asking is how specific it is, how generalizable it is, how, how expensive it is. And I think that's, that's what we hope you can tell us how to do. Okay. The next question is important. Single grant may not be able to do everything. Would it be responsive for one application to focus on creating stable mal cell lines and another application to focus on molecular assets in the cell lines in a consortium manner. So we, we deliberately decided not to do it this way. And applications focusing on just one aspect would not be responsive. We really want to hear the integrated ideas. I think that there's a significant chance that, that these things are these different parts might have certain dependencies that we don't understand yet. And so it's not really possible to, to do it this way. In addition, because it's phase one, we want some, we want some room for differences between, between the centers that we fund. We want some diversity of approaches. That said, the extent to which something like this can be done is, is, is something that's very, very interesting possibility for, for a consortium discussion once applications are funded, successful applications are funded. So it is something we'll be thinking about. Right. Here's another question, which is in selecting genes. Should one have in mind that they should be functionally tested in different types of organoids, such as cortical organoids, liver organoids, et cetera? Yeah, this is a distinct, this is a, this is a possibility. It's, it's completely, it's a completely reasonable approach, although obviously it spans the number of tests and costs. So again, there's some balance here. Maybe, maybe there's a, maybe there's a more clever way to do this. Right. So I think these are all, these are all answered. I'm sorry, there's something going on in the, there's something going on in the chat that I, I, I'm not sure. Let's see. Okay, there's a, there's a question about, for computational teams, it's difficult to envision a data analysis center given that assays are still not defined. Will there be another opportunity to synchronize post-letter of intent period? So I'm gonna, I'm gonna flag this question and, and leave it for Ajay after the next, after the next press, after his presentation. So if it doesn't get answered, please ask it again at that time. The next question is what time of interactions between I think, I think this is meant to be production sites is expected. Yeah, whatever is, whatever is useful or maybe it's funded sites is expected. Yeah, whatever is useful, I think, I think that these are two possibilities. If you think, again, once the consortium is formed and people know who they are and what they're doing, it will be easier to imagine this, how to do this. And I think that the practical approach, and this comes up in several, in several ways in several different parts of these applications. My, my practical advice about writing around this kind of thing where there's a, you have to come up with a plan and yet you have to be flexible is, is to come up with the plan that you think is best and justify it in a thoughtful way. And then indicate what parts of it are flexible or flexible, flexibilities to share and limitations that are, that, that, you know, that are realistic ones. I think that's the best way to do that. But I really think that it's quite important that we and reviewers hear what your opinion is of the best way to do this and what that justification is. What kind of like either assays are expected, gene expression, epigenome mapping, et cetera, or just say the phenotypic assays. So the, the, we want both molecular and that includes molecular omics and informative cellular phenotypic assays. We want both together.  They're generalizable. We have a feel for how much they cost and how informative they can be, but, but not, not enough, I think. And I think we need to push beyond that. Again, in order to be able, the part of the goal is to be able to use this catalog to interpret other kinds in combination with other kinds of data that are not produced by this, this consortium. That includes other phenotypic data, other cellular data to be able to put it all together across different kinds of data resources to make useful biological conclusions, to ask useful questions. And, and I think the richer the data, the better the chance of doing that though, exactly what data has to be, have to be thoughtful about that. Okay. I, I think the next question is can one create or and test multiple null, null alleles of a gene? I think it's supposed to be for functional testing. So I, I'm trying to, I'm trying to understand this question and I may need a little bit more information. Are you talking about, for example, different isoforms? I don't know. So it, it should be a strong allele. Obviously, a null allele, we really want something that has, has close to no functional protein as possible. And that's pushing things towards, towards strong phenotypes that are interpretable. But it has a downside as well, which is it's also likely to result in some pliotropy in many cases. And frankly, I have no idea across all genes how that's going to play out. And I'm very interested to think about that. I think that has important implications for potential phase two. It does say in the FOA that, that null alleles are, are the default. But if there is very good reason to believe that a null allele won't be informative, for example, because it's so lethal, then, then it is perfectly fair to propose alternatives. The next question is does one need to assess more than one organ system? And just careful here. The important thing is, is to consider generalizability. And that means at the end of the day, different cell types, understanding different tissue types, understanding, you know, being able to, to select the 1000 genes and test the 1000 genes in a way that's maximally informative about the whole genome. And I'm sure everybody has their own ideas about the best way to do that. And the best way to prioritize those genes, and that is going to be a discussion. In addition to something you're going to have to propose, at least propose the rationale for it in your applications. But there are ways, I can imagine ways to get generalizability. So it in several different ways. So if you do propose a single organ system, you're going to have to talk about, please, how in the application, how that is going to be generally informative across the genome, or across different tissue types, or across different cell types. Okay. Yes. Mr. Sajek, can I take one of the questions in here and ask you a very specific? Yes, you can, but you'll have to move closer to your microphone because I'm having a hard time hearing you, please. Okay. So one of the questions here is that that goes, my understanding is that this RFA prefers the final deliverable to be individual human clonal individual clonal human IPSE lines for each knockout gene for distribution to different labs in the community for further studies. I wanted to ask you a question about interpreting community. What is the interpretation of the word community we are using in the FAA? Do you expect these to be made available to anyone who asks for it from the entire biomedical research community? Or is it just the consumption? Right. So making it available to the entire community is obviously going to be prohibitive. It could be prohibitive, especially if these have to be maintained and expanded indefinitely. So I do think, again, yeah, I don't have a great answer to your question, RJ. I think it's a really good question. But I think applicants will have to propose what they can do and what the practical limits are. At a minimum, I think that there should be the ability to exchange samples within the consortium. And because of the way it's structured, that's between the four to five funded production groups. And then we can talk about more more after that. There are just a whole bunch of complicated issues in addition to cost, which includes how informative they are and things like that. So I don't think that it's practical to require something as extreme as having a resource or having preserved and expandable cell lines that can be extremely widely distributed without adding something else to this program. All right. Here's a couple of more. RJ, do you think that that was a fair answer? Absolutely. Okay. Two more questions. One is similar to one that I answered before. That's many scalable pulled screens and things that are dependent on redundant measurements and multiple SGRNAs. But we only use individually verified knockouts, but it's still okay. It is not critical to have an output of verified wheels and individual cell lines as an output. It would be, I think it would be a great thing to have that. But there are technical trade-offs and the technical trade-offs I could see could push you towards a different kind of system. But it's up to you, again, it's up to you to justify your choices in the FOA. There's certainly room for this in the FOA as I wrote it and as I read it. Another question is, are human gastroids an acceptable model? Yes, you would have to justify them. Okay. We have no open questions at this point. We are at about 40 minutes in. So we have about another 10 minutes. I'm going to read off some of the questions that I had as potential FAQs that have not been asked already. One of them is can we analyze our own data? And yes, and this is in the FOA. But there are limited resources, especially after doing all the other things that this FOA is asking for. So if you are going to do this, please prioritize analyses that are designed to characterize the quality and utility of the data for downstream applications. So biological and technical variability data consistency analyses could include, for example, looking for correlations between assay data types or comparisons integrating outside data, for example, from COMP or other perturbation by phenotype data. Those are all acceptable as long as they refer mainly, they're mainly used to help characterize the performance of the system or demonstrate utility. So that it gives a lot of leeway, I think, but it does need to be disciplined because of budget constraints. I do want to another FAQ that I anticipated is slightly different from the one that Ajay asked, which is do the sample cell lines data derived from them need to be shareable? So this is a different kind of answer to that question. So increasingly, NIH policy is that data resources should be derived from samples that are derived from individuals that are originally consented for broad sharing. And this is very important here because if the consents fundamentally limit sharing the data or any other products that come out of this derived data or even in some cases potentially potentially cell lines, then it will be the poor, the effort will be the poor for it. So please talk about the sort of the consents used of how the samples were consented in the recent sharing plan with attention to how really shareable the downstream data will be. Here's a question. How well-defined does the strategy for functional assays in the proposal need to be? Should one group focus on a defined proven strategy or evaluate feasibility or scalability between multiple strategies and presented as such from the proposal? So I think there is room. I think every proposal needs to have at least a plausible phase one strategy at least part of their work. And that was back up in responsiveness. This is not technology development, but clearly not everything is going to be optimized. So I anticipate everyone's going to have to do some optimization. So I think that there's room for both. I don't expect that every application is going to be exactly the same in this regard. But there should be some core element that you really can't justify. You think it's going to produce useful data relatively soon in the program. I hope that answered the question. Again, in my opinion, in my opinion, the sort of more optimization stuff part. And it does say in the FOA that if you shouldn't really be doing de novo technology development, but you can use funds for adopting technologies that have been developed elsewhere or for optimization. And you should talk about both about what you want to do and also sort of how you would bring new methods and or new optimizations in to what you're doing. Because I again, I don't believe that everything is ironed out here. And I think there needs to be room for optimization over the period of these grants. We have four minutes left. And I think we'll just can I don't see any more open questions we have about two or three minutes left. And we'll wait to a few minutes to start up the next one in case people were on a schedule. All right, I think that we can wrap up here for this for the discussion of the production research and development FOA and move into the next one. Thank you all for your questions. And don't forget that you can always can always ask questions. And if you have further questions, you can contact contact us at the Morphic HRI email address that was listed in I think the second slide. All right, Ajay, I think you can go ahead. Good afternoon. So I'm Ajay Pillai and I'll talk about the second RFA in the Morphic program, which is the data analysis and validation centers. So the primary goal of the data analysis and validation centers FOA is to make sure that the consortium's data variability is controllable. Data is useful to understand basic biological processes and that it is understandable for undertaking future hypothesis driven science by the community. So the projects proposed within this FOA have to have a high potential to eliminate the strength and weaknesses of the data being generated within the program and to ensure that the data is utilizable by the community and that we obtain needed feedback from the community for that purpose. Next slide, please. The FOA lists a bunch of non-responsive criteria and I wanted to highlight a few of these here that in this FOA, wet lab data generation would be considered non-responsive. Applications that do not propose to use Morphic data and that do not address collaborations within the consortia and also that do not have a data sharing plan that will be non-responsive. There are other criteria listed in the FOA and you should pay attention to that. Next slide, please. Some of the key challenges for applicants to this FOA is to realize that year one is special in that there'll be more likely than not no Morphic data generation within the consortia. So we expect that you will bring your own data, so to say, or publicly available data to address questions that go to the root of what Adam described and what the FOA describes as the basic goals of phase one for the Morphic program. These methods that you would use to develop and to sharpen using publicly available data is one approach to dealing with the special year one requirements. Next slide, please. Some of the other challenges that we need to keep in mind and a lot of this is not very novel in here, there are standard data analysis challenges that there aren't that we can identify and correct technical bias in the data, that batch corrections can be performed and that other issues of large-scale data analysis need to be addressed in the application. You should also think carefully about what metadata need to be made available within within the data releases for the consortium, what types of quality amount control and quality assurance need to be undertaken for making sure that the data that the underlying biology and the data generation challenges are reflected appropriately within the metadata. And as I mentioned before, one of the main goals is to be is to have various labs within the community use this data to do further more detailed studies for all of the knockouts and their biological role. And so you should think carefully about methods and APIs and other things that you want to propose that will make the data more easily accessible by the community. Next slide, please. There are also consortium responsibilities as the FOA states in multiple places. This is phase one. We need to gather a bunch of information about how this is going so that we can make decisions about scaling this up to genome-wide. So one of the questions that keeps coming up is how are we going to select the thousand genes as a consortium? In general, essentially how good and useful are the data and how good and how we work together to understand and evaluate the utility of the data and the metadata and the APIs that the consortium is going to make available. Next slide, please. A few things about the application and review. So as Adam described earlier, these are all cooperative agreements. And please follow the instructions in the FOA about the research plan and research strategy. Please note that the budget is $300,000 a cost per year and for a period of five years. Also, again, data sharing is required in a separate section, but it is reviewed and scored, as again Adam mentioned in the beginning. There are also specific review criteria for this FOA that you should pay attention to. Next slide, please. And that's basically all I had to say and it's open for questions. I think there was a question that was asked previously that I don't think was answered. So it's effectively something that I said about year one. So the question is for computational teams, it is difficult to envision a data analysis center given that assays are still not defined. Will there be another opportunity to synchronize post-letter of intent period? So it is true that we will not know the precise nature of the assays that are going to be part of the consortia and waiting until the letter of intent period, since it is not required, is not likely to necessarily answer the question. I think generally, so I offered one way in which you can approach the first year when there is no data from the morphic consortium itself. Generally, the FOAs try to tell you what types of assays and also the question and answer sessions today. And that will be reflected in the fact. Generally, indicate what type of assays you can expect the consortium to have. So that's what we will have to work with. So that's the short answer to the question that's posed earlier. If you have any more questions, please type them out. So we have a few more questions. The first one is will new algorithm develop be considered responsive to this FOA? I think the answer is yes. There's another question which says it would make sense that each production center designed their own data analysis depending on the assays. So this question is I think Adam tried to answer this. Let me try and repeat Adam's answer. And if he has to add anything else to it, I'll ask him to chime in. So yes, the data production centers have to validate their own assays. They have to make sure that their assays are reproducible, that they give you sufficient biological signal. One of the roles of these data analysis centers is actually to look at data across all of the different production centers. So there are goals and there are consortium white goals that the data analysis and production center applicants and grantees will have to contribute towards and answer questions about. There are also questions that cut across individual data production centers that would also need integrative analysis and other methods to look at the fidelity and biological signal within all of these data sets. Adam, do you want to add anything else to that? Yes. Ajay, I think what you said is right. The production centers can propose analyses on their own data and it is very likely that certain analyses will depend on the data type. That's limited in the budget. I think that the hidden question here or the spin that I'll put on this question is that it's also important for the data to get out and be analyzed by the same data to get out and be analyzed and analyzable by the analysis and validation centers for all the reasons that Ajay says. And this, together with the last question I think that was asked, it is going to be a challenge. Again, because the analysis center can't anticipate everything that's going to be proposed, but it's something that's going to have to be, there's probably going to be a lot of discussion around this at the consortium level once applications are funded. To Adam's point, it is often much easier in some ways for data analysis to be done by the production centers because they have a lot of metadata available to them, which people usually don't realize are important for when you release data sets. So one way to think about these analysis centers is that they're your first outside group looking at the data and looking at whether enough metadata is available to actually interpret the data accurately. So that's another thread in the same. So I move on. The next question is, should we expect consortium wide portals channels for disseminating algorithms, tools, results, or is the expectation that each of the data analysis and validation centers have individual dissemination channels? So yes, we will have consortium wide portals and channels for disseminating this, so you don't need to have a build up your own websites for public consumption. And I think Colin will address that in his next presentation.  So how you communicate that with the individual community members is going to remain your responsibility, but you don't have to set up portals. Okay, Sean, do we know how we are doing on time? I know there's a lot of it left. Yes, I believe we are ahead of schedule right now. By my estimation, for this RFA 030, we are 15 minutes ahead of schedule. I think we should wait. We should wait another two or three minutes for additional questions. And then in anticipation that somebody might be waiting offline until Colin starts to present, we can start back up in maybe another 10 minutes or something like that. I will remain. I will be sitting here looking at questions if another question pops up. I'm happy to try to answer it. But I do think that we should wait in case somebody was planning just to show up for the final presentation. Oh, so Adam, I just realized I was texting everybody, not just the host and panelists. But can we put up, I think we should just go officially on break and tell people what time we're back. I think that's completely reasonable. So what time would that be? Back at 225. Okay. Sean, can I ask you to reply that just says we will be back for the final presentation at 225? Yes, I can. Thank you. And I ask the hosts to stay live, please. And panelists to stay live. So as Adam said, I think both he and I are available to answer any more questions. We have another question, I think that was addressed previously, but asked a different way. So I'm happy to answer it about the production groups. So there's a significant emphasis on organoids and IPS models. Does that mean the cell lines are not going to be responsive? So cell lines could be responsive, but you have to justify them in terms of generalizability. I'll go a little bit further than I did before. I can see that in some cases, cell lines are going to have advantages. I don't know how that plays out across different cell types or different tissue types or different assay types or informativeness or any of that stuff. But I can see that in principle, for example, there are cell types where organoids are not well developed, for example. So I could see that there are justifications. So it wouldn't be unresponsive. I'm technically speaking for a program director and the review officer. Non-responsive means that it's either so obviously far off the topic or that it is something that's listed as one of the responsiveness criteria. So it could be responsive, but my intuition is that it's going to take careful justification to do this. Well, I've got a question for you, Adam. Immortalized cell lines, cancer cell lines, cells that are not totipotent, those kind of cell lines? Be appropriate or not? Again, I think it depends what kind of advantages they have for striking this right balance between informativeness and generalizability and scale. There's a lot of trade-offs here. And again, they don't play out. In my thinking at least, and I'm sure the people on the phone have considered these issues more carefully than I have, but my understanding is that again, things are developed unevenly. The state of the art is uneven across different cell types and across different kinds of assays and things like that. And the RFA does not absolutely exclude, does not say cell lines are not responsive. It does state of preference for organoids mostly because they can be extremely informative. All right, Colin, I think you're up. Just waiting for that slide. So, third RFA for the Data Resource and Administrative Coordinating Center. This is the FOA that's going to pull it all together for the entire program. The, I'm going to break it down based on the instructions in the research strategy section, which you should very carefully read. And we've essentially laid out five different tasks for the, for the DRAC as we call it. And though generally there'll be sort of two large components. One is being a data host and disseminator and analysis center, which will include the web portal and the dissemination API solid activity. And then the second thing is a tracking and collaboration and coordination activity, which is the coordinating center. So, I have a few slides that sort of cover these different topics in detail. So, the basic data resource, database, an interesting thing here is then collaboration with the DAFs that Ajay talked about. So, there's going to be a relationship there where they work on the analysis and validation of the data, which they get from the production centers. They should do that in a collaborative way. But the final analysis, annotation and dissemination of the Morphic data will be handled by the DRAC. And then another interesting task will be integrating external data and information. So, this program we think will benefit greatly from, from bringing in outside data to help with interpretation and understanding the implications and biological ramifications of the findings generated here in cell lines. For example, conf data. And then finally, serving as administrative coordination center. So, we can discuss these in a little more detail starting with the next slide, which is the data resource. So, imagine that the DRAC will primarily receive Rangel and QC primary data in collaboration with the data production centers. And that will require defining very detailed sort of data output standards. So, this includes not only the primary data, but the associated metadata and protocols from the various centers that probably be overlap with various centers doing similar types of assays. So, that'll have to be worked out on the consortium-wide basis. They will develop a database to store this, which will be obviously molecular data, metabolomics, transcriptomics, that sort of thing, probably imaging data, 2D, 3D imaging data and other sorts of things. You'll have to anticipate that and do that adhering to the fair principles and then make the data available to the consortium and community briefs and use. So, immediately, of course, is making that data available to the DAVs and being able to work on the analysis of the data. The next project that Dennis is collaborating with the DAVs, and since that's covered in the other FOA, and I just talked about it quite a bit, I really defer to him on how he envisions that happening. And then, based on the outcome of that, playing with the data and understanding it, understanding how to analyze it properly, understanding how to annotate image data versus quantitative data, categorical data, the final pipelines or the final repository of all that information will be in the track. So, when you look up a gene and you look up an asset, you'll be able to find the R package that the scribe site was analyzed, you'll be able to find or reference to where the R package can be downloaded, the metadata, the equipment that was used, that sort of thing, and the annotation terms that are applied to that analysis. So, that will identify outlayer phenotypes as mutants. You'll use some kind of ontology or controlled vocabulary for annotation. In COMP, we use a mass phenotype ontology, we use a variety of different controlled vocabularies for image data. I think image analysis is going to be particularly challenging, but with new AI applications, maybe there'll be some breakthroughs there. You know, histology, staining data, forest and stator, you can imagine that you do not want to be hand annotating that depending on expert review. So, that's an interesting question. And then providing a web portal, which we expect you to also work on user interface experience to make that facilitate the interaction by the outside community coming into Find and discover data and provide, of course, robust APIs. I think the next slide talks about data integration. So, it's up to you to identify complementary information resources to implement some kind of interoperability and make that data available. Obviously, my background is working on the COMP program, so I'm very keen to understand how cellular phenotypes and molecular phenotypes for genes that are knocked out in this program relate to the intact organism phenotype we see, say, in the same gene knocked out in COMP where the mouse, you know, maybe deaf, may have a bone disorder, may have obesity, and then how that relates to the various cell-based or organ-like-based assays that are taking place here. So, if you have a way to federate that sort of consolidation of information, that would be what we want to see. And then the second major prong of this effort is going to be administrative and coordination center work, so providing communication platforms, facilitating interactions within the consortium, tracking consortium activities, experiments and data, which is probably going to be part of naturally flowing from defining the data upload standards and tracking the metadata and then analyzing that to understand how progress is being made. And then, of course, it falls to the outreach efforts to promote the consortium resources to external users. And that may be social media, maybe meetings, and maybe workshops, there's a variety of different avenues you can imagine for that. I think the final slide is next from correct, the two slides in. So, again, application review is an important consideration, particularly if you have not previously had a U award. So, ask yourself if you've been involved in a cooperative agreement with NIH, and if you haven't, there's some things that are quite different about these kind of applications. So, for instance, please follow the instructions in the research plan. So, the research strategy section lays out in detail the things you have to address. This is a little bit unique to use. We lay out things in much more detail. Second, check the application review criteria, because we add the general specific questions for the reviewers to address in the review process. So, this should help you understand what the reviewer is thinking about when they go through your application. And then, finally, check the award administration section, because that contains the cooperative agreement terms and conditions. And look at that carefully, because that lays out a very detailed structure of how a cooperative agreement works. For those of you who had used, you know, how this works. So, the budget is $1.5 million total cost per year over five years. And I think that's most of the highlights of the FOA that I want to point out. Next, I think that was my last slide. I have not received questions in the email box. So, we can take questions now if there are any. Your question to Ajay about whether everyone should have their own individual dissemination channels versus the centralizing this. And do you want to sort of address that question again from the perspective of the coordinating center? I think Ajay was trying to dissuade people from doing that. Am I correct? I think we want to have a uniform. We want to have a one-stop shop that disseminates the morphic data that's authoritative and has version control. And you done a lot of from here, you know what you're getting. We really don't need to have three or four different websites that somebody has to go to to make sure that they're getting all the data. So, we really want to consolidate it at the draft, put it in a stable database and disseminate it from one portal. Colin, you have a question in the question and answer box. I mean, so given the lack of year one data, will this FOA address public user supply data as for the analysis centers? I actually think there's going to be an awful lot to do that won't require morphic data. For example, all you have to know is the analysis that's being planned by the production centers to be able to get to work on the markup to specify what the upload is going to look like. And to collect that information and to collect all of the metadata that's needed to be associated with that is a lot more time consuming and harder than you think. It took us years to get that perfected and comp. I think we spent the first two years just working on that, facilitating that whole, automating that whole process so that it worked reliably and robustly. So that's a lot of work right there. Second, data integration with an outside source like comp, that's going to take a huge amount of effort to get that done. Third, evaluating ontologies and control vocabularies, you can get started on that as soon as you know what the assays are. And that's going to take a lot of work. So yes, you won't have data to run QC analysis. The data will be waiting for that too. But I think you will have your hands full in the first year. So it's processing analysis of the data expected to be done by the track. Well, yes, in collaboration with the DAF. And I don't know if Ajay wants to say something about how that shared responsibility and exploration of the data will kind of work. The drag is not going to operate independently. It's not going to say this is our final pipeline, that this is the analysis procedure. They're going to have to do it collaboratively. And we're really putting this resource forward to the DAFs to assist in really exploring the data. Yeah, I mean, in general, I'll use slightly different words to say what Colin said. I mean, a lot of these things are going to be consortium-wide discussions, optimization of pipelines. This may be more easily achievable for the more familiar types of assays than for other types of assays. So we are going to get some amount of imaging data. And with imaging data, there are a bunch of challenges like cell sedimentation and so on, that are going to take a lot of work to resolve and maybe also think about making available the images themselves and get other people to be able to process data and things like that. So there are going to be a range of questions with the range of different answers that we will be addressing during the whole consortium five-year phase. But in general, what Colin said, we will make these decisions as a consortium as to what is best, which pipelines are best, how you bring experience from other work that you have done and other work that other people in the consortia have done, outside the consortia have done. Yeah, so I mean, Colin put a lot of effort into using micro CT on embryos. So we had volumetric data. So there was a volumetric, you know, encyclopedia reference encyclopedia. So we could do automated analysis of that. That was worked on very hard by a lot of people. The histology data was handled by manual curation by experts by a team of histology folks who got themselves organized to do that and use controlled vocabularies. I would say the laxie expression data is a little more ad hoc, you know, for lack of a better word. You know, so there's a variety of different challenges once you get into image and data, for sure. I think we should give it another couple of minutes for additional questions about this RFA. And if we don't see any, we'll open it back up to general questions about any aspect of what we talked about today for the last few minutes. And based on the flow of questions, we will keep going or we'll wrap it up depending on on the volume of questions. I wanted to remind everyone that this is not your only opportunity to ask questions. If you are one of those hesitant people to ask questions in public, you can send us a email. I think we have another question for Colin here. Any more details on what or how much external data to integrate? You know, so we're doing a pilot. We're trying to explore what's really useful. I think we've made it pretty clear that we have sort of open ended requirements. So this becomes sort of a question of review question where it depends on your argument that you justify this data is vitally important to integrate this other data not so important. So we're, you know, counting on you to put that forward in your application. That being said, I would opine that copying an instance of a database is not, doesn't sound like the greatest idea. We have really robust APIs with COM, our INPC database. And we know other people use those and they set up queries on their own on their own portals and they just come in and grab data out of INPC via the API. So I would think a live federated system like that would work better, but defer to data informatics experts. I'm looking at you, Ajay. Yeah, I mean, I, yes, there is really no point in replicating another resource within through ETL or any other method into the more fake resource. But there are things to be learned from all the other resources. And one can potentially write applications and algorithms that do integrated data analysis to some extent. And if we have to worry about providing those sorts of data sets within some cloud environment or something, there are other methods available at NIH to make that sort of thing possible. So that's going to be part of the learning experience. I mean, there's obviously a lot of large scale screens going on. There's the RAID screens going on. There's databases for all that. There's functional variant screens going on. I think there's a lot of stuff out there that is ripe for integration. I think this next question is for you too, Ajay, in the Q&A. Yeah. So the question is, how do you see prioritization of data analysis applications in terms of their complementarity versus quality? I'm not sure I understand this question. Let me take a particular interpretation, which is what I think this question is about. If the question is about how the reviewers are going to react to an application to figure out whether or not that application's data analysis method is directly applicable to a particular data production enterprise, then the answer is nobody, the reviewers are not going to know. So I think the general expectation is that we have Colin and Adam and I and the FOAs have talked about what you can expect generally to be the types of assays. And we should try to focus on what your core strength is in being able to address analysis of those types of assays. I'm not sure that I have answered the question. Maybe there is an interpretation of this question that my colleagues have. Or please clarify your question. Ajay, I read this as being, and the person who asked the question should please clarify if I'm wrong. As being a question that's related to the selection criteria that we discussed way back at the beginning of this whole presentation. So I agree with Ajay, the reviewers won't know which other components are funded or not. And it's not a review criterion. So they shouldn't be using it anyway. They should be using the quality of the application and the review criteria. But there are selection criteria after that. So it's a two-stage review process. One is the scientific review that assigns a score, and the other is the council level review. And in the past, NHGRI programs where there have been a big response like this where there's been a big response in particular have done things like select between similar scoring applications based on things like diversity of approach. For example, not to have multiple grantees doing exactly what we propose exactly the same thing or very, very close to the same thing. So that there can be circumstances under which the selection criteria would push things that way. Adam, it's worth pointing out to people where they could find the selection criteria in the application. I mean, in the FOA. In the FOA. Well, I have to. I have to. I can do it. It's under section five application review information item two review and selection process. I just want to clarify the statement that's there in the Q&A box, which says if multiple applications are focused on the analysis of the same types of assays would only one be selected. It was addressed. So I just want to be sure I it might that might be the case if they really were very similar applications. But for example, if they took different approaches to the analysis of the same types of assays, then they might be different enough. I think it's too. It's too. It's too difficult to sort of game out all the specific circumstances to make a decision tree here. So I can't give you that that level of detail in advance at all. But it's the kind of thing that we think about when we get to the fund exchange. But I'm going to give another two minutes in case another question appears if no more questions appear in two minutes. I think we can wrap up. Sean, maybe it's worthwhile putting up the first slide with all the links and the email addresses and stuff. All right. I have not seen any further questions. Again, you are not limited to this form to ask those questions. Please use the program email contact to ask questions. And I want to thank everyone for attending and for all your great questions. And we are looking forward to seeing your applications. Any final remarks from Colin or Ajay? No, I'm fine. Thanks very much, everyone. Take care.


Although the concept of entropy is originated from thermodynamics, its concepts and relevant principles, especially the principles of maximum entropy and minimum cross entropy, have been extensively applied in finance. In this paper, we review the concepts and principles of entropy, as well as their applications in the field of finance, especially in portfolio selection and asset pricing. Furthermore, we review the effects of the applications of entropy and compare them with other traditional and new methods. This article was authored by Guangqiu and Tong, Rukai, and Rongxi Zhou.


Hello everyone and welcome back to KubeCon, CloudNativeCon here in Detroit, Michigan. My name is Savannah Peterson, joined with John Furrier. John, we are in the meat of the conference. It's really in crunch time, day two of three days of wall-to-wall coverage and this next guest is running the show at CNCF, OG, been in the community, doing a great job, I'm looking forward to this segment. Me too, I'm even wearing, you may notice, I am in my CNCFT and I actually brought my tea from last year, for those of you. And the reason I brought it actually, I want to use this to help introduce our next guest is the theme last year was resistance realized. And I think that KubeCon this year is an illustration of that resistance realized. Please welcome Priyanka Sharma to the show. Priyanka, thank you so much for being here with us. Thank you for having me. This is your show. How are you feeling right now? What does it feel like to be here? It's all of our show. I am just another participant, but I am so happy to be here. I think this is our third hybrid in-person back event and the whole ecosystem, we seem to have gotten into the groove now. The first one we did was in LA where you have that shirt from, then we went to Valencia and now here in Detroit I can sense the ease in the attendees. I can sense that it just feels great for everyone to be here. And you guys were face-to-face in LA but this is really kind of back, face-to-face, somewhat normalized, right? And so that's a lot of feedback there. What's your reaction? Because the community's changed so much in three years, even two years, even last year. Where do you see it now? Because there's so much more work to do, but it feels like it's just getting started. But also at the same time, it feels like people are celebrating at the same time. Kubernetes is mainstream, cloud native at scale. People are talking about developer, more developers coming on board, more traction, more scale, more interoperability. Just a lot of action, what's your thoughts? I think you're absolutely right that we are just getting started. I've been part of many open source movements and communities. This is, I think this is something special where we have our flagship project considered mainstream, but yet so much to be done right over there. I mean, you've seen announcements around more and more vendors coming to support the project in the boring but essential ways that happened, I think this week, just today, I think. And so Kubernetes continues to garner support and energy, which is unique in the ecosystem, right? Because once something becomes mainstream, normally it's like, okay, boring. But that's happening. And I think the reason for that is cloud native is built upon Kubernetes and so much more than Kubernetes. We have 140 plus projects and folks have a choice to contribute to something totally cutting edge or something that's used by everyone. So the diversity of options and room for innovation at the same time means this is just the beginning. And also, projects are coming together too. You're starting to see formation, starting to see some de facto alignment. You're starting to see some visibility into how the big moves are being playing out, almost the harvesting of that hard work. Yes, I do think there is consolidation, but I would definitely say that there's consolidation and innovation. And that is something I genuinely have not seen this before. I think there are definitely areas we're all really focusing on. I talked a lot about security in my keynote because it continues to gain importance in cloud native, whether that is through projects or through practices. The same, I did not mention this in my keynote, but around continuous delivery. Generally, the software delivery cycle, there's a lot coming together happening there. And many other spaces, so absolutely right. Let's take in a little bit actually, because I'm curious, you get to see these 140 plus projects. What are some of the other trends that you're seeing, especially now as we're feeling this momentum around Kubernetes, the excitement is back in the ecosystem? Yes, so much happening, but I would definitely say that the underlying basis of all these projects, I brought that up in my keynote, is the maintainers. And I think the maintainer group is the talent keeps thriving and growing. The load on them is very heavy though, and I do think there's a lot more real company, the companies around us need to do to support these people because the innovation they're bringing is unprecedented. Besides Kubernetes, which has its own cool stuff all the time, I think I'm particularly excited about the Argo projects. So they're the quadruplets, as I like to call them, right, because there's four of them within the Argo banner. I had Yuan from Argo on my keynote actually, alongside Heba from Kubernetes, and we talked about their maintainer journey. And it's interesting, totally different projects, same asks, which is more support and time from employers, more ways to build up contributors, and ultimately they love the CNCF marketing support. Argo projects is really a great umbrella. There are a lot of action going on, a lot of action going on. Arlon, I saw that, got some traction. A lot of great stuff. The question I want to ask you, and I want to get your reaction to this. You know, we always go to a lot of events with theCUBE, and you can always tell the vibrant of the ecosystem when you see developers doing stuff, projects going on, but when you start seeing the commercialization, the news briefings coming out of this show feels a lot like reinvent. Like, it's like a tsunami. I've never seen this much news. Everyone's got a story, they got announcing products. There was a lot of flow even from the CNCF. What's your reaction to that? I mean, it's a tell sign of activity, certainly, and engagement, but there's real proof coming out, real visibility into the value propositions, rendering itself with real products. What's your reaction to the news flow? Absolutely, I think it's market proof, like you said.  And I think that I hope this continues to increase, and with the wide basket of project portfolios, that's what I hope to see. CNCF itself will continue supporting the maintainers with things like conformance programs, which are really essential when you have people building products on top of your projects, and other initiatives so that the technological integrity remains solid while innovation keeps happening. I know from a little birdie, Brendan, good friend of mine, that you had a board meeting today. And I am curious, because I hope I'm not going out of bounds on an assumption, I imagine that room is full of passionate people. Absolutely. CNCF board would be a wild one. What are the priorities for the board between now and Cape Cod next year? Sure, so the CNCF governing board is an over, it's like an oversight body, and their focus is on working with us on the executive team to make sure that we have the right game plan for the foundation. They tend to focus on the business decisions, things such as how do we manage our budget, how do we deploy it, and what are the initiatives, and that's always their priority. But because this is cloud native, and we're all technologists who love our projects, we also engage closely with the Technical Oversight Committee who was in the SED meeting that we just talked about, and so lots of discussions are around project health, sustainability, how do we keep moving, because as you said, Kubernetes is going mainstream, but it's still cool, there are all these other cool things, it's a lot going on, right? Yeah, you've got a lot of balls in the air. It's complex decision making and balancing of priorities. Yes. And demands, stakeholders, do you have any stakeholders? Every project, every person, every company.   It's one of the things I'm the most proud of. Yeah, it gives me all the feels as a community builder as well. What an accomplishment, and supporting community members in those different environments must be so dynamic for you and the team. Absolutely, and it behooves us to think globally in how we solve problems. Even when we introduce programs, my first question is, are we by accident being, let's say, default US, or are we being defaults Europe, whatever it may be, because we really got to think about the whole world. Global culture, it's a global village. Yes. And I think global now more than ever is so important and the Ukraine discussion on the main stage is awesome. I love how you guys did that. Because this is impacting the technology, we need the diverse input. Now, I made a comment yesterday that it might slow things down. I meant, as it's more diversity, there's more conversations. But once people get aligned and committed, that's where the magic happens. Share your thoughts on the global diversity, why it's important, how things are made, how decisions are made, what's the philosophy? Because there's more to get your arms around. Yes, absolutely. It may seem harder or slower or whatever, but once it gets done, aligned and committed, the product's better, everything's better. Yes, absolutely. I think the more people involved, the better it is for sure. Especially from a robustness, resilience perspective, because as they say, sunlight makes bugs shallow. That's because the more eyes on something, the faster people will solve problems, fix bugs and make, look for security, vulnerability, solve all that. So especially in those areas, I think where you want to be more resilient, the more the people, the better it is, 100%. And then when it comes to technical direction and choosing a path, I think that's where, it's the role of the maintainers. And as I was saying, there's only a thousand odd of maintainers for 140 plus projects, right? So they are catering. Wow, they have a lot of responsibility. Right? Serious amount of responsibility. It's crazy, I know. And we have to do everything we can for those people because they are the ones who set the vision, set the direction. And then 176,000 plus contributors follow their lead. So we have, I think the right mechanisms of contribution and collaboration in a global way are in place. And we keep chugging along and doing better and better each year. What's next for you guys? Look at, you got the EU of show coming out. Correct. Amsterdam. The economy looking. I don't see a recession for technology, but that's me. I'm going to bullish on tech. Yeah, there's some layoffs going on, some cleaning up over inflated expectations on valuations and startups. But I don't see this stopping or slowing down, but what's your take? Yeah, I mean, as I said in my keynote, right? Open source usage source in times of turmoil and financial turmoil is one example of that. So we are expecting growth and heavy growth this year, next year and onwards. And in fact, going back to the whole maintainer journey, now is the time there's even more pressure on them. And companies, as they manage their workforces and prioritization, they really need to remember they're building products off of open source. This is open sources on which what their business relies, whether they're a vendor or end user, and give maintainers the space, time, to work on what they need to work on. Yeah, they need a little work-life balance. I mean, the self-care there, I can't even imagine the complexity of the decision matrix in their mind. Speaking of that, and obviously culture must be a huge part of how you lead these teams. How do you approach that as later? I think the number one, so the foundation is a very small set of staff, just so you know. Actually, let's tell the audience, how many people are on the team? You know, it's actually a difficult question because we have folks who like spin up and down and we have a matrix support from the Linux foundation, but about 30 people in total are dedicated to CNCF at any given time. But compare, yes. Y'all do hard work, you're doing great. It's a flat organization. It is pretty flat. Serious, really, beautiful. It's actually, in some ways, very similar to the projects and the contribution to the communities there where it's like, everyone kind of like steps up and does what needs to be done, which is wonderful and beautiful, but with the responsibility on our shoulders, it's definitely a balancing act. So first off, it is, I ask everyone to have some grace for the staff. They are in a startup land with no IPO on the other side of the rainbow. They're doing it because they love, love, love this community and technology so much. And then also they're acknowledging that nobody in open source wants to see a bureaucracy. I mean, everyone wants to see lean, efficient. Yeah, absolutely, John's great. It's a great point and I think that it's just, it's amazing what passionate people can do if given the opportunity. Let's talk a little bit about the literal event that we're at right now. Theme today, Building for the Road Ahead. What was the inspiration for that? Detroit. We're in Detroit. People drive here. In case you didn't know, cars have been made in the city. Motor city. It's everywhere being here in the city, which is awesome. There was of course a geographical element, but it also aligns with where we're at, right? We're building for the road ahead, which frankly, given the changes going on in the world, is a bumpy road. So it's important to talk about it and that's what the theme was. And how many folks have shown up? This is a totally different energy from Los Angeles last year. I'm sure we can both agree. Everyone was excited last year, but this is an order of magnitude. How many folks do you think are milling around? Yeah, it's much more than double of Los Angeles. We're close to 8,000. And it's so, you're absolutely right. The energy is just way up. It's so good. People are enjoying themselves. It's been lovely. That's great. So you're feeling good. You're riding the high. Awesome. Congratulations. Yeah, thank you. I mean, I'm a little bit of a zombie right now. Don't look it. We wouldn't know. Nobody knows. They don't know. Hey, if you want to take a break, we got 12 interviews tomorrow. Yeah, yeah. Go on board. You co-host with us. We'd love to have you. Exactly. You're welcome anytime. You're welcome anytime. Thank you. But now it's been such a wonderful show and you folks are part of the reason just that everybody here is contributing to the awesomeness. You're part of it.  And Lisa Marley's over there. Lisa's over there. Yes. And Lisa and team. Yes, the team is awesome. Thank you for your support for theCUBE. We really appreciate it. We enjoy it a lot and we love the community. Thank you. Yes, thank you for your support for Cloud Native. Thank you. One last thing I just want to point out because it's not always it happens in this industry. The women outnumber the men on this stage right now. I'm proud of that. And I know the diversity and inclusion is a priority for CNCF. Top priority. Yeah, can you tell us a little bit more about that? Yes, it is something at the forefront of my mind no matter what we do. And it's because I have such great role models.  And he made a serious lasting impact. And I am not going to let that go to waste. It's not going to be me who drops the ball. We're behind you. All the way. We see improvement over the years. I mean, even from an attendance perspective on stage, I feel like you've done just an outstanding job with the curation and representation. I don't say that lightly. It really matters to me. But even in the audience, looking around, it's so refreshing. Even it sounds silly. The shirts are more fitted. There's different types of shirts.  We've been in this industry long enough. It's a shirt you want to wear. Exactly. And that's the whole point. I absolutely love it. Have we announced a location for KubeCon North America 2023 yet? It's Chicago. Exciting. All right. How have you seen you? Midwest. This is the first time I've said this publicly. I just realized it's Chicago people. The scoop I won from KubeCon. I feel so lucky we got to break the scoop. I was learning from John's lead there. And I'm very excited. Amsterdam, Chicago. It's going to be absolutely fantastic. Yes, do a smart move. Yeah, right. Especially after this. Right. It's actually not a bad move. Priyanka, is there anything else you'd like to say to folks? Maybe they're thinking about coming or contributing to the ecosystem. Anyone and everyone can and should contribute and join us. The maintainers are holding us all up. Let's rally to support them. We have more and more programs to do that. As you know, we did ContribFest here this week, which was the first time. So we will help you get involved. So you're not on your own. So that's my number one message, which is anyone and everyone, you're welcome here. We'll make sure you have a good time. So just come. Okay. Please do it. I can tell you that Priyanka is not blowing smoke. I feel very welcome here. This community has welcomed me as a non-technical. So I think you're absolutely preaching the truth. Priyanka, thank you so much for being here with us today on the show, for helping hurt the cats and wrangle the brilliant minds that make CNCF possible. And honestly, for just bringing your energy and joy to the entire experience. John, thank you for hanging out with me. I'm glad I could contribute in a small way to the group. I was going to say, I was going to say thanks for founding theCUBE so that we could be here in this little marriage and collaboration that would be possible. I thank all of you for tuning in to theCUBE here alive from Detroit, Michigan. My name is Savannah Peterson. I am thrilled to be sharing this content with you today and I hope to see you for the rest of our interviews this afternoon.


As I mentioned in my previous review, I've recommended many times H.G. Wells War of the Worlds and Time Machine. And I'll give Time Machine the same 5-second review I gave to War of the Worlds. And I quote, you should read H.G. Wells The Time Machine, period, just go read it. Like War of the Worlds, it is surprisingly modern in its writing style and how it's told. There is some amazingly good science, particularly about the distant future of the Earth. Like War of the Worlds, it is a very visceral book, lots of intensity to it, and lots of good talk about Time being a fourth physical dimension. And like Mary Shelley's Frankenstein, the Time Traveler himself who was never named, he does all of this without ever explaining how he does it. But it works. Yeah, I recommend H.G. Wells The Time Machine. Please remember to press that like button. It helps my videos get seen. And then subscribe so you can come back next time. I do science fiction book, TV, and movie reviews all the time. And please consider becoming a patron. There's a link in the description below.