Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Developer meeting February 2008.

Developer meeting February 2008: Difference between revisions

From MoodleDocs
(meeting room login)
Line 24: Line 24:
==Moodle 2.0==
==Moodle 2.0==


* Performance tips
* Repository API
* Repository API
* Portfolio API
* Portfolio API
* Conditional activities
* nWiki for Moodle 2.0
* Feedback module
* Feedback module
* Conditional activities
* HotPot module (Gordon)
* Wiki for Moodle 2.0 (Remember to visit the [http://wiki.moodle.org/ 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
* Turnitin Integration? (Dan Marsden)
* Turnitin Integration? (Dan Marsden)
* Performance tips


==Other stuff==
==Other stuff==

Revision as of 12:24, 28 February 2008

Developer meetings > February 2008 meeting



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

  1. Round up of major API changes
    1. Grades
    2. Events
    3. Groups
    4. Tags
    5. Roles
    6. ...
  2. Journal in/out/something else?

Moodle 2.0

  • Repository API
  • Portfolio API
  • Conditional activities
  • nWiki for Moodle 2.0
  • Feedback module
  • HotPot module (Gordon)
  • Turnitin Integration? (Dan Marsden)
  • Performance tips

Other stuff

  • 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.)
  • Introducing Contrib Coordinator
  • Testing Moodle - do we need a more coordinated approach with people responsible for modules (see more comments on this page by Gary)
  • Unmaintained modules - we could really use maintainers for them
  • Other infrastructure, communication, and workflow related issues?
  • Google Highly Open Participation contest

See also