 Just for this wrap-up session, we had planned a bit of an open and panel discussion about, well, the little community in general, including new partners and everything that makes it work. But we can talk about anything we want to talk about. If you've got something you want to raise, I think we should just have a bit of an open discussion. But let's start with the community, looking at the community stuff. And if we run out of steam, and we want to finish early, let's finish early. I think we can go home and have a rest before House of Blues. I know there's quite a few people here who haven't had enough sleep lately. So you might need a little nap, or staying up until 2am. We just got a really, look at the cameras. Jim, sorry, Jim just gave me a really useful list of places to go in the other room, which I'm going to repeat, because I think it's really useful information. So we did discuss before about this idea of a community 2.0, and there was a session that Tom ran, really great ideas. That's an ongoing project of creating a new space for people to share, for people to find each other, and for discussions. And it will probably largely replace some of what's going on on our current community site, moveable.org. But what we're staying there is the open source project, the development side of things. And so it was suggested that we look at some of these things and see if it triggers off any painful memories that you have or ideas about things that you think we should really do, now's the time for that sort of feedback. So let's just look here first at our documentation. How do you feel about a new documentation? Anybody got any thoughts? Inconsistent with what? Inconsistent with existence? I feel like that on most weeks as well. Yeah, probably. It's a weekly, and it's huge, and it relies on the community being a weekly. Although we have people who spend quite a lot of time every release updating stuff. How do you know that every page will lead to a page in the weekly? Are you using it in English? Yeah. The English version has the most content, I would say for sure. Lack of pages. It's great to hear, because it does a lot of work for this over the years. Perfect. And if you come to an IT page, you don't even have to answer them. You don't have to write a page. You can just write what you think should be on that page. There should really be lists here that might trigger an expert. There is no process that I know of. I know that Mary and Helen, the Mary Cooch, who you've seen during the videos on releases, and quite a lot of the release works, and Helen Foster, who's the community manager, and it's like a little being that's fucking all over Little.org. They will often add things as they come up in the forums, but that's about the limit of the process, I think. I think if you felt there was a frequently asked question from your staff at your automated graphic course, you can just totally edit and just go for it. Add it. There are reviews. Do you have any questions at the end of the day? Yeah. Every page has an edit button, and you just edit it. So you need to write in this wicking type format. See, this is the heading. It has the equal signs on each side, so it's all plain text that you type. But generally, you can type stuff and it works fine. Yeah, at the bottom. At the bottom there's NT help, and it's got all international tasks in it all, but for Mary. Okay. Blackboard is a completely different company and projects. See what happened? Yeah, anyone up here? Come on, you're sitting up here. Has anyone got any opinions about documentation or something to say? I think we've got a microphone. I think one of the things that I've been thinking about with documentation and sharing with people is the idea that we've come to a documentation of different stages. Sometimes we come to remember something, and sometimes we come to kind of understand what it's all about, and there are probably two or four or five different other reasons for us to visit a page. The problem is that each has to satisfy all of those needs at the same time, which is a somewhat complicated process. So short of saying, here's the reminder, Wiki, which is kind of a short hand of what's in the learning Wiki. We need to think about those solutions there. If you've got ideas, you can share with us. You can reach out to Mary at www.moo.com. You can reach out to Helen at www.moo.com or www.tomaMoo.com, and we would love to hear your ideas. Eventually, it makes sense for us to be providing the right information, but also the right information for where you are in your learning process. But it's starting in the beginning, you don't have to know the benefit of something, or whether you're trying to remember something or certainly the technical aspects and the deep aspects of it. So it's pretty complicated. I'm impressed by a little box. It's been hours learning things from it, but I struggled with ways to make it better and dedicated myself to it. I wouldn't worry too much. Just go for it. Like if it's slightly wrong information or, you know, different terms. I wonder what performance right now for the application that's going on and what it feels like. I don't know the answer, but it feels like we do. So with that in mind, I think that's what makes sense, because to your point, that you don't know if we're going to maybe edit in a way that throws off of that documentation. It should be. It has to be curated for some extent. So maybe I think there's a lot to do with the documentation and maybe other people who are still the same way. I know by experience that the documentation has been sometimes going to be acute that I'm leaving and maybe it's, you know, maybe to repot, which is a bunch of new papers from the US. Maybe that's not mentioned, but maybe other pieces of the accessibility are mentioned by the way or something like that. And maybe I want that one section, of course, specific to the US mentioned in the documentation. I don't have an event to make that request and I'm just doing an example of what might be the case for D-pad. You know, that's something, could there be a button here which says on each page it says, look at that. More information where you found something missing and then it goes there. It goes immediately away. And maybe we're just going to cure all those things and then this goes back to an idea that we talked about this morning. I don't know about this. From the table that I was putting up, I had an idea that every week an email would go out from you guys to say either the three areas we need help with. Or this week, how in the community, can we help more? I think it was a big part of this idea of how do we design the community website here and to get more involvement having that sort of this page right now and this section needs to be rewritten. Then we would know how many I can help with that. I really want to continue on this section. It sounds like Mary or Tom has been stated that this is Mary. We need more robust acting pressure and maybe it gets rewritten by three or four people that come in and add to that section. It's actually very, very quickly if you already know what you're doing. So I don't know if that's just an idea or another reading but it's always a really do if you want to have something and you're not quite sure if you can find some. It kind of has to be for you. I think for the layman isn't that very difficult. I think that makes sense for people who really understand code and what you use them for. I think it might be something in the middle that I don't know what to do. I don't know what to do with that button. I can go to somebody else. So I was part of the longer discussion about it and I think that Brian's idea about having a central place in the community documentation where we're alerting all these most helpful moodwares about where it could use and want could be very weird. I think that the tools people would use are exactly in the middle that it's probably a conversation that's probably a long discussion and people are subscribed here who are getting inputs from us about what could use attention. I love that. I mean, it's really very literally. Yeah. I think so. The next person will speak soon. Right. I have a Michael's suggestion here this morning about what he said. I know I'm not going to be able to take these questions but for some reason my brain still thinks it's also not as easy as that. So I think maybe a batch of cases where you say well I've made X number of contributions so I received this badger. That doesn't extend out that vegetation. As silly as it is I feel the same way and that was a great way of looking at it. Somebody told me to take it to the grave with those gadgets. Put it on your head. I think it's a little more difficult to use is when you get out to kind of finish it. What you got was amazing job in documenting your portions. What doesn't necessarily get as well documented is the plugins that people may use. As I update the documentation and the repository and the reading or something like that. And also the people. So if you see what I did there with the URL you can type in the URL of any page in Moodle any script. The URL in Moodle if you put it into the docks it will take you to the docks page for that. If I put it into the database module that's what they did in the code and that's what you see in the URL and it will jump straight to the database activity. And this works for all third party plugins. Any new plugin someone writes it automatically will link to the right place in the docks and that's where the docks should go. So if you're making any new plugin just remember at the bottom of the pages there is a link to that. So I don't think it's quite working that but it does rely on people doing that. And it's kind of often forgotten I think that last step. You probably should I don't know if it does actually or not have you noticed it? Well that's another definitely good question because as a contributor there is a place where you put the useful links area to say you fill out. So if there were a way to do exactly what he said the other general page would even have just created links for the other documentation. I don't know if that was automated but there is a documentation link in the plugin's database. I tried the automated QRL and that worked. It takes the developer to do it. Yeah. That's not what you might expect. I think error messages are probably one of the hardest to get documented. Realistically the person that has the document that's the developer. We know what happened or what their logic was causing to happen. Is this an overall particularly topic? It's one of a lot of context there in this world because of what we're doing. The main stuff is all content. We call API to develop it. It's a really useful scenario. There's a lot of APIs in Google. We put quite a bit of effort into that. We are working on tutorials as well. Next. There are also little tutorials for various things for this system. There is a new autogroll I've seen tutorial basically the features developed from scratch how to have a lot of new code. I mean it's been a few different versions of what you guys have made up. Yes. There's a lot of stuff that I've created. It actually exists. It's the web series of API. This is all documentation for how do I create plugins. My question is how do I really use those APIs as an external vendor or someone who wants to write a portal API? I don't even know what I'm supposed to be passing the code later. There is a very good admin script that will show us two five events. It's actually really easy. When you click on that it actually automatically will stay a long time because I'm not writing code anymore, So that's all there is. Now, let's talk about the, the, the, uh, the way which that's defined in Moodle is in this way where we can generate documentation of what it might be called. So it would be good for the relationship of vendors type of you, you don't necessarily have to install Moodle, both of you. Yeah, both of us. I think we, well, we went this way because most things have changed and evolved, and you want them to be accurate. And you put them on a Moodle dock and you have to put them a bit every version of Moodle when it becomes a huge maintenance system. I'll put it at this stage. Most of the vendors are probably saying it was the first time. I think it's really both you and I and really I'm not sure how to do it. So, and this goes back to maybe just now how do we get more data out of this? So maybe, you know, that way is we're talking about where kind of an extended route or not where these sorts of topics can be put out by experts and they can receive a launch. And who doesn't want that? Well, here it is. At the top of the coding with those clients, the top is for the average rate for bugging courses. In the future, there's a bit of an aside, but we do find eventually that the front end of Moodle will probably only use these. But we won't complete the separate front end just like the Moodle web sorry, the mobile part they'll just do that everywhere. And that makes for a very effective API. So that's there. I think it's going to be a lot of information. All right, with the docks we've got let me just talk about the tracker. How many people have used the tracker? So the little tracker has its own login. It's saying it's Gira. There's a lot of projects. We have a lot more projects than you know. It's sort of an internal project. We use it for all kinds of things. The main one for Moodle is this one called Roodle. And we must draft the issues. This is so essential to the whole working of Moodle that we use this constantly every day. When it's down for five minutes it screams from the developers. It's very, very reactive. The whole process is totally built around this. We use it for sorting and prioritising generally the discussions that Maxa about new features are in here. There might be discussions elsewhere at some point that's got some sort of track back. So it is tracking things. It is the definitive source. And it links things together. Here's the files and the issue and it's got links to the repository where the code is sent out from the file. It drives straight in and see the exact changes that they will do. If you think about the whole complexity in this system it's the one. There's so much commotion here over the years. But it's also, we do expect users to come here if they want to tell us about problems or you get this complex system which this scares people a bit. So we usually recommend people go and try and find a forum on Moodle.org and talk about it there and just somebody will eventually turn it into a transaction. Or another way is to go and join Moodle users across the action and right there and then that will fetch the specific boxes to Moodle users. So we recently decided that all the Moodle users who are associated with work on Moodle.org and the mind of recording about it will be here as well. Again, on the spike list of Moodle users there should be no additional questions. But then we're going to post still a good thing to be doing here. I don't have a question to this but I know that when I ask things in the Moodle forums you have to be aware of it. And I'm used to that because I have a lot of developer environments that understand their language. I think it might be shocking for some users sometimes. And then a tracker and someone who says man the dodges can't be done and it's really interesting that I think that it's because you get deeper and deeper and closer and closer to things that they learn from in terms of what you can expect. I don't know if you have a question. When is the last time you got a like number of players over the ticket? It happens every now and then every now and then we have a surge. Yeah, if you should we have a little algorithm we can't remember exactly but it's things that clearly haven't been touched or looked at or thought about for years and then we just go well let's just close that. And anybody who do care about it can read up on this and they'll get an email about it. We are closing this because it seems to be a dead issue if you can just reply and there are a lot of replicates. There are thousands of things. There are a couple of joke ones. This is the one about solving the climate problem. It's a running bug that's been going since 2008. And every now and then somebody makes kind of a joke and keeps on going and we can do this like a climate problem. We need outlets sometimes to make history. There's a few other history. Is there anything? Yes. Yeah. We have a three yard project. So we usually just encourage people to write the best they can. And there is a tree-eyed process. The stable team. We have one team that develops this focus on bug fixing and stable issues. They will tree-eyed a new bug which means look at them and decide what to do with them. And they'll clean up the language or fix the priorities or change the categories and make it pretty interesting. Hopefully through that people will learn how to open a next part in general. Is there a location for defining some tags or I don't think it's components. Oftentimes I see accessibility used in areas that are particular. I personally wouldn't necessarily say accessibility or access. But sometimes what they're looking for is there a place that defines where the user could say this is what that tag would mean and where I should use it kind of. The light is that what you mean? Yeah. What do we do with all the components? I think it's a little of components with accessibility and I think in the end of accessibility there's more documentation. What are you thinking? The usual way components for noodles and they're from what you context like accessibility. You can have any number of them. You can easily create them actually. So sometimes I think but generally it's pretty plain I think but yeah it's taking quite long you have to kind of know it isn't accessibility. And then there's the label which also anyone can just try the label at any time and it'll just buy you a mechanical label so it's a drug sonomy a little bit of a caveats a drug sonomy has. We have a lot of special labels that we use so far the trust approach is working okay. We don't have a lot of problems with normal labels in general. They're totally used in the long page of it having the tracker and they don't have a big read. Which is for people to read it. Oh it's probably, I'm sure it's linked to the page if you search it first. This one's pretty up to date actually we've developed it to keep you on stuff I'm going to keep it to certain here and from a little bit further there we go, try and find. So that's all these are standard labels that we use to kind of group issues together. So the special one you'll see is a little pilot. A little pilot you should get some priority issues that come through a little pilot and you'll sometimes see issues that happen on a pilot. So around this time you'll see a lot of docs required or there's docs required if there's something new in ACI or if it's a new feature there's doc required and that's that's important to check with so Mary Kooch and Helen can go through and make sure the docs are being done prodding the right person to make sure they're done. And a lot of little subsystems and processes like that all the way through. It's an extremely exciting actually it's an incredible thing we're building together. We've got some demo files I'd really like to improve these but they're not so bad. This Mount Orange school if you have a look at it has a lot of content and you can choose a role and really try things but it's quite a lot of content there's quite a lot of time to go through them. That's it. I know they're updated every time through release. There's a QA testing site and that always shows an expert and it can be quite rough and it's available during the QA testing period right toward the end of our six month release cycle we have a period of three weeks four weeks where we have a lot of volunteers coming and when you go into the tracker you'll see links to the current QA process and you can just grab any of the issues that you see there and do it so as QA issues we'll say I can post this in 24 so someone goes and drives that with the current version either on this site or the own copy and they come back and go get that work or it's finished. So we have a big checklist for things to check manually before release. QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA QA Isn't there also, I thought there was an admin script that that's created to auto create courses with a number of users and a number of assignments already computed? There is, yeah, there is, I'm trying to get there right now, but there is a, there is a script that will create random courses, random users, random content, forum posts, everything. There's another form of testing that you want to get involved with early work. Prototype.moodle.net. And we have very early proto-partial things. Some of these have been taken away, which is a little bit of a trick. But you can see here the new calendar. So it's one of the things that are working on that. I'm quite curious to see how this looks myself actually. So you'll find a bunch of noodle parts there that are running on the fresh code. You'll probably have a login also on the front page with the links to the noodle part of the issue. So if you've got some thoughts about how the prototype's going, go and comment on the issue. I think it's all the cool stuff that hasn't landed yet. Of course, they're working on it, they're working on it, they're working on it, they're working on it, they're working on it, they're working on it, they're working on it, they're working on it. Okay, we're running out of time. There was one last thing I wanted to mention after many years is the translation. I mean, many, many more people use Moodle not in English. English is the minority language in the world, in the global world. So this is our website. We built a website for translating things, and it's seen here there's been 1.2 million screens translated. Stream is just a bunch of text, a small amount of text, like all the button on the window, all the things that Moodle uses. And you can contribute. So if you speak the language and you want to get involved, this is a Moodle spot with a whole lot of custom code. And some of you might not know what I'm talking about. The AMOS, what we call it, AMOS, is a port made in the manipulation of strings. And we have a really detailed interface for comparing the English to your new translation, and you can do all the translation things. And the back end is usually gets checking all the stuff in, and it all blows up, and people's Moodle spots. So when they update language packs, it always gets the latest language packs. And many of the language, one language, may have many, many people to contribute as well. And there are sometimes arguments, there's an argument about presenting right now, about how the whole thing should be translated, and that's how it worked out. We had in the early days of Moodle, Spanish suddenly exploded into many flavors, and I just let it flourish. So someone said, well, Caribbean Spanish is very different to Spanish Spanish. I said, okay, make a Caribbean pattern. And it just continued until we had like 15 or more Spanish variations. And then in the Spanish community, they were, so this is bloody ridiculous. Let's all consolidate, because actually the differences were just a couple of words, like new words that weren't like the words for computer or something. And so they consolidate it all back again. And then I came back for a couple of years, and I came back, and it all came back. Moodle has, I would say, quite easily the most translations of any LMS in the world. Now, they're not all complete. And there's supposed to be a report on it, which I keep asking to get put on here, about the report, but here's all the language packs. Who's maintaining them? We keep a lot of them automatic. Can you look at some of the languages? They're coming up with a batch of words. And people are among them. Oh, yeah, you do? Oh, boy. Who are we discovering? That's the language. I actually got the opportunity to create a new language when we entered the K-12 market. There's not a K-12 language pack, because it didn't like to win courses, but they liked courses better. Yeah. The English part version? That's good. Oh, that's good. There you go, guys. So how is the English-Py-Tool different? English for kids? So when I went through it, I noticed the English became a little bit difficult. So the word for it is English-Py-Tool. Huh. So the English-Py-Tool is actually a language that is connected with the English-Py-Tool. Yeah. There's a lot of that. I would actually credit a lot of Moodle's success, the fact that I was able to make some translations really quickly. Okay, so what makes you want to bring up anything else? The Moodle pack. So, yeah, we've got Moodle.com. There's the other half where the more commercial side, but I hate this website. There is a new one that's due to drop really soon. We've been working on it, so I'll make some more for it too. But we have a lot of Moodle packs. But both show you the ones in the country you're in. Anybody got any comments about the partner? You know, I've got some partners for you to ask for a message question. What is the role of partners in the Moodle universe? Don't ask the hard questions. You can ask them honestly if you want to. Oh, yeah? Yeah. Yeah. When we gave them the quotes for that, Drag and Drop is like a third of the work quite a lot. And at first they couldn't afford Drag and Drop, I think. So they'd rather go ahead with our Drag and Drop. And then we had a bit more negotiating and we came to some arrangement to do it after all. So Drag and Drop for your personal calendar, so this is quite easy. But you literally, on the calendar, you'll see an event. It means that by doing a lot to Drag and Drop, it's easy. If it's in a assignment due date and you drag and drop, there's a whole lot of consequences. Right? So there's a lot of dialogue and you need to do a lot of work and you need to do this in a way that will handle any funding that has date. And that's a lot of work. That was the big work. That last bit I just mentioned about the activity. You may not be in 3.4 or 3.5. We'll see how it goes. We've committed to the rest of the 3.4. Yes. There's a lot of analysis that I knew. I've seen this. They went through everything. You know, trying to get our calendar out of the way, teaching, matching everything out of there. Yeah. The problem with that is the middle user's location, the original brief was, make it like Google Calendar. It sounds obvious, but that's when you really analyse it. It's impossible. You can't make Google Calendar. I mean, I don't mean technically, I just mean it's different inside and out of it. So we went back to them and we made them define what they needed as user stories. Very detailed, exactly what things they wanted to be possible. And then we went back to them and put them aside. So all partners, I'll say a couple of words. Just mine's dying. I don't know what I'm talking about. I don't think it's a good thing. Prior to this, prior to living, I had a couple of distance with Lama and gone a lot too close by to Australia, where I was a teacher at the time. I went to Ellucian. I lived at Ellucian for about six years. And everyone in the room, I've run an Ellucian product at their school through the banner of power, community, kind of the week, and how many people ran that. So I know technical team and talking about community over the last couple of days, talking about the role of partners. My research went back on to that time. Most people that ran those close folks products or any close folks product for about a minute, they don't really have much in the way of a community. I think anyone who's running an Ellucian product finally established restoration as they put in support credits in the past. So I think it's just always a good chance to come together with questions and just reflect a second, the difference between close service products, I would say it was made close to us on a magic distance. You guys may have noticed, but it's another one through the speaker panel. And I hope it's us. And I think that when we talk about community, when we talk about our world in the community, I think it's definitely some type of ground that we actually do have a voice in this community because it was open for us. And for me coming up in the restaurant, we have an exchange between the words and I want to listen, because I have so many clients that I work with, they say, can you do that? Can you do that? And I'm sure there's always more. So we can't do that because we're not just prioritizing product. We're at the opposite. We have an ecosystem platform, every single customer with an open phone. I think it's fascinating for me to have the last couple of days to hear about the ideas of leadership in this community and the questions they ask. What community, what work can we do? How can we make the reason that the last night get more of those results? I just hope that everybody will go on to think tonight's first, you know, what can we do as a partner? I look at the kind of thing that we learn in our lives and how can we get the very voices heard more? I think about how are we going to do that? I think we've stressed these questions. I just want to hope that we continue to make kind of decisions, because the people in this room, I think, and what we can do here, well, as a branch of ours, we have a bit of a lack in this community, but I hope that tomorrow's going to be very clear about these features and many more and many even tomorrow. I don't think tomorrow is going to be the language translation piece that I'm going to tell you. I'm starting with a very good demo. So I could tell you that there isn't a word in there. So I think that maybe more than I know it's going to be about education. The thing that's focused on is the incredible satisfaction of the people in this community. I think it's a community that has been part of their way of working in this little village, which in a case, if you're not interested, I think that, again, the community side, you know, people have been getting an opportunity to like and talk to their friends about, you know, what they can do to get married. So, yeah, we're going to have to do more of the work in this area, but here's a particular kind of confusion. Obviously, I'm going to play with a bunch of questions. Well, I would say that there was a huge amount of confusion because of the community to be managed. So I'm hoping that the next time you come around in the vlog, there was this bunch of questions about people who can write and share their experience. You talked to one of these people, so, I think it's always great that we get into a lot of special, you know, an area where you really like to talk to and how you can talk to people It's written about that we want to bring this to the test field. And there's more than that, so I'm going to do that. And I'm going to go out and look at the impact of all of that. And say, for example, we're going to be self-reporting and getting ready for this, and we're going to be able to do that. We're going to have our expert position. We've got a lot of people in the chat board. And we're going to have music from the radio. So I'm going to put up some questions here. What about in terms of, like, I had to talk to you about training, and the little training things they're doing within the room around them, and the person that's in the field. There's a lot of room to get more involvement from the faculty who have a transportation involvement. I would assume that because I don't really come in that way in the way of the way I would do things. I would be able to do that on the one side. Is that the statement? Yeah, that's it. I think you're having those faculty more to the one side for our professors, for our badges. They might be able to see. I think the big difference there was, whether or not they have badges in every school that I found in my institution, for example, that you're going to see them being very well. So I think the ways that we can promote should look at those partners. We're looking at partners to do more. We're trying to get more courses out there. So I think that if you're going to start a family that you're able to deal with more and create more clients, you'll get more involvement. I think that's the most important. One of the cool things we had this morning from the group was that we would log in to your Moodle.org and be placed in a subgroup of your institution. So if you're in some state and you've logged in to the Moodle.org, you'd automatically be put in a state group. Discussion there would be limited to that group. You'd have resources. And they kind of want to blow out the idea of a limited group. So it could be a survey. It could be documents. It could be webinar links. It could be YouTube videos on various topics. But the nice thing about that, I think, is that it becomes practice to go to Moodle.org and find the right people to speak with. Because then, you know, the state is really wanting to be helpful. They're probably pulling people out of that group and saying, they're talking to the clients. They sort of go talk to the foreign language specialist too. And I feel like now you can bring back to the larger group. I was going to say, from my perspective being a partner, I think over the years, we've seen that there are kind of various levels of partners. You've got partners who are really good at serving small clients. So you're talking to 20 users, or they're just starting out. And they're really passionate about helping those users get up and running and get going. We've got medium partners who are figuring out, okay, I'm able to serve both the small and the large. I'm trying to figure out where I'm going. I'm finding my roots. I'm figuring out what you're doing. And then you've got partners like Blackboard, I feel like as the largest partner out there in the world, it's our job to actually help filling gaps where Moodle may not have time, may not have the resources to do, but also to bring forth community members like Erin and Laureen who have information that we discover just by being part of the Moodle community and going to these groups of having conversations and making sure that information is heard and that information is brought out. So, to me, it's a lot about stewardship and being there, that stuff has been here so long. We're making sure that everybody's voice is heard and that it's being brought through the community in a way that can help out. I have an interesting query about just a little bit about the role of the partners. We have a client now that's here. Mary's in the room. Let's see, Mary. Mary, are you here? Yes, I'm here. They're outside in FT and they're running Moodle with us and they have an OPM has come in and just taken over their online program called Academic Partnership. And with anyone who uses it, we have a partnership for OPMs and they're up at the most occasion. And they have a team. They have a team on a sports team and they have a team for the pipe. We have a good group and I have a lot of it with support. And I think it's just a little bit about what's important and what not to work in the project and who's got a core code and that's what it has been all over in the community to provide the environment to partners and they have a team that does a lot of work on it so that it's a good partner to have the highest level customer. And I've heard that repeatedly since the greatest priority is always to get everything ready and the price is going to get to the real world. But I think it's a quality area. We're good at knowing the purpose of community and that this is a community-driven project and I think that it's a great and believable project. And together, I think it's important as well as a provider and for you guys, it's important because it happens after a year that many of these first-person teams have friends who are amazing, who I enjoy and I like to treat during the fucking years that we were going on. So many of these first-person teams should be here for many years to come. And I think the only way that it's paid out is to continue to have that kind of environment. And one thing that we're going to have to do is, you know, I started with one of my friends, and I know it's not happening right now, but in the current days, I know it's not going to work. Real economy is a scale, and if we think it's important to have that work, we can show that with every other comment. So, you know, the best way to do this is to be a partner for that kind of an extension of our community that we're saving in time. And then of course, we can use it as a virtual class and we can tell you how collaborative is an option and here's why this might work and I saw it was a kind of a tool and that's what we're trying to do and we'll wrap it up. So, um, look, I hope that was some useful tips out of there, some good things. We have a content page on Ludo.com if you ever want to ask about anything related to partners or related to other things, come there, you can find us and we can recommend things to you or point it in the right direction if you get lost. And that's the end of the move. Thank you. Thank you for making it an event and it's good to see some of you and meet some of you and let's go and have a bit of a rest and get on to the party. See you around here tonight. Thank you.