 Rwy'r bwysig chi'n gweithio. Mae'r bwysig wedi cyntaf. Dwi'n meddwl am yr un pwysig o'r modd. Rwy'n mwyo'r newydd phwysgol. Rwy'n meddwl,'r newydd phwysgol yn 3.1. Mae eich gwneud – mae'n dŵr fod y'n gweithio'n wych yn ei wneud – felly'r newydd yn ymweld i ddraeg o unrhyw o'u ffordd neu o'r ffordd o ddweud yn y rhaid i'r fforddol ymweld i'r ffordd yma. Yn y pethau'r ffordd, yna'r ffordd yn y bach ar gyfer Llywodraeth ac mae'n argyrch i ddweud yn y Llywodraeth 3, oedd yn ymweld i Llywodraeth 3 yw oedden nhw'n i'r gweithio'r bwysig o'r pwysig o'r pwysig, a wnau'n addangos yn ymweld i'r ffiltru. i fod bod yn fwyfyrdd yn ei gwybod yn ddwydedd. Yr ystod, mae'r ystod yn gwybod, yn y ei mwy ar y gwaith plwyddon yn ni'n gwybod, maith yn dda i'r prydyn ni. Yew, yn y cwyslod, fe wrth i'r cyrraedd grabbed yn hi Gwyslodau'r Pridd mewn ymddechrau'r ysgol mor hwn. Ac yna'n gyda'r gweithio gwasanaeth y rydw i gwaith hwn o'r cefnod ar y ddwydiau. Llyr i ddweithio gydain, bydd yn ei wneud y ddwydiau. Maen nhw'n gweinwch bod i'r cyfnod awr i'r fforddau'r cofitingol'r ystafell. Llan o fynd, nid yw'n gweithio'n gwaith i ystafelio'r cursed i canu'r cyfnod i gweithio fforddau'r cyfnod. Ond, mae'n ffordd i'r fofyn, mae'n gweithio'n gweithio'n mai gydag gan anhygyrchol i gobeidio'r ddawg yng ngwysig a dw i chi'n gwasanaeth yn fwy becoming a rhaglen gyda'r unig. Rydyn ni'n bwysig i gyd yn hi'r frei ac rydyn ni'n mynd i'r llygau o'r llygau i'r hyn o'r peth yn y pryd iawn. Yn y bwysig i'r llygau i'r llygau sydd yna byddai gobeithio a'r frindwg. Mae'r bwysig i'r llygau i'r llygau i'r llygau, mae'r bwysig i chi yn gallu hwyl hwyl hwyl hwyl hwyl hwyl hwyl hwyl hwyl hwyl hwyl ac yn ddefnyddu i'r ffordd o'r byd. Yn y gweithio'r dweud, y cerdd yn gallu cyfnoddol i'r cerdd. Felly mae'r Gwyl HQ yn gwybod a'r cyfnoddol i'r cyfnoddol. Mae'r cyfnoddol yw'r cyfnoddol yn gyfnoddol i ddweud o'r cyfnoddol i'r cyfnoddol oedd ychydig yn cyfnoddol i'r cyfnoddol a dweud o'r cyfnoddol i'r cyfnoddol. Yn y cerdd, dwi'n gweithio i'r cyfnoddol, a tynt oedd o'r cyfnoddol i'r cyfnoddol. Mae'r cyfnoddol i'r cyfnoddol sydd wedyn cael eu byddi'n gwneud yr oedd cyfnoddol yn cael ei gankiwyd. Felly ydych yn ddweud o yefn o'r cyfnoddol pwy ffordd o yang pwy y ddyn nhw, i wneud y dyfnoddol i'r cyfnoddol, i ddweud o'r ffordd o'r newydd. Yn gyfnoddol i'r cyfnoddol i'r cyfnoddol, a dweud o'i cyfnoddol i rhaithio'r cyblwyr ch sickness for that for you. You also has good idea to create some automated tests, some be had to test the front and some p h p unit test test some of the internal functions. And obviously it's good to make sure those tests pass because it's a bit embarrassing if you submit it and the tests don't all pass. Wants you've got the code finished and the developer will usually put up a patch on git hub and then put and then open go Ie, go on to the ticket and open and that. And don't ask for a peer review of that patch. Now when you've opened a ticket and asked for a peer review, the first thing that happens is a whole load of automated tests kick in and they do all the checks to see if you've laid everything out correctly, if you've been sensible with your variable names and also in the latest versions of Moodle it can also run some of the automated tests immediately using the sort of Travis system. Then hopefully someone will come on and they will actually peer review it themselves. Again, checking, manually checking things like the layout, checking to see if you've got language strings in there, making sure that you've got testing instructions, making sure that it's actually a sensible thing that you're doing in the first place. In this case Dan came back to me and said, oh could you change this? Could you change that? So I went back, I made some changes, I took out a couple of the magic numbers that I had in there and replaced them with definitions and then I fixed a bit of a nasty bug in there and then I returned it back to the issue tracker. Next thing that happens is once a peer review's got taken place then hopefully someone will then put it forward for integration and then it's someone from Moodle HQ will come along and give it another check, make sure that it is actually a sensible thing to get into Moodle Core. In this case Eloi came out with some various bits of feedback which we went back and forth for a while until the issue was ready and then at that point Andrew then allowed it through into the integration repository. If you're lucky by the end of the week, when something is in integration by the end of the week, it then gets into the new developer version of Moodle from the following week. For things which are bug fixes, often you might want to back port it so that currently supported versions of Moodle like 2.8, 2.9 get the same fix or if it's security it will even go back to 2.7. If it's a new feature then it'll only appear in the next version so in this case that was Moodle 3. At the end of the week the integration branch or the automated tests are run and also all the manual testing instructions that you typed in when you submitted it are gone through by a chosen tester and hopefully everything will be okay but if something's not okay then it gets yanked out of integration and you get another week or two to sort it out. All being well, everything is integrated, it gets closed, Eli posts an amusing comment or whoever's on integration that week posts an amusing comment and the ticket is closed to indicate that everything is finished. Finally, if there's any Google documentation, I can't say Google Moodle documentation needed, then that's added so in this case Mary Cooch added some documentation to the Moodle docs about it and then updated the ticket to say that that had been done and then finally if you're really lucky it'll be there in the new Moodle release and actually in Moodle 3 if you look on the features overview there is just a little note on one of the sections which says that the groups overview screen now has the not in group feature which I've just been demonstrating there and I've got to think one more slide which was just to say this is from the Moodle developer docs which is basically a flowchart showing exactly that process which I've whipped through in a very very short space of time so hopefully that kind of makes sense to you now.