 All the information on the slide. So our community is in decline. This is the weekly project usage of Drupal for just the past five years, and it has leveled off. And Drupal 8 is sort of a blip on what has been adopted so far. And this has been recognized, and that's why there is one of the major initiatives right now is to make installing it easily to stop that barrier to entry, and we'll revisit that approach there. But so Drupal is a bit in decline. I mean, it's not the end of the world. After all, it's not like the rest of the world is suffering from division disaster capitalism and impending doom. Oh, all right. All right, well, what if this sort of unique and cool community thing that we do still have going is as good a shot as we've got? What if we are the hero we need to see? Last image was a burning planet, and this image is a Drupal conned superhero. So on average as a community, we've got plus six cooperation, maybe a technical challenge bonus for building an inclusive community, maybe a negative one. We'll revisit that, too. Making software that connects people and resources. We've got a slight edge there. But before we get too far ahead of ourselves, let's see what we are up against. This is from the XKCD comic. It shows a line moving slightly from the left to the right. This is what rapid change on a geological time scale looks like. Degree Celsius or a couple degrees Fahrenheit changing over 1,000 years. In today's anthropogenic era of human-caused global warming, we've added more than a degree Celsius with more than two degrees Fahrenheit in less than 100 years, with most of that coming the last 25. And the graph shows that line shooting way rapidly off from the average to increasingly hot rate that you don't see in any of the geological errors. And this is a couple years old. You can increase that solid black line just a little on the current path, the worst path, because we've done nothing to stop it. We're causing warming to define a geological error in our lifetimes. But you can imagine a similar line for the ozone layer. And public action has pushed us closer to the best-case scenario. Acid rain, maybe more like the optimistic scenario, but there are major, major things that we have succeeded. We're still up against the basic problem in political science. There's the classic problem of a concentrated benefit and distributed cost. This is oil workers cleaning up. People in white suits cleaning up an oil spill. And it's from an article that makes the point that cleaning up an oil spill is pretty theatrical. There's not much you can do without a dedication of hundreds of times the resource that actually is. But the point is that a relatively few people are benefiting a great deal from various forms of environmental destruction. And the cost is distributed to everyone. And as long as you have a small group with a high stakes and a much larger group with a cumulative of the higher stakes, but individually lower stakes, typically in political events, the group with the small group with the concentrated higher stakes gets what they want. And everyone all suffers. But the solution is communication, coordination, tools, and networks capable of giving the distributed many the same degree of power to discuss, decide, and direct organizational power as the concentrated few. That extreme wealth correlates with interests that run against humanity's interests as a whole, adds just an extra challenge to that. This is a chart showing US wealth distributions, the perception people have of it. What they think it is is that the poorest 20% of people have like 5% of the wealth. And then next 20 have 10 or something like that. And then the middle 20 maybe gets 20 for themselves. And what 92% think should be the ideal going well into even if all of the richest think that they should have as much wealth as possible, there's still by 92% choosing an ideal that is far more equal than they think it is. Even among the top 20% wealthiest people, a majority of them are calling or think that wealth should be more equal than it is. But that's what people think the wealth distribution. What the wealth distribution actually is, is the top 20% have 80%. And the bottom 40% is you can't even have separate lines anymore. It's just a tiny, tiny sliver at the bottom. And if you take the full, the majority of the population, 60% of the population, it's down there just like 10% of the chart. So most of the wealth extracted from say burning fossil fuels where we as a society have been burning as if it's a magic consequence free source of energy, most of that wealth has probably been wasted. A lot was made. Certainly there's a lot of wealth out there. But if I burned down a store while stealing $100 from a cash register, I destroyed a lot more wealth than I've taken. So it's just because something has been done doesn't mean wealth was necessarily made out of it. But still the baseline of justice and even that narrow sense is I give that $100 back in restitution. But as Utah Phillips says, the earth is not dying. It's being killed. And those who are killing it have names and addresses. So it's just that there is resources out there to solve the problems we have. And it's good to know where they are. But now that you know how extreme wealth inequality is, do you have the power to do anything about it? Not in itself. Knowledge is not power. Marion Kaba, organizer on Prison Culture on Twitter, highly knowledgeable on the subject of organizing and has been working on ending violence and dismantling the prison industrial complex has made that point many times that organization is power, which brings me to Drupal as a service. I am triply excited about building Drupal as a service, Drupal businesses that provide software as a service, especially companies as a platform, especially building these companies as platform cooperatives as companies that are owned by the people they serve essentially rather than being owned by a narrow group of investors that these platform businesses that we're all using every day be formed as cooperatives. And the triple benefit is that Drupal and related technology that work on does give us power to coordinate. Building it is an exercise in coordination itself. And as cooperatives, we'll need to be building more tech to work on mass coordination. So Drupal as a service is a subset of LibreSas. It's free software as a service, Libre Software as a service. LibreSas is a term I coined, but someone else coined it independently. So it's like totally a movement now. Every cloud service, every software as a service, all the big platforms you can think of are almost invariably built on a mostly free software stack. The operating system, the server, the programming languages, the databases, the libraries, all of it. Even if they're open sourcing it themselves, most of, you know, name it big tech company, the majority of their software is running on a free software stack. And they're making piles of money on a relatively thin slice of proprietary code that's pulling it all together. And the question is, why can't free Libre open source software move into that space? And the good news is it is. Drupal is already doing it. Centaro, which is commerce guys rebranding themselves as they move to offering software as a service, launched officially yesterday the rebrand. And they're taking especially tricky bits of commerce that you might not want running on your own site into a service they run. And Ryan Sramma encapsulated Libre SAS beautifully when he said that in addition to the no lock-in benefit of doing fully GPL software, the promise of greater collaboration is why they are especially excited to be doing it entirely as Libre SAS instead of doing a proprietary software as a service, which is a pretty common model of having some pieces open source and then trying to keep some pieces held back. But the benefits of collaborating with the people they serve and other companies and then the appeal to companies that would be purchasing the service of not being locked in are competitive advantages. Also in Drupal World, Round Earth by My Drop Wizard is a combination of Drupal and CVCRM to provide both the content relationship management system and the content management system. And that's in, I think, their second beta right now or second cohort. OpenSocial by Golgorilla was a piece of software that they adopted from the Drupal 7 version that they'd done for a very large activist not-for-profit group. And as they say, it's software to empower people to effectively collaborate and organize, replacing traditional intranets, fueling bottom up organizational innovation. So taking something they did for one client and trying to make a service out of it. And it's been an effort for a while. Rumify is a booking engine that partly provides the software as a service. ProboCI is not Drupal per se, but it's from a long-term Drupal company, ZivTech. Not-pictured.farmier.com is the online-hosted accompaniment for the Farmier distribution for farmers. But it's Farmier with an I in it. It's built on Drupal 7, and they just released their 1.0. And then Open Church site, or Open Church distribution in the website is openchurchsite.com has recently launched a Drupal version. But overall, on the web, as Therese Boythard had said way back in 2015, Wald Gardens, so talking about Facebook and Google and LinkedIn, anything that tries to keep you in their sphere, the Wald Gardens are winning because they have a superior user experience fueled by data and technical capabilities not easily available to their competitors, including the open web. And it is despite the fact that on most of these networks, we are the network. The people on them are creating the value. But open platforms have disadvantages to close largely in making upfront investments with one entity controlling a platform. They can capture that value more easily, just get a ton of venture capital and lose money for a long time before they turn a profit. That's not as easy when you don't have that guarantee of being able to basically have monopoly rates once you capture the network effect if you are truly being open. But open platforms can have advantages over closed. The image here is IndieWebCamp, IndieWebCamp.org, or IndieWeb.org is a collection of a movement. And this is just one small piece of a much larger movement for there to be an open web. They take an approach of simple protocols to try to start to allow the sort of interaction you get in closed proprietary environments, like Facebook, like Twitter, on distributed sites. And Drupal User Swento has made a fantastic IndieWeb module for Drupal 8. And just in the broader open web versus closed web conflict, there is the longer view is that government regulators are increasingly going to be exercising oversight over the data collection and some of the anti-competitive business models of the closed, but very large silos. And Dries' latest blog post writes about that. Shoshana Zubikoff has a whole book out on surveillance capitalism and the new form there. And she likens it to past movements to reign in out of control, basically capitalism. And successfully, when people identified themselves as workers, as laborers, there wasn't generally revolution, but there was enough of an understanding of a common interest that got representation, got governments to take their power. I mean, really increased the realm of what a citizenship was. And now she thinks that there will be a consciousness of people as citizens, as citizens online. That will also have an effect, a common consciousness. And certainly, people are pushing back more against the data collection, all of that. So there's this opening for potentially for cooperative platforms. So going back to Drupal and the health and growth of the community, this slide has been used forever. And it's a rip off of a, it was not originally Drupal. It was like a bunch of different games. But it's a learning curve. And Drupal is the learning curve that goes up straight up in a cliff and veers out and people are hanging off and falling. But the important thing is that at the time, despite the way this joke graph is drawn, the getting started with Drupal step was not actually so much higher than other things out there. And now we are in a place where the getting started step for any software that you have to install is vastly higher than going to Squarespace or wordpress.com. And this is where having entry level accessible software as a service options, I think, is necessary for the help of the Drupal community, because it is how people can get in and start contributing. Personal story, I first tried Drupal in 2004, or 2005 maybe. Whenever it was the better known branding of Drupal was actually a thing called Civic Space, which ironically did try later to do software as a service. Did not work out, but it was a different time. But they bundled Civic CRM and Drupal. And I tried to install that locally, and it needed so much RAM that it just crashed my thing. I was like, well, if I can't visit the... And this was also back when all of the modules loaded when you went to the admin modules page rather than just loading the info file. And so it crashed my whole system, crashed the whole website. And I'm like, well, if it can't handle one visitor, how is this thing ever going to work on a website? And so I was stayed away from Drupal for another year because I happened to come to it first through the Civic Space, Civic CRM and Drupal combined version. That was just too heavy to get started with. And Drupal 8 is sort of like that because to do it right, you use Composer, and Composer is probably going to use up all of your RAM now. So having online services that give you the site builder experience, which is how many people who even later got into development started is critical to both giving the power of Drupal to everyone who can benefit from it, but also bringing in the new generation and people who are not currently in the community. And it's important to have people who aren't already in your community who represent broader representation, especially if we are going to try to seriously do our part as a community to take on some of the things that are out there, like global warming, like surveillance capitalism, the big things, because for surveillance, this has been a state for in the United States, especially black people and in many places, just anyone who's more marginalized who is basically targeted by the government and other powers as a threat to the status quo. So basically anyone who is not doing as well as other people is a threat to the status quo if because there's a danger that they'll fight for justice. And so the kind of mass surveillance that we are facing as a society has already been the case for communities in our society. And very similar to also people who get government benefits that are targeted to the poor versus government benefits targeted at the rich have all kinds of intrusive surveillance, whereas you just get handed your tax deduction or tax credit for having a fake farm on your golf course, for example. And I do wanna leave time for questions. So I think I'm coming up on five minutes left. So I will just move to the end, but just in closing the one project that we're, that I'm involved in is trying to make a Drupal as a service that does give that entry level for smaller groups, it's Drutopia, and trying to take on some of the bigger questions of how to direct resources to those who need it, those who know some of the, problems that we're dealing with, feel them more acutely, and we should be taking leadership in how to organize. So I will be putting up all resources and links up here. They're not up there yet. And also please go to the event schedule and go to this to rate the session. That's too long a URL, sorry, to be easy. I'll link it from the short URL also. So thank you. So I've read, I think I agree with the idea that, so multi-tenant SAS products versus single-tenant SAS products, right? The idea that you can build a multi-site Drupal instance where the configuration between customers is the wall that hides the data between customers versus a single-tenant where you're building a distribution and that distribution is what's turned on per client. So they basically completely handle and have their own full instance of Drupal, which I think I lean towards. Curious to have any practical resources for building a distribution where the thing I'm chewing on the thing, the problem that I have is how do we handle configuration management custom to that instance? Okay, this is great, okay. So custom to that instance, configuration management, right? So configure split helps us with that significantly, right? We've got configuration for development, configuration that we're pushing toward that central project, right, the distribution. But what about configuration on a per customer basis? Any ideas? Yeah, you've hit the nail on the head and I mean that's been sort of the essential preoccupation of Tritopia from the beginning. I mean the good news is that Drupal as a whole is sort of recognizing that need, that we've solved the configuration from a single site, going from dev to test to prod, that's fantastic. But then when you want to be able to push out updates from your central, yeah, from your distribution and still allow customizations, it gets a little tricky. So right now we're using config distro, which is building on config split I think and a million other things. But it looks like something like config overlay, which will save only the changes for a specific site is gonna be a lot cleaner, because then you basically commit like just what you're gonna override on that individual site with that. So it's essentially not a solved problem, but it is a solvable problem for sure and it is one that a lot of work is being done and that is the configuration 2.0 initiative isn't necessarily chartered to solve that, but that specific problem, but it's highly on the radar and the configuration 2.0 initiative is supposed to make it easier to solve this problem and I do trust that Willis, but yeah, that is the sort of key technical issue and then the fact that it's harder to share the PHP code base, the idea is like, yeah, the code is locked down. It's like you can choose from these modules, but you can't add other things when you're doing Drupal as a service in the multi-tenant model, like you said, or the single-tenant model on many things. But yeah, right now you can't even share the PHP in an opcode cache, but that's sort of a scale issue, like okay, we'll figure that out when it grows and then the other thing is building Drupal in a more headless fashion. I'm really excited by the Hacks project, which replaces a lot of the front end and would sort of make it possible where you just power down the Drupal site when you're not using it or even using something like Tome when you're dealing with more simple sites. So for our end of looking for like being able to serve relatively low resource groups, we're looking at all those things. For a lot of services, that's not gonna be important because the value that the Drupal site is providing is enough to keep it running all the time with those much resources it needs, but then the key thing you brought up of the configuration is that not solve, but there's many initiatives. I mean, there's the core initiative that's improving all the options and then there's already a bunch of things that are sort of offering that option. Yeah, thank you. I think we're at time, but if any other questions, I will take them. Thank you.