Hi everyone,
This weekend we're holding our first ever Moodle 2.0 sprint to help get 2.0 beta out as soon as possible!
To take part in the sprint, simply choose a feature in Moodle 2.0 which needs finishing, or some 2.0 bugs which need fixing, then when you have time at the weekend, get coding! Remember to drop by our Jabber developer chat room at some point and let others know what you’re working on.
Penny, Martin and I will be taking part in the sprint. Anyone else thinking of joining us?
Oh wow! If I only knew about development I' d be in
Just wait until Moodle 3.0 ,..-maybe I'll have learned a bit by then.......
Just wait until Moodle 3.0 ,..-maybe I'll have learned a bit by then.......
Mary, there's no need to wait till Moodle 3.0. We'll be holding some Moodle 2.0 testing sprints soon, in addition to the code sprints! 
delete the message that let you just now? that is what collaborative learning?
In reply to Luis Alberto Bravo Caballero
Re: Moodle 2.0 sprint this weekend
lo siento acabo de ver que la pregunta que hice en un nuevo hilo del foro...
sorry just saw that the question I asked in a new forum thread ...
sorry just saw that the question I asked in a new forum thread ...
If I feel I can help at something, I will be in too!
Si je me rends compte que je peux faire quelque chose, j'aiderai!
Si je me rends compte que je peux faire quelque chose, j'aiderai!
I'm not a developer's rear end but if you need a testing resource then let me know - I was a QA guy in a previous life. I'm also trying to find out who is around the place this weekend from NetSpot - might be tricky on short notice but I'll do my best.
How are things like development standards and code quality going to be managed if its an open invite?
How are things like development standards and code quality going to be managed if its an open invite?
Hi Mark!
It's not really an open invite in the sense that people that couldn't previously commit code suddenly can.
Those of us who have commit access and are working on things for 2.0 already, will continue with that. People that don't have commit access can test bugs for reproducability and then attach patches to tracker issues, which will be reviewed before being committed just like normal
I wanted to find a way to somehow formally be able to say that a tracker issue has a patch attached (I'm thinking of the Debian bug tracker, which has a tag "patch"), but it seems that if you just write the word "patch" in a comment when you attach a file it can be found.
It's not really an open invite in the sense that people that couldn't previously commit code suddenly can.
Those of us who have commit access and are working on things for 2.0 already, will continue with that. People that don't have commit access can test bugs for reproducability and then attach patches to tracker issues, which will be reviewed before being committed just like normal
I wanted to find a way to somehow formally be able to say that a tracker issue has a patch attached (I'm thinking of the Debian bug tracker, which has a tag "patch"), but it seems that if you just write the word "patch" in a comment when you attach a file it can be found.
"reproducability" Penny?
grrrrrrr
Argh! I have an assignment due for the OU course I am studying that I must do this weekend, and you put temptation like this in my way. If you see me there, ask me if I have finished my assignment, and if not, kick me out 
Tim -do what I do - just don't sleep. That way you get everything done!
I have to get ready the house ready for the inlaws-to-be but any free time I find myself with I'll be happy to spend on development, so count me in
I'm free on Saturday, I'll drop by the channel and see what I can help with!
I'm in!
I hope to look at all the bugs Penny has been bugging me to test, enrolment changes, general bugfixing and possibly investigate a dropbox portfolio/repo plugin.
I hope to look at all the bugs Penny has been bugging me to test, enrolment changes, general bugfixing and possibly investigate a dropbox portfolio/repo plugin.
Brilliant! Good to hear that lots of you can make our sprint! Anyone else?
In addition to our Jabber developer chat room, Dan Marsden has suggested #moodle on freenode as another meeting place.
Anyone else?In addition to our Jabber developer chat room, Dan Marsden has suggested #moodle on freenode as another meeting place.
I'll hopefully get some stuff done although this weekend is exactly 1 week until my wedding. A major Moodle release and a wedding are not good things to try and do at the same time :\
What's this thing with Sam "having to get ready the house ready for the inlaws-to-be" and you, Andrew, "1 week away from your wedding". What's this "getting married frenzy" ? Spring is in the air?
Best wishes to you both.
Joseph
+1 to Joseph's comment "Best wishes to you both" Sam and Andrew!
I doubt your wedding has been as long in the making as Moodle 2.0
Yay thanks Dan.
Also more portfolio plugins would be awesome
Also more portfolio plugins would be awesome
I'm up for fixing some bugs this weekend. I've got about ten months experience working with Moodle in a development context.
I'm also interested in doing any QA-type work if there is any to be done, either on this sprint or on a future one.
I'm also interested in doing any QA-type work if there is any to be done, either on this sprint or on a future one.
Thanks again to everyone hoping to take part in our sprint tomorrow and/or Sunday. Please see Development:Sprint for details of the event.
Brendan, your help with QA will definitely be appreciated once Moodle 2.0 beta is released. We're hoping to hold several sprints for testers and documentation writers (as well as developers) during the beta period.
Brendan, your help with QA will definitely be appreciated once Moodle 2.0 beta is released. We're hoping to hold several sprints for testers and documentation writers (as well as developers) during the beta period.
Hi!
I could not resist the temptation, and decided to work on MDL-20139. I read all the discussion generated last August, and made changes to react to that. I really hope this will be committed before Moodle 2.0 release.
Thanks for the idea, I would probably not have gotten this done without it!
I could not resist the temptation, and decided to work on MDL-20139. I read all the discussion generated last August, and made changes to react to that. I really hope this will be committed before Moodle 2.0 release.
Thanks for the idea, I would probably not have gotten this done without it!