 Good morning Drupalcon. Hey, how's everybody doing out there? It's wonderful to see all of you here. It's a beautiful day in Pittsburgh, and we are so thrilled to have you. I am privileged to be the first person on this stage today to welcome you all here. My name is Tim Lennon. You might know me as Hestanet on Drupal.org. I'm the CTO of the Drupal Association, and we are the non-profit foundation that supports Drupal and puts on Drupalcon. And we're thrilled to have you. Thank you so much. In a spirit of gratitude, I do want to say some thank yous. So first, a thank you to the Drupal Association staff and the more than a hundred volunteers who are all here or getting sessions ready or mentoring or speaking. Thank you, everyone, for everything you're doing to make Drupalcon happen. I want to thank our sponsors as well. Their financial support makes all of this possible. And these sponsors are not just vendors in some expo hall. These are people who help to build Drupal. Some of the greatest experts in the community, people who've been here for a dozen years or more. And I encourage you to go to their sessions, talk to people, learn and network with all of them. I also want to thank the supporting partners of the Drupal Association. You may not know the DA as a non-profit organization runs Drupal.org as the infrastructure for the project. We provide security information, updates, localization hosting, all of these things and all the tools you're going to use to contribute on Wednesday and to collaborate with each other throughout the con. So thank you to all of the supporting partners who've helped fund this work and keep the Drupal Association going. We really appreciate that support. Finally, I want to thank you. All of you as the attendees here in Pittsburgh, everyone who's come together, you are the heart and soul of this community. And Drupalcon is about people. It's about the hallway track. It's about meeting each other, making new connections and new friends within the Drupal community. And I encourage you to do that throughout the event. So this week, we do need your cooperation here in Pittsburgh is the hometown of a beloved children's educator in the United States that some of you from the rest of the world may not know, Mr. Rodgers. And Mr. Rodgers' message was that everyone, each and every one of us, especially the children, is special. Each person is unique and that we can all be more civil, more loving neighbors to each to one another. And in that spirit, we ask that you please cooperate with our COVID safety policy and wear your mask indoors throughout the event to help protect and support your neighbor who may be more vulnerable than you and who needs your support. We also remind you of our Drupalcon Code of Conduct. If you're ever concerned about something that might be happening at the event, you can contact the conduct at association.drupal.org email address or find a member of staff or someone at the registration office. And we'll get you support as soon as we can. Finally, please respect the photo policy. If you see someone wearing an orange lanyard, that is because they would like not to be photographed. So, you know, if you can find another angle, get the photographs you want. We love you sharing all of those, but please respect those who do not want to be photographed. We also want to invite you to some events throughout the conference. So, right after this keynote, we would like you to join us for the group photo. You'll go out the doors to the left, find the big Drupalcon. We'll all gather together to take this photo of the community together. We also want you to join us for the welcoming reception tonight in the expo hall. And lastly, and perhaps most importantly, we'd love for you to join us in contribution. Contribution is what makes Drupal thrive. Drupal is built by people. No one entity, no one person builds Drupal. It's you who builds Drupal. And you can join us throughout the week. You can find mentors. If you've never contributed before, you are probably the most important here. And we want to see you in contribution and help you take that first step. So, a quick sneak peek at what's coming up for the Drupal Association, and there's more that you'll learn about this throughout the week. In particular, there will be a public board meeting here tomorrow, led by our CEO, Tim Doyle, and members of the Drupal Association Board. They'll you learn more about what the Drupal Association is going to be doing over the course of the next several years. A plan to accelerate innovation by empowering makers, market ourselves as a platform of choice, and grow the Drupal Association. We'll also be showing a new open web manifesto, taking a stand for the importance of the open web and the future of the internet. One of the things that we're doing as part of these efforts to present a more modern Drupal, a better Drupal to evaluators is we're going to be overhauling Drupal.org itself. So there's a new look and feel coming. This is just a preview. This is not yet the final thing. It's not live. Don't start refreshing your phones. But Drupal.org is going to be updated with some brand new information for everyone out there evaluating Drupal, looking to choose the best platform on the web for their needs. So look out for more on that information soon. And I want to say thank you to our design partners, Third & Grove, who's one of the supporters of the Drupal Association, and to the volunteers of the Promote Drupal Committee, which has made up a folks like you who said we want to step forward and help build a more modern Drupal.org, a better presentation to everyone who's visiting and invite them into our community. If you'd like to learn more about Drupal.org itself and the tools we use for contribution, you can join the Drupal.org engineering team panel where we'll be talking about that acceleration that'll be here in the ballroom today. You can also learn more about Drupal 7 and the plans for End of Life by attending the security team panel that'll be happening today in room 323. Finally, and last but not least, Drupalcon Leal is coming soon. So save the date. Registration will be live very, very soon. And you should look out for an interesting plushie hiding around the event that you can take a selfie with perhaps and earn a free ticket to travel to Drupal.org. All right, with that, it is my pleasure, my privilege and my honor to invite members of the community working group up to the stage to announce our 2023 Aaron Wynne Born Award winner. I was afraid that I was going to carry it up and show who it was. The community working group, its mission is to foster a friendly and welcoming community for the Drupal community people for the Drupal project and uphold the Drupal Code of Conduct. We have a couple of events that are on the screen, cool. Coming up, we have the community working group's office hours where we're going to talk about anything you want to talk about in the community. We have a Code of Conduct presentation going during the community summit about how we created the new Code of Conduct that was just released. And then we have a community health team where we basically are trying to recruit you to come be part of us and that will be neat. Each year, the Drupal community working group is honored to facilitate the selection of the winner of the Aaron Wynne Born Award. The Aaron Wynne Born Award is named in honor of longtime Drupal contributor Aaron Wynne Born who lost his battle with ALS in early 2015. The community working group with the support of the Drupal Association then established the Aaron Wynne Born Award. The award includes a scholarship and stipend to attend DrupalCon with recognition during a plenary session at the event. Nominations for the award is submitted by community members. Then members of the CWG combined with past winners vote to determine the winner. The award itself is handcrafted each year by a member of the community. This year it was designed and crafted by Russell Eck from Canopy Studios. We had a bunch of really great winners and nominees over the past years and it's our honor to introduce this year's winner. The winner has been a Drupal community member for over 17 years. One of the nominators wrote, what sets this person apart however is their unwavering commitment to kindness and their above and beyond dedication to the Drupal community. Another nominator wrote, their contributions have been immeasurable and character and commitment to the Drupal community make them a shining example of what this award represents. This person is actually the person that granted me commit access to Drupal.org and the voters did not even hold out against them. He's done a lot of work in Drupal. Oh, damn it, I said he. But more well known to a project that I'm sure when I say it, it's going to give the person away. D-Dev. Yep. And so that's been up this year's winner, Randy Fay. Look at how beautiful that is. So great. Thank you so much. Thank you so much. I just, I'm just, I'm so honored, of course. And I know that there are so many of you out there that are more deserving of this, but thank you so much. And it's just, it's just a pleasure. And thank you so much for being such a great community to work with, because that's what makes it so much fun to share and to work, you know, to work with you. You're interested, you're engaged, you, and that's what makes D-Dev become what it is, is your involvement and questions and improvements and features. And then it just, thank you so much. And it's great to be here with you and what a pleasure and what an honor. Thank you, Randy. And congratulations. Let's have one more round of applause for Randy. And now I'd like to welcome Tim Lennon back. This bubble wrap is broken. All right. Thanks, everyone. We won't take too much longer. It is time to get on with the show. So again, it is my privilege to invite onto the stage Dries Bajtar, founder of the Drupal Project, co-founder and CEO of Acquia. Thank you, Dries. Thank you very much. Good morning, Pittsburgh. First of all, Randy, congratulations. It's so wonderful to see you in after all these years. Yeah. Very proud of you. Very happy to have you. And for those that don't know D-Dev, I don't know if we explain it actually, but it's a local development environment. So check it out. If you want to run Drupal on your desktop, on your laptop, you can use D-Dev to do so. Good morning. Welcome to Pittsburgh. It's exciting to be here. I've actually never been to Pittsburgh. It's first time for me. And on my way to Pittsburgh, I looked up a little bit about the history of Pittsburgh. And what I learned is that it was originally, or it's known even today for being sort of an industrial city, you know, creating steel and coal mining, these kinds of things. And I like that because it's a city where things are made, you know, a little bit like Drupal, things are made. And it's also a city that had to evolve itself over the years, because obviously industries have changed. And Pittsburgh has done that. And I like that as well. I like that because it reminded me of Drupal. You know, Drupal has a project. We have a famous quote that is, the drop is always moving. You may have heard about that. And we have values and principles. And principle seven is all about that. Principle seven is about how we can sit still, how we have to keep innovating. And so I really like that. And because of those things, I decided to make the topic of my keynote innovation. So we're going to talk about innovation today. I think that's really important, because if you stop innovating, as you probably know, you tend to lose. And that is not an option for us. It's not an option for us, because the mission that we're on, the mission that we're on, what we do is just too important. We have to keep innovating. We have to make Drupal super successful, if only because our mission is so great. And so the topic for today's innovation, I'm going to cover that in four different segments. License to innovate, jumping S-curves, and letting a thousand flowers bloom. And then I think the much awaited Pittsburgh, our innovation contest that we've been writing about in the last month or so. So let's start with the license to innovate. So to talk about that, I need to tell you a little bit about the history of the Drupal association. The Drupal association was actually created in 2005. And it was created because we started to organize events. And we would solicit sponsors. And those sponsors in the early days, they would wire their sponsorship dollars to my personal checking account. That's how it used to work. And obviously that's not a great thing to do, because technically that is considered income, and I have to pay income taxes on those sponsorship dollars. And so we decided we needed a better way. We needed a checking account that wasn't subject to personal income tax by me. And so we created the Drupal association as a tax-free or nonprofit checking account. And from there, we started adding other responsibilities to what the Drupal association does. The Drupal association got involved with our infrastructure with Drupal.org. Some of you might remember me talking about the big Drupal server meltdown in 2005, where we had to buy much more infrastructure. The Drupal association also continued to help with events like this event. It's organized by the Drupal association. The Drupal association then got more and more involved with helping to grow and foster the community. For example, by helping to run different working groups. And then more recently, the Drupal association had gotten more involved with innovation. You can think about the automatic updates initiative, project browser initiative. These are all examples of how the Drupal association is starting to help us innovate more on the product site. And I feel that's an exciting change and we want to do more of that. And to talk about that, I would actually like to invite on stage Tim Doyle, our new CEO, as well as Buddy, our chair of the Drupal association. We're going to talk about this for a little bit. Take a seat. Hi. Awesome. Welcome on the stage. Thank you. So we're going to have a quick 10-15 minute conversation about this. Maybe I'll start with Tim. Tim, you joined us eight months ago. This is your first Drupalcon? Well, this is my first official Drupalcon. I snuck into Drupalcon Prague because we were still in negotiations. But the board felt it was important for me to understand what Drupalcon is about. So I snuck in there. We're sunglasses, a hat, and trench coats of no one knew who I was. But it was a very valuable experience to get a better understanding of the culture of Drupalcon and of the Drupal community. So this is not your official first. It's your official first Drupalcon when you've been undercover. Tell us a little bit about yourself because most people probably have never kind of met you or don't know a lot about you. So tell us a little bit about yourself. Sure. I'm mostly in government and not for profit in the community development, housing, and finance space. In 2006, I was fortunate enough to join a public sector startup that was created by state agencies here in the U.S. just ahead of the Great Recession. State agencies saw storm clouds on the horizon economically because they saw the complaints coming in from consumers. And so from kind of a grassroots initiative, they got together and said, we need to build a system that allows states to work together collaboratively on supervision but maintain their independence. So I was brought over to help build that system. And over the course of 14 years, 15 years, I played different roles there. Product owner, product manager, marketer, salesman to try to sell states, etc. So that was probably the most meaningful experience. And really where I got my kind of deepened my IT background and understanding what it means to launch a product, to develop a product, to rejuvenate a product, etc. And you helped that grow to roughly what size? Yeah, we did a great job. I was a second employee in 2006. We launched in 2008. We went from seven states in 2008 to 50 states in the District of Columbia using it by 2011. The staff grew from two to on that project about 50 or 60, and the whole organization grew to 170. So it was, we just did a tremendous job in fulfilling what the states wanted us to do. I'm very proud of that. Awesome. And tell us a little bit about yourself that's maybe not on your LinkedIn profile, is that to speak? Not on my LinkedIn. I'll try to keep this PG-13. No, one thing that might be on my LinkedIn, but in my 20s, I took a detour off of my career path and I accepted a job. I left DC and accepted a job in Western Maryland working in the woods at an alternative school for juvenile delinquents. It was an alternative to prison. And these young men could decide to go to prison or they could decide to spend 18 months at the school, living outdoors in a campsite, cooking over fire, chopping wood in the winter to stay warm. And the goal was to form a community that would, with adults and these young men, to help them reform their lives and change the trajectory of their lives and take them out. Really focus on group therapy and family dynamics and then bring them back so they could leave more productive lives. If anyone has kids understands, it was the most challenging job in my life. It was transformative. When you deal in this arena or if your parent, as I said, you understand that you face your own strengths, your limits, your weaknesses, your doubts are just right in front of you. And it would not be where I am today without that kind of detour on my career. Well, in special, I don't think I knew that actually, so thanks for sharing. Good. Let's go back to Drupal. So you've been on the job for about eight months now. Any kind of observations or things you've learned so far? Well, yeah, it's a little bit like drinking from a fire hose. There's a lot to learn. Of course, I was aware of open source. I used Drupal as she had my own job, but I was not of the open source community. And so I really spent the first six months trying to learn and listen. I really believe deeply that in order for me to serve the Drupal Association, to serve the board effectively, to serve the community, I need to understand. So I've met with half the CEOs of our certified Drupal partner program and talked on a variety of issues. But there are a lot of common themes that came out too. I need to re-energize Drupal, bring back some excitement, especially getting young people wrap up our efforts to get young people to be joining into Drupal, becoming part of the community, first time contributors, etc. Also need to tell the Drupal story. I heard, you know, folks talk about Drupal as an amazing product. Some people say, oh, maybe, you know, there may be storm clouds ahead for it. But a lot of the CEOs told me, no, there's so much there. We're not effectively telling the story. And we need to effectively tell the story to end users. I imagine folks in this room, you're here because you're already believers. How do we reach a non-believers? And part of that is, I think also, identifying what is the market segment that we're going after in the future. And I know the Drupal 7 conversation later today, I believe, will be part of that conversation too. About what is, you know, identifying the market segment and then aggressively going after that. I also heard, I talked to a lot of community members. The community is incredibly committed, very impressed by that, incredibly creative and incredibly opinionated. The joke in that, maybe. The joke in DC, you know, I've dealt with a lot of lawyers in my life. And the joke is you get two lawyers together, you have three opinions. I think you could get two Drupalists together and have three opinions. But I think that contest of creativity is fantastic. That's where the big ideas come from. And I think that's a good thing to have that contest. Awesome. So you probably, you know, picked this up. But, you know, Tim has this interesting background with not deep nonprofit experience, but also growth and innovation experience, which we thought was very interesting. But maybe, like, obviously, you're the chair of the board. You were involved with the CEO search. You're part of the search committee, as we call it, that, you know, looked for our next CEO or ED. But take us back a little bit because obviously, as a board, we had, you know, off-sites and we brainstormed about what do we want to do and what do we want to look for. So maybe give us a little bit more of that context and background about how we actually ended up with Tim, so to speak. True. Like, it was an interesting time, probably in 2019, I think it was. And in 2019, we said, like, oh, wow, we are like a Drupal Association. It's financially stable. We have a lot of supporting partners. You know, what is next? In 2019, right? And we decided to meet in March 2020 in Atlanta. So the board came together and I think it was on the 5th of March or something. And we all traveled in and we were really excited and we started on the first day with, like, all these, like, yellow posters, like, you know, asking questions, you know, where should we do and what should we do. And then, basically, we got a phone call saying, like, hey, there's this thing happening in the world and, like, the schools are closing, so you should just maybe go home. And we changed from completely, like, having this, like, what are we going to do next into, like, survival mode. And we were just, like, okay, how are we going to do next DrupalCon? You know, what are we going to, like, how is it going to affect us because, like, one of our profit that we have from DrupalCon is actually helping us to support the Drupal Association. So that was, of course, two years' process, right? And I think the opportunity came and, of course, the opportunity comes when we need to search for a new person for the job. And then we say, like, okay, so we did it again, but this time it was actually we were able to sit in a room and brainstorm and we talked about the Drupal project has always been run by Dries and the core committers and the community. And the DEA has been the supporting partner for the Drupal project. But now it was a little bit time, like, can we do something more? Because we hear it from the organizations. The organizations say we want to contribute more to Drupal, but we just don't know how. We don't know, like, what is going to make an impact. How can we actually change the needle? Because there are so many things that we need to do and we need to innovate. And can we at the Drupal Association actually help with that? So we started to look at the things like, you know, innovation, marketing, you know, how can we do those things? And that was the qualities that we were trying to look in the new CEO. And yeah. And of course, maybe, you know, we're going to go into that on the next slide. But the big part is about how are we going to fund all these things? So there's, I think, these three, you know, themes that's going to be innovation, marketing and funding. Yeah. So let's go into that. Yes. So the last, I don't know, eight months or so, we've been working on what we call our strategic plan. And so we've been having meetings, you know, all of us and other board members to kind of figure out what are the areas of focus. And, you know, Badi mentioned innovation, marketing and fundraising to build more capacity. But maybe let's go and obviously there's like a layer of detail below those three high level things. So let's unpack that a little bit and let's give people a little bit more color on what that means. And before we do that, let me say we just have to kind of stay high level. Because tomorrow there is an entire session dedicated to these topics that will be in this room as well. And I'll show you the details on the screen. I think they just came on. So we can just kind of give you a teaser and then tomorrow if you're interested, you can come and learn more about all of these things. There will be a lot more details tomorrow. But yeah, there's three themes, innovation, marketing and fundraising, which is the three year strategic plan. And really with innovation, we're talking about positioning the DA to be 100% focused on supporting makers, creating makers, promoting makers. How do we focus everything we do about leading to more makers? And we just hired Alex Moreno. Alex, can you stand up and wait? Yeah. A first step into trying to add capacity at the DA. Because I came on, the finances are strong, but the board's ambitions are also strong and we need to match our finances with the board's ambitions. Marketing is an initiative around getting to end users. So we'll be rolling out a number of initiatives around how does the DA take a more active role speaking to end users. And maybe for a little detail there, we have a very small team, the Drupal Association. And if we want to do marketing and we want to help with marketing of Drupal and we want to help to bring that out to the companies, like how are we going to talk about Drupal? Then of course we need to build up a lot of capacity on the marketing side as well. So I think that's going to be challenged by how are we going to be able to do that because we are actually running on a very lean budget, right? Yes, it's very solid, stable, but lean. But I would say I'm very impressed with the Drupal board. I would like to thank the board members that are here. We spent the last two days in a retreat and folks flew in from all over the world to help plan this, to just focus on the strategic plan and the things that the Drupal Association needs to do. One thing as a new CEO always does is looks at the board and it's one of the most, if not the most important decision in taking a job. I was very impressed with the Drupal Association board. The last is fundraising and two things I would say to that. One is we're looking at how do we raise revenues that we can then plow back into these marketing efforts and these innovation efforts. We'll look at that in generally two ways. One is what do we do now and how do we build on that? And second is to begin to develop a philanthropic mindset at the Drupal Association. And that's a longer term project so that's not something that you do in six months or 12 months. But the good work in supporting the open web and we are a digital public good now. These are things that philanthropic funders look for in an organization that they can get behind and so we want to find funders that are aligned with our mission. It's something that we've never done at the Drupal Association. We've never applied for a grant and as you probably know there's a lot of grants out there in the world. So one of the things to help us with that is to really focus a little bit more on the open web as being a key part of our purpose. And so one of the other things we've been working on is manifesto. Yes and you'll that's a board open board meeting will be presenting on that. So you'll see the details have a chance to read that. But it really is our statement when people ask what is what is the Drupal Association was a Drupal community about. We're about an open inclusive web and it's the manifesto that really lays down our values in this and that speaks hopefully to the wider world. But certainly we'll speak to funders. Excellent. Well thanks for that. I'm going to ask you to exit the stage. Thank you very much. So if you want to learn more about this join us tomorrow. We can go into a little bit more detail and also expect us to communicate more and more of these things as we finalize them. So next I want to talk about jumping S curves. So let's talk about what that is. What do I mean when I say an S curve and here's a slide that I've shown before. You might remember that from different keynotes and it's basically a classic chart of how innovation evolves right. So you see these S curves typically the beginning of the S curve is so an innovation that starts off slowly in the middle of the S curve. You see like rapid innovation and then it peaks out. And then the next S curve kind of starts at the end of the previous S curve and eventually you have to make the jump to the from one S curve to the next S curve. You know you have to make that leap and that's what I mean when I say you have we have to like jump S curves. And so to stay relevant an organization or an open source project or really anything in the world needs to be able to make these jumps. And there's many many examples of that like one great example that actually learn about from Guy Kawasaki is around refrigeration. I don't know if you notice but back in the day there was this thing called ice harvesting where people would dig ice out of frozen lakes in winter and then distribute that ice to different restaurants and places and homes to basically preserve food. And it was a hard challenge and people would do all kinds of things to store ice and try to make the ass ice last until summer. It's incredible. And eventually there was like an S curve jump innovation which was an ice factory. So now imagine these huge factories producing ice and then still doing the same thing distributing ice around for food preservation. That eventually led to a personal ice factory which became a fridge or a freezer right which we have today. And so it's a classic example of how technology evolves and there's many others and there's a few important things we can learn from all of this. And so if you look at home entertainment as an example you can see on the screen sort of the different S curves but an important lesson is that going from one S curve to the other can actually be a little scary. And often is polarizing. And that sounds a little bad but let me give you two examples. One imagine going from rental stores to shipping DVDs. Well guess what the rental stores went out of business. They're pretty much gone if they're not entirely gone already. And that wasn't an easy transition for them obviously. A more recent example is going from traditional TV where you had advertising to streaming TV. And all of a sudden people could jump over the ads. Guess what that was extremely polarizing for the advertising industry. They weren't very happy with that right but it was still an unstoppable innovation. Another great example of sort of S curves is around communication. And you can see that here how we went from the telegram to the telephone to the cell phone to eventually a smartphone. And what's interesting about this one is that it often can take time for sort of the next S curve to be recognized. These S curves coexist for a while and often we poo poo the new S curve. And an example of that is the telephone there's this famous quote that you can see on stage. It's from Western Union basically saying the telephone is never going to be relevant. And obviously they were very wrong about that. And similarly more recently with the advent of the smartphone we didn't really realize how powerful the smartphone was going to be. That it could be used for much more than phone calls. Now here's another S curve the camera which is a subject that I love. I love photography so I study photography a little bit at least. And you can see there was an evolution from cameras using glass plates. These were big bulky cameras back in the day to a more portable camera which ended up becoming the 35 millimeter analog camera. And then from there we went to digital cameras and ultimately smartphones have overtaken basically cameras. Now it's interesting about this example and you'll find this in all of the examples is that very often the beginning of an S curve starts with a single person or maybe a very small group of people. And in the case of the 35 millimeter camera it was Oscar Barnick and he actually had a health condition where he couldn't drag along these heavy glass plates cameras. And so he set out to build a portable camera and he did something very cool. So at the time cinema or film was very popular and he decided to take a spool of film. You know you've seen these big spools and to flip it on its side to turn 90 degrees and he then decided to build a camera around a single frame of a roll of film. Isn't that cool. Instead of using these big heavy glass plates. And so that led to the first kind of portable camera. Now Barnick was lucky to work at a company called Leica and Leica at the time was building microscopes. And so they had a lab and tools to like build things like microscopes and obviously that helped them build a camera. And Leica also had a great boss and he saw music. He saw music. He saw some potential in his early camera and he helped him basically commercialize his prototype camera that he built for himself. This portable camera and to bring it to the market. And you can see as an example here some old advertising. It says Klein film camera and I'm not German so doing my best. But I can read what it is because I speak Dutch and it means small film camera or small portable camera. Anyway so Leica started promoting this camera and many many years later eventually it led to this 35 millimeter cameras being mainstream. Like every Nikon Canon all these cameras that you know were all coming out of this little innovation by Oscar Barnick. And the reason photos are the size that they are is because the original size of a flipped film strip. So it's very interesting. Anyway the lesson is innovation can start with one the power of one is an important lesson as well. Now Drupal has made several jumps on its own in the early days of Drupal we were kind of at the end of the static weapon at the beginning of the dynamic web I would say. Now PHP and MySQL were just born and they allowed us to build much more dynamic websites and Drupal successfully transitioned over a few S curves you know call it the social web the mobile web web 2.0 whatever you want to call it. We rode that wave up and there was a jump in S curve. Now the next question is what's going to be next for Drupal. Some people say is it Web 3 with crypto is it AI is a JavaScript is it headless but really who knows. We don't really know because as I mentioned these S curves they can be you know the coexistent it's not always clear what the next S curve is going to be. And so the trick you know the thing that we need to do is we need to figure out what that S curve will be and then eventually make the jump. Right now the tricky part is there is no real user manual for how to do this. It's hard to do but from these examples that I gave there's a few lessons a few things that we can learn. In fact we can learn how it's not done and it's not done aimlessly. Right if you think about these examples there is always some kind of vision or purpose. Barnack wanted to build a portable camera that was his vision you know the clear purpose. We also know it's not done by an innovation council. It's not necessarily top down it's very grass roots it's somebody somewhere deciding to build something cool. And again the Leica example is a great example of that a single person trying to solve a problem. We also know it's not pure luck. Usually there is a support environment something that helps an idea flourish something that helps an idea become big. And again in the case of Leica it was the lab that he worked in it was also his boss that wanted to help commercialize his invention. So had a strong advocate or supporter. So we know that is also often the case. And finally we know that it doesn't happen overnight. Because it was actually a long time between Barnack inventing his camera and 35 millimeter film becoming a big thing. These things take time. Alright so these are four kind of ingredients. Purpose and vision. Some sort of individual a supportive environment and then time for the idea to grow and develop. So that's how these S curves happen. Now there's a lot of people that invent things that don't result in an S curve. Maybe it's one invention out of a thousand let's say. So that's where we have this notion of letting a thousand flowers bloom. So like we need to create an environment where people can create things and we can launch lots of different experiments and see which ones will actually take off in a very grass roots way. So I'm going to talk a little bit more about that. So to map it onto what I just said. To let a thousand flowers bloom you need a sun because we want experiments and innovations to grow towards something right. A vision and a purpose. We also need seats people that create ideas. Sorry let me talk a little bit more about purpose. And so the good news is we have purpose and we have a vision in Drupal. We know we're all about the open web. We want to build a web in a way that makes it accessible and inclusive and safe and secure for everyone in the world. That's an important vision or purpose. But we also have a vision and I talked about this at the last Drupal con in Portland where I said Drupal is for ambitious side builders. And I showed this slide actually and maybe I'll recap it real quick. But this is a slide from my presentation and I said what makes Drupal unique is that we appeal to these side builders and that we're going back to our roots on the left of the developers. Developers write code, they use a command line, they're very technical, they love frameworks. And on their right you have content authors and side builders and they like to not write code or they don't know how to write code. They like to use the UI, drag and drop, with the wig, those kinds of things. And they love using SaaS solutions but there's this interesting gap in the middle between developers and content creators which I call the ambitious side builders. It's a people that want to use the UI but if necessary they can also use a little bit of code, they might be able to use the command line. And when I announced this at Drupal con Portland, people really liked it. I got a lot of positive feedback. Now people also ask me like can you talk a little bit more about it because as we think about building things for these people we need to better understand what they are these people and what they like to do. So we workshop this a little bit and we'll have to do more work on this but just to help you understand this a little bit better. The ambitious side builder doesn't always, doesn't typically identify as a developer. They wouldn't call themselves a developer however they're very technically savvy which is a different thing. They can use the command line on a basic level but they might be a little bit nervous about it. Imagine somebody having to execute something on the command line being a little bit nervous and executing it and then feeling a huge sense of empowerment. Like wow, I just did something really cool on the command line. They don't like getting stuck with SaaS solutions and they really wish we had like a layout builder and page builder, these kinds of capabilities as part of Drupal. So more on this later. Then we need individuals, right, the power of one. And that can be anyone and guess what, what's better than the power of one? The power of many and we have many, many people in the Drupal community that can help us innovate and that can start great ideas. And I want to highlight one which is Kevin Quill and I don't know if he's here. I hope he's here. But Kevin single-handedly started to create the open AI chat GPT integration. And I think that's interesting because I remember the early days of the web and I was so excited about the web's potential. And as I tried chat GPT, I felt that same sense of excitement, right? Now there's a lot of questions about AI, legal questions, ethical concerns and we have to figure those out. But I love that Kevin took the initiative to build an integration so we can start learning about it. We can start experimenting with it. So you can see here in the video how he was using chat GPT to automatically generate some text, which I think is pretty interesting. And you can see it's going to do a few other things like suggest a title. So one of the features is you write all of these texts and then you can go ask for some title suggestions. And then you can very quickly incorporate these titles in your articles, press releases, blog posts, you name it. In this case, you have to copy paste it. In the future, there might be even easier ways to do that. But our capability is the ability to summarize text. So next you'll see Kevin highlight some text and then summarize it, which is also quite interesting. I'm excited about this too because some of our competitors recently did press releases. And in the press releases, they said we are going to invest in this. And here we are in Drupal already with a fully functional prototype. Everybody can use this today, by the way, you just have to install the modules. It's pretty cool. So next is sort of that support environment, the soil. And the good news is that Drupal has this. We have an incredible supportive environment and it starts with our license. The open source license gives everybody the four freedoms. Everybody can use Drupal, change Drupal, share these changes. It's that incredible soil for a supportive environment. But we have more. We have all of the tooling that the Drupal association created. The tools that allow us to collaborate with thousands of people. We also have a lot of processes and documentation and governments. We have events like this that all encourage people to contribute. And in fact, we recently hit 50,000 contributed modules. Did you know that? It's pretty cool. All right, but that doesn't mean we're done, right? It means we have a lot of great things going and it has led to a lot of great innovation, but we should always ask ourselves, what else can we do? I want to briefly focus on two things. The first thing is product innovation. I believe that everything starts with Drupal being great. If we don't have a great product, the rest doesn't really matter. You know, Drupal needs to be so compelling that everybody wants to innovate on top of Drupal. That is a key thing. And I'm very excited because Drupal 10.1, our next release, it's just like a week or so away or a few weeks away, will be filled with new features. I think I've never seen a minor release like Drupal 10.1 that has so many new innovations. So let me talk to some of them. Single directory components, great for designers. A streamlined content modeling experience. Also really cool. More flexible block and page management. We added accessibility testing to Core. That will be great. We've also added this new capability so that the Drupal Association specifically can send you messages in Drupal. Maybe there's a new release or a security release. We can notify people about events so we can bring more people into the community. We've made improvements to the content authoring experience. You can see that here. It's kind of using markdown and it automatically recognizes formatting things. And we've also made Drupal faster. We've made improvements to BigPipe. We've made performance improvements to the toolbar. So Drupal 10.1 will be faster as well. And these are just a few things. There's actually many more features that I couldn't fit into this slide or in this keynote, but I hope you will learn about all of them this week. You're at the right place for that. And I'm sure there's many sessions about it. The second thing we should focus on is how can we simplify the innovation process? How can we simplify the contribution process? And just a few weeks ago, all of the core committers we met in person for the first time. And we spent three days together. You can see some of the photos. And we created hundreds of stickies with ideas of how we can simplify things all the way from improvements to our tools, all the way to how we streamline our governance and decision-making processes. But also we talked a lot about culture. For example, one of the things we talked about is how can we make sure that perfect isn't the enemy of good? How can we go faster? Now, I can summarize three days of brainstorming and work in this keynote. I just wanted to let you know that we had that meeting and that we left that meeting pretty excited. And that there's more things to come. All right, so next is time. We need to give sort of these innovations time to grow. But the other thing that we need to do is we need to then find ways to spotlight great innovations, right? If you have all these innovations happening everywhere, how do we tell people what's important and what's not important? Can we help grow certain innovations faster, the ones that have potential? And that's actually where things like the project browser will come in. Originally, right now, the project browser is focused on helping people install and update and find Drupal modules. But in the future, we can do more to spotlight great innovations. Imagine the app store on your phone. It doesn't immediately go to update these things. It will also help you discover great new things that are being launched on the app store. We can do similar things in the future to help everybody in the community learn about great innovation. Recipes is another key component of that. It's not on the slide. But recipes is also a way to bring innovations to end users. Hopefully, you'll learn more about that in the initiative keynotes, which I believe is tomorrow or Wednesday. But yeah, I'm sure there's other presentations about this as well. And so really, to summarize this part, we want to give the Drupal Association a license to help us innovate. You know, maybe philanthropy can lead to a million dollars that we can then use to fund extra capacity. We want to think about how to improve velocity and remove friction from the contribution process so that it becomes more interesting to contribute. Then we want to have tools to identify and nurture all of these great information with things like Project Browser. And then last but not least, we want to continue to make improvements to Drupal the product as well. So I feel pretty good about all of these things. Now, if we do all of these things, we should see a lot of great innovation. In fact, we have a lot of great innovations already. But at some point, we'll also have to make the leap, the jump from one thing to another. And we may not know yet what that is today. But as I explained, based on the example, we're going to have to make some risky decisions or we have to make a decision that might leave certain people behind. Because we can be everything to everyone. So we have to be willing and able to make the jump when we see the next S-curve. So I'm going to leave it at this for now. But next I want to talk about Pitchburg. So Pitchburg is an innovation contest that we launched about a month ago, not that long ago. And we have five judges that I actually would like to invite on stage to come on. You already know me. You already know Badi as well as Tim from the Q&A. But we have two new people on stage. One is Julien from Skilt and then we have Martin from Acquia. Welcome. You might wonder why are these our judges? Well, Badi and Tim and myself, we started this. And then we collected money from different sponsors. And Skilt and Acquia gave sort of the most money. And so they were able to send somebody or, you know, basically nominate one of their employees to be the judge. So that's how we ended up here with the five of us. And in the last month or so we collected 35 submissions. Very cool. And we raised $75,000 from different organization that you can see on the screen. The Drupal Association pitched in money, Acquia, 1x, Skilt, Palantir, Digital, Polygon, Zucha and ImageX. They all contributed to this contest. So thank you to them for helping us with this. So we had 35 videos. And then what we did is each of the judges actually watched each of the 35 videos. And we had a scorecard and we ranked each video based on a number of criteria. Things like how big of a problem does this solve. And also like what would be the impact on Drupal, how many people would benefit from this innovation and stuff like that. And so we ended up each with our own individual ranking of these 35 videos. So we independently ranked them. And then we aggregated our rankings and we ended up with sort of a combined ranking. And then we basically took the top seven of those submissions and those are the ones we're going to show you today. Now, there is another step involved here because we can actually fund all seven of the top seven that we selected. So after we watch the videos together, we're going to ask you, the audience, to help us narrow down the selection to the ones we can actually fund. And I'll explain that in more detail later. I just wanted to give you the highlights so that you pay attention because you're going to have to vote after watching the videos. So we're going to show you the videos. They're shown in random order. They're not ranked by our ranking. So let's do that. Hopefully you're excited about it. All right, let's go. All right. We start with, do you hear me? We start with the first proposal. It's a decoupled layout builder and if the submitter is previous next, Kim and they are known in the community for contribution. And what they are thinking about, and this is a theme that we actually got a lot of submissions around this topic. And why? Well, we want to be enabling ambitious site builders to actually do their things. And what he's going to be talking about is how to rebuild the layout builder with React. And let's just take a look. This is our previous next in Australia. And I'm here to talk to you about an exciting project that will transform Drupal's layout builder. Today I'll walk you through our vision for the couple editing that will shape the future of Drupal. A bit about us first. At previous next, we're no strangers to Drupal contribution. In fact, we're proud to have been amongst the world's most prolific contributors to Drupal over the past decade. With your investment, we're going to improve the layout builder UI experience. We'll do this by rewriting it using React. So where does this need come from? Layout builder was built using Drupal technology that hasn't changed much in 10 years. Page Edits used Drupal's Ajax API and this means a round trip back to the server for UI updates. It's an experience at odds with what users expect from the modern web. Applications that leverage modern JavaScript frameworks perform optimistic updates. They update the UI immediately and then update state on the server in the background. We want layout retrieval and updates to happen in the network editing. We'll achieve this by building a proof of concept for layout editing using React and identifying the pain points. It's a major jump just as the change to block-based editing in WordPress was. We can leverage prior art from the WordPress community with the uniquely Drupal focus on structured data. To do this will mean providing React versions of all our formatters and widgets and a way for developers to create their own. This is a big change but it's something WordPress did to set themselves up and we used it to make this video. We'll need a JavaScript way to declare layouts and blocks and we have a lot of metadata about these components already so we aim to automate some of this. We'll leverage JSON API where possible but also create new JSON endpoints for data that doesn't map to entities. Once we achieve a non-tweague way of rendering widgets, formatters, blocks and layouts we will be able to keep the layout state in the browser, mutated immediately and persist to the back end in the background. We will be able to do this with $20,000 US dollars to develop this initiative concept. To recap, we'll write an experimental decoupled layout builder module, design an API for describing and clearing React versions of layouts, widgets, formatters, block plugins, demonstrate communicating with Drupal to retrieve an update, structured content and build a proof of concept for a decoupled layout builder. This is a very cool idea that our whole team is stoked about. Amy June for the first time right before this event. So welcome. I know you're in the back end with the cool kids. I love this one. Thank you. I love this one because you'll see she's talking about how do we rebuild the core contributor support materials and how do we nudge folks to meaningful contributions without turning them off as mistakes are made along the way. I think there's a direct tie between Drupal and Drupal. I love the tangible outcomes and deliverables. Let's take a look at the pitch. I am Amy June Heinlein, Volkswagen Check on Drupal.org and Aaron Winborn, a winner. And generally a good person who believes anyone can contribute to Drupal. I've been a mentor since 2016. In 2019 I was asked to join the core mentoring program as a team lead. I have the unique privilege of working with the technical writers, the coders, the developers, the designers, and connect them with first time contributors with skill sets that match their specific contribution needs. I also work with the community working group on the community health team. And right now my current project is creating productive language and dialogue templates around conversations about gaming and attribution system. I also work with the community health team to provide workshops that we present at flagship events like Drupal con and build a program that empowers mentors outside of the core mentor group to present and help with mentor contributions at the local and regional camp level. This would involve perhaps modernizing the slide deck we have for Drupal con and creating a more interactive workshop for the community health team. And I also work with the community health team to provide workshops to give the workshop at their local or perhaps virtual event. Second, gaming the system is creating tension in the issue queue between contributors and maintainers. Some of the solutions that are being thrown around and discussed might block some contributors from receiving credits and perhaps demoralize them. And I also work with the community health team to provide workshops for contributors who are starting in contributions which would highlight issue queue etiquette and appropriate first tasks for beginners and when to move past novice issues. It would also highlight some of the do's and don'ts around adding files and submitting patches of merge requests. So with those two things I'm also working with the community health team. And third attend Drupal con Lille and Portland to run the workshops at actual events and get feedback so we can iterate and grow these programs. Thank you. The next one is Drupal Gutenberg for Enterprise CMSS. This is Torandre Gretland from front come in Norway. I feel like I'm in Eurovision. We are going from Australia to Germany. I've heard before but let's listen to what Torandre said. I'm Torandre Gretland from front come. We're a digital consultancy focusing on Drupal with about 120 people. We want to make Drupal the most easy to use Enterprise CMS. You use a CMS to manage content and the question is not can you do this in Drupal because the answer will always be yes these days. Our solution must be easy, effective and inspiring. And most complex websites are not easy, effective and inspiring. They're difficult and clunky. We solve this with the Drupal Gutenberg editor and our clients love it. In fact we haven't built a Drupal website without Gutenberg since we started the project back in 2018. We make the editor experience closer to the front end but with an extreme flexibility with possible options that works out of the box. This is the greatest enterprise tool for CMS and content creators inspiring them to work on content, update and optimize it for better conversion. More than 3,000 Drupal websites use it already and outside of Drupal the editor is already used by more than 80 million websites. The Drupal Gutenberg project has been up and running for a while now but we want to take it to the next level. We want to make it work for a few days where we physically gather people from the WordPress core team that built the editor, the Drupal core team that knows the needs and possibilities for the admin initiatives and so on and the Drupal Gutenberg team from Frontcom that built and maintained the Drupal Gutenberg module. We want things like creating a Gutenberg starter theme and a starter pack where Gutenberg is set up with a complete front editing or to use it within the layer builder. Our goal is to make sure that Drupal Gutenberg of the future is always using the latest and greatest person from the WordPress team and better enable Drupal developers to contribute back upstream. We want Gutenberg more tightly integrated with Drupal and to do this properly we need to gather the people that should be involved. This is a great opportunity to make it the most easy to use enterprise CMS. There you go. Obviously some of you in the room are wondering, well, pitch A, I think it was, it's about decoupled layer builder, this is about Gutenberg, why would we fund them both? When we saw this in our combined ranking, we actually deliberated, we talked about this and we actually felt like they are the last pitch around Gutenberg is about bringing together all of the different stakeholders, Gutenberg people, Drupal core developers, layer builder people, we can figure out who the right people are to figure out how do we actually get a great layer builder into core and the second pitch could then be sequenced after depending on what the outcome of the first meeting is. So if you as the audience decide to vote for both of them and we think that will work and we can work with those two submitters, if you will, to make sure that money is really well spent. So I just wanted to give you a little bit of that because we actually did talk about this and we ended up feeling good about it. So that's it. Let's go to the next one. I'm excited about this next pitch because it really proposes changing the way that we build our structures. So with that, let's take a look at the pitch. I'm Brad Jones, longtime Drupalista, full-time digital nomad, part-time paramedic. Greetings from beautiful Lake City, Colorado. I turned 40 this year, but you know what really makes me feel old? I remember when Drupal didn't even have fieldable entities in core. It's true. Drupal was released in January 2011 and fields were a real market differentiator. Think about this. Drupal 7 is six months older than Laravel. We were really ahead of our time. Back to present day, field API is still powerful, but if you're building a new product that needs room to grow and adapt, fields with set properties can be a restrictive pain point. Here's an example. Much of my data model is as you would expect. Profiles, matches, photos, you get the idea. But I also have to keep track of lots of other things like tokens for push notifications. I started with a map field that stores a push token and device ID. When I launched my web UI, I had to store additional tokens and metadata. It's all stored in what at the end of the day is just a text field in my database, a PHP serialized string. If the data isn't normalized, I can't. Thankfully, time has marched on and all major database engines now support JSON data types, which means you can do things that look a lot like no SQL inside of a relational database. And so by extension, Drupal fields and queries. The core team has already decided to require JSON data type support for databases used in Drupal 10. It's now time to unleash that power. So we're going to start with JSON data queries with JSON data storage. At the same time, we can easily extend the entity system to provide standards compliant JSON schemas out of the box. Zero code open API docs anybody? We're not far from being the most flexible and performant data management system out there. I think it would take about $20,000 to pay myself and other qualified developers to knock it out. It's a great idea because we all know contribution. We all know worlds and permissions to manage the policy access to core and it would be great to have a much greater level of freedom. So let's watch this submission about policy based access in core. Welcome to my pitch for policy based access control in core. I am Christian Van Den Endve. You may know me as the author of the group module and I have also written some supporting modules with our purely APIs and they have zero bugs. What is policy based access? It's a type of system where people gain or lose access based on certain predetermined scenarios or policies. How does this differ from what we currently have in core? We have permission based or attributes based access control where you have to fit your access logic into assignable sets of permissions. There is no way to assign permissions. Whether the benefits or some examples of policy based access you may only be able to administer people when you have two factor authentication enabled on your account because we value work life balance you may only edit your content during office hours or because we don't want hijacked accounts to cause a lot of damage you may only delete up to three pieces of content per day but there are many more scenarios possible. For example, we need a centralized permission checker where we can check all of your policies in one place and then we need an API to convert your policies into permissions. Here's the good news. Reviewed and tested by the community. All code written already just needs to be converted into a patch for core. Let's talk numbers. We need about 15 days to get access to core. This will cost about 12K and factorial has offered us a reduced rate of 800 euros per day to get to that number. We have capacity at the end of this year and we hope to use Drupalcon.lil as an opportunity to sit down with core maintainers and help get this into core. It's already 90% complete. All of the code has been written. We just need to write some integration. The things we received really spoke to the need to better enable developers that are just coming to Drupal and make that transition easier. To me, this next pitch is stood out because it potentially leverages AI as a way to make that transition easier but also potentially support both novice Drupal developers as well as something that could be useful for experienced Drupal developers as well. Let's take a look. Hi, I'm Indogas. Recently, I have been working on Drupal artificial intelligence matter issues. Because I think there is a lot of potential for Drupal and AI. For example, here I listed categories of features that could be created and visualized in the current state. But how to create these many features? How to innovate quickly? How to adapt an accelerating world? Maybe with the help of AI, develop a system which could help build Drupal systems using your natural language. Simply select a module you want to improve, give AI instructions in a future with your voice, talk with AI about improvements to the code, review and confirm the changes and keep improving. Code Drupal inside of Drupal build AI features with the help of AI. How can this be achieved? I posted this issue with the details for example giving AI access to configuration, to publish the module with some code. And to further advance this course I'm seeking 12,500 to find 250 hours of development to implement first part of the roadmap and research second part. First part will enable you to talk with AI about the code base and I tested this alone greatly improves productivity. To implement this I will work with other module maintainers to code, test and integrate universally useful features like remote engineering tools. Advance these features for any use case. I will also use some of this time to continue facilitate innovative Drupal AI ecosystem as cutting edge AI research evolves. Drupal will be prepared and ready to adapt and maybe contribute in enabling whole society to adapt as well. All the links of issues will be in video description. Thank you for your consideration. And last but not least this is about Drupal API client. The use of Drupal as a tool to build a Drupal API can imagine if you have a unified clean API for all JavaScript friends. Let's have a look at it. Hi sharks. I'm Brian Perry from Chicago, Illinois and I'm here on behalf of the Drupal API client project. We're seeking $10,000 to build an extensible JavaScript API client for Drupal with the goal of eventually publishing the results under the Drupal core. Drupal core has got great APIs to make data available to a couple of applications, but we fall short when it comes to helping JavaScript developers consume that data. That's where the Drupal API client project comes in. Our goal is to create a framework agnostic base class with defaults for things like data fetching and caching that can easily be overridden to support different implementations or even different API types. This is the base class to create a complete client package for Drupal's implementation of JSON API. Sharks we've handed out some samples by way of a small proof of concept. This is the API client class which has a constructor and implements a fetch method which has a default but can also be easily overridden. And this JSON API client extends that class but implements get collection which allows us to get a collection of resources from the API. And the GraphQL client extends the same class but implements a query method to query GraphQL. Now Sharks we see that you have some questions like why do we believe we'll be successful. We've already had a number of key contributors from the Drupal ecosystem express interest in participating. What are we going to do with our funds? This is a high level breakdown of how we plan on using the $10,000. Primarily we want to use it to be able to allow people to participate who wouldn't have been able to contribute otherwise. And as far as what we're going to deliver we're going to create the project, develop a vertical slice proof of concept that will allow us to put together an early proposal for the Drupal JavaScript maintainers as we continue to work on the JSON API client and also the Drupal client as well. Thanks for your time Sharks and together we can make the Drupal API client a reality. Am I good? Am I done? I was told that I would meet Mark Cuban. All right so these are our seven picks. I hope you like them. Did you like them? So this will be the exciting part and hopefully it will work. But as I mentioned now we're going to use your phones and I'm going to show you and explain how it works but we're going to show you in a little bit we're going to show you a URL that you're going to have to type into your phone. I don't know if you need to get off the Wi-Fi or not. If you have a regular cell phone subscription that works in the US you may want to use that instead of Wi-Fi I'm not sure. We're also going to show you a QR code so you can use that web page. It's a survey monkey tool. You'll be able to stack rank all of the seven pitches and you can do that using your finger by dragging and dropping or you can use arrows whatever you prefer and we'll give you about two minutes to do that. After two minutes the music will stop and the voting will close and we need about 30 seconds to sort of tally the results and put them up on the screen and then we're going to reveal the winner. As I mentioned we can't fund everyone so the outcome will be a stack ranking and then we'll go down from highest rank to lowest rank and we'll kind of see how much we can fund because actually if you add up all these numbers it's over 100,000 and so obviously there's going to be one, two, maybe three that fall off the bottom and hopefully that was clear so let's go. Let's do it. Let's see. People need more time. Let's give it a little bit more time if that's possible. We do want people's votes in as much. I think there's some internet connection issues, right? So let's add a little bit more time. We have 435 already. That's pretty good. I think it might have gone in. So while you vote we'll give you a little bit more time. I will say we had 35 submissions and there's obviously those 7 were pretty good but there was many, many others that were amazing and hard to choose from and one of the things we're going to do is after the Drees notes or after today or tomorrow we're going to publish all 35 videos. So I would definitely encourage and of course if any of you want to fund one of these videos you can if your company or yourself want to help contribute funding to any of them please just come talk to us. You can talk to the Drupal Association, you can talk to any of the judges here on stage and they'll help you to the right mechanisms and people to do so. So how's it going? The numbers are up. We have now almost 600 submissions. I think that's good. It's not meant to be academically precise. It's 600 that's probably good representation. I think this room takes 1100 people or something. So we're having at least half of them answering here so looking good. Whenever we're ready I think it's going to be fun. So any moment now the results could come on screen and we'll see. So the question is going to be for those who know Eurovision are you going to say the numbers in French? Because Drupalcon is happening in France in this fall. Let's see. Talking about the Eurovision one of the things that's interesting about it is that we're not responsible for half of the votes and then the audience which is people all around the world are responsible for the other half of the votes and we kind of like that idea and we try to bring that into this a little bit where the judges gave some points and then hopefully you'll all be able to give some points as well. The other thing I can say while we work on the results potentially doing it again at future Drupalcons if you like it and if you think about it it's really a matchmaking program between some of the best ideas in the Drupal community and then funders people that want to contribute to Drupal financially and not something that we've really had in this form and it doesn't always have to have this shape or form the results are in. But number one is clearly the decoupled layer builder so we should fund that. Gutenberg is number two. Definitely need to fund that. I'm pretty sure we can continue funding Jason data in schemas which appears to be the number three. We had almost 700 submissions or like voting. Yeah we had almost 700 so I think that's good. Which was number three? Number three was the Jason data and schema. How much do we have then? 62,000. 62? Alright we've got more. So the next one I think is the Drupal API clients. We have 75,000. How much do we have left? We're at 72,000 now. So we only have 3,000 left. We have 3,000 more. Alright so what would have been the next one? Trying to policy based is that right? No the B, contributing the mentorship. Amy needed 6,000 and we have 3,000 to give. Right. So we have 3,000 short so anyone that wants to fund 3,000 come to us. If not we'll fund you for 3,000. Somebody's raising their hand? Okay so come to us afterwards. Thank you very much. Very good. So unfortunately we're out of money. But it's for today. Yes but hopefully we can find other ways to fund these remaining projects and then some of the projects we haven't shown. I'm going to go through some of the things that we need to do. I want to thank everybody. Two quick things if you have questions for me about today's keynote or other things there will be a Q&A session later today. You can see it on the screen. Second announcement we are going to leave the room and take our group photo as mentioned and that's going to be next to the agenda. So I just want to thank everybody that contributed and sponsored the contest. Thank you.