Driesnote (live) / DrupalCon Global 2020

hello everyone welcome to the DRI's notes the plenary session where Driss byte art will talk about the current initiatives in Drupal the success of launching Drupal 9 and a number of other important highlights for the community I'm very happy to welcome you all here for this session and pleased introduced Drupal Association executive director Heather rocker to give a brief update about the Drupal Association programs before Driss gets started thank you Tim so I'm here today representing our Drupal Association staff and our board of directors and officially welcome you to Drupal con things are going great so far this morning we're very excited that all the things that needed to happen are happening so thank you for being here and for being part of the experiment of taking this online so I get a few minutes today to share with you some of the insights about our work and the goals of the Drupal Association you can meet our team and learn more about our mission by visiting us this week in the exhibit hall and I won't have time today to walk through all of our programs and updates so I hope that you'll take the opportunity to watch the DEA update to the community in the on-demand content and also join us for the drupal.org engineering team panel and the QA with the board and staff both happening live tomorrow as Tim said I'm Heather rocker executive director of the Drupal Association and I'm thrilled to be here with you this week although this definitely wasn't our original Drupal con plan for 2020 Drupal cons not only a mission centric program for our nonprofit Association but it's also our largest source of funding last summer staff and a myriad of volunteers began the hard work of putting together Drupal con Minneapolis which was scheduled to happen in May of this year however in March it became clear that there wasn't a safe scenario for us to bring the community together and have an in-person event as we had planned as we evaluated all of the options one thing was certain we wanted to find a way to convene this community and create the opportunity for further collaboration and contribution everyone has worked so hard to end sure that we could bring the energy and excitement of a typical DrupalCon to life in this new virtual format and sometimes with change comes opportunity and DrupalCon global has been no exception moving this event online have the added benefit of allowing us to dramatically widen our scholarship program efforts with a particular lens on diversity and inclusion so we've been able to provide more access than ever before for those underrepresented in technology thank you to the organizations and the local drupal associations that partnered with us to recruit new scholarship attendees I hope you'll get a chance to chat with a few of the over 150 scholarship recipients here with us at Drupal con this week many of them are new to Drupal con and some are even new to Drupal so welcome thank you for being here I do want to acknowledge the hard work of the program committee the summit leads the speaker team and the steering committee which laid the groundwork for Drupal con global we owe many many thanks to these event volunteers from the community and we've even recruited some from beyond the Drupal community so welcome to you as well this event would literally not be possible without our sponsors many of these sponsors pledged their sponsorship dollars back in March when the there was no certainty about what would happen with Drupal con they pledged to stick with us as we figured out the new plan and we so appreciate their ongoing support be sure to visit them in the exhibit hall this week thank you also to the Drupal Association supporting partners fundings from these organizations help us do the work that we need to do and creates funding that's non event related which is really important from a funding diversification standpoint work we do like supporting the development of Drupal 9 maintaining drupal.org funding infrastructure and contribution testing fees driving diversity inclusion and equity programming collaborating with various drupal working groups like the security working group which keeps the project secure enabling contribution and even expanding the types of contribution we recognize none of this work would be possible without these organizations so thank you so we can't talk about support without talking about Drupal cares the Drupal Association along with so many other organizations was deeply impacted by the Cova 19 crisis we had a lot of difficult community conversations about what the project would look like without the Drupal Association while we were still crunching numbers on every possible financial scenario we got a clear signal from you the community that you stood by ready to support us in help and the Drupal cares emergency fundraising campaign was born I appreciate how Matt Westgate frames the work of the Association and why our continued work is needed early into the launch of the Drupal cares campaign Drupal founder Drees and his wife Vanessa made an important pledge to support and encourage other donations and that became the matching gift challenge where every dollar donated was matched by a dollar up to $100,000 then a group of dedicated business leaders from the Drupal community came together to make the campaign even better this group announced the launch of yet another matching gift challenge which made every individual cash donation and every new or renewed membership have tripled the effect so now we're talking about $300,000 in support community members got creative we even saw wonderful projects like pixels for Drupal the Drupal 9 module challenge and more the point is every action mattered every donation whether large or small every tweet of support that you sent every new or renewed membership you made a difference you ensured that we met the drupal cares emergency fundraising goal of half a million dollars and not only that we met it but we did it in record time you demonstrated once again the power of this Drupal community and the power of the open source model itself as as Driss said this was really important so that we could refocus Drupal thanks Drupal hugs and all of the Drupal happy things to everyone who participated in Drupal cares and as you can also see from Jesus quote about the Drupal cares campaign this was all happening at the same time we were launching Drupal 9 and Drupal 9 is here this is where there'd be thunderous audience applause and participation so I'm just going to envision that's happening for all of you at home because it's very exciting not only did Drupal 9 launch but it launched during the earliest of the three projected release windows on June 3rd of this year which marks an incredible accomplishment by this community and everyone involved there are many opportunities to learn about Drupal 9 during Drupal con global this week if you want to fall in love with this community just take a look at celebrate drupal.org members from around the world contributed photos drawings videos and more all celebrating the hard work and collaboration it took to launch Drupal 9 and in fact this site is now also showcasing Drupal con global celebrations and videos so post your submissions this week and be part of the ongoing fun as we celebrate Drupal simply put contribution makes Drupal what it is it's obvious that code contribution is essential in fact we couldn't have launched Drupal 9 without it and the work for Drupal not Drupal 10 which it launches in two years actually needs to happen now as well contributions is important as ever but we need to create a broader range of what's recognized to recognize and encourage contributions of all types to the Drupal project so we launched the contribution recognition committee last fall announcing it at Drupal con Amsterdam and it was part of the Drupal Association's commitment to creating a frictionless and truly rewarding contribution system for this community so the committee has paused to do the kovat 19 crisis the DEA team stands ready and will keep working to recognize more kinds of contributions and to make the process of crediting contributions even easier speaking of contributions don't forget to join in this week not only if we brought the conference online but thanks to volunteers you can contribute online as well before I leave today I want to talk about one of the most important focus areas for the Drupal Association and that's diversity equity and inclusion we know that diverse representation is low in technology and with data shared by Drees at the DRI's note in seattle last year we also know the numbers and open source are even more troubling luckily the values and principles for our community are a natural conduit to this kind of diversity equity and inclusion work and frankly it's why Drupal has been a leader in this space for years last month the Drupal Association we released our official statement in response to the ongoing violence of racism and communities around the world and particularly here in the United States we made a commitment to follow these words with actions though we began this year with diversity equity and inclusion plans and goals for the Association we've accelerated those activities in recent months it's important to me that our team is doing the work so that the increased cultural competency and inclusive decision-making within our team can be applied to the work we do for the Drupal community and short my hope is we create a positive ripple effect so I'm excited about some of the things coming out for the community as well we're collaborating with a cohort of Drupal training organizations to create a program focused on developing Drupal talent with an emphasis on supporting those typically underrepresented in technology and open source this pilot program is scheduled to launch this fall and I'm excited about how we can not only move the needle on diversity but also provide the developer talent that is much needed in our community with a more diverse equitable and inclusive community the Drupal project will thrive and will drive even more innovation so that people can make a positive impact through Drupal you can also help us make a difference this week Acquia and last call media will both donate five dollars to black girls code for anyone that registers interest at their booth in the exhibit hall in addition message agency is hope hosting a special intermission later today in remembrance of the tragic death of George Floyd in addition they'll be making a donation on behalf of all DrupalCon attendees to black lives matter I do hope that you'll join me later today for this important time of reflection on behalf of the Drupal Association our team our board our volunteers thank you for joining us at Drupal conglobal I'm literally humbled by your presence at this event we just didn't know if the community would meet us here and and be as excited as we are so we're really just so very thankful that you're here and I do hope that we'll spend our time wisely together this week that we'll learn from each other and we'll make connections that move us forward as a project and as a community and now I have the pleasure of sending it live from here in Atlanta Georgia to Berkeley California so we're gonna go East Coast to west coast so that Fatemeh can officially introduce the DRI's no thanks Heather welcome everyone to your first virtual trip booked on this is all really new for us isn't it it makes me think back to my first triple con which was four years ago in your leans where I was totally new to Drupal I didn't know what it was whoo core contributors were what if you was or how many of these things work together there were so many things to learn people to meet bots to be confused and slime to collect I also remember being a volunteer and during the closing we were supposed to hand out stickers for next year's conference to attendees as they left the hall and I was so excited that I went and handed a stack of stickers to juries we had a really good laugh about that and I even have a picture to remember it by but that first duple con was just really overwhelming for me and sometimes confusing as I can imagine this one might be for so many of us I know that we have fond memories of DrupalCon I know that I will really miss hallway conversations game nights and even heckling eating onstage at trivia but that being said I am really looking forward to exploring all of the different ways that we will engage and connect with each other virtually this week and I'm so excited to welcome all of the people for whom this is their first DrupalCon being virtual we've been able to open up opportunities to bring in new speakers and new attendees who may not have been able to attend otherwise we're so happy to have you here and I hope that you'll be able to learn a lot connect with this community make friends and feel inspired to take back what you've learned I also think that this is a great time for us to reflect on the community that we want to be and the traditions that we want to take forward with us Pantheon is proud to be a sponsor here at your book on global at Pantheon we're building the world's best operations website operations platform to help empower web ops teams to take control of their websites and deliver results by iterating quickly learning and experimenting so if you have a Drupal site that you'd like to take to the next level you should come meet us at our booth and find out more and who says virtual conferences can have swag we're giving out t-shirts and turn all your questions and just hang me up so come stop by and check us out without further ado on behalf of myself and my awesome colleagues at Pantheon I'd like to introduce you to one of Drupal cons classic traditions gone digital the very first virtual drezna everyone please welcome the founder of Drupal live from Boston fast back to the East Coast trees thank you very much that was a great intro all right I think you should be able Assam I think you should be able to see my screen now for those that don't know me I'm Greece I started the project and I'm still depressed aday you can find me online as you can see here we have a lot to cover today the main topics for today are the release of Drupal 9 and then I'm gonna talk a lot about Drupal 10 and what we're going to focus on next but before we get started I wanted to recognize that there's a lot going on in the world right now and to start I wanted to extend my sympathies for everyone impacted by Kovach 19 this has been hard this has been hard for many including the Drupal Association as Heather talked about for those in the black community we know that you carry an extra burden and I want to be clear that I and the Drupal community stand in solidarity with you the need for increased diversity and inclusion was a major theme at last year's Drupal con and you may remember this light where I talk about why diversity and include inclusion is so important not only is it the ethical right thing to do but it also improves innovation and creativity and collaboration as a project we are committed to making Drupal a more diverse and inclusive place for black people and other people of color so that we can all drive at this year's Drupal con we actually have our most diverse lineup of speakers ever which is something that I'm very proud of and we will continue to make this a priority going forward I feel responsible you know as as Drees as an individual but also as a project lead of Drupal to talk about diversity equity and inclusion but also feel like we need to make meaningful changes and and concrete actions it's not enough to just talk about these things so there's a few things that we're doing in addition to what Heather just talked about one of the things that we're doing is we're reviving the values and principles committee and we're going to review our values and principles through a lens of anti racism our community working group and community health the team is already in process of reviewing our code of conduct to make sure you know to update our anti harassment language and things like that to make it very clear that we do not tolerate discrimination harassment and racism in our community we will continue to track and publish diversity data so we can hold ourselves accountable I will personally make a donation to black girls code and in addition Acquia my company is donating $5 to black girls code for everyone that joins our booth and clicks their register interest button and I know this is just the start I know this is not enough but we will continue to make progress and work on this until we see true racial justice so I wanted to thank you and thank everyone that's you know working with us that's helping us work through these crises both Kovan 19 as well as the financial challenges of the Drupal Association as well as topics like racial injustice obviously I would have preferred to meet in person but I'm still very happy that we were able to you know pull off this virtual conference and able to meet sort of virtually and while that does feel different you know still feels really good that we are together now here virtually and it feels really good actually knowing you know all of the things that we do I truly believe that Drupal is in a very unique position where we can have a real impact if you think about some of the side effects of of what is happening is that you know in times of financial crisis many organizations have to do more with less and when you have to do more with less budgets are cut and frankly open source and Drupal become more relevant we've seen this in all of the previous financial crises but also because retails and stores are closed many organizations are actually going through an accelerated digital transformation where they have to move more of their business online and again this is something that makes Drupal even more relevant today and so you know on a positive note I would say we have some other exciting news obviously and that is that last month we released Drupal 9 and we release it on time as we said we would and maybe a little unconventional this time around but we still found an appropriate way to celebrate the release of Drupal 9 with people all around the world and have a very quick video of that that I would like to show you [Music] [Music] [Applause] [Music] [Music] isn't it awesome I just love how much progress we've made in the last four and a half years and how we were able to to celebrate this there's so much great things that we did just to give you a few quick examples obviously throughout the Drupal 9 release cycle we added media management which is great because it gave us a completely new way of managing images and videos and it's a lot more user friendly and it was ever been before we also worked on a new way to create layouts and to manage layouts with the layout builder and really dramatically improved page building in Drupal which is awesome we made amazing progress through our API first initiative which is all about it advancing drupal's web services support to help build headless or decoupled applications and you can see you know some pretty famous organisations in the world have begun using this to build no native apps and to you know push content in all sorts of devices and modalities and maybe best of all and this one I'm particularly proud of is that we delivered on our promise to make Drupal 9 the easiest update or upgrades and in the recent history of Drupal just looking at some of the stats you know a third of all of the modules are actually already Drupal 9 which is record breaking and then another third of all of the modules there's only one line of change required to make them fully Drupal 9 ready so hopefully we can make some progress on those this week and so all in all Drupal 9 has the easiest upgrade path in the last 15 years of Drupal and maybe longer which is awesome and our users love it like if you go and Twitter you see people tweet about it every day and here's just a handful of the streets where people say how smooth are not easy the a great pad is I personally upgraded my own site I know that's a simple site but it took no more than 20 minutes to upgrade my personal blog from Drupal 8 to Drupal 9 so that was a very special feeling to be able to do that so all in all it's difficult to highlight everything but there's just so much that we've accomplished and so I think it's fair to say that we really climbed a mountain together and made progress on each of these four strategic tracks which I think has been fantastic if you look at that through the lens of data you have data points like this where we had 55 buck fix releases of nine major releases thirty-five alphas betas and release candidates in twenty four security releases that's a lot of work for the core committers and the release management team so big kudos to them for you know doing this like no like clockwork as a heartbeat for the project we also have a new innovation model where new features can enter a Drupal core as experimental and can then sort of graduate to become stable features and we have 13 major features go through this process which i think is a great testament to this new innovation model and how well that's been working in total over 4,500 individuals contributed to Drupal 9 and you know over 760 organizations contributed to Drupal 9 which is really hard to believe and it's even more impressive if you look at the names on a slide there's just so many names of people that helped make this happen it's really kind of amazing to think about that and then of course a lot of these people have been supported by organizations so thank you all for contributing to Drupal 9 it's a fantastic release I think it's maybe the most progress we've made in a long time and I really think it will change the perspective that the world has on Drupal because you know we may drupal a lot easier to use and a lot easier to maintain which is some of the feedback or criticism that people have so I think it's a fantastic accomplishment and I really thank you for contributing and making that happen just as a quick reminder if you are on Drupal 8 still you have about I think 16 months or so two upgrades and some quick math I hope that's right and if you're on Drupal 7 you actually have more time which may sound a little counterintuitive but you have more than two years before Drupal 7 its end of life that's something that we've recently changed we extended it by a year and after that actually you have a commercially extended support as well so if you're on seven we encourage you to upgrade but if you're not ready to upgrade you know you can stay on Drupal seven it is well maintained and supported with bug fix and security releases um so that's a little bit about Drupal 9 and so now I really want to spend most of the rest of the presentation talking about it what we're going to do next what are some of the new things that we're gonna do as we think about Drupal 10 now before I dive in I wanted to share a few quick things one is that we learned from Drupal AIDS that we actually had too many initiatives if you remember that Mountain slides there is more than 15 initiatives on that mountain and in fact not all of the initiatives were on that mountain so that was a lot and we didn't finish them all despite a lot of great progress the other thing that we know already is that we won't have the same amount of time to build Drupal 10 then we had for a building Drupal 9 and I'll come back to that in a minute here to explain a little bit more but with these two things in mind my goal for today is to propose five initiatives for Drupal 10 and I know that sounds like a lot less and it is but it allows us to focus and allows us to make great progress now when I think about five initiatives I want to make sure that these initiatives are well balanced right and what I mean by that is that need to balance both technical debt and innovation we need to consider different stakeholders or personas for example we need to think about what developers want but we also need to think about what site builders and content creators want and even sellers people involved with convincing potential customers or users of using Drupal going forward we also need to balance a long term and short term goals which can be hard and the last but not least we need to work towards a strategic vision that makes it really really clear to individuals and organizations as to why they should adopt Drupal like it should be obvious if you're doing this kind of work you should use Drupal to be really differentiated compared to other solutions now the way I want to go about this today is in two steps when step one is to make a list of all of the important initiatives to consider so I'm going to make a list maybe twenty to twenty-five potential initiatives and then we're gonna have the heart you know chore I guess of selecting just five and that will be hard but we're gonna try and make sure that they're well balanced my right so that's the plan and so let's start with making the list of initiatives to consider and so the way I think about this there's sort of four buckets of initiatives to consider one are the initiatives or the things that are mandatory because they're security related to are things that we've already started that are still pretty awesome that people still want but that we haven't finished and so things that we want to finish three are things that existing users are asking us for things that they want to see in future versions of Drupal and last the fort bucket it's things that we know we need to do to attract new users to Drupal and to stay relevant in the long term so things that users are asking us for are tend to be a little bit more short-term whereas things that will attract new users and that make people feel confident about picking Drupal for you know to build their sites for the next you know decades tend to be a little bit more longer-term so let's go through these four buckets and let's start with the things that we need to do because we feel they're mandatory to do and a lot of that comes down to keeping Drupal secure as you know Drupal depends on a lot of third-party components and each of these components have an end of life if you put that in a timeline like this you can see some of the components or the dependencies that Drupal has and for some we already know when their end of life and then for others we know there is a new version either there is a version already or we know a version is you know the new version is eminence but they haven't really communicated their end of life but the point is each of these components that we need to track them and manage their end of life and in this case symphony for and ckeditor for we know their end of life at the end of 2023 and really what that does it forces us to end of life Drupal mine as well right and so what we need to do is we need to release a new version of Drupal well before these are end of life because we want to give our users you know all of the users of Drupal 9 time to upgrade their site before these components are end-of-life and so really what that means is that we're targeting the release of Drupal 10 to be around June of 2022 now some of you may you know panic a little bit or be afraid because that is actually you know like two years away or even a little bit less than two years away and you know obviously there will be an upgrade from Drupal 9 to Drupal 10 but let's not forget we made upgrades easy and we will continue to make upgrades easy just like we did from Drupal 8 to Drupal 9 and in fact there's a lot of things that we have learned from that that will allow us to make it even smoother so don't panic the upgrade from Drupal 9 to Drupal 10 should be easy now what that means for those of you that are contributing to Drupal 10 or thrive the Drupal 9 development cycle is that actually Drupal 9.3 alpha they serve the last opportunity to introduce new features or replace existing features or API because we do need some time to prepare for Drupal 10 and to remove deprecated code for example so really what that means is that we don't have a whole lot of time for innovation for implementing new features and capabilities in fact if you compare that the Drupal 9 we have less than two years compared to 4.5 years and we only have three minor releases that we can use to innovate you know compared to eight minor releases in Drupal nine so that's just something to keep in mind and another reason why five initiatives for drupal two and scenes you know sufficient anyway with all of that said the first initiative that i think we should consider and we may not have a choice here is what i've called the drupal 10 readiness initiative which is really all about making sure that the dependencies or the components that we use are properly managed and that we have you know proper security coverage for all of them now if you go into a little bit more detail you can see there's a long list of these initiatives here and for each of them we need to figure out what to do often it's just an upgrade but in some cases we need to think about it do we stick with that you know components or do we actually want to change it to something else like for example CK editor for CK editor 5 is a major rewrite with lots of API changes so you know we need to decide do you want to go with CK editor 5 or is this a good time to maybe reconsider our options now some of these initiatives and these upgrades I should say of components are actually very good right like some of them actually give us new capabilities new API snoo innovation so it's not just maintenance work we actually in some of the cases get real benefits and user benefits due from these initiatives and you know ckeditor would be a great example because they've made a lot of improvements and they allow like collaborative editing and these kinds of things with future versions of seek editor as you can see the total effort for all of this is large I mean some of them are extra large on their own but then if you add up everything it is kind of a large undertaking to get ready for Drupal 10 and this is not even everything that we have to do so that's really the first initiative that I believe we should consider and so I'm adding it here in the bucket of things that are mandatory so with that let's move on to the next bucket which is things that we've already started but not finished and there's actually a lot of amazing things that we've started but not entirely finished and so one example is the media initiative which gives us this new media library to help manage images and videos now it actually ships with Drupal 9 its stable when it ships with Drupal 9 and we encourage people to use it however it's not enabled by default so if you install Drupal it's not part of the out-of-the-box experience now we don't love that because it's such a great feature for you know beginners and you know people that are less technical they really benefit from this and so what we want to do is we want to finish this right we want to add some of the things that are missing like integration with some parts of Drupal some usability and accessibility improvements and things like that in the same boat is the layout builder again it is stable it ships with Drupal 9 we encourage people to use it but it's also not enabled by default and that's a shame because it's a much better experience a lot of usability improvements come from using the layout builder so we need to finish it in order to do so we need to think about replacing the you know existing or the old block you i we also have to make some usability and accessibility improvements and some other things as well our new admin fee the name of that theme is claro is more or less in the same boat its ships with core but it's still beta so it's not stable and it's also not enabled by default and it's such an improvement in terms of the administrative experience also in terms of accessibility that we want to enable it by default and ship it to be the you know default experience for everyone and so again there's a few things that we need to finish like media integration toolbar support and we want to make sure that the module administration page as an example looks really good so I think it's pretty close but it still needs to be finished and so what I did is I actually bundled each of these or all three of these things into one initiative and the goal is to push them over the finish line make it an out-of-the-box experience for Drupal and that will be very important because it will make Drupal a lot easier out of the box and that is very important because you may remember from my Drupal con Amsterdam presentation that we did some user research we interviewed CMS users not just Drupal users but different users of different CMS's and we asked them what they're sort of perceptions are of the CMS over time and what we've learned is that beginners don't love Drupal to put it you know plainly but then as they advanced as they become more experienced they start to love Drupal more and more which is why this line goes up and to the right though is interesting is that other CMS's at the exact opposite trend line you know when we spoke to WordPress or Adobe or site code site core users we learned that the beginners loved those platforms but then over time as the user became more of an expert they start to love these platforms less and less which is kind of remarkable that Drupal trends serve the exact opposite direction but it speaks to the opportunity it speaks to the opportunity of improving the beginner experience because if we can attract more people to Drupal give them a great experience we should feel confident that they will stay with the platform for a long time and so that's why I believe the easy out-of-the-box experience is an important initiative to consider I believe that ease of use of Drupal is probably the number one thing that we should focus on other than obviously security but there is more another example is Oliveira and Oliveira is our new front-end theme that we've been building for some time now Oliveira is not even in core yet it doesn't ship with Drupal yet so the goal here would be to get Oliveira included in a future version of Drupal 9 make it stable and also enable it by default so down again we leave people with a first great impression and a great theme to look at and learn from and so a new front-end theme is another initiative that we should consider another one is automated updates today when we do a security release you know organizations that use Drupal often have to keep an expert on call to help with that security upgrades and these security releases then to happen around noon you know Eastern Time and of course for some people depending on where you live in the round in the world that is sort of an inconvenient time zone and so making security updates automated would be you know a great win now some of you may recall that this was actually an existing initiative which means that we have a pretty good plan for this initiative and that we've actually already made a lot of significant progress and some of that thanks to the European Commission will really want this feature for themselves and have been funding a lot of the work on automated updates so let me give you a little bit more of a detailed look at where we're at so that you can you know maybe help contribute to the initiative so if you think about automated updates you know if I simplify what needs to happen when an automated update or cures it's basically four things first we need to prepare for the upgrade which means Drupal needs to check that it's in a let's say healthy or clean state that nobody modified or hacked Drupal core as we say once we know that Drupal is in a clean state we obviously have to figure out what needs to be updated the things that need to be updated may have dependencies that need to be updated so there's a whole process on figuring out what are the updates that I need to download or what Drupal needs to download once we've downloaded all of the different updates or packages we want to check that they're also not compromised right we want to verify that these are things that we know and are safe to update and once we've downloaded everything once we have verified everything we need to switch to the new code do these new updates and that's actually a little bit complicated because we want to support different workflows maybe some people want it fully automated maybe other people want a quick manual approval step so we need to be able to fit that into different workflows but then we also need to account for what to do when things fail right so we need to have the opportunity or the ability to do a rollback if the update didn't work and so you know switching to new updated it may sound easy but it's actually not that easy and so if we think about these four pieces the way we have been working on them you can see on the screen so you know we've been working on integrity checks that's actually mostly done to manage the dependencies and download the updates you want to switch from composer one to composer two they make that really the core of that system which it's designed to do that and composer two comes with some much-needed memory improvements which you know why that is interesting to verify the updates we have a package signing system that works in the background with Drupal the doric that's mostly done and then to do the whole switching to new updates we will be using a custom boot loader again I won't go into more details here but this should give you kind of an understanding of the plan where we're at and then hopefully also how you can get involved we can help in each of these four work streams we would love your help so if we do that if we finish that I think that would be fantastic it will allow site owners to sleep well at night it will reduce the maintenance cost of Drupal and so I think it's a fantastic feature all right so there's a whole bunch of other things of course other than automated updates that we are working on and have been working on and these are very valuable these are you know I'm passionate about many of those however I decided not to include them here because I don't think they are the most important or the most strategic relative to sort of you know defining five strategic initiatives now that doesn't mean we should work on them we should definitely keep working on them especially if you're passionate about it but it may mean that we're not prioritizing all of the resources around them so for example the committee time or the time that committers spent they may prioritize other initiatives over these initiatives so wait times might be a little bit longer and things like that but by all means we love this work and keep working on it if you're passionate about it alright see these are the two first buckets so now I'd like to move on to the third bucket and that is to talk about things that users are asking us to do now the way to figure out what users are asking you to do is to do a survey and to do user research and so guess what we did a survey over 2000 people took the survey which is awesome it's a lot of data points and one of the things that we asked every participant to do is to self-identify so we know sort of whoo you know took the survey so you can see you know there's back-end developers 50% of them identified as back-end developers their site builders and the difference between back-end developers and site builders just to be clear is that site builders tend to me more WYSIWYG and drag-and-drop write it so they don't necessarily open up an IDE to create a custom module they try to do things through the UI content creators and then sellers so sellers meaning those that help you know sell Drupal to potential users now if you do the math it doesn't add up to a hundred it's actually over 100 and that's simply because people can self-identify as more than one persona like a lot of content creators are also site builders some developers are both back-end and front-end developers so that's why the total number is more than 100 now what I did is for each of those personas I looked at the data and I looked at the top two requests for each of the personas and the way I filtered the data is that I looked at the top two has voted on by the persona so what that eliminates is maybe a content creator voting on you know back-end developer features so I thought it was important to kind of use that filtering and then I also filtered by Drupal 8 experience so quite a few people that took the survey had not used Drupal 8 yet because they're still on Drupal 7 and so if I didn't filter the data by Drupal 8 experience a lot of the requests would be for things that we've already implemented you know try Drupal 8 in Drupal 9 right so that's why I filter the data this way so it's basically as an example you know what do back-end developers experience with Drupal 8 asked to do for other back-end developers that's the idea if you look at the data there's actually quite a bit of data points for each of those personas hundreds answers that we considered and then what I did quite simply and by the way I will make all of these data available and all of the details so you can do your own analysis but this is my analysis and so then what I did is I basically put the stock two requests for each of the personas in a table and so I'm gonna reveal it to you now I'll go you know bottom to top to build up some suspension given that a lot of you are back in developers but sellers they basically asked for things that help them demo Drupal and the number one thing was a better looking administration theme and the second thing was out-of-the-box integrations specifically integrations with marketing technologies because that's what end-users tend to ask for they want to see that Drupal can do the things that they want to do and that it looks good and that it's easy to use so no real surprise there content creators also asked for a more modern administration UI and you know one that's responsive and snappy and sort of application like and then they also asked for easier to use page building tools so despite the layout builder they want even more easy-to-use page building tools that could be improvements to the layout builder but also I think out of the box blocks like maybe to add a title or an image or different components on pages so that's content creators so moving up site builders they asked for automated updates and more modules in core now the more modules in core is interesting and we did have a little bit of a follow-up research on this and the reason why is really many fault one is you know 80% of the websites use you know very similar modules and people are a little bit tired of having to download these modules and install them they just want them to be there but also by adding them to core it removes some of the maintenance burden it makes it easier to update those modules and so actually some of that could be fixed by automated updates in core next front-end developers they asked us to modernize the JavaScript in core and you know to look at JavaScript frameworks they also asked for a component based theme system and I won't go into the details of what that is here but more modern way of building and designing front ends last but not least back-end developers they asked for improved API documentation that was a number one ask and we did have a question in the survey that was kind of a deep dive on that specifically and what this was about was actually less about the quality of the API documentation it was all about the discoverability and the search ability of the API documentation so that's what we learned from the survey again the details are in the detailed survey results but it just wanted to be easier to find the documentation that we have and the second thing was to replace the hook system with events and this one actually made me smile because you know years ago this was a little bit controversial where most people loft the hook system now people want the event system and I think that's great because it means two things one their serve a general interest in moving away from old Drupal isms but also I think people want one system versus two system so cleaning that up is important for the developer experience no doubt so these are the top juice for each of the personas now you may wonder what didn't make the list because some of the and some of the questions in the survey have you know more than ten different options so a lot of things didn't make the list I won't go through them all here I'll put them on this slide so if you're watching a recording you can hit pause you can read a little bit more about them here to see what they didn't make the list now next I wanted to look at what beginners versus experts are asking for and for me that was important because of what I said earlier the need to really focus on the beginner experience based on the research presented in Amsterdam and so what I did is this I basically came up with this star system where I would have two stars when half or more of the respondents of the survey said drop everything that you're doing and do this which if you think about it more than half of the people that took the survey were extremely passionate about it so two stars is an incredible endorsement - for a feature or a feature request I gave something one star if one out of three people said drop everything and do this which still is an incredible endorsement for a particular feature and not everything on this list got a star and so when you do that for both beginners and experts you can actually see not only what do these personas have conviction for but also is there a consensus or a lack of consensus between you know beginners and experts and so if you fill that out it looks something like this and if you look at the data you can see that clearly automated updates is the number one it's the only one that has two stars for beginner and expert so a lot of conviction from both experience levels and also a lot of consensus because both of them really want this the number two is clearly a modern administration UI it has the most stars next to you know automated updates and it also came back in to persona so what I did is I put all of those you know top feature requests in this bucket and I added two stars - automated updates and one star to a modern admin UI and I did that sorry just as a reminder so we don't forget about what had the most votes you know based based on the survey all right so next the fourth bucket is things that we must do to attract new users and for drupal to stay relevant for the next decades let's say there's this longer term and you know there's nothing new here i've been talking about this for many many years actually and as recently as DrupalCon amsterdam where have you know reminded people that we are evolving from a browser only world where a CMS was a standalone application where he did manual entry of content and it would generate an HTML page for HTML pages you know we're evolving from that world to something much more complex something much more rich where you have many different integrations with back in technology and marketing technology weary of many different output channels not only you know web pages HTML pages but mobile applications chat voice you know you name it and all of that happens in many different formats you know could be JSON the XML could obviously be HTML too and that's really where the world continues to go and as I mentioned I believe this is a multi-decade trends you know we're years into this so this is nothing new but I think we have a long way to go and I think we should expect an acceleration of this trend as well just to put that in perspective you know one data point today there's about 20 billion devices and it's expected that in less than 10 years there will be 300 billion devices connected to the Internet generating data with or without this place but you know just an explosion of content and explosion of data and so that's why it's really important for Drupal to continue to evolve from a web content management to what I call a Content repository to more of a structured data engine where we need to think about you know supporting more kinds of different content maybe binary content even where we need to think about it managing much more content than we've ever managed just more volume of content not only different kinds of content and where we need to make it really really easy to integrate with both these vacuum systems and these front-end systems and so the integration part is really important you know back-end and front-end integrations now in addition to that there's actually another important trends Ana Trent is a front-end developers don't always love PHP you know even though PHP is faster than ever before even though PHP is better and richer than ever before front-end developers don't always love it right so and if you look at the numbers while PHP is vast while PHP powers like almost 80% of all of the websites in the world which is incredible the numbers are starting to decline and if you compare them to the JavaScript numbers you can see in this case you know react that the adoption of JavaScript and react is literally exploding and it doesn't look like it's gonna stop any time soon the same is true actually for other frameworks like view you can see view same thing growth is of the charge then if you put them next to each other you can see them you know PHP styl like what ten times or more than ten times bigger then react on almost you know ten times bigger than react and view together so there's no reason to panic PHP is strong but you know I do think we should really look at embracing more JavaScript in Drupal especially for the front-end and this made me think if I were to start Drupal today you know almost twenty years after I started rupal if I were if I were to start today I would write the front end in JavaScript to be quite honest I wouldn't write it in PHP now it's a different story for the back end I may not write the back end in JavaScript but the front end to me with all of the richness of the JavaScript community all the components that they have to build from thence it feels like a no Bray to to do that so I put JavaScript and web services on the list and so this is the list right so this is the 10 and you know the list of initiatives that I think we should consider and so now let's select 5 which is a hard part so what I did is that just kind of flip this on its head if you will and I created these empty slots for five initiatives to consider alright are you ready um so for me the first three initiatives are actually no-brainers you know we have to get ready for Drupal 10 we have to make sure that Drupal is secure so we have to manage these components the next two easy out-of-the-box a new front and theme I believe they're so important that we're so close we need to finish them it's the right thing to do it's like we're so close to the finish line and pushing it over the finish line is where we unlock the real value of all of the work which is improving that beginner experience so yeah for me these are really important at afford one I also think is obvious you know we have been working on it and it's by far the number one request you know by far the number one feature request so automated updates in my mind has to be item number four and not only is it useful for security updates and hopefully other updates I actually do believe it's very strategic if you think about what we're doing you know I've been pushing for this idea of the assembled web which nowadays people call you know composable architectures where you can basically you know mix and match modules to build different kinds of applications in a very composable way sort of like LEGO pieces which is exactly how people describe Drupal so we have a real strengths there but if we could make it easier to manage all of these components and to datum it really could accelerate this vision of the assembled web or composable architectures and if you think about what could come after this is not just automated updates but also making it easier to you know find and install modules where you've like a marshal browser from within Drupal and maybe a distribution browser from within Drupal I think now we take a lot of complexity out of Drupal and getting started with Drupal so really good for beginners but really also long-term strategic in terms of you know ease of use flexibility composable architecture so I'm actually pretty excited about that for more than one reason so now last but not least again I have to go with the vote of the users which is a modern admin UI they got the second most votes after automated updates I think it's really important so let's talk about that so some of you may remember we actually had an initiative to modernize Drupal's admin UI and we actually did a lot of great work we identified sort of all of the parts and we identified what was hard and easy we did prototyping and I think even showed some of these prototypes in previous Drees notes or Drupal con presentations and we set various things in motion but we also learned in doing all of that work that the scope is very very large that redesigning the complete administration UI is a lot of work and so you know we should have known better and that includes me and all of the core committers that this was huge but I'm still very grateful of all of the work that we've done because the fact that we learned so much and so if you think about the scope there's all these pieces that we had to do which may not be obvious at first but we identified a number of architectural changes we need to make some of them pretty hard like how do you validate configuration entities as an example and then we identified that we had not complete coverage obviously with our web service API is and that we needed to add a lot of web service API is and we did that and some of that lives in contrib and all of these things are necessary to even begin to redesign the administration UI using JavaScript components which is what we want to use and so you know good progress was made but we don't have a new admin UI to show for because it was just so large and so what I'd like to propose next is that we actually kind of pivot and that we reduce the scope and that we take a small but specific step to set this admin UI work in motion and I'll explain what I mean by that so first of all if you go back to this slide there's all these pieces and you know obviously we're not showing you all of the details but the way I think we should go about it is is basically follow the Pareto principle which effectively says that you should focus on the most impactful problem first and then once you solve that problem you move on to the next problem eventually you arrive serve at the finish line after you solved most or all of your problems now actually think we solved some of the biggest problems already in my mind that's getting content in and out of Drupal which we did by adding the JSON API module but if I think about what could be the next biggest problem in terms of impact I think it's menus you know if you think about all of the sites and applications that exist almost all of them have a menu to navigate it's also really hard for JavaScript developers you know because you have to think about hierarchies some of these menu items may be module defines or programmatic if you will some of them are user-defined you have to think about pad aliases access control I mean menus sound easy but they're actually really hard and as a result most applications hard-code them like nobody built them to be sort of dynamic they're all hard-coded because frankly there is no web service API in Drupal for managing menus and when I looked at some of the competitors they don't have an elegant solution for this either so it seems like there is an opportunity to solve menus so that you know you don't have to resort to hard coding them which you know it looks a little bit like this where a developer has to check out the project make code changes you know commit those and then you know deploy them and go through the whole deployment process along the way so you know there has to be a better way and for us CMS experts it's not that hard to imagine what that would look like meaning the better way is for in this case our June to be able to make changes through the menu in the Drupal back-end and then have these changes automatically reflected in the front-end application like this is what everybody expects a CMS to do yet in the headless CMS world and in Drupal this isn't solved properly right and so we can solve this we would empower our June and obviously you know and Maya too because she wouldn't have to do this all the time right and so specifically I believe our mission should be to provide the best way for JavaScript front ends to consume configurable menus managed in Drupal now that's a lot so let me break that down and help you understand what I think we should do I believe we should have an official component for react and ship an official component for react I believe we should have an official component for view as well so that we are not dependent on one framework and that we can build this with you know abstraction in mind and I think we should really think about the developer experience and specifically the front-end developer experience so that we deliver it in a way that they expect it to be delivered which I imagine is true NPM you know the way other components are made available to them when building an application and if we do this well we could have another advantage over some of the headless CMS's and actually have a better developer experience and a better end user experience now for some this may sound like maybe a small step right aa-men use is that really that interesting and I think it actually is really interesting because in reality and I alluded to this menus are pretty hard right not only do you need to add more web service API coverage for menus but you really need to figure out how to manage these different kinds of menus and hierarchies and when you're talking about menus you can't ignore things like pad aliasing and routing because when you click on a menu item you expect to navigate to another page so it really kind of pulls out some of the harder pieces to figure out and then maybe the hardest part is figuring out how we actually make an official component how do we go about testing JavaScript components what about documentation how do we create these packages how do we do release management for respect jiz what about security what about the dependencies on other JavaScript's packages and so there's just a lot to figure out so while it sounds easy to do menus I think it's actually quite a bit of work now menus I think are a real problem and I think it's actually a problem that many front-end developers have but what I'm actually more excited about is all the things that it sets in motion for drupal specifically so if you think about it what we're going to do with this first official components menus is establish a clear pattern and a pattern that can be repeated think of it as a recipe or a playbook right once we figure out how to build one opponents and how to manage a component and release a component and package and desta components we can really start building many more components in parallel all following the same pattern so if we can enable all of the contributed modules to build components in a uniform way make it part of our tools and workflows I really I I would expect to see a lot more components components for blocks and forums and shopping carts and maybe carousels and views and toolbars you know you name it and once we have enough of these components we'll be in a much better position to start improving the admin UI right if you think about building our own admin UI well we have menus too in the admin UI so that's an example of a component we could use we're also using views in the admin UI if there was a good component reviews we would be able to use that too and so again it's what it sets in motion which is so exciting to me and for me ultimately it actually solves a very big what I call industry problem a problem that everybody has and by solving it we can be the best the couple CMS in the market and let me explain what that means today we often have to make trade-offs if you go with a headless or decoupled approach you're really optimizing for the developer experience because you allow the developer to use Java Script which is what the majority of front-end developers outside of Drupal typically want to use but when you do that you really compromise what I call the non developer experience the site builder and the content author because they lose things like menu management but also layouts and previews and many other things right and there's other modes like progressive decoupling and really that's not the ideal solution either because as a front-end developer now you have to learn both Twigg and JavaScript because you know that's what progressive decoupling means and so the question is can we build something that doesn't compromise one persona that you know is both a positive experience and I think we can if you think about the menus if we can build a menu component that can be used by a front-end developer but that then connects into Drupal to generate you know the menu or the content of the menu it would be a win-win for both personas and that would be a big deal and I've been blogging about this for a couple of years and you may have seen some of my blog posts in those I put these complicated flowcharts to help you know people decide should they go with couple decouples you know or something in between and there might be an opportunity to get rid of those flowcharts or at least make the choice a lot easier or not as dramatic so an official JavaScript components an official react an official view JavaScript component we've never had this would be a first in the lifetime of Drupal in 20 years of Drupal and I think it's actually a giant leap for Drupal to add the first official component so what I am proposing is that we don't do the modern administration UI that we learned from the past that that is too big of a scope and that instead we focus on a JavaScript menu component to make that first step and to you know set that snowball in motion to make that start rolling and if you think about it a little bit more it's actually very strategic for other reasons because I believe it allows us to make some progress on some of these other important initiatives it really connects into a lot of things it helps us modernize JavaScript it helps us evolve into a component based theming approach it improves web services because we have to add more API coverage and eventually I think it can me to ease your page building and a more modern administration UI so I'm not saying it solves these initiatives what I'm saying is it helps us make some important part so I think of the JavaScript menu component initiative as you know very strategic actually as I just explained in the last five to 10 minutes so here's the five proposed initiatives that I think we should discuss and consider and I've had an opportunity to run them by the core committers and they're on board and I talked to some others about this as well but open for feedback by all means and I believe they're well balanced you know as I said in the beginning we need to make sure they're well balanced I think they help with technical debt and innovation I think we're looking at different stakeholders beginners and experts but also developers and non developers and you know making progress to be a great headless and decoupled CMS in addition to be a great traditional CMS this approach of API first but not API only I think if organizations and individuals are very clear reason to adopt and I think it puts us on a path to be long-term relevant last but not least I think it's hard work it's a lot of work but also achievable maybe a stretch a slight stretch but it feels achievable in the next 16 months to make some growth progress I would actually love to see a stake like a flying start if you will with the JavaScript menu components imagine we could add a first component in Drupal 9.2 maybe we can get some more components in by 9.3 I know this is a little bit wishful thinking but um it might be worth a shot so you know we have to get organized around this we don't have all the details figured out or we haven't made plans for everything we need initiative leads for each of these things in some cases we already have leads in other cases not and we've also learned that it helps to have a main sponsor and a main sponsor is an organization or someone who provides resources usually time and talent sometimes money to to help drive the initiative you know with the help of others including volunteers so they don't have to do all of the work but they are you know the main sponsor so we're also looking for main sponsors if you're interested we have contribution tables at these events you see the link at the bottom of the page you can join those and raise your hand and it will help welcome you and help you get involved so if you want to learn more about some of these things that I just talked about we actually have a lot of sessions on these topics you can see them here some of them are tomorrow some of them are Thursday by all means if you're excited about this please do get involved and if you do this well I think the Drupal 10 press release could be you know pretty exciting and so kind of drafted one so let me try and read it to you okay here we go this would be June 2020 to Drupal 10 extends Drupal strength in headless or decoupled applications and for developers that means that Drupal 10 simplifies the development of JavaScript applications Drupal allows developers to user framework of choice but it ships with out-of-the-box support for react and view for marketers this means that Drupal 10 allows the building of omni-channel digital experiences without giving up the ease of use marketers and content creators expect this makes Drupal the best decouple CMS for less technical users Drupal 10 also ships with automatic automated updates this makes it drastically easier to maintain Drupal sites and up and to apply security updates it also advances drupal support for composable architectures like Drupal 9 Drupal 10 continued its focus on improving the beginner experience with a new look and feel and an improved out-of-the-box experience I think that could be great if you can achieve all of that in two years I think that's worth another celebration so if you are excited about this please help I really do you believe that it's not only fun to work on but it's also really an opportunity to have a positive impact on the world with that I'd like to thank you I will make the slides available on my site I will make the survey data available on my site I probably need a week or so to do that because this week is pretty busy I will not be taking questions right now but we have a dedicated 45 minutes Q&A session tomorrow so if you have questions if you want to talk about this more or other things you can ask questions about anything please join the Q&A session tomorrow all right well thank you very much thank you dreams and thank you everybody who listens into the DRI's notes my name is Tim Lennon you probably saw me at the welcome session this morning I'm the CTO here for the Drupal Association and I wanted to spend just a couple of minutes here in an outro saying thank you to everyone who was here and also reflecting on and bookending something that happened at the beginning of the presentation so I'll actually share a slide or two in just a moment when we get there but first I do want to thank I have the rocker executive director of the Drupal Association for her initial presentation for all of us and for talking about the initiatives being led by the Drupal Association to support the community I want to thank Fatima for a wonderful handoff and introduction to the DRI's note it was really a great conversation and some wonderful memories about Drupal cons past but now I'd like to spend just a moment of reflection we made a large theme of both the Drupal Association update and Jesus update diversity and inclusion in the Drupal community and I wanted to share some personal reflections on this subject because I've had a little bit of a personal journey with this issue before and after my time with Drupal and the Drupal Association so let me share just a slide or two with you to close us out today and I'll share a bit of a story so my name is is Tim Lennon I'm just a I'm a sis white guy in the Drupal community so why am I here to talk about diversity inclusion in the outro I'm here to talk because I've learned three skills recently that I think are really critical and important for all of us who believe in the value and who believe in those values in our daily lives in our work lives and everywhere so I think those skills really represent the the three skills represent the ability to be vulnerable the ability to be empathetic and the ability to be an ally so I want to talk briefly about those so first vulnerability for myself vulnerability means being able to talk to all of you who know me as a technical individual as someone who leads initiatives for the Drupal Association and works on drupal.org to talk about something that's outside my comfort zone and frankly outside of my expertise empathy means understanding the needs and wants of people around me understanding where people are coming from and looking to my own experience and experience of others to learn from it I'm gonna share some fairly personal stories about that in just a second and then Ally ship means understanding how to take action in a way that supports the community rather than relying on a community to do work for you so on the note of being vulnerable it's it's always difficult to talk about I'll share two two ways that I've learned empathy over the course of my my recent life and later career in in college at Reid here in Portland Oregon I was part of a household and kind of community that was very close with the transgender community on campus we had housemates and things like that rotated and out of ours and several other campus houses for folks who needed it for folks who were perhaps going through transition and other sorts of things and my best friend that I grew up with was part of that community and I learned a lot from living with that community of people and talking with these people who were were and are some of my closest friends unfortunately my best friend died in 2009 in an accident and since then I have been honoring and remembering her by finding ways to be involved as an ally and active in this community and to bring it to the other things that I do and the other parts of mine my passions more recently when watching the protests all around the United States and around the world I and my wife went out to the Portland blacklivesmatter event and went there to bear witness and participate with what was going on in the community and support the community listened to the land acknowledgments and the given by the Confederated Tribes of Warm Springs here in Oregon listen to the founder of the Portland black Black Panthers speak about their experience and it was very meaningful and very difficult to someone who often feels like there may be part of the problem to understand how to be part of the solution so to talk about good Ally ship for just a moment what that means to me is understanding the experience of others listening to their voices elevating their voices and knowing knowing how to engage and how to help in a productive way so just to talk a little bit about that engagement Heather our executive director injuries both talked about various initiatives that are going on and one of the most important kind of principles behind this right whether it's our internal Drupal Association training or whether it's partnering with Drupal diversity and inclusion to bring a code of conduct training to the community or to provide booth space or whether it's just changes to our own hiring practices or things like that is that everybody has actions of their own that they can take within an organization and that is part of good Ally ship and the other part of good Ally ship is knowing how to engage your community so the Drupal diversity and inclusion group is a self-organized part the Drupal community that has existed for I believe it's around four years three or four years now and has been organizing ad hoc speaker trainings and other events it's not in the official higher hierarchy of Drupal governance it's a totally independent group and I have found a lot of value from regularly attending conversations with that group I've certainly found places where we've been in disagreement as well and that's okay too as long as we know how to do it respectfully one of the things that I do want to say though is that if you are an ally or someone who wants to be an ally seeking out support seeking people who are maybe more experts than yourself ask for help but don't expect that help but don't expect people to do the work of educating you for you so if you have some issue where you have a significant diversity or inclusion concern and you want to engage some a group within the Drupal community like didi and I you know engage upfront ask if they'd be interested in participating but don't come to them with a problem that's already happened and asked them to solve it for you right it's about engaging in a way that shows thoughtfulness that shows your own education and willingness to participate so also don't depend solely on that group there's a group of great people who want to be participating in helping this community as a whole but everybody can do this work everybody can participate individually so the Drupal Association is doing some of our work entirely independently we want to do some more work together as well there's work that the core maintainer team can do to talk about how we choose no more new core maintainer x' there's work that any individual Drupal business can do to choose to talk about their hiring practices and training and even how they interact with clients so I just wanted to share some of this vulnerability some of this empathy and perhaps inspire some people out there to do the same I want to say thank you to the DNI group or helping me in my journey over the last year or so I want to say thank you to the Drupal Association leadership team for some of the really internal trainings that they've organized for us as staff and I want to say thank you to all of you listening for taking this to heart taking it seriously and perhaps thinking about how you can engage with it yourself in your own way so thank you very much everyone with that we'll get back to the slightly less serious stuff if you want to have a Drupal con t-shirt that will be available on the community driven community LED t-shirt store if it's important to you to complete your collection feel free to pick one up and also feel free to participate in the group photo that's what we always do at the end of a juries note as we all go gather out in the courtyard somewhere and take a group photo we're going to do a version of that virtually so let's go ahead and we can take some selfies of us attending DrupalCon upload them to celebrate drupal.org and then tweet them out with the hashtag Drupal con photo and we'll use that to assemble a mosaic group photo for this virtual DrupalCon event so thank you so much again for being here thank you so much for your attention I hope you're as excited as I am about the initiatives that Teresa's outlined and and about the ways that we can evolve and improve our community have a great one take a look at your schedules get ready for your next event you should have a little bit of time to get rolling and thank you again everyone bye

Channel: Drupal Association

Views: 3,574

Rating: 4.6226416 out of 5

Keywords: drupalcon, drupal, 2020

Id: 9ot0rIlhbNE

Length: 90min 8sec (5408 seconds)

Published: Mon Jul 20 2020