Randy in the George Orwell's Classic Moral 1984, the supreme dictator that over caused a big brother, he systematically reduces the number of words that the citizen slaves could use, the fewer the words, the fewer the ideas, and the narrower the thinking, and the less power, of course, in the people's minds and for the people. And the language of this totalitarian world was called Newspeak. And sometimes when I listen to the concepts and the discussions here, it kind of sounds to me like Newspeak, meaning that we are repeating the same words, same concepts all over again. How do you see it? How do you see the concepts and the discussions? Yeah, I think it's an excellent point, Esko, and it's interesting. If you attend conferences and have conversations like this, you find that there's a continuous struggle around language. What do we call this that we're trying to do? You know, so we're combining profit and purpose and or mission-related organization or impact-related organizations. And so we're struggling with how to define the totality of the work that happens. And there's so much good that's represented here at Slush. And you see these, you see people just struggling with language. What do we call this? It's one part profit, it's one part purpose. We're focused on mission. But how can we define and begin to understand what a new language is? And I think that's a struggle right now. We need folks that will help us translate into that new language for the future. How do you see the future, what comes to the demands, for example, that Al Gore was mentioning? Should we kind of revisit our ideas about what business is? If we go back to Adam Smith, so before he wrote The Wealth of Nations and he came up with the idea of the invisible hand, he actually already wrote something that perhaps is even more relevant for us in our time. In the theory of moral sentiments, he argued that the stable society was based on empathy. And he underlined the importance of a moral duty to have regard for your fellow beings. So should we recreate this or visit our ideas that come from our past, which we perhaps have forgotten? I think we need to revisit those ideas. I think one of the interesting things is that TS Eliot has this great poem that I like called The Dry Salvages. And it's really a collection of four different poems. But there's one line from The Dry Salvages that has always stood out to me. And TS Eliot says it this way. He said they had the experience, but they missed the meaning. And so often, particularly in a consumer society, we have the, in a way, we have the experience of products and services, but we miss the meaning. What does that mean in our lives? And we've heard over and over again, I think, from various speakers, who are talking about how I think this next generation is changing and they understand what's the meaning. They want to, you know, where do these products come from? How are these products advancing us? How are they speaking to ethics and morality in ways in which perhaps in the past we didn't talk about that within that kind of context? And so I think one of the great challenges and great opportunity for us in the early years of the 21st century is to begin to recapture that empathy and that sense of morality, meaning, as maybe TS Eliot would define it. So those might be the universal values that should be present also today. Now I have this crazy idea that work itself is not changing. It's always been the same thing and it's always going to be the same thing. Work is solving other people's problems. The way we define those problems and the way we solve them is changing. And of course today we can define problems in a variety of new ways compared to the old industrial logic. So how should we think about this? How should we solve the problems? How should we define them? What's your advice for us? You've seen the word from many angles. Yes, yes, well, I mean over something like approaching 20 years in philanthropy, you know, we've seen, I've seen and I've probably read thousands and thousands of proposals coming from people around the world. The ones that stand out to me the most are those proposals that take a more holistic, systemic view of the problems. Too often we take kind of these silo sort of narrow view of what our problem is and think that that very narrow problem set can be solved by a very narrow solution set. And the reality is that's not the case. We live in a world where we're all connected and we're probably in this group where at most maybe three degrees of separation from one another at most, maybe four. And so I think we need to translate that into how we think about solutions as well. I work in philanthropy as you know and even within this group we tend to view philanthropy perhaps sometimes as something on the side and we call it charity. But it doesn't, it isn't understood in the definitions for entrepreneurship and sometimes broader commercial activity that's taking place. So in a way what you're saying is that it's not enough to make good products with least possible harm but you have to understand the bigger picture around it. Perhaps even that it's not the customer per se but it's the society and the future of the globe. That's absolutely right. Yeah, yeah. We've kind of hived off, you hear it in the language, purpose and profit. And that sort of defines how organizations and even how we distribute financial capital to organizations. Of course many are trying to put that together but they're still separated and don't kind of get to the level of scale that we need to be able to have a more holistic view of the solutions that are required in the 21st century. Something that Finns are very good at and that is very interesting for us Finns is to go home idea of games. And I'm a believer that the future of business is going to be closer to the games that we play. And now this also brings us to a problem on what comes to the whole picture that you showed us. Because the games we play have been played under the assumption that the unit of survival is the player, meaning the individual or company. And now we know that actually the reality is that the unit of survival is the player in the game being played. And the way we play those games today are kind of destroying the game and making it impossible for the game to continue. So do you think that that might be an approach to understand what's going on? Is the same take this kind of a game theoretical logic to business? I think it is, you know. I think there is, I think you're speaking to imagination. You're speaking to the ability to experiment that takes place within that theoretical orientation around games. In many of the massive games that take place now around the world, and as you said, Finland leads in this area, there is wide participation among people from around the world in many of these games. And so it does provide, I think, that theoretical framework and construct for us to think about it in the daily lives that we live. One of the interesting things in games is that games allow people to take responsibility. So they can kind of allow people to assume leadership as and when is needed. And that's very different than the kind of the structures that we are normally relate to as we talk about work. So being responsible, being able to make a response, being able to choose might be one of the key issues in the future. But how would you kind of, again, how would you help us to create more opportunities for choosing things, more things that are available, more opportunity spaces? Yeah. Well, I think the, you know, obviously a game takes place on a platform, right? And there's certain enabling conditions that exist within that platform environment for people to participate in the game. And to me, there's an analog to that in the daily lives that many people live, is they don't have the benefit of the platform or the enabling conditions to be able to participate in an economy with opportunity. And so in many ways, Humanity United, you know, it seems like an odd name for a private foundation, right? But we came to the realization that the big problems and the big intractable challenges that we face in the 21st century can't be done in isolation. They can't be done alone.  You know, we named ourselves Humanity United because we believe it speaks to the essence of solving the big problems that we face in this 21st century. And so it requires that people who don't have opportunities, that we aim to create the kind of enabling conditions where people can participate and can make choices that, you know, billions of people around the world today don't have the kind of choices that we benefit from and many of the people here at Slush benefit from today. I think the first industrial revolution really revolutionized the world in the sense of creating opportunities for consumers. But can it be that because of the price of our tools is going down so dramatically, actually what's happening today is we are democratizing opportunities what comes to production. So the tools we have should be understood as cognitive tools that help us to make, in a way, wiser decisions, how do you see the role of this kind of cognitive tools in the future? Yeah, I think that's one of the areas where technology, and there's so many here at this event, they're creating ways in which the technical expansion of these tools is leapfrogging what the developed economies had to build in the 20th century. And one of the benefits is we're beginning to leapfrog that. So the landlines, of course, you know, is the kind of classic story about how many undeveloped economies don't require landlines because they leapfrog right into the mobile environments. And I think that is a tremendous asset for emerging markets, emerging economies developing countries to be able to catch up, if you will, to the opportunities that are afforded us. So you mean that actually countries that are developing with the help of modern technologies can leapfrog to be making much, much wiser decisions that we are making here today? I think so. And frankly, I think there's a marketplace there for the ambitious entrepreneur to be able to capture a market that is going to explode, you know, in the latter years of the year, or in the mid to latter years of the 21st century, because that leapfrog will take place. Absolutely. And there's just, there's an argument for getting early competitive advantage. You know, as a result of that, which will have the effect then of lifting hundreds of millions of people out of poverty, right? And so it's a huge market opportunity, I think, for entrepreneurs, as they think about the expansion of technology into the mid 21st century and the opportunities that are presented there. So if in a way you could say that work is solving problems, then you could say that learning is really asking questions. And then the basic thing is that what kind of problems we solve and what kind of questions we ask. And could we spread then a larger, in a way, more moral base for asking questions? Because I think this is one of the basic things that we have to understand today that business is a moral system and all business decisions are moral decisions. Is that the only way to go or can we still wait a couple of years? I don't think we can wait, Esko. I really do believe in this idea that we're coming to this convergence around where business and the role of business as a moral agent, there's getting more and more understanding about what that confluence is in the future. And that sounds theoretical, it sounds almost philosophical, but I still believe that those who understand that early are provided a competitive advantage in the future around business opportunities. And that this particular talk we talked about, most people ask what's the next big thing, but we want to ask what's the next good thing. And I would say the combination of that is what's the next big good thing. That we can do, which begins to separate that idea that if you want to do something big at scale, then probably won't have much purpose related to it. Or if you want to do something purposeful, then it won't have scale. But I think the future opportunities out there actually combine those two. And that's where this language question trips us up. Because we're still trying to figure out, okay, impact investing, purpose, profit, mission-based, what is it? But soon it'll come together and we'll... Somehow, maybe slash 2018, they'll define new language, but somehow we'll develop a language where we can speak about more. Would it mean in practice that if we talk about customers, we should also talk about the ecosystem at large? And if we talk about short-term results, we should always talk about long-term. And have a kind of a more varied view to whatever we do. And perhaps that leads us potentially to solving more valuable problems and asking more important questions. I think that's right. The temptation right is to pick the low-hanging fruit. And I think pretty soon a lot of that fruit will be picked. And we're going to have to start reaching a little bit higher. And I think that's a good thing. And I think it will require us to do that. Can it be that we could actually say that philanthropy is one part of the venture capital scene, and philanthropy is actually making the biggest bets and taking the biggest risks also? I think so. So a lot of philanthropies, certainly in the U.S. and perhaps around the world, there's a lot of risk aversion in philanthropic practices. And I've just never understood that. I think most philanthropic dollars should be used in the most riskiest settings. And we should view philanthropy as not something that's off to the side or, quote, charity or something like that, but it's one tool among many within the continuum of financial assets that we draw from. So you have grant-making and program-related investments and debt and equity and all kinds of sort of tricked-out financial capital tools, but they're all part of one continuum that's deployed to drive, you know, a positive social life. So this is a message to all the startups here. So if you don't get venture capital money, you know where to go to. Thank you so much for joining us. Yeah, thank you so much, Tesco. Thank you.


