 All right, I did it. Thanks guys. All right, so update from the month of November. Yes, as Chris mentioned, we did get the 2015 leadership plan and budget approved in the month of November. And we'll spend some time reviewing that today. But just getting that practice published out to the community, a lot of work in November for our staff and we will actually have a community call tomorrow to review the budget and leadership plan was in there and answer questions that the community has. So that's scheduled for 830 a.m. Pacific time and you can find more in the blog post at sos.drupal.org to be able to sign up for that. And of course, we'll record it as well and make the recording available to folks too. Some other highlights from November. We started recruiting for the licensing working group. We have about 7 applications for the 3 to 5 spots or the 4 to 5 spots that we'll want to fill on that working group. And those are, there's an announcement up on sos.drupal.org in the news section. So if anyone out there is interested in helping out with that work, you know, go ahead and pull that out now. And we'll be presenting a slate of candidates to the board at the January board meeting for adoption there. And then I just wanted to show off some of the work that was done in this, you know, around this timeframe as well on the things. We were in, a lot of us were in Amsterdam together, obviously, and we heard Chris's keynote about helping to create more social capital in the Drupal ecosystem and how we can use Drupal.org and profiles to help thrive some of that. So we have definitely been taking some steps to make that happen. One of the things that was recently deployed was a change in how commit messages happen. So this is just a screenshot of the new system and Josh, I don't know if you want to briefly fill folks in on how this works and what the next step is with org credit. Yeah, so right now it is a system to generate the commit message on an issue. And in short, what it does is it summarizes for the maintainer who's going to make the commit. It summarizes everyone that was involved in that issue. Whether or not they made comments, whether or not they uploaded files, which could be a patch, it could be a design comp, it could be numerous things. It gives you an opportunity to include an author or omit the author, and it auto-generates that little bit of text at the bottom that we can use as the commit message. There's actually a really good discussion going on right now for the next step, which is all around what contribution credits should look like for contributing organizations. I think we're really close on that one and actually I'm hoping to get a comment out based on some sprinting we did as a team here at the association to figure out how to implement what it would look like to implement those commit credits that include organizations. And so I'm going to be posting an update with some implementation details and I'm hoping Dries and Angie will be able to kind of round out the conversation on and we can start getting towards implementation for that next step. So that's one end of that, by being able to record the data, right? Exactly. And the next end is the front end, which is how's this going to look on profiles. I just want to go back in time and remind everyone that we didn't really get to start building a tech team until April of this year. And at the time that Josh came on and we started building the team, this is what the profile page looked like. And so the social credit part was the long list of stuff that you said you had done, right? But that was all user entered data was not driven by actual transactional data from people at work. And then of course we have the sort of we can recognize members and supporting partners, but there's not a lot baked in. And over the last few months, those, those profiles have really started to shift and become more organized and start to be able to display that data in a much more meaningful way. So this is what it looked like, what right before, answer them, maybe? Yeah, right on that timeframe. Yeah. And then this is what they look like now. So we're also getting those profiles set up both on the back end, getting the user fields set up in the right way. And on the front end, design-wise, getting them set up to make that social capital more visible to the rest of the community. So this is what they look like now. And what we're working towards is some version of this, which Danny Norton did a lot of work on. And we spent some time talking to Kevin O'Leary who did some work on that for your presentation and imagining what they might look like. And this is the sort of thing we're working towards. And it's getting really close. We actually have all the fields migrated at this point. The board packet, I think, said that there were two left, but that was at the time that I filled it in so that we could get it into the board packet. But every field has been migrated at this point. So really the next step is some layout work. And then as we start calculating some of the contribution credits based on the data that we've been pulling off of user profiles, we'll be able to do a little bit more. We actually have some really exciting information coming there that we're going to try to figure out how to put into some reform in the next month or so that highlights user contributions across every possible contribution type that we currently track. And there's some really, really fascinating stats out of that. So I just wanted to spend some time on that because I know it's going to be an important thing for the association to support the vision there. This is where we're at is getting ourselves technically ready. And obviously there's a whole nother... I guess we have a bushel of worms, it's a can of worms, it's a can of worms. There's a whole nother can of worms in terms of figuring out a system around this for valuing some of those credits and what that might mean in terms of some of Prisa's suggestions about giving folks sponsorship credit or advertising, et cetera, et cetera. But we are moving forward on the technical aspects here. So just want to stop there and make sure everyone's clear about where we're at. Sorry, Holly, this is Angie, just one quick question. So I've seen a lot of the work that's gone into the user profiles and I think that's great. Is there a similar effort underway for organization profiles to better highlight the contributions that they're making, or is that sort of tabled until after we get the storage stuff figured out? I think the first step there, so we definitely are going to tackle the user profiles first for layout purposes. There are a couple things that I think we can tackle on organization profiles in the short term, in terms of just making them layout a little nicer. If you're a company that has more than 20 employees with an account, your page looks pretty horrible right now because it turns into a giant flag with the poll being your list of users, which is kind of an interesting metaphor, but we'll leave that there. So we definitely need to start with that user profile layout and just the general org profile layout. But as we look at those commit credit formats and we start parsing that, as soon as that feature is there for people to start adding that commit credit in a particular format, there's no reason why we can't start collecting that org commit data. And that can happen. Our goal right now is that that's in place and that we're collecting that data in the February timeframe, and that we would be able to start displaying it. We're probably going to need about three months of data before we can do meaningful display of that data. So somewhere around the LA timeframe, you should start to be able to actually see, oh, this is how many commit mentions a particular organization has. And most of that is around just the time to build up enough commit mentions that it looks meaningful on the profile. We have enough data to know how to display the right way. Yeah. Yeah. Then there's a lot of iconography stuff. So we're not going to parse it. I guess we can't really. Okay. So it would only be going forward from whenever we start collecting data. We are going to back parse all of the individual data, but we won't be able to back parse org data. Yeah, the only real way to achieve that from a commit credit standpoint, if we're actually doing it on the commit, would require changing the commit messages historically. And I don't think we necessarily want to go down that route. But it's definitely a case where we can start it going forward. I will say though, I think there are some things we can do with orgs that highlight other contributions that we can do more quickly. You know, how many sponsorships have they done? How many times have they renewed as a supporting partner? How many job posts have they bought on Drupal jobs? Like the things that we can count, I think we can start actually showing those on the profiles pretty quickly. Other questions about this work? Looks like good progress to me. I wish we could go faster, but I know it's a lot of work. Yeah, there's a lot of... No, that was me. I was just saying to Dries, he always wants it to go faster. Oh no, I'm sorry. I think a lot of these things are... Well, the way I look at it, it's nice to have these little widgets to generate the commit message. I mean, it's a nice little improvement. I think the improvements through the user profiles are great. But I think the real game changer will be the organizational profiles and these more advanced systems that we can build on top of it. So I'm excited for those things. Just a lot of steps in between, which understands why. Yeah, they go hand in hand. We had to do this base work first. I'm excited about the org profiles as well because I think we have an opportunity right now. We're very marketplace focused with our organizations instead of being contribution focused. And I think we can kind of shift that with the org profiles so that we're highlighting big organizations that aren't just Drupal service providers but are big contributors to Drupal in really meaningful ways. So I think this is exciting because I think it expands what we call the community of users and we can show it in a very cool way on the site. But you're right. Once we start collecting it, we're kind of starting from... That base. We're starting from that base, which is a little bit unfortunate just in terms of where it falls in terms of the timeline of Drupal 8 and contribution towards Drupal 8. But I think ongoing it's going to be a really powerful display. So this is Jeff. I totally agree about we do want the focus to be on contribution in all of its forms. And that's good. It's unfortunate we can't do it for the past, but we do have an opportunity around this fundraising that we're going to push for for D8 too. So in your list of examples, we should think about could we do something to highlight people who are financial contributors to our D8 drive? Yeah. That's the point. I think we absolutely could. Just about anything on an org that we can tie to a triggerable action by the association staff or by people who have had the elevated privilege to assign that contribution or to award that contribution to that organization. I think we can start calculating those and using those to do things like determine the order of the marketplace layout. We've actually already talked about taking the first step of ordering marketplace organizations by supporting level first and then kicking into alphabetical from there. It's looking at you guys. I want to move on. I don't want to be stuck here all day. We've got other stuff to catch up on. But I, you know, obviously if you have other thoughts, we want to hear them. But maybe another menu. Your silence is consent. So commit messaging and profiles. Those are huge. I think the other area on grouple.org just to talk about quickly. I know we spent some time talking about the investment we've made in infrastructure, but, you know, a lot of that was to pay off a lot of technical debt. And at this point, on the infrastructure side, we've been doing a lot of work to move on to our own services and off of the OSUO itself, which has been great because it's gained us a lot. That investment has meant a lot more efficiency for us. And I don't know if you guys have tried to use the site this week, but it's ridiculously fast now. It's so exciting. I remember sitting in Sydney with Angie trying to look up users so that I could link to their profiles in a blog post. And we'd literally search for a username, get up from the table, go to get a drink, come back. And my search results would be there. Holy, that was because you were in Sydney. Oh, okay. Right. I think it was faster now, though. It's so much faster now. But I think the really important thing is that moving the item to our own services on a third party service is a good point. And the point is that it makes grouple.org much more portable. So we have a lot more flexibility in terms of how we architect that site in the future, which is great. We'll touch on that a little bit in the infrastructure working group update as well. Great. So those are some big shifts that have been happening in November. I think the other big focus for staff has been on getting the 2016 working plans in place. We obviously already sort of put a budget together and had some broad brushstrokes, but the teams have been working on their particular work plans for the year. We have a new person on board, Carrie Lucina, who's focused on revenue driven by grouple.org. And so I know the revenue committee at this point has seen her work plans, but we're going to start seeing more of that roll out in 2015. We have lots of experiments there that are going to be going on. And I think just one other mention is, you know, I think, I don't know if it's a D8 list or not, but I'm going to say it is. But I think for the first time in a while, we actually saw in the last two months, traffic on grouple.org equal to traffic for those same months in the previous year. So we're hopefully that trend continues and we're coming out of that traffic slump and that's going to support all of the community and revenue work that we need to do. So hopefully we're moving in the right direction again. And then just very quickly, you know, one thing that we're watching very closely right now, Triple Con Latin America registration. We currently sit at 82 folks. The goal is to have 400 people in the room. And so we just passed the early birth deadline. So in a normal con, we would expect a much greater percentage of registrations to have happened by early birth. But given the fact that we're both in Latin America and that the registration rates don't increase drastically between price points, we're not sure how concerned or if we should be concerned at this point, but we're just watching that a lot and coming up with, you know, alternate scenarios for how we're going to deal with that. But it's definitely happening. It's just a matter of how big it's going to be at this point. So any questions from the rest of that update? Go on to the community reports. Sorry, I was on mute. Yes, please. We can move on. Okay. I'm going to unmute you for the revenue committee and then you myself. Okay. All right, great. So the revenue committee met this past month. Some of the things we wanted to share was that the incomes coming in pretty much as we've been projecting, we've had some great overages in Triple Con sponsorships and Amsterdam came in much higher than we had anticipated. We were really nervous there for a while. And then everyone came back from vacation and I'll tell you more about that in the Amsterdam wrap and did really well in the hosting listings in the web ads. We, it's great that we were able to go over in some areas because we had some hospitality around Drupal jobs. Just kind of really finding that the workflow there needs to be improved and Kerry and Josh and others are improving that workflow so we can improve conversions and get that set up for a strong 2015. And then also the supporter program was a little bit softer than we anticipated and some learnings there was just that we need to really front load our year with selling that program. By the time we get into Q4, companies are just really not in a position to make commitments in the same way as they can earlier in the year. So we're making those adjustments now in our sales processes. The other thing that we focused on in our meeting, Holly touched on this a bit, was that Kerry came to the Revenue Committee and shared the different Drupal.org revenue programs that she is modeling and is ready to roll out and Josh and the tech team are helping to build those products out. And so there's going to be lots of experimenting and so the Revenue Committee gave their feedback and we also started to brainstorm other areas for Kerry to explore. And we do have something in 2015 Q1 to share that kind of information with the board so we can make this more broadly known. But it's certainly really exciting some of the things that we're working on there. We've also come up with some plans for the Drupal 8 fundraising campaign that the board will be doing and we're working together to get our training ready for the board retreat in January. And we also started working on the co-marketing campaign where we are going to sponsor two industry events next year in Europe so that we can have more of a Drupal marketing focus while our DrupalCon in Europe will be more of a developer conference focus. And so we're starting to figure out what that might look like and which events to go sponsor. And when I say an industry event just for those that don't know what that is, it's kind of like going to an e-commerce event and promoting Drupal and making sure we have a booth there and bringing in some companies, Drupal shops and people with that expertise to help us highlight the Drupal message to attendees. And that way we just get right in front of the chief marketing officers and other evaluators for Drupal business. So in summary, that is what we've been working on. Excellent. Thank you. The Governance Committee. Sameer, is that you? Where's the list? It's Matthew and I just unmuted you. I'm Matthew. Matthew, sorry, it's Matthew. I'm sorry. You unmuted yourself, Matthew, at this point. Ah, there we go. How did I mute myself? The Governance Committee did not meet this last month but we'll be going over some things that we discussed a couple of months ago later on in the meeting. All right. Thank you. Finance. So the Finance Committee met but I did not meet with them to review October Financials. Can you hear me? Yes. Okay, great. And also to review the Operations Work Plan for next year. All right. The Executive Committee. We did not meet. I think I can move right along to marketing. Yeah, during last month's meeting I mentioned that we were in the process of self-nomination for the Marketing Committee Chair position. We've gone through that process and today we'd like to offer a recommendation. There are a couple slides at the link there that says New Chair Recommendation. And the recommendation is Gina Montoya. She is with Blink Reaction. There's some information there on her background, her marketing experience, her experience with Drupal but she does have some great marketing experience, some broad experience. She's been in the community for some time now so she knows the community well. She actually knows Drupal pretty well. She's got some technical chops in addition to her marketing expertise as well. So I think she would be a great fit for Marketing Committee Chair and would love to have her approved as the Chair if there could be a vote. Are you recommending we take a vote today or? If possible that would be great. I just want to take a picture. Is there any questions from anyone on the board? So this is Jeff. Does she have a copy of the latest Charter and do we feel we need to review or update the Charter before not necessarily nominating her but sending her into action given that we've sort of meandered a little bit over the years on what the function is there? She is familiar with the most recent Charter and I think we revised within the last six months. So we're pretty current I think on the Charter and she is familiar with it. Another question. Has she been involved with the marketing of Drupal in the context of the Marketing Committee or is there no history there? Well frankly the Marketing Committee has not been very active because there's been the lack of a chair so she has not been involved in that. She is a marketing person for Blink Reaction so from that standpoint she does market Drupal. Actually and Blink Reaction have done a bunch of those funky videos and stuff around DrupalCon and stuff. Yeah they've done some pretty innovative stuff and they've been really active. They've been doing a lot of fun and innovative things not just with their own marketing but within the community and highlighting what the association is doing and highlighting various aspects of Drupal as well. Has she been involved in any events or anything like that? I'm looking at her profile right now and it's pretty sparse. She has primarily camps that she's been involved in. Are you talking about on the organization side or just on the attendance? On the attendance. I'm curious as to how involved she actually is in the community. She said every DrupalCon. Yeah she's pretty involved in the community and again I would point to Blink Reaction. There's some great leadership there with Ray Saltini and others. They're very involved in the community in general. Any other questions? Well if we do want to vote I'd like for somebody to submit a motion. I move that we vote to accept Gina Montoya as the chair of the marketing community. Second. Alright thank you. Yeah I'll second. All those who are in favor please say aye. Not in favor please say no. Aye. Aye. Aye. I think I heard about seven or eight ayes and no no's. So I believe that is accepted. Great thank you. Will you inform her? I will. Awesome. Thank you. Thanks for bringing her to finding somebody that wants to chair the marketing committee. I'm very excited to see the impact of that. Absolutely. Alright. I think the next item is the DrupalCon Amsterdam wrap up. Megan you want to unmute yourself? Yeah can you hear me? Yeah. Awesome. Okay there we go. Just kind of answered a couple months ago. So I wanted to just give a recap of what we've done with that event in terms of getting our KPIs and what attendance in our financials look like. The feedback we got on content and overall feedback of the event and also some of our learnings and how we're going to apply that moving forward. I also just wanted to point out that Rachel Friesen is the event manager for Drupalcons and unfortunately because of timing she couldn't be here to present it. So I'm doing it on her behalf but you'll be hearing from her moving forward on these kinds of things. So if you can just advance the slide. So I thought I'd just do a recap to help us all remember the excitement of this great event. So we had over 2300 people come together. It was our largest DrupalCon in Europe and was really exciting especially because we weren't sure if we were going to make goal. Then we exceeded goals. That was wonderful and people just came from all over and people came on bikes and we had another amazing session with Jam and Robert Douglas. And had a really diverse group of sponsors and it was just a wonderful event overall. I think we all enjoyed learning about Strupwaffles. And so why do we have Drupalcons just to kind of frame this conversation. We always go back to this. The board met gosh almost two years now to talk about really what is the purpose of a Drupalcon. So grow and strengthen the community accelerate the project promoting Drupal and generating revenue to fund community programs. And so we really designed this event to achieve those different objectives. And so also I know that the board heard a lot of this data because I did a preview of where we were coming in right before we got to Amsterdam. And so I am going to share some of this data again for those that are listening in. I just want to put that in context. But in our board packets we report out on our KPIs their goals and also things that are important for us to monitor to get some benchmark numbers. And you can see that they're really annual goals that we're tracking but if we break it down to Amsterdam the numbers were really great. We combine it with Austin. We're really doing well in our KPIs. We did have some soft numbers around Austin which is why our attendance KPI is yellow and also same. And that kind of is reflected on the revenue side where that's yellow. I do want to point out the net promoter score in Amsterdam did drag us down quite a bit. And that's why that is red. I'm going to go into that later on in the presentation. I couldn't for yesterday. All right. So anyhow let's just dive into attendance and financials. So compared to Prague Amsterdam really did an amazing job in terms of attracting people and training training really grew as well. And so that was really encouraging. Business Summit Community Summit also had really strong numbers not too much growth there. But if you want to just kind of advance I can talk to you a little bit more about who attended. And so you can see that Drupalcon Europe is very much a developer event. 51 percent say they're developers which is a higher percentage than what we have in North America. But it's very consistent here in Europe. And just some other fun facts is that we also had more attendees that were members. And so using Drupalcon to attract members has been a good platform for us. It's nice to see that growth year over year. And also from a gender perspective we haven't really been moving the needle too much on attracting more females. We have about double this in North America. So something we also just want to think about as we are creating our diverse community. Of those that are attending it's important to note that we have a lot of advanced skill level. So if you can imagine a lot of developers that have advanced skill level that are coming to the show. This show we did have a little bit more diversity on this front compared to Prague. We got a little bit more intermediate and beginner. And I'll talk a little bit about that as we get further into the presentation. It's also important to note that of these people that are coming we're really attracting employees from Drupal shops. This is pretty consistent year over year as we're seeing in Europe. And something that we're just going to keep looking at especially if we want to do more to attract more developers. Where could we be attracting them from. I think the site owners a.k.a. end users is a great market for us to help us move that needle. And we are coming together from all over the world 59 countries to be exact. I just want to drill down and let everyone see that when you look at who's really coming. I mean the attendees are really primarily coming from Europe. And obviously a really strong pull right around where the event was held in the Netherlands as well as Belgium UK. Obviously US is still a nice percentage there but you don't really know if we say we're international might be like one or two people from China one person from Vietnam. Some people from Middle East right so some handfuls but those are important community members that we're bringing in helps us get that international feel as well. And so I don't want to marginalize the fact that we aren't pulling from all over the world. I just want to point out that this is very much a regional event. And because we had this surge in the last two weeks for our ticket sales we exceeded goal which is really great help her bottom line tremendously. It's going to help us fund our community programs and I can go a little bit more into detail on the next slide. So you can see how ticket sales versus sponsorships rolled in. And we also identified some expenses we had heard from some community members that be nice that we shared a little bit more insight into how the money was spent. And so we are providing this breakout here between venue catering 80 internet and power. Obviously it's just really expensive to put on these events. And so we're happy to share more insight if people are looking for more detail on that front. Yeah. I just want to take this moment may end just to point out that if folks are really interested in more detailed analysis of what exactly happened in a particular Drupal con the way that we've established our financial reporting now. You can see all the accounts for each program that we run including Drupal con Amsterdam separate from Drupal Austin and those are in the financials that we post on a quarterly basis. So in January when it goes to the quarter financials. So October November and December of 2014 people will be able to go in and actually see those totals in those financial statements in excruciating detail. I would say. You mean glorious detail. Glorious. Absolutely. All right. So let me just kind of drill in so we can see what happened those last two weeks of ticket sales and this is new information I think for the board since you got the snapshot right as we were rolling into Amsterdam. And so 29% of registrations happened in those last two weeks. That was one ticket crazy pretty significant. 73% of those registrants were conference conference tickets that's kind of a mixture of people redeeming sponsor coupons but mostly it was people buying tickets. There's also 28% of those registrants were people buying single tickets. And also what I saw from that before and after snapshot of the data that I shared was UK was leading as the top country. In terms of attendance and in those last two weeks the Netherlands bumped up those really people buying from the Netherlands coming in at the last minute. So if you can go the next slide. Yeah and so when I drill down into conference ticket registrations. We saw an increase in beginner developers who purchased at the last minute and that's why we have a slightly higher percentage of beginners. It was about 11% last year in Prague and this year was 15% so I feel like we just had a lot of people that were kind of kicking the tires that was close by the. So it was just easy to get in and and learn some more. And then of course it's just important to point out sponsors to redeem their tickets at the last minute so that was one of the things that pushed those numbers up to. On the single registration front 71% of single tickets were bought at the last minute. And it's a great product that we've been offering the last couple years and it's nice to drill down and see that it was evaluators taking advantage of this. And it was also great working the Drupal Association booth on the exhibit hall. I talked with a lot of people that just said I'm just coming for the day. I'm kind of interested just want to see what this is all about. Some were developers and were Drupal shops and didn't really talk to any site owners who were evaluating. But it definitely just gave people that easy entrance in and most of them bought their tickets for Tuesday because obviously Tuesday you get trees. And so I think that's a real draw. Maybe some will look at, I don't know, maybe I'll raise rates on Tuesday. We could change the name to Drees Day. Yeah, I like that. Raising the roof. Why don't we go ahead and take a look at the content and the feedback on our content. Obviously that's the real meat and potatoes for our events. This slide, you know, you might want to take your time to look at this. But what it's really saying is in Prague there's a lot of Drupal 8 sessions that were highly attended and in Amsterdam. Our top attended sessions were mostly Drupal 8, very developer focused. But if you go to the next slide, you can see what the top rank session was this year, was a Drupal business session for Drupal shops held by Susan Rust. You can also see that there were no sessions that were top ranked that were coding and developing from that track. Of course, core conversations makes a lot of sense, but that's number two because we have so many advanced developers on site. Just something that I want to drill down to kind of understand a little bit more about this data, but that was interesting to share. What's the Krill track? You know, I'm not sure. I think you're much of a core convo also. I think so, I think so, yeah. Krill track. It's name tracks of people. Okay, so one thing that we should know about the session evaluations is that we did not get as many people participating as last year that happened in Austin as well. And so we as a team are looking into this to see what we can do to get more participation because this feedback is so critical. So if you looked at the sessions, the percentage sessions that got a 4% or higher or a 3.5% or higher for their ranking. Those numbers dropped and that's that was a little disappointing. So we drilled in and studied why and it wasn't the content. It wasn't the speakers. It was the room size. Because we had such a surge of attendance at the last minute, it just really packed the rooms and made it difficult for people to get into the sessions they wanted to hear or it was just really too crowded. And so that's something that we're looking at to make sure we can adjust for next year. And also just kind of wanted to drill into sprints just seeing really nice uptick in our sprints and obviously this is to help accelerate the program and I just want to do a special thank you to our sprint mentors. We have a lot of people that come out to help facilitate this event and that's a great things happen there. And I do believe trees gave out ice cream. Or was it an Austin, and I just made that up. That is right. I was actually really good at ice cream. Yeah, maybe we should have done stoop waffles. Oh, but there was, I mean, I bought ice cream in Austin, but in Amsterdam there was also ice cream. Oh, nice. Yeah, no, there was this ice cream truck outside. I must have made that one. No, it was actually better ice cream than in Austin. Oh, the truck, that's right, the truck. Yeah. Okay, good. Why don't we just go ahead to the next one. And so this is just a summary of what I've mentioned just about, you know, emphasis on Drupal Aitner in terms of what people wanted to go to. And we'll just keep working on getting more people to fill out those session evaluation forms and, you know, the scoring really is reflected on room size, not on the content. So I just really want speakers to hear that loud and clear. So if we can go ahead, we also have attendee feedback. And Dries, I just thought this was just great picture of you getting feedback from your, I don't know, your Drupal, what's a Gingerd Doppel? Get the word. Doppel Gingerd. Anyhow, yes, thank you. Still taller than him. He may be funny, but I'm taller. There you go, you win. So, you know, it's very common for people to want to attend Drupal Con to hear sessions and network and brother skills. We did see a switch in the reasons for people attending this time and location came up. Yeah, that was really important to hear. And we really nailed it with Amsterdam. And so, you know, location matters. And we saw that in the ticket sales for sure. And also, in terms of, we asked people, what was the most useful aspects in Prague? It was sessions, networking, keynotes. And so it means that we're really like, they say why they're coming and we're delivering great value there. We do always see that the exhibit hall has a little bit of like, and that's so useful. And if you go to the next slide, you'll see in Amsterdam, the same things were considered useful. So that's how we know that the content was good, the speakers really delivered. The networking was great. And again, the exhibit hall was, you know, perceived as not very useful. And so we're going to drill into that a bit, maybe look at the format of how that's orchestrated. But it could just be that because it's more of a developer conference, there's just a different perception of that exhibit hall. So we'll do a little assessment there. And also, I was a little surprised that email communication had more people saying that wasn't so useful. So we're going to look into that. But overall, we did also see some really good numbers around email communication and click through. So, you know, we'll look into that as well. The one area that it is concerning was that people felt that there was less value this year than there was the year before. And if you go to the next slide, you can see that in the net promoter score. Whereas Prague, we had 49. Amsterdam, we had 25. So we really drilled down into people's comments to understand what is happening there. And really it came down to catering. When we felt that we weren't going to make budget because of softer ticket scales, we had to make some changes with catering. And we did three days of box lunch. We normally do one day of box lunch and two days of hot lunch. And the box lunch came with a sandwich that kind of had just a slab of cheese and meat. It was not really robust. And so catering is a really important thing. And so it was a decision we felt we had to make and couldn't make any changes at the last minute when we realized that there was more funding there. But it's something that we can really look at for Barcelona and something we're working on now. Of course, coffee is another thing. Coffee and catering can hand in hand. We'll just keep trying to do more on that front. And so obviously our goal is to get that net promoter score up much more next year. So just in summary, Drupalcon Europe is primarily a regional developer conference. You can really see it in the demographic data that I showed you. And so we really want to embrace that next year. We're also going to take a really close look to see what we can do to capitalize on location, keep improving content and networking because we know that's important. The catering, obviously, is a real driver and we're going to look at room size. So I'm sorry to interrupt. I'm not 100% bought in in the regional parts, to be honest. I mean, only 20% was from Amsterdam, from the Netherlands. And even with Belgium included, it was only 30%. I mean, which is a good chunk, but I'm not sure it's so regional. I should say it's European. Yeah, I agree. For Europe, it's pretty European. It's very European. I think when I say international, I think global. Like, there weren't a lot of people from Australia. But it's still, I mean, it's still most conferences in Europe. They're less European, I should say. That's good feedback. I mean, I think people in Europe don't tend to travel much to conferences outside of their country. So I think this is still pretty diverse in just based on my gut feeling from having gone to European conferences. That's great. Well, that's great to hear. And it's also good to have that same vocabulary too. So thanks for mentioning that. And so just to kind of close this out, you know, obviously looking forward, I'll just keep working with the community. They're providing great sessions. We'll keep looking for ways to make sure that networking is happening. These are the real drivers. And then I kind of mentioned all the things that we're going to be working on that we have a list here and Rachel and Stephanie and Amanda and Lauren are all working really closely to start figuring out how to make these changes quickly for next year. I'll be coming to you in Q1 of next year to talk about what Drupalcon in Europe can look like and how that can be more of a developer conference. So stay tuned on that front. One thing that I found interesting about the presentation was the fact that most of the attendees come from Drupal shops. That kind of implies that even as we shift it to a more developer friendly conference, we probably also need a reason for their bosses to come. We've got an accurate feeling. Can we need to have the Drupal shop bosses attending? Yeah, I mean, because the highest rated session was a business session and, you know, if the bosses are showing up, they're seeing the value of the conference as well. As opposed to if it's something they just send all the developers to, like, do we worry about that kind of like impact things in a bad way? Yeah, that's a good question. I'll have to look at that. Joe and Lee have done a great job creating content for people to give to their boss and say, hey, come to this event. So we can look to see what the pick up was on that. I can also look to see if the business owners are coming. I mean, we had great numbers at the business summit. And so, you know, I just kind of feel like that audience is still always so hungry for real training and Susan Russell is a real pro in business training. So I'm not surprised it resonated. So I'll see if there's anything to be concerned about in that front. What I saw there was an opportunity to get more developers coming in from end users as a market that we could tap into. Yeah, OK, gotcha. All right, thank you. And most of these bosses would be developers themselves actually for smaller Drupal shops. And if you look at the business days, we had like almost completely new audience this year. Not many repeat visits for the business days, for example. So, yeah, I don't know how to read all of this, but it's really like, do we need to cater for these people? Like we can actually ask, we kind of know who these like 100 or so people are. You mean to do a targeted outreach? No, I think if you should actually ask and just email these people and ask, like, what are you looking for this event? Do you actually want to have like business content for yourself? For is it more important to have a bigger content and so on. So, yeah, I think you're, I think so. I think I think there's a lot we could do for Drupal businesses, especially in Europe. Okay, so I'll add that to the things to look into. Any other comments, questions? Thanks, Megan. Okay, thank you. I love that you guys do a deep retrospective, I think. I think it's important that we learn, you know, keep learning. So thanks for doing all this work. Very helpful. All right, let's move on to the budget and leadership plan. Excellent. So, you folks on the board should be pretty familiar with this, but I did want to, for, you know, to seek out the public, share some of the top-line items. Just quickly, but again, we'll have an opportunity to go through this in more detail in a webinar or webcast tomorrow. Sorry, Joe. So, just to sort of frame things where we're at, you know, in the last year, I think that the organization, the Drupal Association has done a lot of work to increase the transparency for the community and our accountability to the community. Establishing a dashboard, having a budget, producing more detailed and parsable, parsable is not a word, but detailed and parsable financial statements, I'm going with it. You know, all of that has been really important for us, just to establish with the community that, you know, we're going to tell you what we're up to and we're going to show you our progress towards that and, you know, the stance will shift and our plans will change, but here's what's happening. And then we did a lot of work also at the Association to really professionalize how we operate and I think wrote in here, you know, in a good way, because I think we want to, we certainly want to be professional in all the ways that are positive and good in terms of, you know, putting ourselves out there in the right way and being responsive to people and all that good stuff without necessarily being, you know, professional in the stodgy way. So that's really where a lot of our focus was in the last year, getting the system set up, getting teams built, being able to create things that create systems of process for communicating with the community. So we built a really good foundation, I felt, in 2014 and we've got lots left to do. We grew really quickly and we're still catching back up with ourselves, you know. But mostly the point is we're still learning. Last year was the first year that we did a dashboard out there with metrics that we were tracking, understanding what we can do to help across, you know, across the organization and we didn't always measure the right things. So you'll see a lot of shifts in the 2015 leadership plan. We're going to try measuring other things too. And then, you know, I think one of the biggest struggles that we've had all year long is what we have sort of figured out how to sort ourselves and do our work internally well. How to handle our work with the community has been, you know, we've had a lot of tension around that and I don't mean tension in the negative way of, you know, like people are fighting, but there's been a lot of questions we've had to work through to sort that out. You know, we want to maximize participation while also making sure that we are taking care of things in an efficient way, right? So we're still working on that and it's still a strategy that we're trying to master. So that's just background and fringe sort of like where we're coming from and who we are right now as an organization that I think really informs what you'll find in the leadership plan. In our leadership plan, we always just start with our vision and our mission just as a reminder that this is what drives all of the work of the organization. So everything that we do and articulate should line back up here. These are our big baseline filters. So if we're talking about taking something back on and it doesn't feed the mission, we don't do it. When we are talking about revenue opportunities for Drupal.org, we try to find revenue opportunities that also align with our mission, right? And are serving our community. And we also do the same with our values. This is something that we come back to all the time in ways that we talk about our work just in a big session on values at our staff retreat last week. So these are touchstones for our work as well. In the factories, we had a big session where we got to talk about your keynote and what do we think that meant for the association and how can we have these conversations and move that stuff forward. And there was a group who broke off and did a breakout session specifically around those topics and how we make sure that our values continue to be represented in a system like that. So the values are at the cornerstones. Those don't change very much. What does change year-to-year is our strategy for getting at that mission and vision. And our two big strategies this year in all of our work is to... The first one is a carryover from 2014. We're still really looking to enable, promote, and highlight community contributions. So again, big emphasis on making sure that even though we're professionalizing and trying to provide a baseline of support for things like Drupal.org and Drupal.con, these are still community-driven places where individuals come to make awesome... Well, and organizations come to make awesome stuff happen. And we want to continue to make that really easy and really possible for folks. Or make it easier and more possible than it was before if it wasn't easy to begin with. So that's really important for us. And the second strategy in all of our work is to be able to leverage the data that we have or understanding of what's happening at Drupal.con or how users are behaving on Drupal.org to run experiments and make decisions more quickly. And what that in effect means is no more giant projects. So no more... We're not going to redesign Drupal.org from top to bottom and put a goal around it and drop it in the community's lap. We are going to break it down into components, test out certain bits of it as we go, and do things iteratively with obviously a plan and an end goal in mind. But we're going to be doing all of this work in a much more experimental way. And that of course means that everyone here has to set goals for their experiments. And there's lots of data involved in that. So those are our strategies for how we're going to approach our work. How do we do it with the community and how do we do it in smaller iterative chunks so we can learn and change quickly as we go. The things that we really need to focus on for 2015 continue to focus on Drupal.org improvements to carry over from 2014. Unlike 2014, we actually have some detail behind what this means this year because the team with the working groups and feedback from the community have launched a roadmap. So if you want to see what the big end goals look like for 2015, you can go to Drupal.org slash roadmap and get all the details there. But again, we're painting broad brush strokes. This is a place we want to get. We're not going to define it perfectly right now. We're going to run lots of small changes while we learn about what colors we're going to fill in on this picture that we're trying to paint. We also need to operationalize our revenue program. So we grew really fast this year. The board let us make an investment in building a technical team. And we are really working hard at the same time on diversifying our revenue streams. We have lots of new revenue streams launched, new sponsorship programs, Drupal jobs to name a couple of highlights. We have lots more that we're looking to launch in 2015. And we need to make sure that those are set up so that nothing operational stands in their way of success. So it's easy for us to run those programs, to deal with the money that comes in, to provide the service and value to the community and to the folks who are giving us the money so that we are in a great place by 2016 to support a steady stream of additional income. So that's going to be a really important thing so that we can carry our work forward in the future with a nice solid foundation of revenue. And then of course a Drupal 8 release. This is another one that carries over from 2014, but we really need it this time. We definitely want to make sure that we support a release when it happens, that we make the most of that opportunity in terms of rallying the community and engaging them in that release and getting it out there in the industry in a smart way so that we can make this the best release that it could be. So I just want to pause for a second because I muted Donna because her cat was very hungry, but now she has a comment so I'm unmuting her. Sorry about that. Holly, I just want to go back to the Drupal.org improvements. I just went to Drupal.org slash roadmap and I have a small concern there that my expectation of that URL would be it's a roadmap for Drupal rather than a roadmap for Drupal.org the website. So yeah, and then you look at it and you go, this tells me nothing about where Drupal is going. Okay. Yeah, I'm done. We need to go to Drupal.org slash dot org slash roadmap. That's a joke. That's a bad joke. Moving on. Okay, that's fair. Anything else there, Donna? No, that's it. I'm done. So these are the three big areas of focus that the teams are really centered around. We set KPIs in a leadership plan that follow up on those imperatives. We have three levels of metrics that we track. The first are sort of mission-based KPIs, so these are sort of top level. Do these numbers we think represent that we are meeting our big organizational objectives? Every team also has program-based objectives, so we do have metrics that we track specific to Drupal cons, for example, attendance, revenue, session evaluation scores, et cetera. And then we have related data that we're also tracking that might not be goal-related, but it's data that we think could tell us what's happening. So if we miss a program objective, we can look at that related data and understand what might be influencing that low number. So we're tracking three levels of metrics across the organization. What you see in the leadership plan, those are our mission and program-related objectives. And then every team also has their own dashboard with their program objectives and a bunch of related data that they're tracking from month to month as well. So an example of what our mission-based KPIs look like, we have a general direction of being a well-run organization. So we are interpreting that mostly through financial numbers at the moment, that we're able to pay our bills and also that we are tracking to our budget as anticipated. So are we able to actually create a budget that has meaning and then perform to the budget? Part of the strong community is another sort of long-term board objective. So we're looking at the change here this year. We're focused on all the community touch points. So we want to be able to show all the times that we're able to interact with a community member throughout the year as well as memberships, we think, as an indicator. We're going to increase membership number. That just shows that our value to the community and the membership retention, those people stick around. And then a growing group will adaption and another objective for the organization set by the board. So we're measuring that by increasing the number of people sites that are out there. And right now we're also measuring people as a percent of the web overall. Program objectives. There's more detail here and I'll go into a lot more of this in the web track that we do. We can just get a sense of how we track a layer of detail down for each of those programs. So that's what the work that we want to accomplish. The goals we're working towards in 2015. And then the budget is how we financially tell that story. So just to give you a sense of where we've come from and where we're going. This gives a sense of 2011 through 2015, which is the budget that was just passed. We've definitely grown a lot as an organization in 2011 revenues were just over 2 million. In 2015, we expect to be over 6 million. If you will recall our 2014 budget, we were anticipating a negative $750,000 net revenue. And that was that deficit spend was approved by the board as an investment in the tech team. That basically ended up getting deferred because it took a while to get that tech team on board. So we just didn't realize the salaries as quickly as we had budgeted. In addition to the fact that we had a good chunk of change devoted to hiring contractors to get some work done. We just wanted to accelerate what was happening on triple.org. But without anyone on staff to help manage those contractors, we used very little of that. So we will not have as big a deficit spend. And basically what we did end up doing is pushing a lot of that ask into the 2015 budget. And you'll note that we are looking at a deficit spend for 2015 coming out of this. I think the key note is for us, again, is sort of underscores the importance of operationalizing our new revenue lines so that we can get the maximum amount out of them by the time we hit 2016 and we can be in a revenue neutral place. To give you a sense of what the income growth has looked like, I just want to thank Rob Gill for introducing this chart to me because I use it in all kinds of things now. It's awesome to show any kind of trajectory. But just to give you a sense of how revenue has grown and where that growth has come from, the cons have had a significant source of revenue growth from year to year in the budget. You'll notice that in 2013 to 2014, the cons are actually a loss or there's a decrease in revenue from the cons. And that would be because in 2013 we held a triple con in Sydney. In 2014 we did not run a third con so there was no revenue associated with an additional con. And despite the fact that we didn't have our biggest lever for growing revenue, we still grew revenue between 2013 and 2014. So we feel really good about our ability to go into 2015 and turn on some of these new revenue programs and start staffing to support them and really get to this much expanded place. And if it looks like triple con, like we're leaning more heavily on triple con for revenue, the reality there again is that now we have a third con that's represented in the mix. So that's where a lot of that growth is coming from. Although we do expect some additional revenue increases from... Holly, I have a quick question on how to read this. Maybe it makes sense but it's between 2014 and 2015. Are these actuals or do I read that from the end of 2014 to the beginning of... to the end of 2015? Yeah. Where did you go for the beginning, to be honest? The wrong tool on here, I forget. No, I don't know. So basically everything, if you go to 2011 and then the green stuff at least since 2012 and then the green stuff that goes to 2015. Those are all actual projections. So the last... Did that, yeah, were your mouses? I guess that's all projections for next year then. Yes. Oh, you can see my mouth. That's good to know. Yeah, these are budgeted. Everything from here over that's actual. Got it. That wasn't clear. Good point. For the level of detail for this chart. And I think although we're... We had the same story last year when we were asking for a deficit fund. The important thing to note is that we're in a good cash position, the organization. Although we are cyclical, very highly cyclical in the way that we recognize revenue in our income statement because of the cons. The fact is that cash comes in very consistently throughout the year. So from a cash flow perspective, this really isn't an issue. And we are not going to experience any very narrow months where it's like, oh, I hope you make it. We have cash in the bank and cash comes in all the time. So we're going to be fine from that perspective. Although, I will point out that we only get to do a big deficit fund like this one time. We're going to have to get ourselves back to even after this. But I feel very confident that we can do that based on what we've been able to do with revenue. Just to underscore that, and this is some of the revenue stuff that Carrie's been working on and worked on with the revenue committee of the board. We're definitely expecting to see lots of revenue growth come from the Drupal.org site itself. So posting those things is one area that we've had in place for the last couple of years. We will see some growth in 2015, but when we get the Drupal 8 traffic bump, we anticipate we can grow that even more. We are definitely going to expand the web advertising program in 2015 and move that into 2016 in a significant way. So in 2015, we're going to do lots of experiments with that. I do want to make sure that everyone is clear that it is not our intention to throw ads up all over Drupal.org. That our intent right now is that ads show up in very key spaces, not in spaces that our developers tend to be in, and that ads are delivered to users who are unauthenticated or not locked in. So if you're working in an issue queue, you're not going to see an ad in your issue queue. If you're in the marketplace, you might see some ads. And then Drupal jobs as well. We're definitely looking to grow that from its launch in 2014 to doing some tools improvements and building some systems around it to support in 2015 and to grow beyond that. Just to share a couple of assumptions around this is that why do you think this is ultimately very doable? A lot of this is driven by traffic. And when Drupal 7 launched in 2011, Drupal.org visits increased by 30% over the previous year. So we're not going to base our numbers off of the 30% growth in traffic because that seems highly aggressive, but we'll go with 15% to be nice and conservative. And that's where these numbers are being driven from. They're based on the idea of a 15% growth in traffic. So the other thing to note is that we are making an investment in our sales force and the operations that support them in 2015. So we should be in a great place by 2016 to really go ahead with these kinds of numbers, which again would make us get us to a revenue neutral or positive place. Holly? Yep. This is Jeff. Apologize for the interruption. That number of that increase on the job board is not consistent necessarily with what we've been discussing on the Revenue Committee, or at least in my memory. I was wondering if Megan could comment on that. Are we comfortable with that increase there? It's a double share. It seems too low or too high, Jeff? It seems big. When we looked at it the other day, we were going to go from 40 to 80. Not from 40 to 215. 40 to 80. Yeah, those are numbers from this year that we had originally projected 80,000 for this year, but because of the different reasons we know about, we're going to be hitting closer to 40. So those are just 2014 numbers. And that this number is being reported by having a product manager, improved workflows, driving traffic from D.0 and lots of crossings and content management, as well as different campaigns that can really support this, and a lot more work going behind this product than being able to do this year. It's worth noting, too, that this is also relying on the deprecation of the jobs content type on groups.drupal.org, which we're counting on driving a pretty significant amount of traffic to Drupal jobs. That notification went out this week, and they will be completely deprecated by mid-January. Have we had any feedback from the community on the deprecation of that? I've had two comments so far. I just sent out the notice last night. One of the comments was on Twitter. One of the comments was on the issue. For the most part, the maintainers who have been associated with groups are really excited about the change. And it's been very minimal. Like I said, basically two people providing either negative and or questioning the move. Like, how are we going to make sure that small companies can still afford to post jobs? And we do have a plan for them. Okay. Thanks. So, Ironic, since these small companies are planning on growing and hiring people, and there's a cost to doing that. Yeah, for sure. I think one of the areas we're looking at is emerging markets. You may not even be a small company, but if you're a company in an emerging market where perhaps the financials don't align with, say, North America and Europe, and we're looking at what our options are there in terms of doing coupon codes or maybe doing some sort of grant process. We just pulled all the data from the job site for the whole year, what's got posted there from groups. Yeah. It's mostly North American. It's mostly North American. Yeah, it's like Johnson and Johnson, right? Yeah. So, I think we're going to be... I think the big question there for me, or not a big question, but I think the answer to a lot of that is, well, we were providing that service, we being the DEA was providing that service on Drupal.org free of charge for goodwill reasons for a long time. Like, we're not honored to continue that process of sponsoring something for free if we have a product here, and even if we did, I would imagine you would want to drive the traffic here regardless of whether someone pays zero or whatever the top package is. We don't want to be running the same service in two different places just because some people expect it to be free. Right. Right. How are we going to stop people just posting job ads in groups anyway? They just do it regardless of if it's a job ad post. That's a great question. They'll still do it in individual groups, right? It will be up to that organizer to police their own group. And actually, that's just... They care about it. Some groups don't mind that jobs are posted there, and I don't think we mind that jobs are posted there, right? Right. It makes sense to have a jobs group. Correct. Got it. Got it. I think that's a good question, Jeff, because, yeah. Well, yeah, and I ran on LinkedIn. I ran like a local meetup group years ago, and it was just relentless how many of the posts were really just job posts. Yeah. So it is a problem, but... I think we make it a policy, and we hope people help enforce it. But to me, this target looks like the right one, to be honest, like a $200,000 target. Yeah. Because what we need is we need these high-margin products, if you will, that make enough money that we can help fund our engineering team. So if it was only going to be $80,000, I would be like, why are we doing it? Yeah, I guess I have a lot of reservations and concern just given that we've had it. You think that the first six months that it was in production would be one of the highest subscription rates, right? And if we were going for $80,000 and we only got $30,000 in the first six months, then you have to do something different in order to get $200,000 in the next six months or a year. And I think I heard a good answer, I thought, from both Megan or Holly and Josh, I can't remember who said it, but Josh's point about deprecating the existing job board, definitely I would imagine drives some business there. And then somehow some continued or increased awareness about this job board. I haven't seen anything come to phase two about it. I would have thought that we would have been solicited a little bit more for posting there. So maybe a harder push in awareness now that we've worked the kinks out and we're real proud of it. No doubt we can make $200,000 with a job board personally because it's one of the biggest problems in Drupal. And companies are spending hundreds of thousands of dollars finding Drupal people. And in aggregate, people are spending a lot of money trying to find Drupal talent. But yes, I think we need to push it more. It's not even, even though it's one of the biggest problems in Drupal, it's not even on the main page of Drupal.org. That's something that we've put through the content working group and we do have a plan for putting the top three featured jobs on the Drupal.org homepage in the coming weeks. We're just squeezing into our... We're just being linked to the job board because so many people are trying to... I think the problem is awareness, basically. And I think if we open it up and we drive more people to it and we kill the other job boards on D.O. Then I think we have a good chance of making that number. Yeah, I think the problem is a clear one that people are interested in it. I think the next step is just do they know that this is a place to post or to look and that is an awareness problem. Yeah, it's like with any product. It's like you can't expect to build it and then people to just come to it. Yep, nobody has that expectation, I think, here. No, no, I'm not trying to imply that. I think, I guess what I'm saying is I don't feel like we've actually pushed it to the extent that we could push it. So in a way, the fact that we did 40,000 may be remarkable. Yeah, and I think some of the work that we're going to do on the Drupal newsletter, for example, on integrating jobs into that, there's definitely plans to get it out there in a more proactive way. I feel comfortable with that number. I just want to watch time again and shut up quickly if that's okay. The last thing I just want to point out is what does this work represent? What does the budget represent programmatically? The roadmap, which is the Drupal.org roadmap and not the Drupal roadmap. Three Drupal cons in 2015, so Bogota, Latin America, Los Angeles and Barcelona, and then preparing for an emerging market for Drupal con in 2016. Community cultivation grants are still there. We're going to continue with that program. The camp support fiscal sponsorship that we do. Global training days, all that good community work is going to continue and we'll actually see some more community work come out of this as we get past Latin America. And then some new programs, so the Deblay Accelerate, which just launched and are working on clarifying and going big with. The European marketing events, so we'll be able to get, as Megan mentioned in a wrap, that Drupal con is mostly a developer-focused event and we still have a need to get Drupal out in front of an evaluator audience. We'll be experimenting with that by going to a couple of industry events in Europe. And then we also have $100,000 in that budget for a design system consult as part of the Drupal.org evolution in 2015 in that roadmap. And then it does fund some new hires as well, so it pays for all the 2014 hires in full now. So it looks like we're doubling the staff from 2014 to 2015. What we're actually doing is really fully realizing all of the tech team hires or engineers or wizards, whatever you are to me. And then it also funds the new staff person who in part helps support the Drupal 8 Accelerate program. And then the additional stuff that we'll be hiring are focused on that revenue side of things because they're imperative. Anything else for you guys? So Holly, do you want us to vote on this? Or is this just an update and we may evolve based on the off-site that we have in a few months? Yeah, it's just an update and I just wanted to share it out in the public board meeting. Because you guys have already voted to approve the leadership plan and budget in the executive session at the last meeting, we're clear on that front. Okay. Got it. Alright. So, we're going to move on to the governance committee election recommendations. I believe that's an update from Matthew. Yeah. Let's go directly on to the next slide. So, what we're going to talk about real quick is community elected seats and term limits. Let's go on to the next slide. So, in the last time that we talked about this, we were asked to sort of explore what the challenges were and how to deal with those challenges. Some of the biggest things are that the loudest voices are often those that are most interested in doing something like cleaning house rather than those that are really actively interested in moving the association forward constructively. And I think that also we also have a situation where those wanting to run are unaware of the real responsibilities of being on a board, which is a challenge as well. And then finally, we've mitigated some of these challenges through changes in terms of transparency, but do you think that those are the two biggest things that we've got in terms of challenges for community elections? Let's go on to the next slide. So, there's a general agreement amongst the governance committee that there's a kind of bar that someone needs to elevate beyond in order to run. The last recommendation that we came forward with was serving on the committee and it was felt in general by the board that that was too high a bar. And so we came back together and talked a little bit more about it and we came up with the notion that potential candidates should maybe attend three board meetings, not contiguous, and that those three board meetings should be over the last six months. Let's go on to the next slide. So, the benefits of this bar are that Holly can easily track who is attending the meetings. It shows effort and desire to participate in the process. It allows people to see what's involved in participating as a board member. So, what do people think about this? I have a question. Would this go into effect not for this upcoming round of elections, but for the elections in 2016? I think we couldn't do it for this round of elections coming up. We wouldn't have anybody who would have qualified. That was my sense as well. I think moving forward in a 2016 capacity, it's more than reasonable. We had a six meeting a little time for me, given that we have board members who haven't even made six there that six possibly. But I think the general idea of that is great, because it's a low barrier to entry. It's a little bit time zone challenged if you're in the honest time zone, but otherwise, and then you know what you're getting into, it's sort of like training the whole time. Actually, on that point, I wonder if we should be considering rotating the the fact that we have the board meeting at the same time every time might be worth us considering staggering it a little bit so that it's not time zone. I mean, it's fine for me. I'm used to it now, but it's a good point that it does make it impossible for people to participate. I would be in favor of looking at rotating times if other people are. That seems reasonable to me, especially if we're wanting to attract a highly diverse group of people. I'm fine with that too. Cool. Could you clarify what that means? It means at least once a year, you're all going to have to have the board meeting at 4 a.m. Once a year, we would do our board meeting in Australia time. Yes. I'm really just trying to understand. No. I think it was Denise raised at some point that one of the things that she's seen is a common thing for cross-continental teams is they just rotate their regular meeting time so that it's not the same time zone every time. Someone's always the best, but it's not always the same people. You just stagger a little bit. This would be for monthly board meetings? Yes. The calls, not for in-person. Right. I would see in-person would always be the local time. Obviously. Well, yeah. Okay. So would we do it? We would do it based on who's on the board then. We would go west coast, US, east coast, US, Europe. Then we would jump to, I guess, in this case, we would jump to Australia back to west coast, US. The board composition changed and we had someone from China or India we would then stop there on the way and we just keep rotating that way. Is that what you're suggesting? I would actually do so I would look at how many people do we have on the west coast, how many people do we have on the east coast, how many in Europe and Australia. Right. It would make sense to like... Well, it's more that it's proportionate, right? It's okay that we do this in the middle of the night or really early in the morning for me because it really is only me. But if we're expecting other people to participate in our board meetings and making this a requirement for them to be a candidate, then it actually is something that we need to do from a convenience perspective because we're saying, well, hey, you want to participate but you've got to do this at 2 a.m. your time which is what it is for probably earlier parts of Asia and you've got to do that three times in the next six months if you want to put your hand up to be on the board. But also they're the ones that are trying to approve a commitment to the organization not the other way around. I don't know... If you approve that commitment then it's in your time zone but what I'm saying is as a board then we're going to then work towards someone that we believe might be interested in attending a board meeting. I don't think we should do that. I think we should have a set rotation based on our board composition. I would agree with that because I think otherwise what happens is we're anticipating where we're going to get people and let's be honest the other big problem is we just don't get anyone interested at all that's the whole problem we're trying to solve. That's not true Jeff we never have a lack of candidates for elected positions. What we have a lack of is people participating in the actual election. I think we have a problem in both. We've never been satisfied with the turnout or frankly with the interest of the position. Can I propose that we maybe move this one offline and then come back to the board with a proposal? Because we're running low on time. I think the problem we're trying to solve at this moment in this discussion is separate from the idea of is this a decent threshold of participation to demonstrate. Then we can solve for how to make the board meetings more accessible in a separate conversation. It sounds like everybody is in spirit in agreement that having people attend a few board meetings to show interest and a desire to participate is a good idea. I just want to register. I agree we should move on. I just want to register that we don't want to set that bar in such a way that it exacerbates our lack of diversity rather than I definitely don't want anyone to take away that I'm just being selfish. I would be more than happy to do it but I want to be explicit while we're doing it and reach out to those people and say hey look once a quarter or once a year or whatever we're going to do the board meeting on your time to show you that we want you to participate I don't want it to just be like it's a round robin of convenience for people. I want it to be more like it's for a purpose so that we get that you know what I mean. I think that the proposal on the table however from governance committee is a really good one and it's basically that starting in 2016 in order to be eligible to put yourself forward for a community position you have to have attended three board meetings in the six months prior to the election so I'd like to move that we adopt that as our policy. I'll second that. I'll second that. One quick question. I know we want to move off this. Are the meetings publicly recorded? Yes. Could some listen to a recording in lieu of that even though we can't actually track that? No. I don't think that that should be, yeah. I think it should. That's not the motion on the table. I guess that's how I was answering it. Okay. Can somebody repeat the motion maybe just to avoid confusion if any? The motion is that beginning with the 2016 community elections in order to stand for election the nominee must first have attended three public board meetings virtually in the prior six months. And I'll second that. Great. Thank you, Tiffany. Those in favor please say aye. Those not in favor say no. Aye. Aye. Aye. Noor. Aye. We're missing some people still. Did we lose people? Maybe she do. Sorry. Let's start over and let's say please say your name and then aye or no. Donut, no. Matthew, aye. Jeff, aye. Vessa, aye. Angie, no. Do we have everyone? Do we hear Samir? He said in the chat he has to leave. Yeah. Do we have Rob and Mike? Yep, this is Mike here. I'll go to the mic. Rob, are you there? He's not lying. He's muted. I'm not. There we go. All right. So what is that? Two nos and six eyes? Maybe Angie can tell. Yep, that's the math. So I think it's accepted. Yep. All right, thank you. Okay, let's go on to the next slide real quick. There was a suggestion that we... I'm sorry. Yeah, before you go there, there was also a question on like the staggering of the meetings. Are you enabling it obviously by somebody following up on that? Yeah, I think the governance committee will. Yeah. Okay, thank you. All right, so then there was a suggestion to increase the number of seats. I'm not going to read this slide. I'm just going to say that the governance committee at this point doesn't think that that's a great idea that we should go ahead and table that and see whether the bar that we just set helps solve this dynamic a little bit and whether the two-year staggered terms are working. Any thoughts on that before we move on? Then we also were asked to think about term limits and as we all know term limits are important for the health or in our organization. Make sure that people don't burn out and it's a good way to just make sure that we get new blood on the board as well. So we suggest that we pick a year and acknowledge that some folks will be over term. Some folks will end up going more than six years to let those folks finish out their current terms so they rotate off gracefully and we go into the next slide. We recommend that the appointed terms continue at three years but any appointee can fill two consecutive full terms for a total of six years. We talked a lot about partial terms and thought as a committee that we should exempt partial terms so anybody that's brought in midterm they would complete a seat time as an appointee and then they would be able to sit for two more terms and the feeling was the same should be the case for elected community members and then if folks want to be considered again they want to be eligible again for appointment after rotating off for a year they could reach out in terms of that. Thoughts on that? That seems reasonable to me. Any concerns? Yeah, sounds good. Alright, do we actually need a vote on this? Or is this We need a vote because it's a change to the bylaws. Okay, so I move that that appointed terms should continue at three years. Appointees can fill two consecutive full terms for a total of six years. Partial terms will be exempt from this rule and after rotating off for a year, individuals can be eligible again for appointment. I've got a question before we go forward with that is Tiffany we had a bit of a chat about this just the partial thing, allay your concerns on this because I think you're feeling that six might be too short. Yeah, I think this is fine. I think as I'm slightly uncomfortable voting on it today because it is a change to the bylaws and when there's a bylaw change I actually like to see the wording change for the bylaws. But in concept I have no problem with this. Tiffany, would you like me to take this away until the next meeting and come up with some specific language for the bylaws? That would make me feel more comfortable. Okay, I'd be happy to do that if everybody else is in agreement on that. I was going to say that makes it really straightforward. I think you've got buy in this time and it certainly addresses my concerns so I'm comfortable with it so I think it's not wasted effort to try and put it in how we would change the bylaws specifically. I'm happy to do that word crafting. Before we do that let's just do a straw poll. If anyone is opposed it sounds like many of you are in favor but if you're opposed to this please maybe raise your concerns. All right. It sounds like everybody seems to be in favor with this in principle. Great. Thanks for your time everybody. Anything else? That's it. All right. Excellent. You're welcome. I just want to do a quick time check. We only have 15 minutes left so I want to see do we need to go into executive session or could we go and do the quarterly working group updates? We only had one thing via executive session and it happened via email. I don't think there's anything that's not self-explanatory in there. If it turns out it's not but it does need discussion it's fine to push till January. Are you guys comfortable with that? To basically keep going with the open session and do the working group updates or does anyone insist on the executive session? Let's just go. Great. Let's do it. Okay. I'm going to unmute George, right? George is the most patient man ever and you are now unmuted at your reward. Hi. Can you all hear me? Yeah. Hello George. Hello. Hi there. I will try to go pretty quickly here and not take up too much of your time. Hi there. This is the Drupal.org content working group update and if we want to move to the next slide once again a reminder of who we are Tatiana, Jeff, Roy and myself. Megan was on the committee. She actually stepped down in the last quarter but I also want to acknowledge that there's a couple of folks who are kind of ex-officio folks who are not represented here and that's Philip and Carrie as well as Josh who are participating in all of our meetings and kind of representing the marketing and content sides of the Drupal Association so we are well represented. Moving on to the next slide once again the kind of annual plan that we've been working on is doing the foundational work necessary to hit the ground running for Drupal.org next year as well as assisting staff with landing pages, marketing initiatives content policies and other issues as they arise. Moving on to the next slide what we did last quarter it was a very busy quarter for us actually. At DrupalCon Amsterdam we had a pretty well attended session where we spoke with the community about the progress of the project to date we spent a lot of time talking about the work we did earlier in the year with Whitney Hess on the persona development and user research portion of the project as well as kind of our roadmap moving forward into content strategy and then into sort of the design system development. We drafted and issued content strategy RFP and selected after we had a lot of really great folks issue proposals we selected form one to lead the project and we actually had the kickoff meeting I think just two weeks ago it was a two day session at the Drupal Association headquarters. Folks from the content working group we attended remotely kind of took turns participating in the session and then of course following along with all the notes and everything and Tatiana does a very good job of keeping us very updated. The terms of service which had been put out to the community this summer and had gotten a lot of pushback had come back to us for after being revised and we reviewed those, added some additional comments identified some areas that we thought was important to make sure the community really understood what it was and what it wasn't before being presented to them again and that was a successful process so the terms of service have now been adopted and we also and this is something all the working groups were asked to do at DrupalCon Amsterdam review and discuss changes to our group charter and moving on to the next slide the current project status report once again content strategy is on track and going well and then the next big thing that we're going to be kind of tackling as a group is developing the RFP for the design system development which we'd like to issue early next year most likely as the content strategy project as after it's completed or as it's wrapping up based on timing next slide current challenges so with Megan gone we're actually short a member so that's something that we'd like to address but that's related to the second item because our charter is kind of in flux right now and is likely to be revised in the near future we'd like to actually hold off on that search for a new member until the charter has been updated and approved by the board of course it impacts how we explain to folks what our group is about folks potential willingness to be part of the group and of course working group membership does need to be approved by the board as well so we want to make sure everyone is on the same page about that moving on to the next slide what we need to be efficient and this was actually related to a lot of the feedback we had in the kind of all working group session where we talked about how we can refine and change our charter one thing that is really helpful for us to have is a really clear understanding of the board approved strategic objectives we are fairly fortunate as a working group and that we among the working groups and that we have a pretty clear understanding of the interests of the board and the strategic goals of the board and can be very responsive to those you saying you have inside knowledge I am saying I have close relationships with many folks on the board oh really at least Tiffany told about that ah some closer than others so yeah so that is an advantage that we have that the other working groups don't necessarily have to the same degree and I think it has really helped us be able to take a very strategic look and to be able to look at the big picture and so you know if there is a way that that can maybe be better codified into our charter that would be wonderful the other item of course is more interaction and alignment with branding and marketing we obviously have you know in the past and with Kerry we have you know pretty good interaction with Drupal association marketing but we really have no interaction at all with the branding and marketing committee and I think particularly in the work we are doing in the next year where we are really talking about how we present Drupal.org and the Drupal project to the world at large it is going to be really great if we are able to work really closely together so I know you guys just approved a new chair for that committee and looking forward to you know working with her and working with the committee moving forward. Next slide, what we are planning to do in the next quarter completing the content strategy project reporting results to the community we are hoping to have some sort of preliminary results that we can provide to the board in advance of the retreat in January we are not expecting that the project will be complete or that we will have final findings but we should at least be able to give you kind of a preview of what we are expecting you know will come out of this project. Defining needs around the design system development and developing the RFP for the design system Josh and I have had a number of conversations about this and we have talked about it in our working group meetings you know there is two priorities that we are really looking at as part of this one of course is the ability for the Drupal Association staff to not only be part of the solution but to really own it so we are not looking at this as something where we hire someone from the outside and they come in and they dump a bunch of stuff on us and disappear we are really looking at the existing Association staff as well as any new staff members who might be brought on to really be part of this and really own it and to be able to extend it into the future and of course Holly mentioned this earlier rapid iteration and deployment of incremental changes which would be documented via a continuously updated living style guide so once again we are not looking at a large monolithic redesign where it is turned on all at once and every single page on Drupal.org suddenly looks completely different what we are looking at is you know a rollout of different design elements perhaps different sections or properties Drupal.org properties that might receive more of the design system before others do and so we will have a really good opportunity to just kind of test out different components different sites see how things are working make tweaks iterate as needed and really evolve this as we go and then of course as I alluded to before once the charter changes have been finalized which again we are hoping it will be in the next month or so we need to do a search for and nominate a new member for your approval so that is what I have are there any questions if that doesn't sound like it well thank you all very much I really appreciate everything you do over there yeah thank you George, I appreciate it Hi everyone this is Tatiana and we are a quick update from the software working group we don't know changes to our membership so we are still Angela, David, Kate and myself and previously we were mostly focused on prioritization of features and software requests to help guide the processation that brought them up for next year and once that was done and presented to the community in Amsterdam we kind of switched to our next focus which was update in working with Charter now we will talk a little bit about why we are doing this and how we are doing this so basically working with Charters were written more than a year ago now and back then we didn't really have any video and texting as a sort of two people so the situation changed but Charters didn't so we kind of started to notice that they don't really match the reality a few months ago and now that we also have a year since we actually created working groups for the first time we are able to make some conclusions and see what is working and what isn't and all of that kind of which does to think about the context the way we did it first we started this as George mentioned with all working groups meeting in Amsterdam where we kind of got all working groups in a room and talked a bit and all of us acknowledged that there is a need for some changes then software working group as well as all other working groups had internal conversation and came to the working group on general direction of the changes for Charter and we had second all working groups meeting in November which was we are looking out where each working group came with their suggestions for Charter changes and we discussed and found some same things and same ideas across all the working groups so obviously once we have the actual text that we presented for the board for approval but just to be a little bit new this is kind of the general direction of our thought what we want to change is in particular in software working chapter we want to say that the role of the working group is more advisory versus more actually doing things the working group would advise through CTO on the role of MAP and provide input on prioritization of features and working group would also help with getting feedback from the community and distribute info from us about plans to the community the type of changes also want to modify the leadership tool streams which we have right now we have three of them established so we want to kind of merge all them and then we have a group of people who are experts in specific areas of Google the talk or specific topics and we will consult them and get their input on prioritization and as we just do our incremental changes on Google the talk we will contact specific people who can give us specific feedback for this or that future so our next steps are to actually write the text now that we know what we want to say and try to get this text consistent across all the working groups and this will be something deposition staff will do once we have the text ready we will give back to working groups for review and approval and once all working groups are fine with that the text will be presented to the board for approval and we hope January, February, we will try and when this will happen and that's most of what we hope Thank you Tatiana I think one other thing to point out there we're keeping an eye on the Go ahead Achi Hey I can talk one other thing to point out there is we're keeping an eye on the Drupal.org infrastructure blockers to Drupal 8 we still have a set of 7 or 8 issues that all of the criticals in Drupal 8 are gone those issues are we have a problem at the moment we're sort of trusting the community to get those things done but I think we're monitoring that closely to see if that's going to actually happen or not I think I think another thing that we'll probably work on over the next quarter is just setting up better communication between the teams and stuff like that too I've got a thought on the these three teams then bubbling around in my head ever since Prague when they all came together for the first time I think it would be really useful for these three groups to have a formal face-to-face outside of the pressures of Drupal Con I don't know, I think budget wise it's probably going to be difficult some of those members might need to be sponsored by people to be there but I think it would be really useful if we could facilitate that happening like we have our strategic board retreat I think these groups need to have something similar I don't know that there's as much overlap in those groups as you might think they're actually pretty well cordoned off from one another I think that's a problem I don't think it's a problem I think a bigger problem is I could support something like that plus the Drupal Association tech staff or something like that but the problem is that these groups are all there's this thing in the center and I don't think all of us have met all of the people on the other side and that kind of thing so it's like this weird problem I would think that the day I stop would definitely be part of that definitely be part of that some good feedback we are technically four minutes over time I think we try and do working groups still if people do have to go because of other obligations I think that's understandable but for those I can stick around five more minutes please do thanks Tatiana thanks Tatiana so I'm filling in for Gerhard and Narayan who were unable to make it today and also for Rudy who happens to be out sex so we were kind of a little bit decimated on the infrastructure side for today's call so I'm just going to go through this really quickly this is the who we are you guys can read that annual plan a lot of this was covered in the kind of update that Holly provided so I'm not going to go into it in full detail but go ahead and go to the next one the big things for the last quarter network isolation we are working on some gateway servers that allow us for greater network isolation within the OSL we are also doing network isolation for things like our test bot infrastructure that we put on the Amazon web services environment we are continuing to work on the get move moving that onto newer hardware we're working on the staging and production those are nearly complete Narayan's been doing some great work in there helping us out upgrading the Drupal.org database servers Holly mentioned those were actually launched at right around 5 p.m. Pacific time on Monday and we immediately noticed a 100% increase increase in performance on query times in terms of how quickly overall the site is performing this also may have allowed us to close out a couple of tickets that have been very long standing about white screening problems on searches of issue queues and things like that so we were really excited to get that hardware in place it took us a little longer than we planned but it was well worth it actually frightening how little resources we're actually using on those machines we keep joking about putting stuff on them we've also introduced some Drupal specific monitoring one of the ways that we knew that we had that big of a performance increase is because we're actually using New Relic in an evaluation stage right now on the applications and the server monitoring current project status the open stack now hosts all dev and staging VMs we have nothing on the older hardware the new private network switches are being used which is good that ties into the gateway process that we were talking about earlier Edgecast CDN is in front of all Drupal.org and subsites and there's definitely been some performance noticed from that we're also testing, it says Fastly but we're actually testing both Max CDN and Fastly looking for a solution for our download traffic so this would be a traffic that comes from FTP.Drupal.org typically packaged projects CF Engine has been removed from all the servers except for Solar, Media and Util and we're very excited to get those last three knocked out here in the early part of 2015 we continue to work on reducing technical debt obviously removing CF Engine is a big part of this also rewriting all the puppet modules simplifying our server management and Holly touched on this this is really important to the future of Drupal.org we have to become independent of any particular hosting platform so that we can be as nimble as possible and use all the best practices we should be using and that's all about the disconnecting those central services that we're currently using at the OSL. A big thing is actually going to be when we start transferring off of their mail servers that will be one of the bigger transitions that we have to take on in early 2015 obviously there will be a little bit on the Charter Updates front coming out of the infrastructure working group and those last little bits of finalizing actually we could cross off the first one because that was actually finalized all right. Thank you it's the benefit of having a fast talker for the last one Thanks, thanks Josh That was great Josh, thank you Thank you very much Any questions on that from anyone? No questions All right I think we can wrap up the meeting I'm sorry we didn't manage to go a little faster so we could still go to the executive committee but unfortunately none of these things are urgent and so we can postpone them to next time Thanks everybody for participating, thanks for all the updates and all the amazing progress it's great to see all the updates in between the different board meetings for Charter Thank you guys Have a great holiday and I look forward to seeing you all in person in January What are the dates on that? 21-22 And Holly does that mean we don't have a normal board meeting in January? We have a normal board meeting in the middle of our retreat where we schedule it That's another comment Okay Thanks everybody, you're all awesome I love you all Happy holidays everybody Happy holidays, thanks everyone Great meeting Bye