SF Developer HackFest: Difference between revisions
Helen Foster (talk | contribs) (→Round table discussion: Further plug-ability and expandability: proposed format plugin changes) |
Helen Foster (talk | contribs) (→Round table discussion: Further plug-ability and expandability: shared activities system) |
||
| Line 95: | Line 95: | ||
Mark N then described his proposed format plugin changes (see [http://moodle.org/mod/forum/discuss.php?d=95882 Proposed format plugin changes] forum discussion). | Mark N then described his proposed format plugin changes (see [http://moodle.org/mod/forum/discuss.php?d=95882 Proposed format plugin changes] forum discussion). | ||
Tim H demonstrated the shared activities system, an abuse of the course format ;-) (see the modules and plugins database entry [http://moodle.org/mod/data/view.php?d=13&rid=1558 Shared activities system]). | |||
==General discussions== | ==General discussions== | ||
Revision as of 00:02, 10 June 2008
Developer meetings > San Francisco 2008 Developer HackFest
- Date: 9am - 5pm Monday 9th June 2008 - see the San Francisco 2008 Developer HackFest calendar entry for conversion into your time zone
- Location: Best Western Grosvenor Hotel, San Francisco
- Online location: Elluminate Moodle Developers Meeting Room - login using your actual name as login name and password moodle
Developers and anyone wishing to become a Moodle developer can share code and ideas, and help shape the future of Moodle. This event is FREE, thanks to the sponsor Remote-Learner.net.
Everyone is welcome, either in person or online :-)
Overview
- Overview of development for Moodle 1.9 and Moodle 2.0 (Martin)
- Current Moodle 2.0 Roadmap run-through (Martin)
- Brainstorming session to vote on priorities (Martin and all)
Wish list
- file / repositories 12
- student info api 8 (eg banner, peoplesoft)
- mobile/offline learning support 4
- user testing / usability 6
- section/course templates 1
- ldap enrollment plugins 1
- course formats / pagelib 1
- auomating backup/restore more 1
- module api (classes, add tabs to user profile) 2
- performance/caching 5
- randomization in quiz essays 1
- gradebook interface / ajax 5
- agents for automating tasks for teachers 2
- better handling of course instances 1
- email / messaging 1
- delete sections 1
- case studies on implementations 3
- opensocial API/docs/forum 2
- statistics reports 2
- web services / standard API functions 5
- better navigation for students (terms/my moodle) 2
- FERPA 3
- group based enrollments / site-wide groups 3
- more capabilities (eg for course settings) 1
- new wiki 2
- more control over page layout in themes 1
- chat speed / robustness 1
- developer training 1
- gradebook improvements (eg calculated outcomes, easier extra credit) 3
- module quality review 2
- eportfolio / outcomes 1
- early warning systems 1
- progress tracking / competencies 2
- more collaborative tools 2
- file sharing 2
- offline gradebook 1
- video handling 1
- whiteboard / conferencing 2
- moodle networking polishing 1
- forum improvements (compiling, usability) 1
- roles user interface improvements 1
- conditional activities 1
- assign activities to users 1
Round table discussion: Options for getting Moodle to communicate with external systems
Existing plugins include:
- Gradebook import / export plugins
- Auth plugins inc. single sign-on
- Enrollment plugins
- Backup / restore
- Question bank
- Glossary import / export
- Database import / export
- Upload users
Martin L advises avoiding using LDAP unless absolutely necessary. With large systems e.g. Banner, export then import using an enrolment plugin. Use an intermediate database table for enrolment info so as not to be completely dependent upon the student information system. Consider error handling.
Tim H talked about the gradebook export function in XML format for pushing gradebook data into external systems. Martin D mentioned that there's also an option to publish data through a URL. The gradebook has an option to export only changed grades. Michael P said that any gradebook changes should appear immediately in the external system.
Martin D explained that student info APIs are really complex, so all we can do in Moodle is build and document a toolset.
Future options: Development:Web services API
Round table discussion: APIs
Round table discussion: Further plug-ability and expandability
Michael P demonstrated flexpage format (see also Using Moodle New format- Flexible Page forum discussion).
Mark N then described his proposed format plugin changes (see Proposed format plugin changes forum discussion).
Tim H demonstrated the shared activities system, an abuse of the course format ;-) (see the modules and plugins database entry Shared activities system).
General discussions
- Gradebook interface improvements (Nicolas Connault) - Overview of community feedback on 1.9 gradebook, run-down of current development, discussion of ideas for improvement, better defaults etc.
- Google Summer of Code 2008 (Helen)
- I (Tim Hunt, OU Moodle developer and Moodle quiz module maintainer) will be there. I don't have anything in particular that I want to say, but I am very happy to talk about anything anyone else wants to cover that I know about.
- It might be good to have a general discussion on general testing/QA issues. Eg. bug triage, encouraging more testing/QA contributors, the weekly review etc. --Dan Poltawski 13:14, 30 May 2008 (CDT)
- I second Dan's idea! It would be great if we could brainstorm a more coordinated and systematic way of doing QA! Thanks! --Wen 00:09, 9 June 2008 (PST)
- Also, it might be good to have some discussion on a better voting mechanism (e.g., a moodle block on the moodle.org front page that have something like http://www.twiigs.com/) to encourage moodle community users to vote on important issues (e.g. default settings, etc.). --Wen 00:29, 9 June 2008 (PST)
- Including global (or context) groups in Moodle 2.0 roadmap (and talk about that), as Petr agreed in the tracker (see MDL-11826)
