 We're going to kick this off, actually the easiest job of this meeting, just wanted to welcome everybody. We have board members here, maybe raise your hand if you're on the board, so people know. Then we have some board members on Zoom. We have actually former board members as well, maybe raise your hand, or at least two, there is exactly two, and then obviously we have a lot of staff as well, so maybe raise your hand if you're staff, awesome, so then we have a lot of other people. This is our first public board meeting of the year, and so what we'll do today is we'll ask for a, or we'll give an operational update on some of the things we've been doing, and then in the end, there will be time for Q&A, so we'll leave enough time for questions. Any question doesn't have to be about the operational update, but any question about the Drupal association and the work we do, you're more than welcome to ask, and I'll pass it to you. Great, so, oh this is good, I'm recording this, so if I start to sit down it's only because I don't want the people who will watch the recording to be watching my belly button, so, but I am really excited to have this public board meeting, it's my first one here in North America, and I have been in the executive director role now for, well almost a year, just under a year, so it's very nice to be able to just share our messages and everything that the staff has been doing over the last couple months, but it's also just as important for us to have these face-to-face conversations, so I'm looking forward to the Q&A too, and so let me just go through the agenda, okay, let's move that down, so the agenda for today, just for those that are new, we have our standard board packet, it's nothing new, let's see, I don't want to share a screen, I can do that, let me share a screen for those that are watching, great, good, so it's our standard board packet, nothing's changed over the last, really the last couple of years when Holly Ross set this format up, so we, but just for those that are new to it, we have our agenda, we identify what committees we have and what board members are in those committees, how to participate, we have our committee updates, we've only had recently one committee meet, which is around finance, and just for time's sake, I'm going to make this public and you can read those kinds of updates on your own, and then we have operational updates, just what have we been focusing on in different areas around DrupalCon and Drupal.org, we talk about the highlights and also where there's been some challenges that we have our eye on that we need to focus on, so I'll let you read all of that on your own, we also have a dashboard of our work about the different key projects we're working on, as well as the metrics, and then I give an update in these packets of how we're doing, and so this is another thing you might want to go and read after the after DrupalCon when we all have like our brains working again, and so what's, I mean what I like about it is that we just try to be really transparent about where are things going well, but also you can see I just kind of stopped here on some red, like where are some areas that we really need to improve, and so you know it's good for us to be really honest about opportunities for improvement, but also areas where we can really celebrate successes, and it's always all of our successes because we always achieve anything we do together with the community, and so what we're going to do today is focus on the operational agenda that is in the orders of business here, we're going to hear from the engineering team about a couple of their recent milestones, we're also going to hear from Carrie Lasina who's our director of revenue about the industry pages that we recently launched, and then we are going to hear from Rebecca, and so she's going to talk about DrupalCon branding, and then I'm going to talk about what we are doing with our community challenges right now and how we are bringing everyone together through community discussions. I've asked Whitney Hess to come and give a brief update to the board, she's the one who's been mediating those discussions. I'll ask the board if they have any questions, and then I'll open it up to all of you for your questions as well, but I'll see if there's anyone on Zoom who would like to ask questions through that, and just a heads up, I'm going to make sure we get through all of this, and I want to make sure we leave enough time at the end for Q&A, so if I do say that, if you see me telling a staff member like either we're gonna skip this one or make it shorter, it's only because I want to make sure we give the community the time to ask the questions that they have, and again all the presentations are linked into this document, so we can always go back and you know you can see anything that we might have to skip over. All right, and with that I'd like to introduce our director of engineering, Tim Lennon. You will give an update right here. Hi everyone, I'm gonna go ahead and give an update on Drupal.org, let me see if the presenter wants to come up. I'll give an update on Drupal.org, and I'd like to talk about kind of the journey from Dublin to Baltimore in terms of what we've been doing since the last public presentation about Drupal.org and the work that we do. We're gonna start talking about the project application process changes, and the revamp that was recently not quite completed, but the significant changes that have happened to that process. So basically we're gonna talk about how the old process of having to apply to be able to create full projects and release on Drupal.org has changed, and how we have a new security advisory opt-in process for projects on Drupal.org. So we undertook this project in four phases that were pretty critical. One was making sure that as we made this change to allow anyone to contribute projects to Drupal.org without an application process that we preserve important signals about those projects. Security advisory coverage signals, providing tools to allow the security team to manage that process, but they have an opt-in process and can manage the workload of new modules that are receiving coverage, then opening the gates to allow any user to promote projects to full projects and create releases for them, and then to build tools that will help provide code quality signals, because we want it to be easier for new users of Drupal to discover the best modules to use to see signals, not just about security, but about code quality, about testing coverage, all those sorts of things, and we want to incentivize code review. So we're on that last step right now. We have already opened the gates, but I'll talk about each of these in a little bit more detail. So the security coverage signals we've added, if you maintain a project or use projects on Drupal.org, you've already started seeing these. We added the shield icons to indicate which releases on projects are stable releases that receive security advisory coverage from the security team to help keep people informed of those. We also added some signals to indicate when projects don't have releases that are covered and don't yet have stable releases, and we're working on a core patch to provide some of that signal within Drupal. We've also updated the advisory coverage process to be an opt-in process. The maintainers of projects can work with the security team to be able to opt-in their projects to receive security advisory coverage now, and something they'll do from their project pages. And finally, we want to provide some in-place messaging for all the new project maintainers on Drupal.org to understand what it means to cut a release of their project. And so we provide some messaging whenever you go to make a release to encourage people about making a stable release, about opt-in security advisory coverage, if that's what they want to do. So that was phase one of this project. And then with all those signals in place, we went ahead and opened the gates. And so we've actually seen a pretty significant uptick in some new projects being created on Drupal.org. We've seen users who have had accounts, brand new accounts, able to make projects for the first time and some users who've had accounts that are nine years old that made their first project. A lot of really cool things there. Some anecdotal things on Twitter of people who'd been hosting projects on GitHub because they couldn't navigate the old application projects who said, hooray, I've just moved back over to Drupal.org. A lot of things that we wanted to see. And so we're looking to measure the impact of that and see what the contribution environment looks like after this change. What we're working on now is additional project quality indicators and just, again, as I said, project discovery indicators to help people evaluate projects. So we recently added the ability to star the modules that you use. So we're going to be able to use that in waiting the search for the most commonly used modules. We're looking at different ways to add code coverage signals. We haven't decided on exactly how we're doing that yet, but that's some sort of work in progress to focus on to focus on discovery and quality signals. There's a huge amount of people to thank when it comes to the change to the project applications process. It's something that's been in place since back when our version control was all before we were using Git. It's been a long time coming. Yeah, back on CVS. So it's been a many year process and there's been a lot of people involved in understanding the changes and understanding what we need to do to open up this process in a responsible way. So just thank you to all of these people. I can't list all the names. There's too many, but a lot of people helped us make this happen. Thank you. All right. So the next thing I want to do is talk about the way we recognize contributions from organizations on the Drupal.org marketplace. So back in Dublin, we were talking about the introduction of the issue credits system, but wherein users could attribute their contributions to a particular organizational sponsor and how we were using that to rank the marketplace. But so prior to Drupal.com Dublin, we studied that data with the help of Matthew Tift and Dries and found that 69% of the contributions to Drupal were in some way attributed to an organization, whether that was an end user organization, an employer, a university or even a client. So that was pretty enlightening. It put some data behind what was sort of anecdotal evidence that people had observed from who they knew in the community. But having observed that, we started thinking about ways to recognize not just these issue credit contributions, these code contributions, but other kinds of contributions. So as I said, we observed service providers, marketing agencies, integrators, technology and infrastructure companies and end users, all as part of the contribution ecosystem. So those other types of contribution beyond code include these. And these are now all part of the marketplace ranking algorithm for organizations. So issue credits are still one of the primary factors, but we've now weighted them based on the most widely used modules. So contributions to core get the most significant impact on an organization's marketplace ranking and on the other modules that are most widely used. And then we also add additional contribution credits, rather than issue credits, you can think of them as additional weight for organizations that have provided Drupalate case studies in order to promote adoption of Drupalate by showing off the best success stories for supporting partners of the Drupal Association who help us maintain the infrastructure for organization members and for organizations that are listed as supporting projects by the maintainers of those projects. So we introduced that shortly after Dublin and have been monitoring those changes and seeing how that impacts the kind of contribution economy around Drupal. What's next for contribution credit and the notion of crediting contributions? For individuals, we're thinking about how we can extend some of these ideas. The notion of a ranking algorithm makes plenty of sense in the context of organizations in a marketplace, but for individual contributors, it might not be the right way to recognize those contributions. There's this notion of thinking about a user's profile sort of as their CV within their contributor CV within Drupal. And so we're thinking about ways to pull in the kinds of contributions that people do and recognize them on the profile in different ways. For organizations, we do want to expose those contributions of the non-service provider orgs better. The marketplace, of course, is for those who are providing services. We also have an all organizations view where you can find universities, you can find community groups. One of the most significant contributing community groups is actually an organization page for the community of Ukraine. And they're within the top 15 contributors if you look at all organizations. So we want to make that more visible. And then we want to revisit the study that Matthew and Dries did together to get the next year's worth of data and see how it's evolved since that was originally done. I'd also like to give a brief update on the technical advisory committee. So the technical advisory committee consists of Angie Mosh, Steve, Angie Byron, Mosh Weitzman, Steve Francia, who are helping us to evaluate developer tooling options for Drupal.org. So we have a process that we've been going through for some time. We did some initial evaluation. We did a deep dive with staff in Portland. There were some initial recommendations made to the board. We recently posted a blog post talking about some of the short list of options. And now we're at the phase of looking at prototyping and kind of a pilot program. So we'll go from there, evaluate with community and gather feedback, and then figure out how we prioritize this work. But just to recap, some of what was in the recent blog post, we've been exploring a few options in tooling, whether that's GitLab for developer tools, Git Hub, continued enhancements to Drupal.org's tools, and the way that any kinds of integrations would work. And so we've also had some meetings here at DrupalCon. So we'll have more updates in another blog post coming out in a few weeks. And yes, thank you again to the technical advisory committee for working with staff to help figure this out. So the last thing I'd like to update on is something that not everybody may have seen, but is that the Drupal Association is currently, we've put out an RFP for infrastructure services, and we have a number of different potential partners who are currently working on proposals. More or less what we're doing is looking for a partner who can help focus on the lower level infrastructure, the middle of the night pages to make sure that Git is still running, all that kind of stuff, so that we can focus on mission work as the association team that directly serves the community. That's features for the community in a direct way, and not just the keeping the lights on with the servers. So we're going through that process. It's not yet complete. I don't have any announcements. But the timeline, we posted a request for information to solicit vendors on the 9th. We received letters of interest on the 24th, and we've actually just extended the proposal deadline from the 28th to the 8th. So my slide is now out of date as of this morning, but we'll be getting proposals and evaluating those as the association and the center of our infrastructure team volunteers to see if we can find a partnership that will help us manage the association infrastructure. So finally, there's a lot more that we've done in the past several months that I just don't have time to talk about today. So I'll be giving a session on Drupal.org tomorrow at noon. If you're interested in learning more about what we've done, including things like the stable release of the Composer Facade, coding standards checking available on Drupal CI, documentation enhancements for contrib in particular, and the community initiative of putting together the Drupal 8 user guide and getting that published. So we'll have that and other updates as well as a Q&A specifically with the engineering team tomorrow in room 321. Excellent. Great job. Okay, next up is Carrie Lasina, our director of revenue. Talking about the industry pages. You can if you want. Oh, it's already up. So I'm here to talk about the new Drupal.org industry pages, which is an initiative that the association launched back in February. We initially launched three pages focusing on higher education, government and media and publishing. These pages were designed to inform and inspire technical evaluators and connect them to service providers and technology vendors who can help them further along in their Drupal adoption journey. We also wanted to showcase the community's innovation and creativity and their ability to help solve end users challenges and their problems. This is also a pretty valuable resource that Drupal businesses can point to as they're pitching Drupal. This is a really high level idea of what one of the pages looks like, Drupal for government, but I'll go through the content points in a little bit more detail. We knew anecdotally that this is something that the community really needed. We heard from many shops that they were sending evaluators to Drupal.org and there was just no meaningful content for them. And this was very much validated by the positive feedback that we got when we were doing user research against these pages. For example, somebody who worked in the government sector said, you know, this is amazing. I wish I had this information when I was pitching my state CIO on Drupal. The association staff reframed the concept and then we reached out to different parts of the community for input. So we talked to decision makers and influencers at end user organizations as well as agencies who pitched Drupal solutions within these verticals. And we made a call to the larger community for feedback. We also analyzed how users were interacting with existing content under Drupal.org like case studies to help us inform some of our decisions. This is a phased launch. So we just launched these first three verticals. And right now we're just learning and trying to improve the pages as we go. The second phase will be to add additional industry pages like healthcare, finance, nonprofit, or e-commerce. And as we continue to build out this initiative, we're going to continue to take feedback from the global community. The industry pages are part of the about Drupal section that's promoted on the homepage of Drupal.org, which is the highest traffic page in the site. It gets 350,000 visitors a month. And we do know that 50% of those users are new to Drupal.org. Try Drupal, about Drupal, and case studies get the highest engagement rate so we can make certain assumptions about those users. Like they're probably more technical and they're trying to learn about or evaluate Drupal. So the content was primarily designed for users that know about Drupal at a high level and they're leaning towards some open source solution. We didn't want to assume that every user knew what Drupal was. So we kept that in mind as well since some people will find the content through search. And we're also serving up personalized content. The case studies are geo-targeted for the Americas, EMEA, and APAC regions. And this is really important just to show localized brand names and case studies just to help show evaluators that Drupal is really a viable option for them. So for example, these are the case studies that we show in the Americas, EMEA versus APAC. Here's a closer picture of what the page looks like. And the story that we're trying to tell is that Drupal is the open source CMS of choice within this industry. And we're telling that with really meaningful stats about adoption rates like 71% of the top 100 universities use Drupal. We're also telling the story that it's not just Drupal and it's very customizable. Drupal solutions entail Drupal plus various third party integrations and an expert host to get you your vertical specific solution. And then of course we tell the story with case studies that were built by well-respected agencies within the community. It's also a good opportunity to tee up correlating summits that happen at DrupalCon. So in this case, we were promoting the media, the government, and the higher ed summits at Baltimore. And then if the user is ready to talk to an expert, they can fill out this lead form to get additional information from sponsoring partners. Just a little bit of information about sponsor participation. The phase one launch does include sponsors for the Americas region. Because this is very premier visibility on the homepage of Drupal.org, but it also had very limited availability. We had to try and find a way to fund this work and make it as fair as possible. So when we went out and offered this to partners, we did sort of an internal rating system that considered code contribution levels, years of supporting partner participation, as well as whether or not they had relevant case studies. And in order to get this out the door and just get an MVP up and running, we haven't secured sponsors for EMEA or APAC. We just selected case studies that already existed on the site. And we're promoting the marketplace filtered by those regions. And over time, we will open it up to sponsors as well. So just a quick thank you to the launch sponsors that helped us get this off the ground by providing all the really great content and the organizations that participated in our user research, as well as the community at large that gave us really valuable feedback. And this is definitely a joint effort with many different parts of the community. And so we really appreciate it and are excited about it. Yeah. Lots more work to do. Yeah. Excellent. All right. We're going to make it through all the things. So now Rebecca. So Rebecca joined us mid-December as our new marketing communications manager. She hit the ground running. Can I sit here? Okay. Yeah. Okay. So I'm going to talk about Drupalcon branding. What is the Drupalcon brand? This is a question that I don't know if you've asked yourself, but it really depends on where you've been. And which location you're at what year. You can see there are some consistencies, but there really isn't a true Drupalcon identity. And this is historically because they've been built around the city and there's a unique brand and website for each location, which has some really great pros. The community gets really involved. People get really excited about what's going to be the next city. What's it going to look like? But it also provides some issues that we need to solve for. We don't have a clear identity, which is a problem when you want to have a recognizable brand to draw new people to the conference, to get new attendees, speakers, end users to attend, and creating an environment for more collaboration and innovation with new people and new blood. It's also a huge inefficiency in both time and money. Creating a new brand and website for every single Drupalcon is a big undertaking. We are really estimating this at this point in the process, but we think this is probably going to save about 10,000 per con, so about 20,000 a year, plus a lot of time on staff, time for engineering and marketing, which is a big deal. Moving forward, we're going to have a unified Drupalcon brand. It's going to hopefully create a visual unity and visual identity that goes between each Drupalcon, but also has elements that tie Drupalcon to Drupal and the association as well. Specifically, our goals here are to have brand recognition for the conference, make it clear to community, to outsiders, and on the website, what Drupalcon is, and then also allow for future expansion and different site functionality, content architecture that makes sense for what we're doing. So we did an RFP. We had amazing responses. There are some really incredible designers and developers in this community. We went with two interviews and we chose 611, who are over here. Thank you for joining us. They are out of Italy. They're currently working on our Vienna branding and have started with 2018 and our new brand as well. So we started with brand elements. When you start a branding process, I don't know who here knows branding process, but you think about what you want to convey in your communication. And for Drupalcon, that is technology and human aspect, and that's what we identified. So for that technology side, we have the hexagon modular shape, and then for the human side, a more fluid circular drop shape that represents the community Drupal association. It also has a grid technology aspect, which speaks to technology, but also speaks to convergence and all of these things coming together into one space. And we create Drupalcon. Be human, think digital. So within this brand, you'll see the drop, which is a unique drop specifically designed for Drupalcon, but maintains the same shape as some of the other drops that it used. It also has this hexagon modular shape for the technological side. It breaks down into hexagons, but also triangles and other shape aspects that can be used in different ways. So these are just examples of what merchandising might look like at future Drupalcons, and you will see elements used in standard ways from event to event, but you'll also see we don't want to use the city aspect. So there will be certain things that change depending on where you are, and you'll be able to see the first iteration of that tomorrow when we announce 2018. And that's the new Drupalcon. Great. All right. Well, I wish I could have all of the staff come up and give an operational update because they have been working so hard and doing amazing things. I'm just very, very proud and I feel very lucky to have the opportunity to work with all of them. So stay tuned for other board meetings. I'm sure you'll meet them at other ones, Ann. I'm sorry. Okay. We're going to do the board question, so I'll make sure to ask that one to me when we get to the board Q&A. Excellent. Now, so I would like to... Yeah, this one right here. So I think everyone in the room knows we've been going through some community challenges recently and I'm just really glad we have this opportunity to be here face to face for those that are able to make it here into this meeting. Obviously, it's just a small group and there are so many more people in this community that need an opportunity to be heard and hear others and process some things that they've been hearing. There's lots of ideas that are coming out of our recent community challenges such as our governance and what does that need to look like and what is self-governance? How do you create that? What are all the boundaries between the DA and the Project Lead and the community working groups? There's just all these really important questions. And I've been in listening mode. I know I've said that in writing and sometimes it might have sounded as if like that's just what you say. But it's actually very true. Just a quick little background as I was in... I worked for the state of New Jersey and did a lot of public hearings and I spent five years going into communities when we'd have to tell them that we're going to increase the cost of their buses and trains. And especially when you go into Newark or Camden or Jersey City, you're dealing with low-income communities who can barely afford to get to work and now you're making it harder. And they're angry and they have questions and concerns and fears and you have to be present and listen to all of it. And even if it just feels like there's more of a mob in that room than there is a discussion, it's important to be present and open and vulnerable to all of that because someone in that room has an answer and someone in that room has a good question that needs an answer. And when you're in government or when you're in these kinds of leadership roles, it's your job to hear those things and help solve them. So I just want to let you know that's where I've been coming from over the last couple of weeks and that's where I'm going to continue to be in my mindset of how I want to approach all these community questions. And I think we've identified as a community lots of different things that we want to talk about but we needed a good safe place to have those conversations that are constructive. And so that is why we came up with the community discussions. These are a series of conversations that are being mediated by Whitney Hess and we wanted to start right away. So we have some here at DrupalCon. So we have a room that is holding sessions that range from 15 people to maximum for those that really want to have a more intimate conversation. Sometimes it can be overwhelming to be with a lot of people. But we also have some of the sessions timed at, I mean set for 45 people to participate because some people just want to hear other people talk and kind of process what they're hearing. Maybe they don't want to speak but maybe they do. And so we've tried to be diverse and lower any barriers to get people to participate. And there's certainly a bit of privilege to be able to fly in and come to a conference and participate in this. So we also wanted to make sure we recognize that and recognize we're a global community. We want to hear from everyone. And so we have made virtual meetings as well that will be hosted on Zoom and don't start throwing plates. There you go. They're going to be hosted on Zoom and we're going to have them timed. So they kind of hit different time zones around the world so everyone can participate. And hopefully there's enough options for all of them. And then of course Whitney will be mediating those as well. And the other thing too is we want to be as transparent as possible. Not everyone's going to want to come to these sessions but as you can see in the diversity and inclusion slack is sometimes just nice to follow along but you have to know where to go. So we want to have a canonical place on Drupal.org. It's really easy for everyone to follow along in the process. So what we've done is we have created a page in the community section of Drupal.org and we are going to post meeting minutes from all of these sessions so that everyone can have the opportunity to see what the discussions were what the points were. It does not disclose who said what. There's no identifiers in there. We make sure anything like that is removed. And so it's you know we'll be having blogs and reminding people what the next session is and where to go find the meeting minutes and having summaries. And really right now what we want out of this is to ground the community and the association but really everyone in the voice of the community because you know there is quite a spectrum and I like to say let's not manage by loud operasy. There's a lot of people that have a lot to say and are very comfortable speaking out loud but there are a lot of people who are not speaking up or at least not publicly. Maybe they'll come to me privately. So how do we hear all the people in the full spectrum and so these are designed so that we can get grounded in the true community voice and all the things that we're going to hear and all the themes. I'm confident that we're all going to be able to work together and look at this and say like you know what let's do this let's move in this direction. So I'm really excited to get to that point but right now we need to have these constructive dialogues. And so you can find all this information in the blog post that I put on Drupal.org it's on the front page it has all the information about the community discussions the times, the places etc. So I just encourage you to go if this is a topic of importance to you I'm assuming it is and I also encourage you to you know tweet about it let other people know that this is a resource for everyone and so I think with that I'd like to introduce Whitney Hesse who has been mediating these and we're just really fortunate to work with her. We've worked with her in the past on a community project but I'll let her kind of come on up and introduce herself and also gives a it's all right safety first thank you Megan thank you everyone I'm going to keep it brief I am incredibly grateful to have the opportunity and the trust of the board and the community to facilitate and mediate these community sessions we are have held three sessions so far they were held yesterday we have two today and two tomorrow and so far we have seven scheduled in May as Megan said at a variety of times so that people around the world can participate at times that are convenient for them we will add more sessions if we need to to ensure that everyone who wants to be heard has an opportunity to be heard now having only had three sessions so far I'm hesitant to named themes but I do want to share what we are hearing that there are a lot of unmet needs in the community and the ones that are coming up most frequently are safety transparency understanding clarity trust progress and healing I think many of us can identify with feeling that we need these things as well now there is a tremendous appreciation for the safe spaces that we have created and there is a desire for more of these spaces at Drupal camps and local meetups there is a desire for clarification of Dries's many hats where his authority begins and ends which hat he's wearing when he's making any particular decision and consideration for sharing the responsibility with others to avoid conflicts of interest whether in reality or in perception there is also a desire for a community elected group for dispute and conflict resolution who receive training to do this effectively and whom they report to is TBD but there's also a desire for more community elected seats on the Drupal Association Board as well and lastly when cases arise there's a real desire for informing all parties immediately providing clear communication with the community that balances transparency and privacy at every stage in the process so thank you again for the opportunity to mediate these discussions I hope to see many of you there and I look forward to sharing more of our findings as we continue thank you thank you again I just encourage you all to attend these sessions we definitely want to hear your voices and so right now probably should have ranged differently because I'm sure that would have opened up tons of questions from the community but I I have in here that we need some questions from the board it could be about any of the operational updates or anything else they really want to ask so I'm going to read Tiffany's first and so this is a question for about the branding and the typography is different from the word mark for Drupal Association and Drupal itself what is the advantage of the approach do you want to come use the microphone sure so there's purpose and advantage the purpose being that it have a unique identifiable brand that is its own the advantage being that while Drupal and Drupal Association have have different typography and it's a more playful sort of community typography the Drupal Khan typography is specifically designed to fit the new brand as a whole and provide that fun and flair but also provide it in a way that is I don't want this to come across wrong but in a sophisticated way that reaches broader audience outside of the community that was the good answer so yeah so does that mean we started with the Drupal word mark and started with that font and then rule it out and said that's not appropriate to go in here no not at all no we didn't start there we just knew that we wanted to do something different and that Drupal Khan has never had the same typography so can I just like start from a complete slate yep or something up there totally yep any it is yeah there's a follow up for that because I didn't like how Drupal Khan brand name matched the city it felt very much like like the concert poster yeah I did does that mean that that method will be going out or will there still be some part of the basement where it's published there will still be some customizable factors within each city they will some of them are yet to be determined we've really just gotten to the starting basics in the past month that we've been working on it but there are going to be you'll see the hexagon and you'll see the Drupal Khan and the language that we use around it and you'll see specific elements the whether it's a hexagon in one city or a triangle in another city or a circle somewhere else those things might change as well as some of the visuals that we use in the in the branding yeah yeah is this I know that's a question sure we just have two minutes left for the board questions so quickly on that I think one of the things on this cost either re-print a lot of signs you know you're going to pamphlet sign signage but here's the left one right I mean I mean we were putting things like arrows happening this way every single comment's like this one's with the this purple left right that's a large expense if we went that round this is when this I'm assuming there's some port of demarcation I'm saying these are repeatable and these aren't going to change these are going to change yes have you guys come to that yet or still we're still working on it but largely a lot of a lot of the print signage on site will remain the same and we'll we will have to reprint to be clear we can't transfer them from location to location for various reasons but but the imaging and the cost savings in that arena will come from designer time having a standard template yep redesign yes arrow exactly thanks I didn't mean to rush I just want to I want to get I'm going to try complete time for the community too that's a community member yeah okay I'll come back to that one so but just one more question from the board we're having more questions guys hi everybody welcome back Jacob just said welcome back on the answer to responses is it that you're getting right now about roughly how many of you received and is there any sort of common themes you're seeing in the direction you have you've got the responses back I had to sell the deck but you said you received no we got we got letters of interest for people who are going to respond to receive the full RFP but we haven't gotten the actual final proposals back yet so we actually don't have that that's a strong response so you feel good about how many people have said yeah I do feel good about the breadth of candidates that we have it's a little bit broad yeah yeah yeah okay okay yep back for one more anyone else on the board have a question I was going to follow up about the interest so we also we do currently use some infrastructure from I guess some of these providers are using some external infrastructure that's good um well actually mostly our current infrastructure is at the open source lab and actually within the scope of the RFP it may be possible that we offered two options for kind of those proposals one is for managed services using some of our existing infrastructure and one is for kind of a complete package and participants might bid on either one or both of those options so but right now we're you know we do use like Amazon web services for Drupal CIA we use open source lab for the existing server infrastructure for DDoDo itself yeah we have a few things in a few places so one quick follow up are there any any learnings from like what way that we also use providers that feed it into the new risks you see from this this transition that's a kind of a broad question I'll try to keep it like relatively brief our primary goal is to to better enable the on staff team again to focus on the future development side so are the the clear focus of the RFP process is to find someone who we feel will be successful at being responsible for the lower level elements and so if we did not feel confident in that we would not select any any of the proposals that that option is still on the table so yep great good questions thank you all right well let's go ahead and open it up to the community you can this is your time to ask questions and if we don't have answers I want to make sure I get your name so that I could research the answer and get it to you but I would love to build those questions and start to answer that yeah I'll do that one second go ahead I have a question about the brand curious why or maybe you did consider the approach of just having a continuous website or arrow signs or whatever but that the city actually creates that that uses the word that deliver itself that is good I mean I really would want to give that to yeah to Rebecca so do you mean that the city community itself would build just like the little birds you know the site would look at the site right I'll say the one thing that we kind of like the website is that we would kind of have the infrastructure set up is in fact essentially archiving the city and so we build a site each time and that doesn't necessarily nearly change the brand we've got whole new little places where there's Black Battlet I mean you can say all of the sessions how all of the valuation the registration data and you don't even have to ask a site under delivered videos and registers and things like that it's a part of the eventual process of shipping great all right okay I'm going to ask this question from Buhansha what is revenue from various countries and what is the assistance given back to these countries that's a really good question I don't have the revenue broken down by countries but I can do that it would include both you know ticket sales we definitely track where people are coming from when they buy tickets membership we track that in our donor database and then of course through sales force where we track all of our supporter sales and our sponsorship sales so we have all that data and I could break it down by country and I'd be happy to get that back out to you and then in terms of return you know our two main platforms that we focus on is Drupal con and Drupal.org Drupal.org serves 20 million unique visitors and so I'd say that's pretty global when I look at the statistics I'd be happy to share the statistics so you can see how that money is being used to pay for the hosting and the engineers who are working on the develop developer tools and everything else that Drupal.org has to offer and yeah and so I could show you the costs and then also the impact it's having in the different regions we can get you the regional geographic data on that as for Drupal con right now you know right now we're doing two Drupal cons a year and so there's one the US and then one in Europe in the past we have done a third Drupal con a year one was in Bogota Colombia and the other one was in Mumbai India and oh right and we did Australia and Sydney right I was like the only one I haven't gone to since I've been here I know I can hear Donna right now and so you know of course we want to see what we can do in terms of Drupal con and supporting other communities right now we are focusing on securing our financial health and doing that third one was putting a lot of pressure on our budgets because it was always operating at a loss and so we just need to get stronger footing and then from there we can start to kind of look at that again so hopefully that you know I try to just give you a broad high-level view into that bohan but I am I'm gonna have to remember your name I'm looking at the screen bohan Shah so I'll look you up and I can get you that information and share it out I would say at a high level of just my guts to be wrong I feel like we make most of our money in North America really and when we do Drupal cons the other non- non- North American events are more of an investment for us true there is sort of a redistribution for lack of a better term from money coming from North America that goes to the other regions yeah that is true at a high level that's what's going on just to go to the Grand Rehabilitation yeah and bohan if you didn't hear that I forgot to mention that we have Drupal cons scholarships that help people from around the world be able to come to Drupal con and we have the community cultivation grants so like in my when I intro for Dries I was able to highlight a few of those recipients from Mexico and Vietnam and the Democratic Republic of Congo sport games as well well we are fiscal sponsors of camps so that's um as providing a non-profit kind of bank so they don't get taxed and we can hold their money and they don't have to put in their personal bank account so that's you know a way of supporting just not financial great any other questions in the room go ahead yeah with the uh book and the projects for modules yes I have a couple thoughts on that one is there used to be there has historically been a lot of discussion about new modules about similar module modules that already exist and asking why don't you just help with that older module so I think with the opening of gates we're now going to have a lot of similar modules it seems to me that we I think about putting some emphasis on telling people about similar modules again if I'm a module page yeah I think you know we have a our follow-up issue for sort of phase four of this process where I focus mostly on code quality signals also includes thinking about that do we have module problems great um we're trying to figure out ways hard to necessarily programmatically identify whether the modules first serves the same purpose but maybe ways of reporting that and then making that information available for both containers so I can think about teaming up yeah great and the second thing is that if you're not already I think you're going to be prepared for the fact that sites out in the wild in front of you using modules that don't have the review using security review that they've got in the past and that Trudeville's going to be blamed for security matters yeah that's that's potentially a concern and that's what but it's mitigated by a couple of factors so one of the big problems with the old process is that people who couldn't get through the application process who are waiting for six months or a year or more well I'm not completely I don't want to put down the change I think it's a good change but I think it just needs to be prepared oh absolutely yeah but and I think I think that's a problem that's already existed is what I'm trying to get at because when once someone hosted that once someone took that and just hosted it on GitHub instead people may have started using it on their Drupal sites and they still they would still think that it's a fundamental problem with Drupal not realizing that it was maybe not hosted on the home of the project so I think that part of what addresses that is those better security signals that we want to have on the project pages where people can now find that information and then hopefully within core we can get that patch over the finish line and that'll help I think that'll help address that but it'll keep people informed in a way that actually we we haven't even done before today so great and just for those that are on Zoom they can't hear anything so I'm going to repeat questions but just for those that are listening in on Zoom that was just a a nice caution of kind of Drupal's brand and people's perception of Drupal now that modules aren't going through the security review yeah well they all as soon as they all do yes right good point any other questions oh okay good so I'm interested in knowing more about the organization on the credit system sure and the work that you're doing around organizations contributions specifically I would that our organization's membership and there are people that have moved on that still are listed oh yeah and I'm wondering if it can be improved such that or what you're thinking about anything yeah so the question is how are we managing how a person with a user account on Drupal.org marks what organization they're part of and letting the organization page owners actually control all of that yeah that's something we certainly need to fix we have a couple ideas on that we just need to to get that sort of squared away ideally we'd be able to have the organization owner moderate who can yeah list so that'll be on the list and that would that would also be in fold it should um I would think we would architect it in that way so that it would be based on those those ones selected by the the organization owner that's a good question thank you okay I know you had a question yeah just about the DA staff really quick is there any resurgence of a community staffer for the g.d.nado groups because I was just in the community summit and we'd like to know who's taking over for that or you know who should field our our findings the question is do we have plans to bring and a community staffer to take over gdo because it's it's d6 and it needs some help no I'm just as a dedicated staff member oh for a community we used to have you know so I don't know who's handling that role if you are or if our comms if we have community section questions or input just fielding that on the DA that is a really good question so we are definitely smaller so just yeah so for those that are on zoom it was just it was clarified it's just who is on staff that is answering questions like an online community manager basically and the answer is right now because we're smaller we don't have a dedicated person we do get questions that come in and really we kind of crowdsource them as staff just to to bridge the gap in that area and certainly something we have been seeing in the last six weeks as a big need so that's the answer maybe not the best one sorry okay that'd be great any other questions go ahead so I have a question one specific incident or the decision that was made but more generally I'm just going to compare two two different so you said what's been learned so far how whatever the decision is how it's been so just to repeat the question it was you know given the recent decisions that were made and how it was communicated what are our learnings so that the next go around when there's something sensitive to communicate how can we do it better right let me do this sure all right this is Jis those on Zoom I don't know if you can see me I mean I think we've learned a lot obviously you know first of all I would like to say that the way this came about was unexpected right so in this particular instance that person decided to go public and really what they did is it left everyone me Megan the community working group with you know various sort of loose ends if you will where we hadn't sort of aligned everything we there is a lot of open decisions that that needed to be made still at the same time we had a sudden need to communicate so we definitely made mistakes starts with me communicating and we could have communicated way better but you know we were under a lot of pressure when we had to communicate and that was a contributing factor to to the communication not being great so I would say in a normal situation we go to a process and in that process we would obviously get you know better in sort of preparing for communication and all of these things um so I think how do we prepare better in exceptional situations it's always a little bit difficult but there's definitely a lot of lessons learned where I think we would immediately do things different for example the blog post that I did I should probably have waited instead of trying to I mean literally what happened is I sort of woke up and there's all this you know activity on social media and a lot of it was you know heated let's say and so I felt the need to to communicate quickly and I think one lesson learned is to probably you know take take our time and to really you know figure out the right communication in in sort of as a group not just you know me as an individual so that's one immediate reaction I think a lot of things that we learned is that maybe that our code of conduct needs potentially some work so it doesn't it doesn't stop or start sorry it goes beyond just communication as well there's a lot of different things that we didn't weren't simply weren't prepared for so not sure if you want to add something or not sure oh yeah we can cancel screen share um sorry I'm just gonna cancel screen share so we can see people's faces so I think um you know I echo a lot of what I was he making a face oh thanks sir thank you for the thank you for the plucky relief yeah I mean I echo everything that Drew said I think from the association standpoint it's um you know in some ways I'm still processing but I think the the number one thing is just remembering to be very empathetic with communications I think in extreme times so some of the feedback I got as well as you know I mean just reading my post um it has a different voice right I think it comes off as terse and like very corporate and there are reasons for that they're and I don't want to go into it but it's um very much tied to the situation and that that Drew's described also just not really sure what how to say it without going too far because they're there's so much that was just happening all at once right and so it's like you want to say something but at the same time you know everyone wants so much more and you can't give it to them so I think that that the communication was I knew it would never make the mark but I could have at least been more empathetic in my communication and not taken the advice of being so corporate statement right because guess what we're not we're not a corporate I'm the only business in this entire situation right like we are not proper business but we can't talk like a business it's not our culture to talk like that and to change the way we communicate suddenly around a really hard issue where there's all these questions just adds more questions and it's also just frankly shitty right I mean that's how it kind of comes off so those are just some things there's just so much more that I'm processing in terms of communication you know when I worked for the state of New Jersey just using that example again you know they were on the five o'clock news like every day that PR you know the PR part someone gets hit by a bus right someone get you know there's a train collision something derails right like every day something would happen they could be on the news and they had a story and we were like 100% the opposite of that because we are such a great wonderful community that we've never had to think about crisis communication you know and boy I'm really sorry we didn't because we could have done a lot better job helping all of us get through this with better communication so that's one area that I'm really going to focus on too I'd rather plan for the worse and always in for the best but anyhow I hope that somewhat answers your question one quick follow-up so do you feel you know hopefully we don't have any more volatile decisions going forward but if something something happened tomorrow do you feel more confident now do you feel like oh thank god we weren't all we weren't we now feel confident and we're more confident I can definitely say yes you know I mean that confidence also comes from some more retrospectives really making sure we had got all the learnings like that's what we have Whitney is to help us hear those voices right there are some things that we hear and understand but there's blind spots right so we're looking for the blind spots but we definitely found resources you know I just mentioned we became smaller as an organization right so we don't have a I don't have a this we don't have a that but now I know who to go to for this and that and but I think what will give us even more confidence is when we actually have the plans in place and you know we have training internally of how to use those new plans whether it's communication or you know new code of conduct code of conducts and how to how to monitor that and what that means and you know there's just so much that we have to do and I think the confidence comes from the doing concerns that you don't you know the plot codes only says they were meeting minutes briefly and I was wondering if there is already plans and if and that if only can guarantee you can land for me but they don't really know where is my voice going to be used later on that's a that's great feedback thank you I want to repeat that yeah and for those on zoom that couldn't hear it the question is it's great that you have in community discussions and you're taking meeting minutes but no one knows what's happening afterwards and and so that's that's great to hear so thank you I just put up on the on the screen where we are putting the meeting minutes on triple.org and so I think what I'm hearing you say is like maybe I need to tweet that out no we're not you're saying saying what are the results yeah is that the only thing I have to report is we can like by the public proposal to condense that everything in one yeah come on over and is everyone okay I just want to time check we are over one o'clock and other people have sessions but I'm okay staying a little bit longer okay so thank you for bringing that up and my personal aim is to provide the greatest degree of transparency in my process is possible so that this process helps meet some of the community's needs the reason why that hasn't been communicated yet is because all of this came about very quickly so we're still trying to catch up but I'll tell you what the process has been so far and what we're aiming for it to be with the understanding this might be revised so so far I have been engaged in a discovery process where I've been having one-on-one private interviews with a wide variety of people around the community in leadership positions and not just to get as many different perspectives on the situation as possible and ideas for long-term changes that can be made to community governance and community management in general we're having these discussions here Tupacan and the discussions being held online for the global community from there I will be pulling together themes that I'm hearing across what the shared needs are that are not currently being met and some strategies for how to get those needs met changes that need to happen with the governance model changes that may need to happen with the code of conduct et cetera I will be sharing those findings with the board and with the community and we may also have a way for the community to come together to refine those ideas and to start to create a strategy for how this needs to be addressed that's the initial phase that we're in now after that we'll be in the implementation phase where we take those ideas and that planning and we start to actually make concrete changes to things we don't know what's yet going to come we don't want to be overly prescriptive we don't have want to have too rigid of a process that doesn't allow the community to really be heard and direct where this goes so we're being purposefully fluid and maybe a little bit vague so that we allow for that direction to change based on the community input I think it would be helpful saying that you will believe everything that will be shared with everybody absolutely it's the only danger of people that they say absolutely it doesn't help and on the people I'm saying I think everybody understands that you will not come up with a solution of everything and that's what we need to do and yes saying that the information will not be complied if you give it to everybody agreed not everything is fully captured in that as well yes that will absolutely be done I will make a point with Megan to ensure that that is communicated and I really appreciate your question and bringing this to light so we can do something about it thank you are there any deadlines for the kind of first steps is also yes when you could make a foundation where you feel you could be able share some we shall be gathering yes there have been so so far we have set the end of June for a strategy to be completed around planning what needs to be changed not implementing it that will have multiple milestones between now and then with the more formal communication around the themes that we hear from the community discussions coming at the end of May once the online sessions have been completed thank you so is that documented somewhere on the site that's what he was just raising that we haven't formally communicated that out to the community what the process is and the reasoning for that is that I've only been engaged very recently and we had a lot of planning to do for Drupalcon so my apologies for not being able to get that sooner but it is my number one priority coming out of this week thank you thank you maybe that could be on the page get there all right I'm gonna have to just take one more question because I know some board members have meetings is that okay okay I can't um to who would like to ask the last question go ahead oh oh sorry since you went once would you like to let go sure so your blog post talked about the mission of the Drupal association and its connection to specifically Drupal.org and Drupalcon is the idea that these community discussions will lead to some changes that are something related to the Drupal association that this is actually part of the purview of the mission of the Drupal association says it's a charity and it's not you know a trade organization a a broad charter yet these two specific things are usually what we understand the association to do I just wondered how you thought that the community discussions fit into that yeah mission that's a great question the question is we have a nice broad mission statement and but when you look at what we execute we focus on two large platforms Drupal Drupalcon and Drupal.org and serve the community through that but our mission being so broad what is it you know are we looking to take on more as we go through these community discussions and governance and for me I think my regardless of the community discussions I want the association to be able to do more like I'd love to keep stepping into our mission I always see so much need and you know it always pains me when we can't address it more and more broadly and right now because of the financial situation we're getting our feet underneath us we're focusing on the most core things to the community and the two things that we've been asked to be stewards of first and foremost which is Drupal.org and Drupalcon and through that we are definitely becoming healthier as an organization and getting our feet underneath us and I do want to look at how we can expand when we have the funds available to invest more broadly right so that's just generally what I would like and then as we go through this these governance type of questions will the community say we want you to do something more we want you to take something on I certainly will want to help any way I can at the same time I have to remain sustainable otherwise everything just falls and nothing gets done right so I have to balance both okay well I'm sure there are more questions and I'm afraid we're out of time but I'm really glad we could stay in extra 20 minutes and get all the questions out that we could I'm an incredibly accessible person I don't always get as many emails as I would think I'd get but I don't I mean no no I mean it's a million person community don't trust me guys I work really long hours but it's a million person community and I think people don't really just how accessible and easy it is to for me to set up a time to talk with you and so now that you've been here you know me please know that I would love to just sit down and chat if that's something that you'd like if we didn't get to all of your questions because I really care I just think this community is pretty amazing we are going through some interesting times I'll just leave it at that you can fill in the blank of other than interesting but I also and the eternal optimist and I know together we're going to come out and be a lot stronger because of this so but it's going to take all of us having these conversations to make that happen so anyhow with that I'm going to conclude our first public board meeting of the year and we'll have another one on June 26th that one will be virtual but also public so you can go on to the association site and get the dates and times and we'll be promoting that as well and in the meantime I hear your need for some more transparency in a couple different areas but especially around the community discussions and so I'll be working with Whitney right away and we'll make sure that happens okay well thank you very much everyone thank you