 Morning or good evening or good afternoon everyone depending on where you are in the world. Thank you so much for joining us. I am here with Tim Lennon and he and I will give you an update about what is new at the Drupal Association and specifically what's happening on Drupal.org because you're supporting partners and all of your money goes to fund the work that he and his team do. I just want to really make sure you feel connected to the area that you're investing, which is so critical. So just to get started, little housekeeping, if you could just remain muted during the call. That way we don't get background noise because we are recording this and we'll send out the recording in the slides to all supporters after the call. We do want to make sure that we field your questions. So there is a chat window for questions. Tim will be watching the chat window. I can't actually see it. And so he will stop us as we need to answer questions. And as you hear things, if you like what you're hearing, feel free to tweet it out and make sure you tag at Drupal Association. We've got some news and as I mentioned, we've got a Drupal.org update we'd like to share with you. First, I just want to thank all of you for recognizing that Drupal.org is a big asset for our whole community that we all benefit from. And it's so important that we give it the funding it needs to not just exist, but to evolve with all of our needs. And it's the supporting partners that are providing a very large percentage of that funding through this crowdsourcing model that we've come up with called the Supporting Partner Program. And I'm actually going to be working on a report so you could see where funding comes from for Drupal.org and how much is coming from the supporters. It's really quite impressive. And so we just want to say thank you for recognizing that just, you know, yes, you can download Drupal and run a company with free software, but you are the ones that recognize that giving back allows us to do more with this community site. And you're the ones that see that it does cost money to move this forward. So, so thank you. All right, let's go to some news. So on the community front, there's a couple of things happening that I just wanted to call out the Drupal Association worked with the community to help them move forward with community governance improvements and discussions over the summer. We did hire Whitney Hess who ran several community discussion sessions and found findings of areas where there's consistent people had consistency of needs of where community governance need to improve as well as she identified with the community strategies they may want to use to address those needs. And then she also did a survey with the community to find out more about what the communities needs are and how they want to move forward. That work with Whitney concluded and the community working group heard the need that that we want to keep understanding how community governance can evolve and we want to make sure it's really owned by the community. The Drupal Association is merely helping the community can kind of organize and so that they can kind of take the ball and run with it and the CWG is a community group. So they heard this call this need and they are working with the community now and the next steps to really clarify the areas that the community wants to fix in terms of governance. And we're going to hear soon about their recommendations. And so that that process is kind of ongoing right now but I'm really glad to see that it's progressing we're really thankful for the work the community working group is doing on that front as well as some others that have joined them to move community governance forward. And one of the things that we heard in terms of need in the community is more clarity around Dries Butart's roles he has many roles he's you know the benevolent dictator for life. Which means he's really a project lead for the whole project and of course he has his role at Acquia and he has a role on the Drupal Association board. And while community governance is evolving and it will impact aspects of the community, there are things within the Drupal Association, which only the Drupal Association has governance over and can fix. So what you know we don't want to wait for everything to come together all at once there are some things we can do now to address the needs of the community and Dries heard the call that you know one solution could be that he steps down as chairman but remains on the board in the seat that was designed for him called the founding director seat. And so he has decided to go ahead and take that step. And again he will remain on the board but in this founding director position. And it is renewed every year says to be voted in every year. And so, you know what that does is that he's just not driving all the agendas and managing the committees for the association. And so we need someone else who can do that. The community had also said that they would like to see some outside expertise come in. And to have someone that's neutral to be the chairman. And so we heard that and we have asked Adam Goodman to be the chairman of the board. Adam Goodman has been advising the board for the last eight years on and off. He used to be a volunteer board and now we're a strategic board and he has been the one that's come in and helped to evolve this board. And while he's chairman he will remain in that type of role he's going to keep evolving the board and helping us orient around having a new chairman. And so of course we will want to continue a search for a permanent chairman because Adam's playing an interim role. And I think it's also just important to point out that he is a paid consultant and we will be paying him for this service. And we are updating the bylaws in order to accommodate that we announced that at the last board meeting and we just want to be really transparent about that and we'll be voting on those changes. I believe at the next board meeting. So I think these are really positive steps. We're excited about them but more importantly it just feels good to hear the community and to make some some improvements of our own and you know we're all in this together. Another thing I want to point out that we're doing is hiring a community liaison. This is a specific role to help build a better relationship between the association and the community. We definitely heard the need that there needs to be more clarity and transparency, more engagement. And I think the community needs help understanding more about our programs about our financials is just a lot of things when we became a smaller organization we really lost a lot of our community communication staff, and we're feeling it I think we're all feeling it and our role is to fill that gap and is to foster bidirectional communication between the community and the Drupal Association. And so you'll see this role will do things like be in the social channels and helping to make sure that when there's big questions out there someone's there answering them and also get a canonical space on Drupal.org to put up information about the association so it's really easy to find how are we performing financially now. So so many things community elections this person can run the community elections for us and really make sure there's a transparent and clear process and lots of engagement. So I think it's going to really help build that relationship that we all want to have and help people understand that that the Drupal Association is here to serve the community and how we're doing. And then also to be more agile to hear the needs so that we can find new ways to serve the community. We hope to have Megan we have. Sorry, we had one question. Okay. I think you did you did address it to some a certain a certain extent so Gabriel asked, will trees need to be voted into the founding role each year and will he when is he announcing that decision to step into the new role. You as you already said that role is voted on every year by the board to affirm the position. If it's not filled it would stand empty because it is a seat just for the founder. And then in terms of the decision it was announced at the last public board meeting so it's it's there it's in the recording and everything else I don't know if we'll do additional blog posts or something like that but I'll make sure that yeah so all of that is correct the founding position is like where he actually sits and then you get kind of appointed to chairman and to be very clear it's actually called president when you look in the bylaws is just that most people keep referring to him as somebody language here. And he has always, you know, even like just last November we did the annual voting and just to we do, we've been maintaining that will continue to do it is just, we won't be playing into the chairman role. Yes it has already been announced, and we will continue to communicate out when it's all official. And we also want you to know who Adam is so you will also see probably a blog post with some kind of interview and there as well. Just a little background Adam Goodman is a professor at Northwestern University. He is, he heads up the leadership program there so as an expert on leadership and advising boards and helping boards become better and organizations to become better so you know he has no stake in Drupal. He just likes to see organizations grow and be healthy. Any other questions. Okay, well then I just wanted to give an update on Drupal con Vienna it was a very successful event with 1600 plus attendees. As you may have read or heard through by, I think it was like a five blog post series about Drupal con Europe that it has. It is important. However, right now our operational model and the way that it's being organized right now has resulted in a loss and when we went to, you know, work on the content the programming changes. It wasn't seen as highly valuable before and it's even with the trying to redesign it with community input still wasn't hitting the mark. Which is all concerning we've seen that reflected in ticket sales declining. But I just want to be very clear I think this is a product issue, not a Drupal issue because camps have been on the rise year over year in Europe as people are finding different ways to meet their needs. So, you know, we're looking at this and we came to a conclusion that we do not want to just keep doing a rinse and repeat every year, and, and just hoping it gets better. We need to have a serious rethink and a different operational model that focuses on sustainability as well as value. And so here is what's happening. We're taking a pause of Drupal con in 2018. We are working on a new operational model, we think it should be a licensed model we're exploring that. And we want to find an entity that's grounded in the community to take on Drupal con Europe in 2019 and we would license it to them. And I have a committee of European event organizers helping me to think this through and get feedback and we do have some entities that are considering this so we're working with them to test this concept. At the end of the day Drupal con Europe is important. It brings all kinds of people together from different countries, different personas, the business side, the developer side, and it breaks down barriers and allows very unique and very needed cross pollination of ideas and also it's a huge engine for contribution. So I want you know we are taking extreme care about Drupal con Europe's future. Because we know how important it is and I'm excited for the progress we're making there. And we'll keep everyone up to date what's happening there. But meanwhile, the community in Europe feel strongly that something does need to happen in 2018. They understand that the Drupal Association from a capacity standpoint can't have this big rethink and produce a Drupal con at the same time. That's actually been the problems we haven't had time to slow down to really think this through in a bigger holistic way. You know, we can't hold Drupal con in 2018, but the community feel strongly that it is held something is held that there's a couple things one allows for that cross pollination of different personas and people from different countries. But it also needs to be an MVP and really experiment and try different things. There's a group that stepped up. They've been putting out medium posts. You know me about 12 people in that group and there's so many more volunteers and I really am incredibly impressed with the progress they're making trying to figure out how to bring this event together. And I definitely support them moving in that direction they have a lot to figure out. And they're going to need support and so what I'd like to just say about this is Drupal con or Drupal Europe 2018 is important. And since there isn't a Drupal con that year. If you were sponsoring Drupal con Europe. I ask if you will support this group and what they are doing with sponsorship dollars. I think it is not just admirable but very impressive that they want to come together and try new things and try this MVP approach. So I do have an appeal asking you to support them with your sponsorship dollars. And that brings me just to a big question that's come up, especially for supporters in Europe. One of the things that people have asked me is, wait, I'm confused. If I'm, if you're not having a Drupal con in Europe and I'm giving money to the Drupal Association. What am I funding because I don't want to just fund Drupal con North America. And we don't want that either. We want to make sure people are very clear where their money is going and that they feel good about the investments that they're making. So I wanted to break it down for everyone. Those that are sponsoring an individual and or those that have an individual organization membership, they're paying about 30 to 100 US dollars. That money is funding community grants. That means we give money to the community cultivation group. We give community members, they receive requests from camps from Nigeria and the Philippines and China and gosh, different places in South America. And they provide 500 to about 1500 US dollars to these camps so that they can start growing because you know it takes a while to get sponsorships, especially when you're in new markets, new emerging places. So the other thing that they fund are scholarships to bring people from around the world to Drupal con. So this year, as an example, scholarships will be used to bring Europeans and Africans. South Americans right people from all over the world to Drupal con North America. And so it's not funding Drupal con North America. It's funding these kinds of programs. I just wanted to be clear about that. Also, you as supporting partners, just so you know where your money is going when you renew every year, that is only to Drupal.org, which as you know supports the whole world, including all of Europe, and 44% of contributions coming from Europe. So, you know, you can feel good knowing that your money is definitely supporting your, your region as well as the world. And again, it is only going to Drupal.org. And then of course event sponsorship goes to the event you're sponsoring, right? It helps fund that conference. So if you are sponsoring Drupal con North America, it's going to Drupal con North America. If you are funding Drupal Europe 2018 it's funding that event. So I hope that chart helps. And if you have questions, please let me know. And again, we are working with our financial company to come up with better weather reports that really break it down and make it easy and digestible. So you don't have to just look at PNL's that don't really answer the questions you may have. All right, if there's no questions, then why don't I hand it over to you, Tim, and I can just drive the slides. Great. Thanks, Megan. First of all, I'd just like to repeat the thanks to all of you as supporting partners who fund that the work we do on Drupal.org and my team specifically if you go to the next slide Megan. This is the engineering team that works on Drupal.org every day. And that's not everyone who adds value there of course because we have the people who manage membership and communications and all sorts of other things that happen on Drupal.org and other channels. But in terms of the features that support the business community and developer community, I just thought it would be good to put some faces with names of people you see in the issue queue who rely on your support to be able to do what we do for the community. If you keep going, Megan. One of the changes that we made in the last quarter relating to the adoption journey and promoting Drupal to evaluators and to also to saying thank you to you all as supporters is that we've added a second row of case studies here to the front page of Drupal.org which is a partner and contributor case studies that we feed from current supporting partners or from people who are sort of top of the contribution rankings in the marketplace. So we encourage you if you're a supporting partner and you don't yet have any case studies on Drupal.org and you'd like to eventually participate in this program. The first step is of course just getting those case studies up and then, you know, we'll reach out to you as we're working on rotating through these slots, but we're really happy about this because it helps center some of the critical stories about the success of Drupal right up front on the homepage and really, really promote that to the community at large. Next. Another thing that we've done is we've made some updates to the Drupal.org industry page landing page. So this is the the page where we describe the value of Drupal solutions and different vertical markets so our before that we have right now our healthcare higher ed government and we'll be working on others going forward. We just updated this a little bit again to promote those pages but also to promote kind of the whole cross section of different hosting partners and hosting solutions that can be part of a complete solution. So that's just a small update to that page that we think will help evaluators find the right right solutions for their needs. Next slide. As I mentioned the healthcare page is one of the pages, one of the solution industry solution pages that we're promoting right now it's the latest one to be released. So it talks about some great stories about success in healthcare using Drupal as a solution. And we're just proud to get this next one live and ready to go. And yeah, we'll be following it up with a few more industry solution pages soon. Another small change that we made is that we on the download and extend page we're now featuring community faces and community stories with an appeal for membership. So you can see here we have Fatima talking about the per participation in the community and the value of Drupal just not just as a as an open source project but as a community of people who come together to build something pretty incredible. We're rotating through different faces and stories and we think this is a great way to reach out to people who aren't yet involved and to get them more involved in the project. As far as the contribution journey goes over the last quarter we've made a few changes as well. For all of our project maintainers of contrib projects or core projects who work on Drupal.org we've automated the process of making sure that they get issue credit if they whenever they commit an RTBC issue to their projects. So that just streamlines that whole process and make sure that all of our anyone who maintains a module, whether that's an organization or an individual contributor is getting the credit that they deserve for that hard work that they do for us as a community. We also have updated the testing system with a variety of new features that I think really help one of them sort of reduces a significant portion of the kind of the busy work that can go into doing code review on Drupal.org, which is we now generate an automatic code style fix patch in the test results so instead of having to sort of go in and manually correct your periods and semicolons and extra spaces and all that kind of stuff that a patch is just immediately generated and we're working as a next step to automatically apply that back to the code and back into the issue queue just to reduce that busy work and and increase the the velocity of the developer community in general. One thing that we'd like to do as a future step, although there isn't really low hanging fruit here is we want to take advantage of providing contribution credit for contributions that occur outside of Drupal.org so that means if you're a camp organizer. If you organize sprints if you're a mentor, we want to find ways to recognize those contributions on Drupal.org as part of our contribution marketplace. One of the things that we're looking for here as I say we need to do some work to make this possible in terms of providing an authentication endpoint so that people can integrate that on their camp registration sites and then send back information about who's fulfilling what roles at the camps and things like that it's going to take some work but it's something we're looking into and we just want to let you all know that we're it's important to us to recognize these contributions coming from individuals and organizations that happen outside of just the official Drupal.org channels. I also wanted to provide a short update on project creation as as you probably know about six months ago we changed the way that project creation works on Drupal.org it used to be the case that you had to put in a project application and wait for a group of volunteers to do a sort of manual review before a project was approved to be become a full project on Drupal.org and about six months ago we changed that so that any any confirmed user can now just go ahead and create full projects and we added new project signals on Drupal.org so that the evaluators of those modules can see whether or not they're participating in security advisory coverage or other things and we're really pleased with how those changes have gone we're monitoring it very carefully because the quality and security of Drupal modules is really important and that's something we wanted to keep an eye on but so far we're really just seeing positive signals so there was in the six month period following this change we saw a 58% almost 60% increase in the rate of project creation on Drupal.org anecdotally I've seen projects come back that had been you know so frustrated with the application process that they just didn't host their code on Drupal.org they left it up on GitHub or they didn't contribute it back at all and now those those modules are there for the rest of the community to take advantage of so we're really pleased with that change. Next slide. Let's hear the other note on that front just to just to give everyone some insight into this right the major concern there would be. Oh, if we have more projects do we have more projects that just don't receive security advisory coverage. We are keeping an eye on that the rate of change for those projects is only about half a percent increase over over about a six month period for for full projects that don't have coverage but do have more than 50 sites using them so that's the that's kind of our risk vector. And that's pretty small so we're pleased with that and we're continuing to work with a security working group on other steps that would help address this concern. So as I mentioned one of the changes we were making as as as part of revamping how project creation works is to change the signals for evaluators to project so that they can better understand which projects to use. So this is what a mature project page looks like for the project information that's provided. So for example you have your usage information you have an indication about security coverage. You have the recommended release and you have recent test results and a link to the development version for developers or contributors who might be interested in the project. If you look at the next slide. This shows you what it looks like when a project is still in development so again you see usage information you see a warning that the project is not yet participating in security advisory coverage. And instead of a recommended release you simply see just development versions so we want to make it really clear which projects are mature and ready for use and which projects are still still rolling still getting up to speed. If we keep going one more thing that we did composer is obviously in a huge part of modern workflows especially in Drupal 8 and so we want to and of course if you're using composer to build a Drupal site you aren't necessarily looking at Drupal.org project pages and therefore you don't necessarily see information about whether a particular release is included in security advisory coverage or not. So to make this easier and to support automated tools that parse this information we added security coverage metadata in the composer facade for all Drupal.org projects. So as you can see in this slide the next one and the next one there's now security coverage status information that is exposed to composer for all the projects hosted on Drupal.org. If we continue. Another thing I'd love to talk about one of the biggest things that we do as the Drupal.org engineering team is we support testing for the project and making sure that you know regression testing so that changes to core are known to work in all the environments that we support so that can trade works with the latest development versions of core and really it's a again it's another way to increase velocity for the development of the project as a whole. I just want to give some stats because it's kind of incredible how much we do I'm not aware of any other project that is as robust with the level of testing and test coverage that the Drupal community holds as a standard. So so far in 2017 we're up almost 17% year over year in terms of number of complete test runs that's over 200,000 test runs and each of those full runs within it may have up to 80,000 individual test assertions so it's just a tremendous unbelievable amount of testing. And you're so a supporter dollars help us fund all of these tests that keep this code quality. As high as it is we're also starting to see this reflected in changes in the landscape we're seeing Drupal seven tests decline as Drupal seven modules kind of. Roll off into mostly just maintenance mode and the attention really refocuses on Drupal eight contrived and on those modules, getting really up to speed a lot of them are moving from beta to stable release and just really getting fully up and running and I think we've seen that reflected and not just anecdotally but also in our testing data that that date is really taking over contrived attention. If you go to the next slide Megan. So one thing that we did just because the testing is such a critical part we you'll notice at the bottom of this image underneath the files table and the test results table and issues we now promote Drupal association membership and we may promote direct sponsorship of Drupal CI and testing for the project in the future so just wanted to give you a kind of preview of what that looks like. Next slide. Another feature related to testing again I talked about coding standards earlier we now we also parse code standards information so again just to make sure that especially for contrived maintainers or people who are making some of their first contributions. We really want to surface those. Harder to learn barriers to contribution like remembering how to get the exact coding standards and things like that right up into the test results where they're immediately there and immediately available to be fixed so we added coding standards parsing to the test results. Next slide. Another thing that we've done that we're really really proud of because we think again it's going to really help contribute keep up with core. As you know core is now in a six month release cycle so we have a new point release of Drupal every six months with perhaps new experimental modules new stable modules. With different you know additional new API is available and things like that and if you're working in the contrib space. You have to keep up with these changes every six months with your module and with your testing and previously if you maintain an integration on Drupal at or you'd have to go in and reconfigure your testing to say oh. Eight four kid just came out so now I need to swap things around so I'm testing for eight five coming up. But we've done is we've added semantic labels so now you just say I want to test against the development version of Drupal so in this case you know eight five X dev. And then if a six months release happens that allow automatically update so your testing configuration will chase the current state of core without you having to remember to go in and maintain and update your testing for the modules that you might maintain. Next slide. Yeah, and I think that's that's pretty much it. We have some more updates in the Drupal.org panel at Drupal con Vienna. I don't know if that recording is available yet but you can sort of certainly take a look for that or reach out to me. And if you have any questions feel free to drop them in chat or in the Q&A panel be happy to answer them. Or you can reach out to me I'm hestanet on Drupal.org and you can use my contact form and get in touch. That's great thanks Tim do any questions come up in the chat window. Nope looks like we're all good for the moment. Okay, well I want to thank everyone for listening in but more importantly I want to thank you for supporting the work that Tim's doing that was a long list of improvements that he's making both in terms of trying to connect businesses with the evaluators in the site and also improving the contract. So thank you so much for your contribution journey and providing the right tools and support that our community needs to keep the project moving forward and you know I'm just really excited about future things that they have coming up. Drees the Drees note talked a lot about where we need to go next and what markets we're going into. And how there are some people being left behind so it's like we want to go into ambitious digital experiences and we're going to need composer to support some of that work but some people are in other markets and they're downloading Drupal and they need Support and kind of being able to still build a site more manually and so we're looking at that. And then of course you know the issue credit system the the one that calculates contribution by individual and then aggregate aggregates it by company. You know that was built by Tim and his team and that's how we know by studying that that's how we know that for example Europe contributes 44% of contributes 44% of contribution right so it's a great tool but the fact that we can start expanding that to support non technical contributions really really key and also I know that businesses are often behind camps and so they should get recognition in more ways than just contribution or financial support as a supporting partner and you have just really so thankful for everything that Tim and his team is doing and it couldn't be done without the supporting partners funding their work so thank you so much. If you have questions. Reach out of course you can always reach out to me but you also have your account managers. You can ping us anytime on Twitter and of course be on the lookout for our monthly email updates Tim writes those every month to give you a summary of what's the latest work on Drupal dot org that you just funded. So anyhow thank you so much for joining us and we look forward to talking to you again by the end of the year. Thank you everyone.