 Lillian Gray is the founder and CEO of Wiki New Zealand and we are working to democratise data and pull together data from a variety of sources and make it so that everyone can use it. One of the core principles of that was making the stand that I don't think open is necessarily— Can you hear me? Is that going away? Is that right? Okay. That open is kind of far enough. I think that open can technically mean that some people can access it but still not everyone can actually use something and that we need to work on how to make something truly usable and present things in the language that other people kind of receive and can understand before it's really widespread. So I'll talk a bit tomorrow about Wiki New Zealand and some of my dreams with data and open and truly usable data. But what I want to talk to you today, I've just got five minutes, is that I find open source stuff really intimidating and I find the community intimidating and scary. And the reason I want to share that part of you and share my real honest kind of thinking and feelings is because the journey with Wiki New Zealand, I have learnt that it is not sufficient to have a great idea over in a corner somewhere and then try and convince everybody else to come over here. The role of really embedding something really widespread into people's thinking, into things that people can actually pick up and act and embed in their own systems is getting into their world, getting into their shoes and understanding what their misconceptions are and what they're afraid of and using a language where they can kind of understand what you're trying to impart. So hopefully, so I might say some things now that you find misinformed or jarring or obvious and naive, but the purpose of me saying this to you is so that you understand what some of the misconceptions could be and through my learnings and how I have been interacting with and using open source. So I used to think that the open source community was something that was kind of like an underground kind of community that did things in parallel and staunchly opposed the way that other things were done. And when I started Wiki New Zealand, I had a developer come along and say that they could create what I wanted pretty easily by using some open source tools and I was like, yep, sure, great, didn't really know what that meant exactly, didn't really care, just really wanted the thing that was in my head to exist. And so he was able to knock something together in about 60 hours and that kind of initial proof of concept site was something that I was able to use for kind of the two and a half years following and use to kind of show people my idea and what to do. And I didn't give too much thought to open source and how Wiki New Zealand and how we fit into the community until more recently, like I've been asked a couple of times to talk at the Linux conference and others when I'm like, oh, I'm now kind of starting to tiptoe into this community that I find a little bit scary. And the people that I work with are very strong proponents of open source. I want to understand more about this and really think about how we've been able to win using it and understand how it kind of fits into the world and the models we can use. Because what I find now is with Wiki New Zealand, we've now got like a really valuable piece of software and I'm sitting there with my shoes going, I need eye with my CEO hat on, need to have a sustainable revenue model. I've got people actually coming to me saying, can we license what you're doing and can we pay for it? And I'm like, yes, but my whole team want to open source it and I want to be able to give back to the community. And I'm sitting there going, I don't understand how to operate in this world. I don't understand who to talk to and who can speak my language. Who will come and sit in my boat and say, yep, we understand that these are the priorities that you have and this is how you can kind of embed open source thinking. And when I think about the potential of open source based on my understanding, so I see it as essentially like a big tree where it means that everybody can build branches but nobody has to build their own trunk. And I'm quite a first principles kind of person. So when I think about that, I'm like, it just makes sense. So much sense, of course. I do a lot of talking and stuff about innovation and growing the economy and stuff through innovation ideas and nothing makes more sense than being able to build on the thoughts that people have already had. It seems madness that we're developing software and other things in parallel to each other and solving things in parallel. So why isn't it more widespread throughout governments, throughout other commercial organisations? And I have so many questions about it. So I'm glad we're allowed to ask lots of questions in the next couple of days. Because when I've talked to people about open source and how I feel, like I don't know how efficient the community, it's been really interesting because the reactions often are same. Like I find it intimidating too and these are from people that I think of as being part of community. And I was just reflecting actually as someone earlier was speaking. The word community is awesome when you're in it. It's really cool, right? And when you're not in it, it's so intimidating because you don't know how to get in it. You don't know what that means. And so when I talk to people in the public sector about things about openness and open society, I certainly don't feel like they're part of a community. And so my question is what can you do? What kind of language can you use? What can you learn to help those that currently feel a bit scared to understand the models that can be used? How we can not feel like you have to go right to one extreme of the ideology but actually bring the open source principles and embed them into what we're currently dealing with. And so I'd love it. The next couple of days are a great opportunity, of course, to meet with your peers and talk about the stuff that you already believe in and care about and build on that. But I would encourage you that after that, that you instead find people that don't believe what you believe and take it on board that it's your responsibility to find the language and the stories to bring them on the journey and so that they understand and they know how to embed things into what they're doing. And I'd be very, very open to hearing that kind of conversation from any of you.