 So, we're here to have a little chat about the Drupal South Committee and this, we just thought we'd prepare some information for anyone that wanted to find out about the committee and what we're doing and why we're here, so there's a bit of self-justification in this but also we want to be transparent about what we're doing and how it's running and the things we're trying to achieve at the moment. So, primarily this committee exists for one purpose, this is the primary purpose of the committee and that's to ensure the continuity of Drupal South. We want to make it easier for people to run these events, we want to make sure they get run and we want to make sure that people aren't reinventing the wheel every year but alongside that we see this as an opportunity to expand lots of different aspects of Drupal adoption in Australia and New Zealand and we're sort of trying to cherry pick ideas that people think are good and where there are opportunities. So, a lot of this for us has been about listening to what people have to say as well, so sometimes we might come out and say, we think this but if you guys tell us something else then we're going to listen to that and move in that direction as well. Alright, so why does this committee exist? What is the purpose of the Drupal South Committee? Well, previously when you wanted to run one of these events in Australia or New Zealand, you would usually go to Linux Australia and say, hey, I've got this idea for an event, can I have some money or can you spot me some cash till we get some ticket sales please? And they go, yeah, sure, right. And they might consult with previous organisers who we called Ghosts and those people would usually have had some involvement in the pitch anyway and that would all be accepted and you'd go and do it. But then the next time you wanted to do it, the same thing would happen again and the people would come along and have no idea what they were doing and it would be really hard work. So the Drupal South Steering Committee sits between Linux Australia and these event teams. The Steering Committee reports to Linux Australia on budget, an event, success, so we actually have an official Linux Australia capacity there. And then individual event teams report into us on their events and how they're going and we help them be a success. You'll notice that the Ghosts are missing from this slide, it's not really deliberate, it's just that the Ghosts were kind of necessary in the past, it didn't function without those Ghosts being there whereas it can continue now in a bit more of a structured way. And we're also trying to foster better cross event participation as well so that in any given year there might be some people on one event team who are going to go on and do other ones in the future so they get some experience. Or people who come back and do them again. Alright so the Steering Committee, Subcommittee of Linux Australia, it came out of a six month consultation period led by Ghosts, was formed in 2019 following a community vote. It has five members and we're on rolling two year terms. So we have a, I haven't put it up because it's a bit confusing, but we have a schedule to show when individual committee members will roll off and be re-elected and the idea is that we hold one election, the next one would probably be early 2020 and that elects the next five people and they roll on slowly. So the purpose of those overlapping rolling terms is to ensure that there's always continuity on the committee. You don't get a wholly fresh committee coming in not having any context or knowing what's going on. In any case, the whole committee gets re-elected next year. So current committee should all be in the room down the front, Owen Lansbury, elected as chair, Pamela Barone, Event Liaison and a Code of Conduct Reporting Officer, Tom Tugood, Government Liaison and a Code of Conduct Reporting Officer, Nicole Kirsch, Treasurer and myself, Christopher Skeen and I do Corporate Liaison and Marketing. So how does the committee function? What do we do on a day-to-day basis? Essentially, we're running this with a monthly meeting. Those haven't been public yet, but I think we're open to that idea of having public meetings. Yeah, so if you're interested in attending the meetings, let us know and we'll make sure you're included. We communicate a lot through Slack, through the Drupal South Slack and that's somewhere you can find us and we also are trying to post regularly on groups.drupal.org and the Drupal South website and I think going forward as we sort out what the hell we're doing because we often don't know ourselves, we'll be doing more mail-outs as well through the mailing list to keep people up to date. So we have a few current activities and these are based on some strategic priorities that we work through and also our discussions with people so I'll run through these pretty quick. First of all, we're coordinating the annual event program and now that is primarily Drupal South but it also includes Drupal Gov and it may include one or two other little events as well depending on where we think there are opportunities. We're doing some community initiatives so an example of this is some of the things we discussed in the BOF at 11 o'clock today around meetups so we're trying to find ways to improve the communication and knowledge sharing between meetups and see where the opportunities for those meetups are to work together. One of the interesting ideas that came out this morning, for example, was like shared regional meetups via video hookup, for example, there was some interest in that. Provide some common tools where they're useful for those meetup groups and potentially assist with funding for smaller items should you need them, event or venue hire or pizza or whatever, meetup. We're looking at annual sponsor packages as a way of providing for a more continuous and less burdensome method of funding Drupal South so instead of not really knowing how many events are going to crop up during the year and being asked maybe to fund all of them as a sponsor, you can have one opportunity to engage with Drupal South and then whatever we run comes out of that so that's good for Drupal South in the sense that we have a more predictable funding model and it's potentially good for sponsors and that we can offer value in different places as well and reduce the number of times you have to sit there and stare at a sponsor proposal. Anyway, we're still talking about that one. We're doing quite a lot of data collection stuff currently. We're trying to get a better understanding of the current market and what's going on. So we recently ran the Drupal sponsor survey in Australia and that fed into the huge response, fed into the BOF that was held yesterday and we are about to run a Drupal user survey. It was meant to be ready for this event because I was sick, it's not so it'll come soon but that is a survey hopefully of any and all Drupal users we can find in Australia and New Zealand and find out what they're doing and some of their interests. We also have a growth strategy. Now this is a bunch of various things that we've been poking at and looking at in different ways and I've put them together on this slide called growth strategy. We don't actually have a growth strategy, we just have some things that we're looking at. So some of these ideas are engaging a local marketing specialist to do a little bit of Drupal marketing for us. We're looking at refreshing the website. We've talked about one day decision maker summits like a CTO summit and similarly we're looking at maybe where we could possibly run like a Drupal booth at a related event. Now some of the strategy around that relates to why we would do that. So for example, are we going to places where we expect to be putting Drupal up against other systems like Adobe? Are we competing on behalf of our constituents? Or are we going out to recruit people into intern programs for example? So the reasoning behind that might depend on where we think the strategic priority is and that comes from what you tell us. We're also developing a content calendar and we're thinking about how we can create content, where we can create content be valuable. Obviously we're all volunteers, we have a limited amount of time. We're not going to be spinning out loads of content but maybe a little bit here and there where it's strategically useful. We have regional initiatives which we are looking at. One is the potential of running a Splash awards in Asia PAC and another is how we can share materials and events or not sorry not events materials and speakers with other Asia PAC events. So the Australian New Zealand Drupal group is by far the most active group in this part of the world outside of India. India has a very active group as well but pretty much every other country is quite small so you know potentially helping those areas with some sort of shared stuff is going to be useful too. And the last one on their work towards facilitating Drupalcon Asia Pacific with the Drupal Association might be a bit of a pipe dream or a wish list item but certainly we know we're able to deliver very high quality events consistently and with a high level of organisations so that might be a possibility of rebranding one of these as a Drupalcon. Public sector initiatives so we've incorporated this year the running of Drupalgov into the Drupal South schedule. Drupalgov has always been something that's run a bit ad hoc. I've kind of kept custodian ownership of it but other people have come along and done it. It's becoming a full part of the Drupal South schedule at this point though at the moment we haven't worked out how often or where we might run it. We just know that we think it makes sense to do it that way. And we've got Tom who's our public sector liaison as well so it's his job to reach out there. Corporate initiatives, this is about talking to corporates using Drupal and also agencies to some extent. We haven't done a whole lot here but the user survey is part of that. All right, so how can we help you? How can the committee, what can we do for people who are interested in being involved? Primarily outside of running the events and organising the events we provide support for camps, meetups and other local events. So we talked about that a bit already. We are looking at ways to support the Drupal market and share marketing around Drupal events. So I think just this morning we talked about putting up a shared channel in the Drupal South Slack. So if anyone's promoting any Drupal events or any of their own events that are Drupal related locally and they want a bit more wide press for that they can share it in the Drupal South Slack and we'll retweet it or push it through Facebook or whatever just to amplify your message a bit. And less useful for you guys I think but if you're looking for training or services or other providers then we can help you find those. Useful dates. Okay, the next steering committee elections according to our calendar are July 2020. So that's the first thing if you're interested in standing for the committee that's likely when the next elections will be. And the next Drupal South request for proposals probably going to be spring 2020. We haven't actually discussed this but that seems to be the logical date based on our current calendar. So what do we look for when we do a Drupal South request for proposals? We've done this once already and Owen ran that. Do you want to talk briefly about that? That's all right. I was actually trying to see when the keynote was on. Who would be interested in running a Drupal South? Yeah, what's your name? Nigel. Nice to meet you. So I think as Chris said, we view this committee's role as supporting local teams to run regional events without as much self-sacrifice as may have been required in the past. And I think credit to the team here they did do quite a lot of self-sacrifice because they were already in motion by the time that we formed the steering committee. But one of the ideas that we've put forward which one of the next organisers already jumped onto is to budget for an actual event facilitator slash coordinator to do a lot of the kind of grunt work of printing badges and doing ticket refunds and that type of thing. So we do want to elevate the local organisers into primarily a strategic role of content and programme formats and liaising with great keynote speakers and running really interesting workshops and that type of thing as opposed to being the ones that are actually pressing the print button on tickets and that kind of thing. So I think in terms of future events, we still want to have a back and forth between New Zealand and Australia as much as possible and that might be on a year for year basis. It might be in Australia for two years and in New Zealand for one year. We'll just kind of take it as it comes. And I think the considerations are great venue, location that's relatively easy to get to. I know that all the Kiwis had to get up at three o'clock in the morning to get here. It's not totally ideal, but I think something like Hobart counteracts that in terms of it's such an amazing location. So location is key. And then the big focus is on managing speakers and that type of thing. Does that kind of cover what you wanted me to talk about? I suppose so, yes. I mean, if you are interested at all, come and talk to us and we'll give you more information, I guess. Yeah. Any questions on events? Is the location of the Drupal South dependent on who's organizing it? So ideally, you would have people on the ground in the location that you're running it unless we run one in Fiji, for example. Definitely a possibility. Direct from most capital cities. Yeah. So I mean, that's definitely a consideration. I think the learning from the Drupal Association globally was that they really could not run successful Drupal cons in Europe, unassisted by a local team on the ground. So that's why they've gone with that model of having Coerney. But there might be some ideas that come out like a Fiji or some kind of really interesting location where it's like that makes total sense. Let's do something like that. The other thing I'll mention around events is Chris mentioned kind of summits and in one of the boss, we started talking about actual focused dev days and those types of things. I think the model that we're most likely to go with for that would be a professional facilitator for those events with some local presence again and non content expertise, that type of thing. So we're running a Drupal Dev Day in Sydney, Murray and the need up organisers may play a key role in that in terms of speakers and running workshops and that type of thing. So the message is that these events are where we all come together. But then I think there's a lot of opportunity for individual events that are targeting specific audiences that either don't get a huge amount out of coming to a big group event like this or have really specific needs. So people that are new to Drupal, really highly experienced developers, decision makers, all of that type of thing. We want to be able to have forums for those people to be able to interact. I should stop talking here. Yeah, so we I think our aim is to pick a good team regardless of the location and then make sure that they've got a good venue for the kind of event they want to run. And we're open to the kind of events that people want to run. Obviously, the only thing we really can't do is run the event. So if you come to us and go, this event is really cool, I want you to do one, we probably won't do it. But if you come along and say, this event is really cool, and I want you to help me do one, then we'd be very open to it. Yeah, I'm in a great example be run a women in Drupal event. Okay, don't run a women in Drupal event. If you chose to. Yeah, sure. I'm nearly done. So how can you talk to us? Well, you can talk to us here. And if you can, you can call us at any point in time, you can reach us through the email address, say hello at Drupal South.org. You can use the contact form. You can email us personally. I think most of you probably know us anyway. And if you are engaged in any kind of local Drupal community coordination, you can get into the Drupal South Slack if you're not already on it and participate in there too. So we do a lot of kind of coordination and organization there. And you can get an invite from the Australian Drupal Slack if you just ask or just ping one of us. Finally, and this is really important, we do handle code of conduct reports for our events. And we follow basically the Drupal code of conduct. We do have a copy of this adapted for Drupal South on our own website. By adapted, I mean we put the word South after the word Drupal most of the time. And we have two dedicated code of conduct officers, Pam and Tom. And when a code of conduct report comes into that email address, they see it and the rest of the committee doesn't. So that's a we're trying to follow the best practice that we can for this. And I think have both of you done the training or just just Pam. So Pam's also done code of conduct training as well. Do you want to talk about that at all? Yeah, I should. There's a company called OtterTech that the Drupal Association has engaged with to run a workshop in how to handle code of conduct incidents. And I participated in that. I think it was last week. And it was really interesting. I was a bit skeptical, but it was really informative. It just kind of talked about empathy when talking to both the reporter and the reported person and, you know, strategies for dealing with tricky situations and ways to mitigate things and just kind of how to treat, you know, first complaint, then sort of escalating and how to kind of how to consider something resolved or, you know, just anyway, it was really interesting. So I did that with a couple of Drupal Association people. And yeah, it was well worth it. I think we haven't had any complaints at this event though. So all good. One more party to go. So we take this very seriously and we have as a committee handled a couple of complaints in the last 12 months. So, you know, it's been a bit of a learning process for us too, but we do take it seriously. So yeah, good Q&A. Hi, I'm Heike. Now I'm hanging out on these events since Drupal South, if you don't even know, it was called Drupal South in Wellington. And in 2014, I've organized code sprints. I've organized the Drupal cards. I've done lots of things. And what I experienced, I wasn't in Canberra last year, sorry, but I've, I've, oh, sorry, you record me. Oh my God. Okay. You can complain about the code of conduct later if I go overboard. Okay. So I know most of your faces, maybe after all of these years, you know my face. This is my first problem. We are talking to each other all the time. Like it's the same people all the time. Now I was sitting in the keynote yesterday and we can think about this keynote. We can think about the keynote, whatever we want. But I was under the impression that she's preaching to the choir. But when I look at this, I think she isn't. Because if we want to have, sorry, that's really getting me here. But if we want to have days like women in Drupal, or Drupal death days, or Drupal South, or Drupal whatever, then we just create silos. Yeah. We need to collaborate. I mean, this wasn't rocket science what she said yesterday. It was like very like stereotype. And I thought like, Oh, okay. I actually think that the coder is the hipster. He has more tattoos. So I'm just, I'm just like, I don't understand why we, why we are not trying. So for example, just a tiny example in Wellington in 2014, we were just running and totally Drupal code sprint for Drupal who never seen Drupal. Yeah. They weren't sitting there just around the tables not talking to each other. They got these, was like a game board and they could play the game and move around and stuff like that. And it worked next to your sprint at this time. You're like, you can do your thing and we can make room for this. And then, yeah, so how, how, how do we actually get out of this silo? It is about Drupal and I don't want to make it not about Drupal, but can't it be about more? I don't know. I mean, we want to, isn't, isn't what we want to do in the end do great websites? I don't. No, I, I, I, I guess I don't know what. Yeah, I, I must, I, when you say the silos and you don't think we should do dev days and you don't think we should do. No, I don't. Oh, is that not what you're saying? I guess I, I don't completely know if I know what angle you're taking. And I, I have thought a lot about this over the past few months. So Drupal South will always be the coming together. It's our signature event. It's the opportunity for us to all see what's happening in different parts of our community and ecosystem using Drupal. A lot of feedback that we have had though from buffs that we've run over the last couple of days with sponsors and with community organizers, who else did we run a buff with? So some of the feedback is if I'm a really experienced developer and I'm coming to Drupal South, I'm not necessarily learning things because things are usually at a relatively high level. level and not doing deep dives. I might get at that at the sprint if I'm participating in that. But I think something that Murray said before in the bof was that when they get together in meetups, it's a lot of people who are very experienced who sit around and just talk about deep Drupal problems. If you put someone who's a beginner near to Drupal, who's not a coder, who's a business decision maker etc, they're not going to get much out of those conversations but the really deep developers do. And so having a forum for those we view as being a potential. Yeah I'm not against code sprints. I just want non-developers go to code sprints. Yeah so I think I want non-developers go to code sprints. I've been on a lot of code sprints. So just to go back to what I first said Drupal South will be that but we have identified that there's really key audiences that we're not reaching at the moment or not having a dialogue with whose meet needs aren't necessarily met. And so another example would be business decision makers aren't necessarily coming to Drupal South. They view it as arts to techie, everyone's talking about coding. So there's definitely an opportunity for us to facilitate a decision maker summit where we're talking about Drupal at a very high level as a digital experience management platform or whatever where we're actually positioning Drupal as a real option for them to consider when they're talking about their next budgets. So one thing that I have said repeatedly over the last few days is there's no one-size-fits-all approach. We've got a lot of ideas. We can only initiate so many of them and one of the processes that we've gone through is to prioritise based on need, impact and effort. So if something has a clear need it's going to have a high impact and it's a relatively low effort for us to implement. They're the types of things that we'll start doing early on. Things that have less need, low impact but quite complex, we're probably not going to spend time on. Does that kind of answer your question? I do a lot of consulting. This still looks very from the inside out to me and not from the outside in. I'm just wondering even with the business people, if the problem is that they don't feel that this is something they should go to, why isn't there a business forum that just happens at the same time that Drupal South happens so that they can actually see that we are not all nerds. Nothing against nerds are cool. That's definitely an option. They did run something like that in Seattle where they had a separate business track and my view is that it was quite a big failure. So it was really siloed off from the rest of the event. There really wasn't a lot of interaction. The content that was being talked about there really wasn't that well attended. So we can try different approaches, see what works. We're totally open to experimenting but I think just getting back to what I originally said, Drupal South will be an opportunity to bring a lot of people together but there's opportunities for us to be really talking more directly to people that might not otherwise come to this event. I think also this year there was a little experimentation so largely the same format but Vlad just decided to run some workshops and that actually he wasn't sure whether anyone was gonna show up and lots of people did show up. So that was a huge success and I think his feedback was we should definitely keep doing that because it's a way of attracting people that might not otherwise come. So I think also part of it is like if you feel strongly that there should be a business day at the next Drupal South then you know just kind of start the conversation. This was just an example of what he wants to silo and I just said whatever you want to silo I don't think it's a good idea to take it away from the synergy of this event. So we just basically like there's only so much attention and so much synergy in something and if you split those things the synergy stuff things happening people. No I know but I'm just saying the the conference is it's organized by an organizing team that all volunteers and all bring their own ideas so if you know if we decide that running a business day like to be honest with you I think getting those types to fly to Hobart or to fly to wherever it may be is a bit tricky so maybe we start with running one in one of the major cities see how it goes or again if you know if the people who are organizing the next one feel that there's a big business community that might be interested in that just run one but but the thing is that you know Campbell and his team didn't have the bandwidth to add another thing that's why like I said Vladimir came in and said I want to run a workshop he ran the workshop we have no complaints here like yeah no I know I'm saying though I'm saying that it's it's not about us telling the committee that the organizing teams what to do it's about the organizing teams doing what they have the capacity to do and coming up with ideas and us helping them achieve those but we're not here to tell the cities and the teams what they have to do and what format they have to meet we so that I mean I think when you said it's inside out rather than outside in ideally we are having a bit of outside each time like you know Campbell's relatively new to the community he came to Canberra to learn how it all worked and learn the ropes and I think he brought a fresh perspective so I think that yeah it's really definitely not us trying to tell the community tell whoever that this is how it has to be or this is what we want it's about us finding out what the community wants and then having the the framework to support it more than that well that's how I hope it works out it's only new but that's what I hope happens yeah okay that's exactly what we're sort of trying to achieve just to have a bit of a framework so easier for other organizers and then if you decide to do a business day or do a woman in tech or do an event then at least as templates you can use to make it easier for you because a lot of our companies invest a lot of time into us for organizing events so I think if we can reduce that time that would be I think that's sort of the ideal yeah I mean one of the things we have to look at as well I still remember that decision of actually running Drupal South in a weekday you know way back when and we're actually really privileged to be here on a Friday you know it's a work day on a you know another city our work allows us to do that and so a lot of these smaller events are critical to building this community because there's still what 270 here which are you know really lucky but there's a lot more in Australia New Zealand so we've got to have or you know we've got to build this community and make sure we're all inclusive there but what you're saying with non-code is going to code sprint events I was in Amsterdam I think it was one of the first ones they did it but they had a huge section of the sprint day dedicated to non-developers and it was really really successful so I mean that's something we can we can do here and then be guided by you know what's happening in the bigger community as well. I don't want to I don't want to steal the whole discussion but one more thing I'm sorry I totally got misunderstood this when Owen said that we're going to do this I think what you should or this is just a suggestion feedback I will send it via email if you do something like this it should be like there should be nothing else going on don't you want to talk to everybody like shouldn't this like for it shouldn't this like more of a kind of a panel thing. It is a panel. Everyone's invited but no one turned up. Yeah. Yeah. Okay. Okay. Yeah. Yeah. Yeah. So do you see I saw I saw stuff that you want to work with the Drupal association and Drupal cons and all of us but what do you see as your other opportunities to just not make this between us all the time like how do we get more people. Do you want me to answer this one first. So the last few months have been this kind of broad spread of ideas of where should our focus go. And I think it's it's come down to there's a Drupal product awareness component to what we need to do. So whether we're promoting Drupal into other open source communities into commercial environments so whether we're actually kind of running a generic Drupal sponsored boo that a key event that type of thing to raise product awareness and the Drupal association is also putting a huge amount of work around that. So they've got a dedicated marketing director. There's a lot of work being done around Drupal product marketing that we can all leverage. Another big component is reaching people that aren't using Drupal. So we've done a lot of talking a couple of buffs around how do we reach university students and demonstrate that there's a clear career path for Drupal implementing things like internship programs that they can move into more consolidated training materials and ecosystem for independent providers to do Drupal training. I think there are a couple more people who want to ask questions but I will say that's it's on the radar of things we want to address bringing more people in. We don't have the answer but it's one of the things that we definitely want to do because we don't enjoy just staring at each other. And then the final thing that I'll note is that we know that there's a huge number of Drupal users who are now working embedded in large organisations that we have no contact with as a community because those people turn up for their day job, they use Drupal, either as content editors, they might even be developers and it's just what they use at work. And I think there's, like I said, there's a different way of communicating with that type of audience in terms of content that would attract them that's not based on a sense of it's a Drupal community, it's I'm doing something with Drupal that's advancing my own career and by exposing them to Drupal and the community through those outreach programmes which are yet to be defined, you're then broadening the opportunity of people then starting to engage and that might be at a co-contribution level, it might be attendance at events like this etc etc. So did you want to go? I've forgotten your name. It just goes back to what Tom was saying I think about the code sprint and it just triggered a thought in my mind that I didn't notice a coder's lounge, I know there was the quiet room but it's just occurred to me that a coder's lounge has been absent from this year and maybe last year as well and I don't know if that's a facilities thing Yeah it usually is. So the number of rooms that are available in any given venue determines essentially what can be done there. I don't know, yeah we only had one bathroom, I don't know if there's other ones here, so I'm just going to answer that question. I do have a quick thing is that I feel like it's often a case of how much space we've got, we've actually got a lot of space here. There's actually a lot of places people can break out so sometimes it's something that's practical if the venue is kind of squishy but no I actually have a follow-up question. Sorry just the fact that it's not necessarily just coders involved in this process anymore and the DA is really pushing that fact is that I want to make it more welcoming. I'm going to do some photography outside again but I wanted to make a comment that it's really what I've really found really interesting is that Campbell's journey from two years ago going to Drupal South Auckland to running a conference has been quite incredible. We haven't been overly involved in pushing him in terms of guiding him other than the questions he's asked so a lot of the support he's got has been from the existing community. So sometimes I feel like the steering committee is just about formalising what we're already doing pretty well. I don't know how we're doing it well but we're doing it pretty well so yeah so I like what I hear about we don't need to make it top down. We want to get the Campbell's doing what they feel passionate about and bringing what they bring into it but then saying I need help. I need help for this, this and this who's done it before and how we connect those people up. And now we have money for it too so when you guys have ideas and you need help we can actually help with money now rather than just like cheerleading. So I'll be really quick first of all I just want to say I acknowledge that you guys are all volunteering in your own time so thank you for doing that. And I wish if I knew more of the people who were doing the groundwork like Campbell that we could say that to them as well because I feel like that's a thankless job and probably hasn't received enough recognition. My question however is why Linux Australia and what value is there in that relationship versus being I would have assumed that that would have been a Drupal Association top level sort of relationship. Sure that's a good question. There's a number of reasons. Firstly Linux Australia actually does a really good job of supporting open source communities in general. It supports us, it supports WordCamps, PyCon, Laravel, a whole bunch of stuff and what it does is it provides financial governance, insurance, banking and also a giant pool of cash in case somebody has a massive screw up and messes up an event. I think they have basically a slush fund that sits there for emergencies. So they're providing a guarantee essentially around delivery that's very helpful. They also understand this kind of event and how it runs in this country and then that's really useful. So as a supporter they're a great supporter. They're fairly good at what they do. Their business is supporting these kind of events and in return we give them 6% of gross income basically which is actually not a whole lot. It's a relatively small amount of money from the event and it's factored into our budgets quite easily. Okay good that's clear. Thank you. Yeah the Drupal Association has toyed with offering that level of support in the past. We've had some events in Australia that have run associated with the DA but it's all done through the US. It's all in US dollars. It's US insurances and then it's not practical for them to do it. So the model that most local Drupal Associations have followed is to incorporate themselves. So India and Netherlands, a bunch of other places have incorporated their own local associations off their own back and now the DA has come in off the top of that to say okay well let's all start talking together. Let's facilitate collaboration, common best practices etc etc. So they're more facilitating at that level as opposed to getting directly involved. We've got about 10 minutes. Well, any last questions or comments? Oh thank you. Thank you for coming to Drupal South. Wouldn't happen without people coming. Fiji.