Welcome to the Jenkins documentation office hours. This is the US edition here on December 15th. Today, right now, we have myself, Mark White and Bruno Verrachtin joining us. Thank you for joining us. On the agenda today, we have some action items. We are looking to focus on a couple different topics going into the new year and some blog posts that just came out. We have a lot of ideas and discussion topics for the December newsletter. This is going to be a recap of Jenkins over the last year. So we want to make sure that we highlight as much and as many great things that we were that were accomplished this year as we can. Several different topics and we have some a lot of ideas already for what we can include. So we want to have a bigger discussion with the community at large and see what other people are thinking of or what they might want to see. It goes from everything from platform modernization itself all the way to the advocacy outreach sponsors. Every facet of Jenkins is something that we want to highlight in this case. Then last few items we have on the list here, we do have another LTS coming up that's going to be released in January on the 11th. There's going to be a break due to the holidays at the end of the month. So a little bit of delay there, but just yesterday the RC release candidate has been shared. It's ready to test. It's good to go. We have the back porting ticket ready and all set and taken care of as well. So a lot of progress has been made there. The change log and upgrade guide pull request has also been submitted. So we're just trying to get ahead of everything and make sure that that's ready to go come time to release. There's been some talk about the Pipeline Docker plugin and where it stands in terms of its place within Jenkins and what that means for Jenkins and its extended community of users. There will be lots to discuss on that at a later point in time, but that is something that we're working on. Then finally, just the couple blog posts or another pull request that we've had come up recently, they're really interesting and like to have discussion around since they do address a couple of things that impact Jenkins as a whole. So anything that I might have missed or anything else that anyone wants to add to the agenda today? Nothing for me. Thanks. Neither for me. Thank you. Cool. All right. Thank you very much. So first things first on the action items. Right now we are working on a project to go through any of the tickets that have been created in JIRA in the website category. These are issues that were submitted regarding the Jenkins site documentation, other parts of it like that. However, they are for the most part older and potentially have been actioned on since even though the initial ticket might not have been updated. So right now what we're doing is we've out Friday, so we've created a GitHub ticket for that to go through and review. Mark and I have been going through the list of remaining issues, finding out what can be closed, what doesn't need to be there, what still might be relevant and what we can do to move that migrated into the GitHub so that we can track everything properly, get the progress going and make that information just steadily available and where it should be. That'll also help us focus everything into one place as opposed to being split between JIRA and GitHub. So benefits all around. There's been an item to archive the doc mailing list and switch over to community.jankins.io for the doc sig mailing list. That is something that we'll be taking on probably in January, just due to we're approaching the end of the year, end of the month. The holidays are going to include time off for a lot of folks around here, but that's something that we'll work together on as I'm taking over for Mark for documentation officer for Jenkins. We'll be working together to get to that point and once we have that going, we'll be able to provide some more information. Of course, Mark wanted to add that there was only 70 issues remain on the website project, so we've been able to close out a lot. I think I at least looked through 100 or something and I know Mark had looked through more, so we've done a lot of work on that already, even though it's only been a couple of weeks, which is great. And then we had a few blog posts that were published recently. One, the first one here is regarding the Google Summer of Code Mentorship, and this was written by Jean-Marc Messon, and just goes over the idea of being a mentor for Google Summer of Code and other projects and programs that we work with. She go to Africa, Riji, stuff like October Fest. Being a mentor is really, really important and helps push these along. You get to feel like you're contributing, helping people. You get to flex your knowledge if you are a mentor, and it's not a full-time commitment. It's a smaller commitment that we're looking for, not talking full-day dedication or anything like that. You can see here, we've got about five to eight hours per week, and that's doable for a lot of folks. But for mentorship, it's a really crucial part of all the projects that we work in, and we want to make sure that we can share that with people, potential mentors, existing users that maybe have not thought about this sort of thing before, and new users that are getting into Jenkins and contributing a lot. Recently, especially, we've got new release leads, and there's a lot of people joining up, and with October Fest now coming gone, we've had a ton of new contributors that may be interested. So definitely share this out as much as you possibly can. Make sure that if anything comes up, let people know that this sort of information exists, and that it's something that we'll always be here to help with, whether it's questions, additional mentorship, or otherwise. The next blog post that I want to mention here is Damian DePortal has recently created a blog post and alert, essentially, for this coming Sunday, December 18th. Jenkins will have an interruption and will have some downtime for Jenkins contributors and actually running things in Jenkins. Users of Jenkins won't be affected in the same way, but JFrog, who we want to thank as a continuing sponsor of Jenkins, wants to perform some maintenance just to make sure that everything's working properly for Artifactory. This will look like six hours of downtime between, I think it's 11 a.m. Israel? Yeah, so that's 9 a.m. UTC till 15, so what's that? Till 3 p.m. UTC is the time range, Sunday morning. And also the Jenkins infrastructure status page will also be updated with that downtime window. So click that link, Kevin, so we've got it in the, there we go. Notice that it says, hey, here's the status, and as that outage resolves, this page will be updated to show what the resolution time was. Perfect, great. Is there any other place that this might be relevant to? I know we have the community thread also talking about it, and we were talking earlier about making sure that the tweets and other notices are set up. Is there any other communication or avenue that we need to be aware of on that, Mark? The advocacy SIG meeting earlier today recommended two additional places, the Jenkins CI GitHub organization and the Jenkins Infra GitHub organization. And I submitted pull requests to those two. So if they're merged, then those pages will be updated as well. And if they're merged tomorrow, that's already Friday before it, before the Sunday of the outage, so that's quite good. Definitely. Thank you so much, Mark. Really appreciate that. And following that, we did publish our November newsletter just a couple weeks ago or on December 5th. So just again, our monthly newsletter highlighting November for Jenkins, a lot of the governance updates. We had our elections, security updates, infrastructure updates. Again, standard of what our newsletter is now meant for.  It's going to be a massive post comparatively, but a lot of wonderful updates, a lot of great information. And once again, just a wonderful way to highlight our community, our users, and anyone that is part of the Jenkins project. So now Bruno, I guess I do have a question for you. Really? Usually you've been the one who's kindly converted the Google Doc into an ASCII Doc format. Oh, yes. But this next one is going to be sort of mega monster. Are you still OK doing that? Yeah, of course. I will do my best. And of course, each time, I think it's just about perfect. And then the review begins and so many people point a finger at all the mistakes I make, but that's perfectly fine with me. It's community effort and I feel like everyone is putting it together. So it's it's not everyone Bruno, not just you, but yeah. And and as an aside on that too, for the December newsletter, since there's going to be so much and since we want to make sure that a lot of these, if not all of these topics are at least mentioned, highlighted to some degree, I'm going to be looking through it very carefully myself and reviewing it along with Mark to make sure that everything is good to go on that one. So ideally, you won't have to worry about as much of that in this case, since I'll be helping you out and working on it as well. And for me, it's a lot of making sure like it's it's what I want to do is make sure that these topics are put on there. So if, you know, if Damien provides a platform update or, you know, I'm providing the documentation update, there's a lot of different things that could be in different places, topics that might, you know, be coinciding with other topics or other ideas. But at the end of the day, we just want to make sure that things sorted properly and connected and make sense. And, you know, more importantly, highlights what we've been able to do in Jenkins over the last year. So and again, again, like this is a big one. There's a lot of information that's going to be there. So this is pretty much one of my main focuses for the next week or so. And, you know, and obviously we might not have it published before the end of the month because it's a monthly yearly recap. So that might come in January, that'll come in January. But between now and the publishing date, I'm here for anything that you need. And then the last blog post that we want to look at here is something that Basil Crow has just put together for us, which is really nice. But this is about the Jenkins plug-in development and that fact that we now require Java 11 as the minimum requirement for Jenkins. So this is to address concerns, issues, questions, any kind of general apprehension about it. Basil has done a really lovely job and put this together with charts, links, really good examples and logic and reasoning behind a lot of these changes and what's going on. This was just published a few minutes last hour, so very new to the blog. But it's very, very important in addressing some questions and concerns that folks have had over the last recently. Yeah. So could you go back to that graph, Kevin? Yeah, of course. That one, that one, that little thing on the right is a point of dramatic pride. Notice that the red line Java 11 is greater than the green line Java 8. So we have data that says that Jenkins users are in fact switching to Java 11. Now, if you look at the slope of the curve there, it's quite similar to the slope of the Java 8 adoption curve. So so it gives us good hope that we're going to see Java 11 adoption continue. Now, I'm even more excited by that Java 17 curve because that's a much steeper slope than previous next gen JDK adoption curves, right? When during the JDK 11 period, you see the early parts of the Java 11 thing, the slope of that curve is almost dismaying. It's so shallow, whereas that nice steep jump in Java 17 gives us good hope that, hey, in 12 months or whenever we we're ready to make even more progress on Java 17, great. So special thanks to Basel to so many others who did so much work to make this happen. Yeah, I was there in 2018, 2019 when the switch to Java 11 started. But I have the feeling that everybody in the core development team and in the infra team is pushing for the adoption of JDK 17. So I think it's a first in the history of Jenkins, maybe. Yeah, that's a good thing. We're almost not late. Right, which is dramatically better than past behaviors. Yeah, of course. And thanks, Kevin. Yeah, of course. Thank you, Mark, for all the additional contacts that really helps. And this is really great to see. And especially with I know the Java 17 adaption and so far it's been really, really reassuring and really giving us the results we're looking for, fixing a lot of things and making it easier.  Great. So so now that we've gotten through the action items, just we can go over the some newsletter topics, ideas. Mark and I put this together recently, and it's been coming since Docs Office Hours as well last week. So this is just something that's going to be an ongoing project for the time being as we move towards creating it. But just looking through this, we have a lot of different topics. Platform modernization, user experience improvements, development, acceleration, website improvements, localization, simplification, our Jenkins Governance Board elections and officer elections, the origin advocacy that's been performed over the last year, security updates. We've had lots of those infrastructure changes and updates and sponsor contributions. These are very vast and cover a lot of ground. Is there anything that we could add to this list in terms of a general topic or air to highlight? Or if you notice anything that is already categorized here or listed, is there something you'd like to see for it specifically? Is there something that maybe looks related to something you had in mind and isn't there? We can add it. Yeah, I'm just curious to see what everyone else might think. And we have a lot of we also have a lot of content for almost all of these things. We've had blog posts about Java 11, Java 17. The system was a big change over earlier in this year. We have a blog post for and then the more general topic stuff like back and dependency in front and dependency updates, making sure that we're staying in the forefront of that. Yeah, no, I guess to make the to make the translation easier for Bruno. Bruno, is there any guidance you want to give in terms of how we lay out that Google Doc? So, for instance, I'm tempted, Kevin, if you jump up to the sort of the topmost on the required Java 11 support Java 17 and system demigration, I'm prone to embed links to more details into each of those saying, look here, is it OK if they're embedded as hyperlinks or does that make your experience doing the ASCII doc awful? No, that's fine. That's OK. Um, lists and embedded links is fine with me. OK, all right. So, so you that doesn't because I assume there will be a lot of that. If I'm writing this, I'm going to be bragging and pointing, right? Bragging and pointing, bragging and pointing. That's fine. OK, cool. Right. And thank you very much, Bruno. And since I'm typically working in ASCII Doc myself, I might just end up writing some versions that have the links and everything set up for you if I can. I'll do what I can to help you out, though, on that front. OK, thank you. But just to be OK. Yeah, either way. And yeah, and I think, and Mark, no, this is something I just thought of as far as all these items go when we when we point them out on the newsletter, should we look to keep it brief and keep it to a few sentences for each item since there's going to be a lot or in the case like obviously there where we have the blog post, we can link to it and share that and let that do a lot of the talking for us. But in the cases where that's not where that isn't possible. Yeah, so for me, I think brevity will be be useful here. I would assume even more important is that we want some intermixed images scattered throughout this thing so that people have the visual relief of breaking a breaking a large block of text with with pictures of something. So it may be a Java for the UX improvements. Those should be UI screenshots for. I was thinking for the Pipeline Steps documentation improvements, screenshots of the page for for some of the others. It may the vision presentation. I think, for instance, if CloudBees is willing to allow public access to the DevOps world recording, we should embed the link to that video or even better get their permission to put it on YouTube in the Jenkins account. So then it then it gets registered right in the page as a nice clickable clickable link. So those kind of things for me are are they they improve the chances that people will read it. The other piece, I guess, with something this long is we probably better start with a table of contents so that people can read the summary of, hey, here's this, this, this, this and now maybe another question. Do we have too many themes? So count could you help me with a quick count of the themes? Kevin, it looks like there's at least 12 or 15. Ten. Ten. OK, well, so and the guidelines, I think three, three to seven is typical list length that people tolerate. So maybe we ought to look to, I don't know, maybe we need to think more about should we combine some of these or or or remove them. OK, yeah. And I think stuff like elections can probably go into like outreach and advocacy, maybe. Or yeah. And some newsletter do a TLDR part, you know, with the main topics. And then they go in greater details. I think of the pine 64 newsletter that I read earlier this day. So maybe we could have. Less subjects in the first part, and then maybe do something bigger later on in the documentation. Just a suggestion, I'm not sure that would be a good idea, but so how does the TLDR concept in the pine newsletter work? So they do a one sentence series, a series of one sentence items? Or how does it work? No, it's a kind of summary. It's not let me find it for you. I think it would be more something like in twenty twenty two, Jenkins was able to do X, Y and Z and a big thanks to everyone that helped. Maybe like one or two other ideas that you want to share in that. And then everything would be just kind of formatted after the fact. At least I don't know how it works with pine news. Well, and I just know I've seen some TLDRs like that. So it's just a list and the rest of it is sentences, real sentences. But already you are working with lists. So yeah. Yeah. OK, so the so the TLDR for them is top level bullet, one level indentation, one level below that, no more. So it's a table of content. So it's it's basically what we've done is our outline is their TLDR. Oh, you're right. So I like that. Yeah, that makes life a lot easier if that's OK. Well, and then if we if we make those things clickable and have them jump to that section of the document. Now now it's not just the themes, but it's the themes plus the details of each theme. Right. So nice. OK. Yeah, I like that a lot personally. I think that would be a really good format. And especially where now you can just kind of list everything out as you're going through it. And it's OK that it's as long as it is because you've already got this here. You can jump to where you need to be if we set it up like that. Yeah. No, that's a that's a good I like it a lot personally.  Yeah, with how much we're looking to put on there might be worth. Check trying to know, yeah, for sure. Cool. That's great enough. Thank you very much for know. Love it. So cool. OK. Yeah, I know Mark and I have gone over this list a handful of times and we're looking for any other additional input ideas, stuff like that. Bruno, as far as the stuff that you've been working on, I know that you're leading some of the platform SIG meetings and stuff like that. Is there anything that you'd want to make sure is listed here or? Yeah, I'd love to. But I think I would have to discuss maybe with Damian about that. But I have a few subjects about Docker images for the agents and also alternative platforms like arm 32 arm 64. I think those kind of progress we made this year could or should appear in that section. But I have to discuss that with Damian because what I see is as important is maybe not seen as with from other people as important. It's just because of the kind of things I like, which is not the case for everybody. So we'll see. But yes, I have a few subjects to add if you don't mind. OK, perfect. Yeah. No, of course, that do whatever you need to do. Talk to Damian, you know, obviously figure out what you what you want to. But I mean, if we're going to do a TLDR, something like that, where we are listing out smaller ideas, I like we can include more. If that's the case, I don't want to overload it, obviously, and make it too, too big. But yeah, depending on how we get to that list, maybe maybe it's worth putting that in there. Maybe that's in the development acceleration. Maybe that's something else that we can highlight. I mean, that's a totally different subject that we don't even have here that we can talk about, you know, we find that. Yeah. But so so the the Docker ones that you were discussing, Bruno, I think are a good fit under the platform topic up above. They're they're clearly clearly platform modernization and platform platform enhancements, right? Docker images, new platform support and. Oh, actually, let's I get regularly reminded instead of the word Docker, let's use the word container. Yeah. Because Docker is a vendor of a container solution, but the things are containers. That's awesome. Thank you very much, Bruno. Yeah, that sounds great. I like, yeah, and I like the different perspectives and thought processes, because even if want to like mark or I don't think it's important, it might be very important to the people that are not, you know, able to say as much or aren't taking a minute to share that with us. So I think that's always very, very valuable to discuss and figure out and then, you know, at the very least find out, discuss, decide whether or not it is. So, yeah, thank you very much. You're welcome. We had we had some website improvements, like and that was thanks to a lot of the work in the summer of code projects. We had the secret after contribution contributions constantly, which were really great in helping us with revamping some of the screenshots and a lot of the inclusive naming stuff. They were also able to provide new examples and all sorts of testing, which was great. So a lot of that stuff's going to be there. And we have the blog post for that, so we can always link to that directly. As far as some of the website stuff goes, Mark, would would stuff like the web components fall under this too? I know Gavin was working a lot on not deployed yet. And I'm not sure we're going to get them deployed by by end of year. So OK, so they could be. But but actually, I was thinking we might successfully eliminate a well, no, not really sorry. No, I take it back. I was going to say we could can combine website improvements under Google Summer of Code, but that only works for one of the three items that are there. So that's a bad choice, right? And then we have the plug in health scoring, which is a totally different kind of idea from that, I guess. So right there, there were three other summer of code projects. So so putting website improvements there, we might find ways to scatter those improvements elsewhere so we can eliminate the website improvements theme, but let's keep thinking. OK, because yeah, that sounds good. Because I feel like these could also fit into like user experience improvements or something along those lines, because that does affect how people are using the Jenkins site itself. But yeah. And then Alex Brandes did a lot of work just kind of getting the crowd in peace going. I spent a lot of time at Docs Office hours earlier this year going through it, talking about it, just showing what is possible with it, which is really great. So I want to make sure that that is highlighted really a lot, obviously. And yeah. We can table that for right now. This document is always available. And so is Gitter, Matrix, any other chat channels that you want to throw an idea in please like message me or notice me, whatever it is, by all means so that we can add that in. And then we are a time couple of minutes. So just to kind of finish things up, again, we have the LTS 2.375.2 coming that will actually be released in January. But we have a lot of the pre-work done right now. So the change login upgrade guide, the release candidate, backporting, all of those things have been either submitted or merged already. So any reviews, any ideas on that much appreciated. And then there's been discussion about the pipeline docker plug-in. What that means for Jenkins, what that means for the documentation. It's a lot far more far reaching than initially thought. So there's going to be a lot of discussion that won't be something that gets resolved until January at the very earliest. But it is something that we are very, very mindful of and working on because this can affect a lot of people in different ways. And then finally, just a quick note that there was a pull request that Mark had made suggesting that board member rules can be modified a little bit right now. But there is five board members, one being Conasi Gay and then the rest are elected. If the if there are it's more than 50 percent of representation by a company. It's not allowed. So just discussing ways to work around that. Talk about ways to engage people and get them on the government as well. But something we can talk about later, no worries there. Anything else anyone wanted to discuss? Check in mention, if not, I think we're OK, we'll end things here. And the recording will be available in about 24 to 48 hours. And thank you so very much, as always, for joining us here. We will have a section next week. So we'll check in again before going on going on at my for a little bit, so.


