Developer meeting February 2008: Difference between revisions
From MoodleDocs
Line 32: | Line 32: | ||
*[[How to write a good bug report]] The Tracker page on the docs.moodle.org has been updated (https://docs.moodle.org/en/Tracker), let's try to write good bug reports that would eventually save Martin (and other developers) a lot of time (to read and understand the bug reports...etc.) | *[[How to write a good bug report]] The Tracker page on the docs.moodle.org has been updated (https://docs.moodle.org/en/Tracker), let's try to write good bug reports that would eventually save Martin (and other developers) a lot of time (to read and understand the bug reports...etc.) | ||
*(Brainstorming maybe) Infrastructure, communication, and workflow related issues? | *(Brainstorming maybe) Infrastructure, communication, and workflow related issues? | ||
** Do we have QA test plan for 1.9 and 2.0? If no, should we start to think of creating one to better ensure software quality? | |||
** How to better coordinate testing efforts among different developers/institutions? | |||
*[[GHOP/2008|Google Highly Open Participation contest]] | *[[GHOP/2008|Google Highly Open Participation contest]] | ||
Revision as of 21:47, 20 February 2008
Developer meetings > February 2008 meeting
- Date: 11pm GMT, Thursday 28 February 2008 - see the Moodle Developer Meeting calendar entry for conversion into your time zone
- Location: Elluminate Moodle Developers Meeting Room
Everyone is welcome, though developers with CVS write access will be given preference if the room becomes full.
Please add items to the agenda!
Moodle 1.9
- Round up of major API changes
- Lessons learned in getting 1.9 ready for release (see this page's comments)
- Journal in/out/something else?
Moodle 2.0
- Performance tips
- Repository API
- Portfolio API
- Feedback module
- Conditional activities
- Wiki for Moodle 2.0 (Remember to visit the Moodle wiki testing site and vote for the wiki you would like to be included in Moodle 2.0 before Monday 18 February 2008.)
- HotPot module
Other news
- Bugathon including an announcement of prize winners!
- How to write a good bug report The Tracker page on the docs.moodle.org has been updated (https://docs.moodle.org/en/Tracker), let's try to write good bug reports that would eventually save Martin (and other developers) a lot of time (to read and understand the bug reports...etc.)
- (Brainstorming maybe) Infrastructure, communication, and workflow related issues?
- Do we have QA test plan for 1.9 and 2.0? If no, should we start to think of creating one to better ensure software quality?
- How to better coordinate testing efforts among different developers/institutions?
- Google Highly Open Participation contest