 All right. So I've got a lot of things I want to get off my chest. I've got 45 minutes and probably 167 slides, not quite that many. But I want to talk less about Moodle as just the software and features, and more about Moodle as the project, and there's a lot. We did do a release recently, Moodle 2.9, and that's a picture of my kids there. You may know, those of you who are long-time Moodlers may know, I put a picture of my kids on every release ever since the beginning. This is one of the other photos that didn't make it from that photo session. I just really like the I Like Pie t-shirt. I just don't know why I keep showing this photograph. But they've really grown up. In the time, that's representative how old Moodle is, because they're about the same age. My daughter's the same age as Moodle. That's how long we've been going. And there were a lot of features in 2.9, and I'm not going to talk about them because hopefully our community educators and people at HQ are doing their job and pumping that information out, and I think there's some sessions about it this week as well. I've been spending a lot of my time thinking about the nature of learning in the past year or so, and about the importance of feedback to learning. And to me, feedback is like the universal law. If you think of most good educational situations, you can describe them in terms of what kind of feedback loops have you set up for that person who's learning to interact with other people, to interact with the environment, and to be reflecting. What does that mean for something like Moodle, which is my third child, if you like, also a learning project, and we've learned a lot over the past 13 years, 14 years. Moodle also develops through feedback, and it develops by feedback with the environment, the internet environment. When I started Moodle, gopher was still pretty common, it was everywhere. In fact, it's still running today, I'm quite glad to see, I was doing a bit of gopher exploration last night. But as you know, the whole internet and all our technologies are evolving very rapidly, and I think in a few years it's going to be quite quaint, that we used to rub our fingers on pieces of glass, things are moving that fast. It develops through feedback from people, and this is a critical part in why these kinds of gatherings are so important, but also on Moodle.org and all the things that we have set up to have feedback from the community and around and around with developers. And the reflection part of Moodle is about testing. We have a lot of testing that we do, and a lot more we can still do, to have Moodle evolving according to its own principles. So it's always important to focus on what the goal of what we're here is. Why are we here? And I always like to show this slide, because it shows our mission. Moodle is a learning platform, which means it's not one system, it's a platform on which you build a system. So each institution takes Moodle and can turn it into what the system that they need. We're about supporting teachers with their teaching, we're about supporting learners with their learning, we're about integrating everything for a course. Critically, it's about being open in every way, because that allows privacy and that allows customizability in all the things that we want. It's critical that Moodle be easily used for free, and that encompasses usability, accessibility, and all those things from any device, and not just screens, but other devices that people use to access internet now and in the future. It's about being flexible, it's about scaling to any size, look at the size of this campus, and they can take Moodle and run 15,000 active courses on it, it's quite amazing. There are some Moodle sites that have 2 million users. And lastly, anyone can contribute to global education, and there are many of you here, and I hope you all manage to find each other, who you probably know each other as names on the tracker, or as names on the forums, and you, for many years, some of you have talked to each other and shared things, and you may not have met in person, but you've contributed in some way to Moodle as a global platform. And that's what I love about this project, and I think this needs to exist in the world. We need things like this, things that are open, that have a strong mission to support education, but are not driven by financial interests, are not driven by governmental interests or cultural agendas or anything else, but are trying to be a neutral supporting platform to enable human beings to do whatever they want to do with it. And open source in general is about this, and Moodle's about this, and I feel very strongly that this project needs to exist in some way. It'd be a lot easier for me to go and just get a job somewhere, but I will be working on this for as long as I'm alive, I think. So, through the years, we've had so many releases that's kind of how the releases have looked in the last few years. I'll point out here that Moodle 3.1 will be a long-term support release. That's 100% locked in. So every four releases, we plan to have a long-term support release that we keep supporting for a few years. And I would normally then start talking about the roadmap for the next release, which is 3.0 and 3.1. And generally, things in Moodle fall into these five camps. But I've got a question mark here because I want to talk about a change in how Moodle is going to be working in the future and how it's going to be developing in the future. So currently, this is the way Moodle works, and I don't normally like to talk about money, but I've been doing it a lot this year because when we talk about open source, there is a lot of contributing and a lot of love going around, and that's how it works. But underneath that, there are people who need to eat and have houses over their family's heads. So how do we make free software is what I want to talk about here. So currently, this is how we work. We have a user community that uses Moodle partners, Moodle partner companies do services, hosting, training, consulting, these sorts of services. They give roughly 10% royalties towards Moodle HQ. That's what we use to pay the core developers, and those core developers coordinate the community, take all those open source things that are floating around, and bring it together into a Moodle core release. But also the community themselves are funded, however they manage to, to produce plugins on top of that. We have many of you who here is a developer at a university or an institution or a college or in schools, okay, you can see probably about 50 hands, which is great. And on the last day, we're having a developer-only event on Hackfest on Friday. So that's how it's worked. That has enabled us, through these partners, and I think that's most of the partners, that are around the world, the sort of 67-something companies around the world that support Moodle as a partner. There's three here in the US, classroom revolution, Moodle rooms, and web anywhere. Remote Learner are no longer a partner as of recently. We are going to be adding some more partners in the US very, very soon. I hope to announce them later this week. Those partners pay for this group of people, Moodle HQ. This is us outside the office in Perth. About two-thirds of us are at the office there. About a third of us are spread out around the world. Some of them are here. So these are good events for us to kind of get together as well. So make sure you grab any of these people around the conference if you see them, ask them the hard, curly questions, because they need to hear from you. I say so. And the values of HQ, they're very aligned with the mission of Moodle. It's about learning. It's about being open. It's about respect. It's about being ethical. And it's about experimentation. It's about trying new things and pushing the envelopes. So this is what we do. We work on the Moodle core. We fix bugs. We look after security. We integrate software from around the world. We work on community education. We actually do new developments as well. We have a Moodle mobile app, which just, the latest version was just released, and I'll talk about that a bit later. We provide notification services. So that's how messages can get from your Moodle to a student's mobile app, for example, through the mysterious internet. We also maintain and develop all the community sites, Moodle.org, the Moodle docs, Tracker, Moodle.net, which is our OER platform, Open Educational Resources. We run a MOOC, and the next one is, it runs twice a year. The next one starts in only a few days. I think it's August 9th. So if you're new to Moodle, you may want to join on a free MOOC at last four weeks that we're running, and that's happening soon. But the problem with that is that most of our time, this team are spending this time maintaining core and the community systems. Despite your opportunities for feedback through these systems, you probably feel pretty small. Your voice is not really being heard. You may feel that way, because I hear that, and people say they're disconnected from the roadmap. The roadmap's got nothing to do with me. It's just kind of set on high, and that's not a good way to be feeling. Even if you pay for your own developments, it can be difficult to maintain them yourself. There can be quite a lot of work in maintaining plugins. It's much better if those features get into core and are supported by the whole community. But it's difficult to do that. Every time we integrate things into core, it goes through a lot of reviewing and work to make it happen, to be integrated code-wise and also interface-wise, and I'm not saying Moodle's perfect by any means, but even to do what we're doing now takes a lot of work, and we need to be doing more. We all want Moodle to be faster, to be better, and easier to use, all of us. We all have, I'm sure, a wish, and there is a wishing tree, I hope, here. So you can write your wish on a piece of paper, and I'll talk a bit more about that in a minute what happened at the last Moot, the Australian Moot. So as Moodle evolves, this is what I think needs to happen to it. Moodle is the thing that's in the middle. Maybe I should have called it middle. It's in the middle between students and teachers. It's the thing that's in between. It's the thing that's in between the teachers and the techies, and a lot of you are probably at your institution, are on one side or the other of that, and you're probably always trying to get the other side to behave. It's a constant battle, I know. Moodle is between devices and servers. You're using Moodle on this thing. The actual Moodle site is somewhere over there. It's running on some hardware, physical hardware somewhere else. There are so many things that can go wrong. I daily marvel at the internet working at all. It is incredible. You can use, sometimes when I'm using a text window like a terminal, and I'm logged in on a server somewhere, and I hit a key on my keyboard, and immediately that letter comes up on my screen, and I know that a bite of information has been sent halfway around the world through thousands of connections and come back in a time almost instantly. And sometimes I just hit the key, just going, oh my gosh. Because it is stunning, and we've just got so used to it. Now we're just tweeting and sending stuff everywhere, and it's incredible. But in that environment, what happens if one of those things fails temporarily? Oh, Moodle's down. It always cops the blame because it's the thing you're trying to get to and the thing you're using. Sometimes it is Moodle, but not always. Moodle's also the thing in between organizations and communities, so the officialness of an organization and the community of people there, it represents somehow the face of the university. It's the place or a school or a workplace. It's the face of it in a way. And lastly, Moodle is between developers and pretty much everyone else. So what needs to happen is Moodle needs to disappear. It needs to become almost transparent. We need to be trying to make these interactions with each other transparent. So we're actually talking to each other. We're doing what we came there to do, which is teach or learn to interact in different way in our jobs. We don't need to be thinking about, oh, this is difficult, or this is slowing me down. We want to be getting to a point where we're just doing our jobs. We're not thinking about Moodle. And it's similar to Linux. Linux and Unix as operating systems are in everything. Almost every one of these devices has Unix in it. It just becomes invisible. All the cloud stuff you hear about, all the new internet hosting technology, it's all mostly based on Linux and Unix. So it's just sort of become invisible. So to get Moodle to this kind of point, to be so usable that we don't even think about it, we need more major new developments and we need more full-time core developers. It's just, and I've tried for 13 years to do this, but coordinating many, many part-time people, it's got us where we are today, but it's necessary sometimes to have dedicated people who are working all day in teams, going through sophisticated scrum agile methods to efficiently develop software to the kind of quality we all expect. We also need organized feedback. We need the voice of the community to say, we need this because the sort of territory where Moodle's going into is new. We, a lot of people teaching on Moodle now never learnt on a system like Moodle. It's like the first generation. And we don't even know what's possible yet with learning and using these devices. We're still all learning together. So how do we combine that into a direction so we know what Moodle should be? What we're not doing is we're not going commercial. We're not changing any licenses. We're staying on GPL licenses, as always. We're not selling out to any large ed tech company. We're not accepting venture capitalist funding. And I have nothing against those who do, but it's a very particular thing going on and it seems to be a bit of a bubble round, sort of at the moment, with internet investments. Some of these massive figures you hear about. But that kind of money comes with attachments. It comes with particular agendas. People who loan money, they want it back. And they want it back with a lot of interest. And they want it back with... And they want user data. They want all kinds of stuff like that. That does not jibe well for me with Moodle and what Moodle should be as an open-source project. So the harder way to do things is what we're doing. This is what we're doing. We are these three main things. We're launching the Moodle Association, which is a new association you may have already heard about, but I want to tell you about it again. And maybe you haven't. We are launching official Moodle Moots and you're at one. And I'm so happy that we're here. We're launching Moodle Cloud. So I'm going to go through these three things. Thank you. Someone's a Moodle Cloud fan already. That's really good to see. It's only been a few weeks. So the first thing is the Moodle Association. And this is really the biggest change. It's a separate organisation and it's about designing the next Moodle. Moodle users can work together in the association, members of the association, to decide the Moodle roadmap and pay for it. How does that work? So this is a non-profit organisation. It's owned by users. You know, we are setting it up. Moodle HQ is setting it up, but then we're stepping back. And it's just going to be an autonomous organisation. It collects annual fees for membership. These go into a development fund. There are processes that they go through in the association to determine what their priorities are and what they, what you, hopefully, want to work on. And then the association hires Moodle HQ to develop those things in core. So our job is to maintain a crack team of Moodle core developers who are working together, have all the processes set up to efficiently make Moodle software. The association hires us to do what the community wants. How are these priorities determined? There's a process that we've come up with. It's six-month cycles. There's a four-month specification period where people work on specifications. Somebody will stand up and own a project and lead a particular specification project. And that's just basically to produce a nice document that says, this is what we want. This is who it's for. This is how it works. This is what screens look like. And so on. Then, and all that happens online, with the community, anybody can participate in any project. Then at the end, there's kind of a cleanup period where all these things get tidied up and ready for elections. I believe you've got elections here in about two years, so you're, is it, end of next year or something? It's already well under, our elections won't be that long. These elections will be about depending on how big a member you are, the big members get a big pile of voting points, the small members get a small pile of voting points, but you basically push your points onto the projects that you like, depending on your priorities. We add up all the points and then we have a nice list of priorities. And then the committee that runs this association will then chart a Moodle HQ to do that work. So the levels for your interest are $50 a year, that's Australian, so it's even less, it's probably $80 here. Up to 10,000 Australians again, probably 8,000 or something US. And it's going to be very global. We really want an international organisation and I've already got interest from people all around the world already. We haven't actually started yet. We're just going through the registration process right now and the legalities of it and so on and so on. It's taking a bit longer than I would have liked, but we're getting there and eventually we'll launch it. Shannon Johnston is here. She's one of our project managers. Just stand up, Shannon. So she's looking after getting the association going. So if you've got any questions, you can talk to her or if you're any interest, grab Shannon. Or you can just email us The second thing is the moots. We came to the realisation last year that to do the kind of feedback and have the kind of link with the community that we need, we need to run the moots sometimes. So we've started this idea of running some moots. This is the second one we've run. The first one was in Australia. Some of the key things that we're trying to do is we should stress that I'm not saying that there shouldn't be other mootal moots and that there always has been community mootal moots and always should be run by whoever feels like running one. And many of them are terrific and I get to very fortunately visit quite a few of them around the world. This is to supplement that. It's just to have a more direct connection with mootal development and that's why you're here closer to us on making mootal better because if you have users talking to each other only they may come up with great ideas but getting that actually into mootal core is a very long hard process from there and we're trying to make that an easier process. So some of the things we're doing is to have facilitated working sessions and they're happening today. We're trying to focus on projects and they're about determining what people want and so I hope you take if you're taking part in those take the opportunity to network but also to think deeply about what it is that you need. We're trying to focus on a variety of sectors mootal gets used in all kinds of places and university work place but also unusual ones that you don't think of health. Many hospitals use mootal and it's interesting they often don't have committed e-learning people they just have a doctor or something who says we need to have some training for this or that and they stand up and they do it and mootal gives a tool that enables them to do this there's a guy here in the front pointing to himself he seems to be exactly I seem to be describing you sir and it's all kinds of places so we're trying to get away from just being focused on a particular sector we're trying to provide fewer choices and have more less rushing around and making choices between six or seven sessions happening at one time I hope you appreciate that because I do really look the program committee is always holding me back personally if I was running the program we would all be sitting in this room all day and we would have a series of six minute petrocucha style presentations all day that's how I would do it myself so we've achieved a compromise we are trying to get out of this room so there's a lot of people here but there's a lot more people who can't be here and we're working hard to get good quality video recordings that we can put online and so hello to you online so you'll see a lot of cameras around in some of the rooms and I like kind of a Ted style idea where we have a stream of Moodle videos coming out from Moodle moots around the world and you can just tune into a feed and occasionally get one and I think that's going to be very helpful for the community lastly we're really encouraging research and development and a bit more about that in a minute so that's what we're trying to do at these moots here's the stage this is the Australian Mood couple of weeks ago which is the first one we ran for me to slide there there's 512 people there, 100 presentations this is what the working groups were about we had the first one was on course archiving and rollover, second one was on assessment analytics the ones at this moot are different and very very interesting just to give you an example of kind of the output of that first day of the working group this is from the one I was involved in course archiving and rollover processes it's not about cars archiving and rollover so this is all about what happens at the beginning of the year what happens at the end of the year how do you set things how do you restart things how do you save things which Moodle is not very good at itself and so everybody builds lots of solutions that add on top of Moodle and they're all different so we tried to sit down and work out what was the toolkit that Moodle needed to enable everyone to do these jobs a lot easier and we came up number one bulk course handling and do these kinds of things bulk copy bulk freeze bulk backups bulk course visibility turn them on and off bulk grade item visibility so these hundred courses I want to hide the final grade these hundred courses now show the final grade bang you know you want these bulk operations etc etc there was the idea of a course welcome wizard that says empty course did you know you can restore from the previous year right now something just small things that would help teachers do that themselves probably the best idea we came up with there was about a freeze flag so away at any context in Moodle at a category or a course or an activity to say this thing is frozen it's read only so you can still read it but you can't write in it you can't change it and that simple tool enabled a lot of scenarios that people wanted to be able to lock things or keep them as available for students for a certain number of years and so on similarly a lot of people wanted grade archiving which is separate from a read only course and this is actually to lock the final grades in a read only way that is truly read only like a PDF read only so even if you upgrade Moodle and the code changes and the logic may change that the grades should never change doesn't matter if they're a result of bugs they should be they're fixed and I we went through an issue about this just with 2.9 and 2.8 quite recently but that's there needs to be a way to do this properly and so on and so on we came up with a few things that I'm not going to go too much detail because of time relative dates was another one people said they wanted assignments should be this assignment is due 4 weeks after the course starts or 4 weeks after you get enrolled useful features better UI default visibility settings and so on so I've talked about the association I've talked about the moods so the these kinds of things that happen at working groups at the moods may then become association projects and I hope they do I hope someone from the working groups takes it to the association and pushes it further turns this list of requests into a specification that people vote on fund give to us and we can work on and so the financial model next year will look more like this where we still have the mood partners crucially providing support for the project, the community all the processes that need to be happening as I described before but the association is additionally funding these new developments for new features and the result is a much bigger faster moodle the third thing I wanted to talk about so at the beginning of last month we finally released our little baby we've been working on and it was a lot of fun to put this together and has anybody not heard of moodle cloud yet? if you haven't a couple of hands so if you go to moodle.com you will see moodle cloud you can basically press a couple of buttons and you get a text notification on your phone and then you get a moodle site for free it's instant pretty much to get that moodle site it's always a it's a full moodle version and it's always current we're going to be always keeping them up to date has an unlimited database size which means you can write as many forum posts as you want in there no limits to that kind of thing in moodle but it does have limitations 50 users 200 megabytes disk space which is not a lot and that's because it's a free service and it's costing us some money to run it but we're trying to keep it under a good level that we can support this solves the problem primarily for those teachers who are on their own who can't afford services who are already struggling on a teacher wage to do anything in their classroom already completely overburdened with administrative processes but have the ability to quickly get a moodle going and do something small with their class there we also took the step of adding to this a feature that isn't in moodle but our good friends at Big Blue Button we've integrated Big Blue Button in there also for free but it's up to six people at a time in this session so that enables you to talk real time if you're interested in Big Blue Button you don't know about it they're here and this works really well it's very integrated with moodle so after we released it we had a lot of feedback what sort of feedback did we have we had a lot of people very happy about it there was a lot of articles already it's been something about however immediately people starting to go what happens when I hit the limits how do I make it bigger and so forth the answer is you go to a moodle partner if you really want to get bigger then you go to a moodle partner and that's why we built moodle cloud in this restricted way it's not competing with moodle partners it's actually just providing the missing piece that we never had if you've heard of moodle and you want to try it out you probably these days expect to go to moodle.com and press a button and get it and now you can but some people are saying it's advertising supported that's how we're covering some of the costs of running this server we have ads on it I'm not a big fan of ads either but it is a model that works that lets us fund this stuff we can't do it because it has ads and that's a bit of a shame and some teachers say they want a few more this is the major feedback we get out of all the different feedback we've collected we get these four ones the first one is I didn't get my SMS where's my code and that's probably a very very small percentage but of course it's very urgent so they do always contact us it's under 0.1% or something and that's because SMS is out of our control it's a wild west of technology out there the second one is what's my name on my site it's so easy to sign up apparently that people do it and they forget what their site's called even though we've sent you an email but they probably put in a fake email so they don't have that email and then they forget what their site's called it's a free thing we can't help you too much with that the third thing is people say can I get rid of the ads and when we explain it's advertising supported and the fourth thing is can I get more users and we say again it's limited because of the reasons I said but we're starting the whole thing we're getting used to how all this is working we currently have about 3,500 Moodle sites now on Moodle cloud about 10 gigabytes of files have been uploaded already and it's just it's not even breaking a sweat the system is just really good I'm so happy with our cloud system how well it's working yeah well thanks Michael I was talking about one character going across the internet just when you look at the complexity of this machine we've just built it's really amazing the cloud systems for larger hosting already it's amazing what can be done these days by combining software so we're still studying this whole thing we're thinking about where to go next with it one of the interesting things that we can do now as Moodle HQ having access to so many Moodle sites that are in use is that we can do research on this there's interesting data there we're not talking about anything that's private we can do things like say is anybody using this plugin or what's the balance of use you know how are people using this versus that in future we can actually try new features so we can actually do A, B testing we can roll out if there's a new prototype of something we can ask people to opt into the new cutting edge version and we can test the new interface against the old interface and get data from that so our researchers in the community I think it can be a very interesting tool for us to learn about Moodle and how to improve it and I'm looking forward to that to finish up I just want to talk about our current development priorities what we are working on we don't have an association telling us what to do yet so these are the things that we're working on so number one we're working on usability in general I'll talk about that in a second number two we're talking about we're looking into competency based education this is a feature that's been on our wish list for at least 10 years and it's been implemented in many different ways Gavin Henrich has a talk where he's covering some of those ways that exist now but we need something in core that can handle competencies store competencies per person and update them there is a spec that's under development at this URL here in Moodle docs it won't be ready for 3.0 but we're working on it now it's a priority the third thing is we're finishing templates this was introduced in 2.9 and templates are more of a developer thing but they're like they're like Lego blocks and you build up the page and fourthly a big focus right now is getting the Moodle mobile app really good so let me talk briefly about them this is the wrong photo this is a completely random photo of a giant Lego robot that I found in the mall around here I just thought it's pretty amazing that's like 5 meters tall it's a lot of Lego this is the usability lab that is here on campus today that Brittany was referring to and it's a world class facility with very good facilitation I should add as well where they go through usability studies people using Moodle this is a lady who's using Moodle there she's actually in the room right next to us behind one way glass the other screen is showing her screen so we can see what she's doing on Moodle she's talking about what she's doing we can hear it we took turns in acting as a kind of a help desk if she had any trouble she could call us and a couple of them didn't know they were talking to me so it reminds me of the old days back when I used to be in IT support but it's a real eye opener some of these things we knew from other sources but the amount of information that we collected and organised about things we should focus on was incredible just one day's work so the approach with usability is including accessibility under usability because accessibility is about usability for people who are using alternative methods who are missing sensors the first one is integrating popular plugins and modifications that are out there a lot of people in the community have done work on accessibility and accessibility and it's about getting that into core the second part is taking action on this usability and accessibility testing that we do, that you do that people do around the community and thirdly, listening to the Moodle Association if the Moodle Association says this is just unusable we need to fix it, this is how we will do that and lastly hiring more developers at HQ that have a UX experience specialisation we've not done that in the past we normally say we need PHP developers and we get hardcore PHP developers and the user interfaces we don't have many people who are we need more people who focus on interfaces so that's our general approach there the competency based framework we are starting with Tataura's implementation which is a version of Moodle with add-ons we're looking at building basic well-designed structures in Moodle core for storing the data for manipulating the data but it's designed for expansion a universities approach to competency based education may not exist but if they did want to use it it's going to be different from how a primary school does it which will be different to how a company does it but there are certain commonalities of the information that they all need just like we have users in Moodle we have courses in Moodle competencies will be like another core data inside Moodle and we're building it so that we can add plug-ins on top of that on top of our learning platform to suit people's different needs and we plan to integrate the ideas from Outcomes 2 which Moodle rooms worked on a couple of years ago but it's not a complete solution yet so we're integrating all of that that's our plan the templates I talked about this is the Lego stuff this is for developers it means that bits of Moodle pages can be written in a way that developers can use to build up pages in a standard way and this means Moodle looks more consistent and it means when a designer makes a lovely theme it's easy and it looks consistent right across the board so it's just effective and themes are what you see the things that people really see so it's important to get this improved and the last thing is the Moodle mobile app I put an announcement last night on Moodle.org about the new one you may have already downloaded it if you've got it it's a completely, we've rewritten it from scratch it's a new stack it has plugin support so it's more expandable and already the developers have accelerated like 5 or 10 times the speed of development using this new stack we can make this develop much faster than we could before so it was worth the rewrite and it supports all recent versions of Moodle back to Moodle 2.4 and some of the new things are offline calendar events you can view notes it's got offline books it's got IMS content packages much better interface infinite loads, scrolling lots and lots of things I've got some pictures this is front page with a couple of Moodle sites that's how it looks on a tablet in vertical mode that's what forums look like that's participants list this is on Moodle.org the course there has like thousands of people in it but just load it instantly messages looks like every other messaging app you have seen except these are Moodle messages that's when you swipe it across a bit and you can see the menu coming out and so on it supports more you can manage a space that you've stored stuff on your own device and so on and so forth a really interesting thing that I wasn't quite expecting with this app is the accessibility of it because it has a very standard regular structure and it isn't by the theme of the original Moodle site or customizations made on that Moodle site it's very standard and we've been putting a lot of attention lately on making this accessible making sure all the headings are correct making sure it has ARIA tags and things like that you need to do because this is actually HTML and on an iPad or an Android device they use that and did some testing with Aaron Page who's a part of the accessibility group who was in Montana a couple of weeks ago and he used it surprisingly well completely blind I should mention he used this app surprisingly well and after we've made some modifications it's going to be really good so this is actually a very accessible solution and I wasn't expecting that actually but it's a nice sort of side effect of having an app that's what books look like I'm running out of time but I just wanted to state I hope all this stuff I'm talking about makes sense that you can see the general where Moodle's going, how we're moving forward why we're doing the things we're doing not to be scared by new changes like the association but it's all designed to make this open source project function as well as it can and to make this software among the best software in the world that's our goal and support at all of our endeavours but we're all in this together and we're all walking down this road together and we're going around the corner and we'll discover where we get to so anyway I'm very very pleased to be here I hope I could talk to you personally in the next couple of days, thank you very much