Hey everybody, Dr. O here, I think we've covered everything we need to about epithelial tissue. Now we're going to move into connective tissue.  Well they are all classified as connective tissues. So what makes something a connective tissue? Number one, it has to have specialized cells. Number two, there's going to be what's called a ground substance. So it's a liquid ground substance, obviously like blood's going to have more of a liquid ground substance than bone but they both do have some and they're going to have some sort of protein fibers. So those are the three things that make something a connective tissue. Specialized cells, ground substance, and then some protein fibers. Most common cell type you're going to see in connective tissue is the fibroblast. So fibroblast, they make connective tissues like collagen, they're responsible for scar tissue, these kind of things as well. Your connective tissues do have this extracellular matrix so they make all the stuff that fills in between the cells in your body and then there are three major types. That's what I really want to focus on here. So the three major types of connective tissue are going to be what is called connective tissue proper, supportive connective tissue, and fluid connective tissue. So your connective tissue proper is going to be broken down and we'll do videos in each of these three categories. It's going to be broken down to loose and dense connective tissue.  Dense, we have dense regular and dense irregular so I'll do a separate video on those as well. Your supportive connective tissues, we have cartilage and bone. I won't do a video on this chapter about bone, excuse me, real itchy today. I won't do a video about bone right now because bone tissue has its own chapter coming up. But I do want to talk about bone versus cartilage, key difference because bone used to be cartilage. We'll cover that later. But bone is vascular, meaning it has blood supply and cartilage is avascular. So in this chapter, I'll cover those three types of cartilage, hyaline, fibrocartilage, and elastic cartilage. And then we have our fluid connective tissues, blood and lymph. I also won't cover that yet in this chapter because they each will have their own videos when we get to blood and the lymphatic system in A and P2. All right. So those are, that's what makes something in connective tissue and those are the examples that you will be expected to know throughout the course of this year. I hope this helps. Have a wonderful day. Be blessed.


