 I'm going to be the timekeeper again as discussed at the previous board meeting. We're going to try and stick to these times, so please be concise and then save your questions for in the end and then use the questions box in a go-to webinar for asking questions. I think that would be great. Other than that, the agenda is in the board packet. We're going to do an operational update as usual, then quick updates from the different board committees. I'm going to talk a little bit about DrupalCon Latin America, an update on the elections, and quarterly working group updates. I believe that is it. Perfect. And then we're going to have an executive session as well. I don't know if we did a roll call to see if everybody's here. Yeah, we did a rolling roll call. I think, Elise, did you feel like we got everyone? Yeah. And you just joined, so. Yeah, I think everybody. Got it. I think we're good. All right. Then we're good to go. All yours, Holly. Thanks. Well, hello again, everyone. I literally feel like every month we just did this, but we're glad to be back. So in this month's board meeting, we're reviewing the month of February here, so I just have some updates to share with you guys. Bless you, Donna. Thank you. She's allergic to the half hour time zone. So some new news. This is not actually February news, but just to let everyone know, we did have three new folks start with us on Monday morning. They've all been coming back, so we're really thrilled about that. So Brad Fields has joined the marketing team as a content manager, so he's working really closely with Phil Poolebar and Joe on our content strategy for Drupal Marketing. Tina Cross joined us. She is our DrupalCon coordinator, so the DrupalCon team is now whole and functioning again. It's not that they weren't functioning, but I mean, let me walk that back. They are soon to be at a hundred percent. Quick question. Yeah. Sorry to interrupt. Is Jeff Walpole on the call or not? No. No? Okay. He's texting me that he's having trouble to join, so anyway, keep going, I'll help him debug. Thanks. Appreciate that. Tina Cross has joined us, and then Matt Zagawa has joined us as our chief financial officer, and that is an exciting new role at the organization. Brad's role is also new. He's hoping to help us push our financial reporting into the future, help us have better tools for forecasting and being more forward-oriented, and also overseeing the HR function under his CFO role. So three new folks here, and that is definitely taking up a lot of time this week, but let me go ahead and get back into February mode. Lots of great community stuff in February. So we held three Meet the Candidate sessions for Drupal elections in the month of February. We had over 100 people across those three different calls, which is really fantastic with lots of questions from the community. I just want to underscore it's been so great to have so many folks in the community engaged in the process, both as candidates and as participants. In terms of being on the call and asking great questions of the candidates, and the folks that are helping to promote elections over Twitter, et cetera, it's been really great, and we'll say a little bit more about that later. We also held a DrupalCon last month in Bogota, Colombia, so DrupalCon Latin America, and we'll have an update on that later, but I just want to point out that it was such a great bump in the community participation from Latin America coming out of that con. So we hope that we see lots more of that going forward. And Drupal jobs, just another highlight, had its best month yet in February. We had 118 posts on the site, $12,450 of revenue. And we were able to roll out two new features in February. You can now get an email subscription to new jobs. And you can get them as an RSS feed. So that really helps the job seekers find the right thing or know when jobs that relate to them come onto the site. So that is good. One other note about February is that we are looking to push our metrics reporting into a new place and make it more usable. So we have begun using a tool called Simple KPI. We're building out dashboards around all of our programs so that you can see those metrics at any given time. We'll make these publicly available in the end when we feel like we've got the right mix of things. This month, Drupal.org got all of their data in and we'll be rolling it out across the programs. So in the future, the board packets will not contain every single metric every month. We'll have these dashboards that you can reference separately and we'll use the board packets to raise issues that we need to talk about. Does that make sense? Yep. OK. So that's the plan with that. Just want to point out. Couple of other quick updates on the Drupal.con side. We'll get more on Latin America like I said later. LA is in full swing. And this week, Amanda Gonzer on the content is getting out the messages to folks who sessions were accepted and then sessions that were politely declined as well are going out. And we'll have all the sessions up on the site next week, which is always an exciting week in Drupal.con history. Also, early bird ends next Friday, 27 March. So that's a big time for us in ticketing. We see a big percentage of overall con tickets happen in that week, and particularly on the last day, which is, I think, a great explanation of human behavior. So that's going to be a really big week for us. It's been very toxic age. We are at in ticket sales so far because the con site launched later than we launched Drupal.con Austin, for example. But after we get through the early bird date, we'll sort of have a more apples to apples look and know where we're at. One other quick note about LA is just one of the things that you know that we do is provide blocks of rooms at hotels at a discounted rate for folks that are attending the Drupal cons. And I just want to point out that it's important for folks to stay at those hotels because it is part of how we get a deal with the Convention Center and the other resources that we use. And all of our pricing is tied together around those. And not staying at those venues could have financial consequences for the show. Again, early bird week is next week. We think that a lot of pickup at the hotels will happen around that same time as well. But just we've noticed more and more big blocks of rooms going to other hotels, particularly sponsors and whatnot. And I just want to encourage everyone to really look at the hotels we're staying at. Even if you want to arrange your own block, we would love to work with you to help arrange the right pricing for that block. If you're staying in the venue, we can get credit for that. And that's really important to us. So I just want to say those words out loud. Well, there's a question on that. I haven't looked this time, but quite often the official hotels are really pricey. Do we work to put budget options in the mix? We do. Yeah, we have one that actually has a fair amount of availability right now that's aimed at more the budget traveler or the student budget level. So there are rooms for about $120 to $130 a night, which is super competitive for Los Angeles. Right. It's still a lot. But yeah, cool. Thanks. Yeah. So we do try to provide a mix of hotels in terms of pricing and amenities and all that good stuff. Couple quick things on Drupal.org. Just to let you know, there's a big step forward on the first area of the roadmap, which is streamlined account creation, or use, sorry, Oregon use, yeah, streamlined account creation. So there were lots of improvements to account creation process in February that were rolled out. We think we've got a good process now that is more useful to the user. Also is going to get us better data about that user and is also going to keep the robots out. Hi, robots. We also added newsletter signups as part of the process now. And so that's great. We're starting to integrate more of those communication channels with our community on Drupal.org. In fact, this Thursday, we will send out the first issue of the newly revised Drupal newsletter that has not been sent in six years. Yeah, and we're really excited. We have a great partnership with Bob Kepford. And we're working with him in basically what I'm looking for. Syndicating. Yes, the Drupal, the weekly drop content there. So we're really excited about that. We also got issue comment attribution launched. That actually happened in March, but I'm sneaking it in because I want to say it out loud. We did a lot of work on it in February, and it launched. It launched in March. And we've definitely been watching folks and how they're using that at this point. So right now, people have been actually going back in time and applying attribution to comments from the past as well, which has been interesting to see them do that. But according to a data poll this morning, we've had 47 employers attributed about 1,098 times. So it's starting to go. Is that for core or is that for contrib as well? It's for all projects. Yes. All issues. All issues, all projects right now. And do we know if that's for D7? Can we look at it that way? D7, D8? We could if we did some additional querying specific to the category of the issue. So there's some specificity we could add there. That would be great. I know a lot of the attribution in the first couple days was actually in the issues that were related to adding the feature. So I would say a good chunk of them are all around that. Right now, Drupal Association is in third place overall. I'm just going to put that out there. We've been attributing a lot. That's funny. Good. And then just some random bits from around the organization as well, just on the D8 marketing side. People have been, we've still been very focused on highlighting what can be done to help Drupal 8 get to completion. Jess Mirpo's graph from her blog post a few weeks ago has been really helpful. And that message has been very popular with folks. So that's great. On the revenue side, we launched the Perfect Audience Extension product on Drupal.org in the month of February. And we are prepping to launch a tri-Drupal program, which will be a great advertising platform for hosting companies. But also, and this is where we love these programs, these revenue programs that help contribute to funding but also help drive the projects forward. This should also be a place where we can actually help drive Drupal adoption as well. So we're really excited to get that launched shortly. And I should see that in the month of April. We're running just a time check that we're officially almost out of time for this section. Totally perfect. I just closed my notebook. I have no more words to say. Awesome. Any questions? No? All right. I'm going to move on to the board's committee. Great. Let's start with the revenue committee. And I need to just open up Megan's microphone. So give me one second to do that. OK. Megan? Hi. Can you hear me? Yep. Yep. Awesome. OK, I can make this short. And the revenue committee did not meet in February, but we did put out a, just an update that I can share with everyone. There's just some really great highlights that the G8 Accelerate fundraising campaign. First phase of that kicked off thanks to the board members for being anchor partners and for the others that joined this initiative. And I'm sure there'll be more about this coming soon. But it's really exciting. And also our co-marketing event. We're going to have two this fall in Europe. Sponsors are going to be coming with the Drupal Association to two events to market Drupal. And we started sponsorship sales for that. And we've gotten some really strong pickup. And I'm really excited for that. So you'll be seeing us at D-Mexico in Germany and Festival of Marketing in the UK. So we'll have some more updates on that initiative in general. But so far it's looking really great. And Megan, what were those two events in Europe? D-Mexico and Festival of Marketing. New Mexico. D-M, sorry. I have a little cold. So D-M-E-X-C-O. I think I got that one right. Oh, D-M-E-X-C-O. That's all right. I'll get it later. Sorry. OK, OK. And then also we're just keeping an eye on what right now is we focus on Drupalcon LA ticket sales and sponsorship. We're also keeping an eye on the Drupal jobs and the supporter program. That was just a little soft in February that we've been working with our new lead generation role, which has been filled by Phil Bulbar. And looking to see what we can do to really increase our pipeline there and get that back on track. But other than that, things are looking really good. And we're excited to work with our new CFO match, where we're going to be modeling our revenue growth and really excited to have his expertise and staff and start working with them. Thank you, Megan. Governance, is Matt on the call? He was. Yes, not. Have you enabled this mic? Yep. Maybe it's just Mike. No, I didn't enable his mic. He has a question for me. OK. Well, let's move on to finance and then maybe circle back to Matthew and maybe Zalane. Finance committee met last Friday to review the January and February financials. Nothing major to report. There's some work that needs to be done that continues with respect to getting a merchant account in Europe for us directly. There have been some delays on that, but nothing that should impact our ability to do the next European Drupal Con. There's contingency plans in place. Also of note, the DA team was able to close the February financials on time, which was awesome. That's a huge improvement. And so big thanks to Chris and Leslie and Elise and Holly for doing that. So we reviewed January and February. No big concerns. It was our last meeting without Matt. So we're really excited to have him join us on the finance committee, too. Awesome. I'll go next as the executive committee. So we have been working on Holly's performance review, and Holly has also been working on hers. I think we're pretty close to wrap that up, but we have to do a little bit more work and then deliver the performance review. Let's go, and that's it for the executive committee. Let's move to marketing and then see if Matthew is online for governance. Sorry, we were just looking at the app, but Joe, we'll go ahead and give it to you. Yeah, I spoke with Gina two days ago. I know that she has been working on rounding up the committee and actually finalizing the members. She has done that, so she has a committee. And I believe she also has a date set now for the first meeting. I'm not exactly sure when that is, but I'll find out. But now that she actually has a committee formed and a meeting scheduled, she's going to formulate her plan along with the committee and then we'll start to execute. Thank you. And then I don't know if we were able to un-mic or locate Matthew, but. Oh, wait. Oh, he must have rejoined. OK, hang on. I'm unmuting him, hopefully. Dorothy, do you want to try one more time? We must be having technical difficulties. I will stay on his behalf that he did send an email out today to follow up from an item we've been talking about for a while. So if you want to check your email and respond, that would be awesome. He just IMP me saying he's muted, so I don't know. I opened his microphone, but it's just then his mic disappeared. So it looks like we're just having some technical difficulties. That was Sameer. That was Sameer. Oh, thank you. Could not hear. Yeah. Well, I'm not sure if we have enough time to actually look at the document and report on it. Oh, I think we said that we could handle that offline because we discussed it publicly, and then we figured we could wrap it up via email. OK. That works. Any other questions on any of the committee's updates? Was that a question, Sameer? I wasn't sure. Sorry, you're cutting in a little bit, at least for me. Did it sound like it? It's a bit from the governance committee. All right. Thank you. All right. Well, then let's move on to the triple con Latin America rep. It's a 15 minute presentation. Awesome. Rachel. Yeah. And are you actually going to wrap it? I am. I'm going to freestyle wrap it. Good. Getting towards the end of the day. I need some entertainment. All right. Are there any, like, cipher salad and salt and pepper? Salt and pepper. OK. You're already not wrapping it. So we had triple con Latin America in February this past month. And just briefly. So this is kind of the agenda of what will run down their goals and KPIs, the attendance, financial information, the content of the conference, some feedback we got, and then summarizing everything and moving into the future. So going on. Goals, obviously, for triple cons are to grow and strengthen the community, accelerate the project, promote triple as a marketing and market it as a platform, and generate funds to further community program work. So here are our KPIs related to triple con Latin America. In the center column, you'll see what our goal was. And in the right, I put in what our actuals were. We obviously came in a little bit under as far as attendance goes, but we were able to renegotiate some contracts and some purchase orders and kept our expenses in line with what our new attendance was. And so we managed to come in under our net revenue goal of negative $99,000. We came in at negative $83,000. So that was a great surprise once we balanced all the books at the end of the month. Go ahead. And so let's talk about who showed up. We had 263 people attend, which was great. We had pretty much one-third of the people in that photograph had registered before two weeks out from the event and about two-thirds registered in the last two weeks leading up to the event. So as an event organizer, that was not stressful at all. We basically saw a similar breakdown as what we see in other conferences as far as where people are coming from their job function. We saw a lot of developers, but we did see a nice slice of our other job types. Fantastically, 48% were triple association members, which is a really great number for us, so we were excited about that. We had a higher than Amsterdam percentage of female attendees, but a little bit lower than Austin, so it kind of split the difference there right in the middle. Amsterdam is usually what? Amsterdam is 11? Yeah. But still above what the industry trends are for tech conferences. That's good. People were kind of across the board as far as their skill level, although, again, it really closely mirrors what we see at other conferences. So that was kind of another great way to reiterate that this was very much like any other conference. It was just on a different location and a different scale. So we have people using Drupal in a variety of ways. We had quite a few Drupal shops show up, which was really kind of cool. I know that it was a great place for people to kind of connect in not only just Colombian companies, but obviously from companies all throughout the region. So more shops, fewer site owners. It'll be interesting to see if that plays out. That same trend plays out in other countries. Yeah. So not an opportunity to be a true marketing event, these cons, if that's the way they trend, right? Yes. Yeah. And we did a really good job of representing the region and the world. We had 23 different countries represented in four continents. We had 12 different Latin American countries. And our most populous attendee country was Colombia, if you can believe it. So we had 90 Colombians there, which was great. This kind of gives you a little bit of a view of where everybody came from. We had people from as far away as India and South Korea, quite a few different countries in Europe, and the US sent quite a few as well. So the financials. Again, this is kind of breaking, well, we're going to each of the different line items, but overall the income came in a little bit under with our lower than what we had projected attendance. But again, we were able to keep those expenses in check and renegotiate contracts, so that that didn't run away from us and we didn't end up greater in the hold than what we had projected. So overall things came out pretty great. We had $41,000 in ticket sales and $62,000 in sponsorship. We exceeded our sponsorship goals. That was wonderful to see people really step up and want to engage with the local Latin American community. And again, it was the 37% that came in the last few weeks. I mean, first inverted those numbers earlier, but a lot of people came in the last couple weeks, just similar to Amsterdam. So it was kind of interesting that our last two conferences had both seen massive registration surges in the two weeks leading up to the conference. So please don't be a portent of the future. Yeah. Counting of our expenses. So our overhead of staff wages is our top line item. And then obviously we need to feed people and we need to get our crew to the event. We had event planning services that helped us with contract negotiation and contract negotiation and venue selection. And then registration materials. So that's things like your program guides, your t-shirts, your tote bags, things like that. And then we did offer grants for scholarships for speakers who were able to apply for, I think, up to $1,000. I can't remember the exact amount, maybe $600 and money to go help them get to the event, which was great. So it's $7,000 allocated for that. And... Okay, I'll start. Sorry. Okay, and then one of the really great things we did with this con, which I don't think I've done for any other cons, was we offer translation services. So in the plenary room, which had sessions throughout the day, we translated the sessions into the two other languages. So with someone who's presenting in English, we translated it into Spanish and Portuguese. So that was great that everyone could experience the keynotes and understand what was going on. And then everybody could come in and find a session in their native language in that room. And that was a free service that we provided to the attendees. So it was really well received. The rest just kind of details some of the logistics and production things, space, Wi-Fi, designed for the site, and program guides, things like that. So let's get into the content. We had some pretty highly attended sessions. We had four concurrent sessions. I'll let you just kind of cruise through that list if you're interested to know which were the top 10. This is those. These were the. These are those. The YouTube views. So we had, since we had a smaller than average turnout overall, we kind of as a direct correlation had a smaller than normal turnout for survey evaluations for the sessions. So rather than showing what the responses were from those approximately 13 people who filled out the surveys, we thought we would show which sessions had been the most popular on YouTube. And so this is kind of the rundown on which ones have been most widely viewed. Yeah. And so we had again about 5% participation on the evaluations. So these are some of the observations that we received as far as sessions and content goes. The translation services were really appreciated. Some of the sessions in the other session rooms were presented in, you know, Spanish and Portuguese. And people, we did have, I think, one session where people translated back and forth. They had a friend come up and help them work their way through the presentation. We heard great feedback that the content was just as good a quality at any other triple con. And they were excited that the con was really, you know, delivering that same experience that they felt when they went to ones in North America or in Europe. We did hear a little feedback that there was an interest for a few more business-focused sessions. That was interesting. And we were also pretty excited that we had speakers from a variety of countries and we had a higher than our attendee ratio level of female speakers. I think the screens were actually one of the most aspects of the con. We had a whopping 38.4% of conference goers attend the sprints, which was just wonderful. And if anyone was on site, we had a little bit of a wireless internet issue for the first couple hours of the sprint. But people did a great job of just kind of rallying together, you know, working on things that they could offline. And once we got that Wi-Fi backup and running throughout the whole building, people were just off and running. And it was just a really great turnout. It was a really fun day. We had to kind of help people leave at the end of the day because we needed to let the hotel staff go home. So it was a really great day. But we had a lot of feedback that people really enjoyed the size of the con. So it was a little bit more of a personal feel. There wasn't quite that overwhelming crush with people all around you. So it kind of fostered a little bit more of that developing those personal connections with people that maybe they haven't met before or hadn't been able to come together quite like this before in Latin America. So some of the feedback that we got from the survey, so the top three reasons for people to attend this con were personal networking, the session content, and then there was a tie between business networking and speakers. The one thing that exceeded expectations was personal networking. And ironically, we had three people say that they were not able to find a job and three people say that they were not able to hire for a job. So I think you could find those people and connect them. Satisfaction levels came out as far as the various activities related with the con. People were pretty satisfied with the communication that we provided. They really enjoyed the networking and sessions and loved the keynotes. And the sprints were really something that people... We had a lot of really great feedback about the sprints. The least useful was BOFs. I think that was kind of something that wasn't maybe emphasized in the right way or was something that wasn't promoted enough. So this was some really great feedback that we got. We had zero people say that there was less value than what they expected. And so that was really kind of cool. We had the majority of people say that the value was somewhat more or much more than what they anticipated for the ticket price. So that's a really great reinforcement that it was a great event. So the smallest slice of the pie here is this somewhat less value. There's a couple snippets of feedback that we got. For the most part, the feedback was pretty positive. People really loved the keynotes. They loved the size of the con and that they were able to connect with new people. I think people really appreciated that there were a lot of languages flying around and that it was kind of a fun thing to try and connect with people who were two different native language speakers trying to connect with maybe their second languages or third languages and it was just kind of a fun environment. We heard some feedback from more vegetarian options on the food. And soundingly, it was one of the promoters' scores of any con. That I've ever seen anywhere. People loved Dries and Larry's keynotes. They really enjoyed Sprint's and Tejo was pretty much the unsung hero of Drupal Con Latin America which was one of the social activities I think on one of the first nights. The only real kind of critical feedback that we received at this point was that they wanted even more social events. So they wanted more of it. And so that was one thing that they really reiterated. They wanted more parties. I will just add the caveat as much as I'd love to say. Our net promoter's score was 80 everywhere. Just add the caveat that we had a small conference to begin with which makes your sample size hard and then an even smaller number of respondents to the survey. But we're going to take this 80 and put it in really big con anyway. So overall we found that Latin America came. They came to the con and showed up. And everybody had a great time. It was a great hit. And the sessions were considered to be top quality and were really appreciated that they were translated into three languages. We had a really remarkable donation by Lingotech. They took, I think, 25 of our sessions and translated them into the other two languages for our YouTube channels. So it makes that reach even further. So people looking for these sessions in English, Portuguese or Spanish can go online and find those languages and find those sessions in those languages. Again, sprinters turned out like no other con before. We had such a great turnout for sprints on Thursday. And we did have moments of internet connectivity issues particularly during the first hour or two of the sprints. Overall the Royal Park worked really well for our needs. It was a little bit of a fun layout as far as getting from one room to the other but the staff there was really helpful. Internally we found lots of learnings about the triple con and emerging market. Things that we can pull in as far as internal planning but also community engagement and making sure that we are just kind of tightening things up as we continue to grow this program. Awesome. Thank you very much. I was there and I thought it was really well run and executed. So thanks for all the hard work to put in our first conference today. Thanks. That looks like we have questions real quick. We have a couple of minutes for questions. A question from Angie. Should we make last minute prices much higher to encourage earlier registration? Yes, we do that a little bit as of now but that's something that we could always exploit maybe a little bit more. Kind of boost that ratio. Right now we kind of continue the same pricing proportions year to year and from con to con. We could look into. If that trend continues, we're going to want to really incentivize early registration. And the other, Donna has a comment. Having vegetarian food is a default as triple cons. I love that idea, Donna. I know that's a really great way to reduce the carbon footprint and something we can definitely look at. The food is always one of the touchiest subjects with con. That's something that we hear about whether people love it or prefer something else. I think that's a really cool option for us to explore. We could try it on a day, right? Try one day and probably not a lake because we're already there. I will say for the North American con one of the most popular food comments for special dietary needs is more bacon. Well that's because bacon actually is a vegetable. Oh, okay. The thing about all the veggie through default is that you don't want meat. But you have meat on the side rather than meat in everything. Yeah, yeah. Is there other questions? That was it. All right. Awesome. Thank you. That was a great update. So the next section is an update on the elections. Yeah, and I can probably do this in under five minutes. But I just wanted to remind everyone in this public space that voting for the elections closes on 20 March. So that's this Friday at midnight UTC, which we've discovered is not 4 p.m. anymore, but 5 p.m. Pacific where we live. So at 5 p.m. Pacific on Friday we'll be rolling, turning the voting off. Right now we've got 1,300 votes in the system. As a reminder, last time we ran elections we had about 660 votes total. So it's a good turnout. Like everything else the Drupal community does, all the voting will happen in the last day. We'll get lots more votes is what I'm trying to say. But we've been really pleased with the turnout so far and the enthusiasm from the community. And just as a reminder for the board, once we turn voting off we will go ahead and run the data through the open STV software to determine the winner and I'll be sending that to you via email for you to ratify so we can make a public announcement on 25 March. Any questions about that? Easy peasy. Alright, awesome. Next up is updates from the Drupal.org working group. The content working group, the software working group. And the infrastructure working group. We're going to get three quick updates. Sorry, did I not say that? So we're going to get updates. Any other questions? The format's going to be a little bit different today due to coming off of basically being the first quarter of the year. Not all the working groups were able to meet multiple times and prior to this meeting. And so what we're doing is we're actually combining it as a kind of a single update from all the working groups and George and I tag team this so that everybody gets a little bit of staff and a little bit of working group participation here. So this is the current working group breakdown, just as a reminder to everyone who sits on which working group. And as a kind of a quick review of what was done in the last quarter, one of the big priorities in the last quarter was to take a look at charters and go through those and do some reviews and recommendations. We'll go through that in a little bit more detail here in a few slides. We also had our second quarterly working group meeting and that was a very, very successful meeting. We were able to review the content model from the content strategy project and more information from that is going to be shared here in the next couple of weeks but it was a good opportunity to get great feedback from a variety of working groups. And then we also did a little bit of planning in that meeting to talk about what we want to do during our Drupal Con Los Angeles working group half day. So when we have that face to face time being able to take as much to get as much out of it as possible. So the quarterly working group meeting, one of the things that came out of that that we talked a bit about was that we really need to communicate and prioritize possibly with all the working groups. We invited the documentation working group and the technical working group to the February all working groups meeting. We had representation from the technical working group there. We also have representation from the community working group and the form of members that are on the content working group and on the software working group. And we talked a little bit about how really we should probably include the security working group and that invite as well because if we're really going to hit the group of advisors who can give us the features that we're going to prioritize we really need to extend it out to this larger group. Part of this came from kind of a conversation of when I started the scope was to strictly work with the Drupal.org working groups and what we've seen in practice is that actually created a bit of a rift between some of the working groups who didn't have an opportunity to feel involved. So one of the steps that we've taken is we've intentionally reached out and myself and Tatiana have been attending the documentation working group to hear their needs and integrate that into the prioritization process. It's not too late but there was definitely some hard feelings around how long it took to bring them into that conversation. And one of the things that was a clear takeaway from this is that the content strategy project as a whole would have benefited from earlier involvement, particularly from the documentation working group. This is what I get for letting Holly run the mouse while I run the keyboard. Sure, blame me. So it was like five feet away from me even my long arms getting reached. So I just explained our entire working relationship. Right there, yeah. So whenever the working groups were put together and that governance was presented this was kind of the original layout. And Georgie we're going to talk to this a little bit and kind of talk about some of the background of why it was struck. Yeah, a little bit. So thanks, Josh. So Josh asked me to help present these next few slides. As someone who serves on both the content and community working groups, I can provide a little bit of background and context which many of you will already be familiar with. But basically the current governance model goes back to this some of the sprints that Dries led back in 2012 and out of that those sprints came proposal for two sets of working groups. One set that derive their authority directly from Dries and one set that derives its authority from the Drupal Association Board. So the specifically the three Drupal.org working groups were chartered in 2013 and that's the software working group, the content working group and the infrastructure working group. And their goal was to collectively serve as the product owner for Drupal.org until we were able to hire a full time CTO. So if you go to the next slide you'll see that as it plays out there are some shared responsibilities between the different groups. Even though for the most part the charters have been written in such a way that kind of precludes that so for example as the chair of the content working group specifically says in our charter that we're not responsible for anything that's documentation and we're not responsible for driving marketing. The reality is that the work that we do in the content working group absolutely touches on those areas because we are responsible for the overall content strategy and an experience of Drupal.org which includes documentation and marketing within it. And so that's always been a little bit of attention with the current model. If you go to the next slide you can see a similar issue with particularly the infrastructure and security working groups. I'm not as personally familiar with these but also as well with software group technical working group basically having to do with the different kinds of developer tools and features that are available on Drupal.org and you know and these different groups even though they have separated responsibilities do have kind of a common stake in the outcome of some of these efforts. So if we want to skip to the next slide then so here we are now we now have a CTO who has been on the job for about a year now and it is time to revisit things. So big item number one of course is making sure that there's better communication and coordination between all the groups. So as Josh said starting this year we've been having quarterly meetings the plan is to have two of those in person at Drupalcon two of which will be via video. We also now have an all groups listserv that we're able to share what we're working on with each other and keep everyone in the loop. You know there's some other things that have been going on as well. Obviously Josh has been present at all the content working group meetings and I'm sure other working groups as well. Tatiana also serves on all three of the Drupal.org working groups and so there's a fair amount of staff involvement and coordination with that respect. And then we also all the working groups also participated in the process for kind of helping put together the prioritized list of features that roadmap for Drupal.org I think that process probably needs a little bit more refinement but it is definitely an opportunity for all of us to work together and sort of validate that we're all on the same page. And then I know there's also been some work that the software working group has been doing to kind of streamline their process as well. And I can go over that in summary. The software working group has merged its leadership teams. We used to have community tools leadership team developer tools leadership team and then a localization leadership team and what we were finding is one it was very challenging to get all the meetings scheduled because that was a lot of additional meetings where there was a lot of overlap and many times the people that were participating were participating because they had a particular community initiative or maybe even a strategic initiative that staff was working on that they were focused on rather than updates for all of those projects they were more interested in just having a good way to communicate. So one of the steps that we've taken is we kind of pulled them all together into a list of advisors and we're going to start using them as part of our notification whenever we have a particular feature that we really want feedback from a group of active community members who have been involved in these discussions over time. So if we want to move into the next slide the other thing that we've been working on in the working groups the Drupal.org working group specifically is updating our charters to better reflect the real world role that we play in terms of our interactions with the CTO and the DA staff and the way that process works is that each working group got together met. We suggested our own changes and then we worked with the staff to make sure that the charters were as consistent as possible and made the most sense. And so the biggest kind of change overall is that instead of as in the previous iteration of the charters being directly responsible for execution on our various areas of jurisdiction we now serve more of a community advisory role helping provide Josh and the staff with the context and the expertise and just that kind of community experience that's necessary to make sure that staff is executing on various initiatives in a way that not only meet the needs of the project but are also consistent with the values and expectations of the community. And yeah, and that's my bit. For next steps on the charters, one of the requests that we're making to the board is that you review them between now and the next board meeting. If you provide us feedback during that time we'll work with the working groups during our next working group meetings to incorporate that feedback and then we'll put them forward for a vote in the next board meeting. And that feedback is comments in the documents. Comments in the documents would be great. One last bit of update from the working groups and this comes out of the strategic initiatives that I've talked about a lot of times at this point. What we've realized is that we've actually had a little bit of I won't call it scope creep but I will call it an expansion of really what we are working on and wanting to recognize that. We're updating the roadmap to kind of show this expansion and to describe it a little bit more. One thing that has definitely taken up more time than we had originally planned was Drupal Events. I will say though, I think we've got a registration process that may be one of the best conference registration processes out there. It's really huge improvements. Also the design is phenomenal on the LA site. If you haven't had a chance, please do take a look at it. The content strategy and design project we originally called this the responsive redesign of Drupal.org and really we're incorporating our content strategy work and the ongoing work that we're going to be doing from the design system and this is bigger than we can really represent in a single initiative so this will likely be broken out into some smaller initiatives as we go and we're going to need the working groups help in prioritizing those and making sure that the content strategy work that we're doing is being influenced by all the working groups. We also are recognizing that infrastructure stabilization has taken on a huge role in our work. It's not certainly not as a percentage of our time. This has not been huge but as an importance. It's something that is ongoing. We're trying to whenever possible give ourselves independence from the OSL services and that's so that we have the most flexibility and where we host any given service. So a good example of this would be the migration of mailman mailing less to the MailChamp newsletter service. We can get a better quality of service, better reporting. We've done similar things in terms of doing some of our own independent monitoring which has given us more options for tracking things in our infrastructure and making sure that our services are stable and also in things like the CDN and the recent move of the FTP infrastructure over onto a CDN as well. All of that is giving us a more stable, more independent platform that we can tweak and make perform the way we want. Drupal CI which was definitely a community initiative and our previous prioritization. It's been requested that staff help in getting this over the finish line so that we can get it out of the way as a Drupal 8 blocker. So that's definitely worked into our plate and we've got an upcoming sprint on that actually just two weeks away. Localize.drupal.org has also been something that was a community initiative and Gabor and Sebastian have actually asked for some help in getting that across the finish line. So we're in the next month or so we're going to be applying some staff time to help finish that upgrade because it is also a plate blocker and so it's critical that we get involved in that. And then one of the things that we had on the list but is definitely changing is the update of Drupal groups. The content strategy is going to end up affecting this. So we're trying to pull together in the next month a group of long-time maintainers and or community members that have been participating in Drupal groups that can help us make some decisions about the ways that we want to change the content structure of Drupal groups to make it a better place for our user groups and our local user groups and our interest groups going forward. So that is the summary. Looks like we have one comment. A comment that I put in? That is yours, Dries, go for it. Sorry, I can see the questions but we have about 8 minutes left for discussion if we want. I was just going to throw out that when we created these charters we kind of did the mall thick soup over many months. It's not unlikely that we didn't think and that we find these things in practice may not always work as smooth as they could be working. Some of the recent challenges I guess around related working groups or content related working groups but I mean the documentation working group the D2DO content working group so not entirely surprising I guess that these things may not end up work perfectly and so more than happy to revisit these things as well like even if there was more dramatic proposals so to speak in terms of how we divide things differently or how these working groups work together or maybe potentially merge these working groups I don't know what the solutions are all I wanted to throw out there is that we can think differently about them and make more radical changes if that is what we believe is useful so that's my comment right now. Thanks Rhys, yeah we definitely speaking again strictly for the process that we went through in the content working group we actually did when we got the heads up that we should probably go back and revisit our charters now that the landscape had changed which is welcome for us we did go back and we had a couple of private meetings that the staff didn't participate in and some offline communication where we sat down and said okay let's you know let's think about this really seriously and what changes we might want to make and where we ended up coming to is where we're at so I think the nice thing about these at least our charter changes that I feel like it gives us a little bit more flexibility that we're not quite as our role is not as strictly defined as it was before so for example we in the current version of the charter we're supposed to come up with we are responsible for every single policy that's applied on Drupal.org and that actually is pretty time consuming and it was something that ended up being a distraction for us from our kind of larger strategic goals and you know and we and now as a more advisory group you know we can certainly review and advise on strategy and that sort of thing but we're not responsible for drafting it which means that we can take more time to focus on bigger picture, bigger impact initiatives. Awesome, well thanks for the leadership there and getting people together so that's good to know. I'm really excited about the quarterly working groups going forward and bringing in the other working groups to have a voice I think we're not at the point that those working groups I think necessarily need to go through the same charter revision process but it will definitely give them a seat at the table and helping prioritize the work that staff is able to spend time on and I think that active letting them have a voice and letting them get heard is going to be much more healthy going forward so even without changing any real structure I think it's a positive step and it makes it easier for me to communicate change as well because we can go faster if I have a clear list of people that I know if I have their feedback then I would go ahead to work forward. Awesome, and are you guys going to how are you going to submit updated charters for us to review? In this slide deck if you move back to the Drupal.org working group charters those three are links that take you to the software working group the content working group and the infrastructure working group charters you will notice that they are written very similarly which is kind of awesome given that they were actually written separately we helped compile them so I won't say that there wasn't some wordsmithing in that process but I think all the working groups came to very similar conclusions without a lot of difficulty so there's some definite themes that go through all three of those I will send direct links to those out to the board list as well so you guys don't have to go digging for them later Awesome Alright, well we're kind of out of time we had an 8 minute delay in the beginning but say one other quick thing there's an email threat for the different board members around the board we have to take a vote on where is it again revising the charter to reflect the the term limits correct, thank you we'll do that vote in email the number of us have already voted this is just a reminder to check your email and to vote alright, well is there any other general questions if not we can adjourn and move on to the executive session see you guys there, thank you alright, thank you