Is the future of affordable education thriving in South Africa? How are we going to educate the world, including the poorest of the four? I'm Brett Ellis with UpArts Report. I'm in Sakane, South Africa, at the African School for Excellence to see how they redesign education from the ground up. About 20 percent of South Africa's government budget is focused on education. It's a priority. But the reality is that doesn't mean equality and opportunity. Most Black South Africans go to these government schools. But despite them going to these schools, their literacy and numeracy performance is far below the averages that you see in other African countries that have the same economic status as South Africa. Because of the history of how resources were distributed, even the level or the quality of teaching that's happening in the school is still very divided with obviously the Black majority getting the lower end of that. Can I join your group? We are identifying a problem around opportunity. Okay. And then we use these opportunities. And your problem was opportunities, right? Lack of opportunities. The reason why we founded AC is that we believe every brain is like muscles. And now we needed to figure out how do we create a system within which your brain can come and develop so that you're able to critically solve problems without having to pay money you don't have. The average annual cost of education in the U.S. is $11,841 per student. ASC only costs $800. So the model in a nutshell, each class is split into three different subclasses. First we have a team class which focuses on peer work. I love peer learning. I think that it's the only perspective to learn as a teenager from another teenager. It then moves to an independent portion where the kids get a chance to work independently. They will then move to a class called Dialog. Hi. In my previous school, the teacher doesn't care. But here at AC, we're given a chance to think broadly about things, not to just focus on what's given to us, but to go deeper into that. For each one of our classrooms, we have one trained or qualified teacher working with two learning facilitators. So what that means from a financial perspective is that we're only ever paying a teacher salary per se to one person. The education model that we have at ASC is quality, but also scalable. And that's been intentional since our founding. We wanted to prove that this model could work in a resource constrained environment. And there are resource constrained environments around the world. If it can work in Sakane, it can work in other places where there are a shortage of trained teachers, where there are infrastructure challenges, and where there are resource constraints due to capital. For more information, visit ase.org.za or check out uprocks.com.


Hi friends, I am Pooja and today we will work out the following question. Three consecutive integers are such that when they are taken in increasing order and multiplied by 2, 3 and 4 respectively, they add up to 74. Find these numbers. Let us begin with the solution now. Now let the three consecutive integers be x plus 1 and x plus 2. Now in the question we are given that these three integers are multiplied by 2, 3 and 4 respectively. So the integers when multiplied by 2, 3 and 4 respectively will give. So now when x is multiplied by 2, we get into 2 which is equal to 2x. When x plus 1 is multiplied by 3, we get x plus 1 into 3 which is equal to 3x plus 3 because 3 multiplied by x gives 3x plus 3 multiplied by 1 gives 3 and when x plus 2 is multiplied by 4, we get x plus 2 into 4 is equal to 4x plus 8 because 4 multiplied by x gives 4x plus 4 multiplied by 2 gives 8. So we get 4x plus 8. Now in the question we have that when these three integers are multiplied by 2, 3 and 4 respectively, they add up to 74. So according to the given condition, we have 2x plus 3x plus 3 plus 4x plus 8 is equal to 74. This implies now 2x plus 3x is equal to 5x and 5x plus 4x is equal to 9x. So we have 9x plus 3 plus 8 is equal to 11. So we have 11 is equal to 74. This implies 9x is equal to 74 minus 11 taking 11 to the right hand side of equal to sign, we get 9x is equal to 74 minus 11. This further implies 9x is equal to now 74 minus 11 is equal to 63. So we get 9x is equal to 63. Now dividing both the sides by 9 we get 9x upon 9 is equal to 63 upon 9. This further implies now cancelling out common factor 9. Here we get 1 enumerator and here cancelling out common factor 9 we get 7 enumerator. So we get x is equal to 7 because 1 into x is equal to x and this is equal to 7. So we have got the value of x as 7 thus we have the 3 consecutive integers are 7 and 9 because we have assumed the 3 consecutive integers to be x, x plus 1 and x plus 2 and we have got the value of x as 7. So the first integer becomes 7 then x plus 1 is equal to 7 plus 1 which is equal to 8. So the second integer is 8 and the third integer is 7 plus 2 which is equal to 9. Thus we write our answer as the 3 consecutive integers are 7, 8 and 9. Hope you have understood the solution. Bye and take care.


Rebecca from Art Resin here to talk to you today about epoxy resins and how art resin epoxy resin is different from all the rest. So art resin epoxy resin as it sounds it's made for art purposes it's made for artists to use at home. Years ago David and I were using some of the other products that were on the market and we found out the hard way that not all epoxy resins are created equal. Most epoxy resins will yellow very quickly and most epoxy resins are terrible for your health. So art resin is our proprietary formula and the two things that we prioritized in making this formula were that it stayed clear for the long term on top of the artwork keeping it beautiful of course and to protect our health. Because artists like to work in their studio and at home and making sure that it had no VO season fumes is a really important thing and that is what art resin today has to offer. So let's talk about these non-yellowing properties. First of all you should know that UV light damage has terrible effects on a proxy resin it will turn it yellow in no time and to mitigate that you need a light stabilizer a UV light stabilizer and it does other things such as protecting against gloss loss and it protects against delimitation when it comes to the non-yellowing it will only delay it for a period of time unless you have a hindered amine light stabilizer which is what art resin offers. So those two things pair together in the formula give great insurance against UV light damage. Now one thing to mention for all of you artists out there who like to make cells with silicone oil is that silicone oil will actually yellow your resin over time it's oil and even though it makes beautiful effects in the short term it can cause yellowing in the long term just something to be aware of. Our second priority is the health concerns. So epoxy resins are expensive to manufacture in that the raw materials are not cheap. To mitigate this a lot of manufacturers will put filler into the product and filler does not bond in the chemical reaction. So whereas the raw materials all line up creating strong bonds that are locked into that formula once it's cured the filler does not bond and so there's nowhere for it to go and it comes up into the air in the form of fumes volatile organic compounds nasty stuff that will wreak havoc with your health and your respiratory system you don't want that and so art resin has no filler no solvents everything bonds perfectly together so there are no fumes there are no VOCs and basically your health is totally protected whereas other products require a respirator art resin does not and we've had this evaluated by an ASTM board certified toxicologist making sure that this is the case and no respirator needed. So even though art resin contains no solvents some artists actually elect to put solvent into the mixture in the form of alcohol ink why because it's beautiful and it's not such an issue when you're looking at petri dish art or when you're doing small jewelry in silicone molds and especially it's no issue if you're doing alcohol ink on you paper and coating it with art resin afterward no issue there whatsoever it's more of an issue when people are using a large amount of alcohol ink in a big batch of art resin stirring that all up then you're really compromising that non toxicity that we're so proud of and of course you would have flammability issues around that as well because alcohol is flammable so just something to be aware of and something to be careful about. So I hope that all this detailed information will give you the confidence and the comfort to know that when you're using art resin it will protect your artwork for the long term and it'll protect your health and that's it so from one artist to another be creative and have fun