|
|
(13 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
| [[Developer meetings]] > San Francisco 2008 Developer HackFest
| | {{Moved_to_dev_docs}} |
| | |
| | |
| *Date: 9am - 5pm Monday 9th June 2008 - see the [http://moodle.org/calendar/view.php?view=day&course=5&cal_d=9&cal_m=6&cal_y=2008 San Francisco 2008 Developer HackFest calendar entry] for conversion into your time zone
| |
| *Location: [http://www.grosvenorsfo.com/ Best Western Grosvenor Hotel], San Francisco
| |
| *Online location: [http://elluminate.remote-learner.net/join_meeting.html?meetingId=1176914355734 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 [http://www.remote-learner.net/ Remote-Learner.net].
| |
| | |
| Everyone is welcome, either in person or online :-)
| |
| | |
| | |
| ''Please add items to the agenda!''
| |
| | |
| | |
| ==Overview==
| |
| | |
| * Overview of development for Moodle 1.9 and Moodle 2.0 (Martin)
| |
| * Current [[Roadmap|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 discussions==
| |
| | |
| ===Options for getting Moodle to communicate with external systems, including [[Development:Web services API|web services]]===
| |
| 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.
| |
| | |
| ===API's for [[Development:Portfolio API|portfolios]], [[Development:File API|file managers]] and [[Development:Repository API|document repositories]]===
| |
| | |
| ===Further plug-ability and expandability e.g. new course format objects, redefining page display layer etc.===
| |
| | |
| Participants will be sharing code and development ideas that have emerged in their organizations in smaller groups, with the aim of coming up with a list of recommendations that can be formed into specifications.
| |
| | |
| ==General discussions==
| |
| | |
| ===Gradebook interface improvements===
| |
| *Overview of community feedback on 1.9 gradebook (Nicolas Connault)
| |
| *Run-down of current development
| |
| *Discussion of ideas for improvement, better defaults etc.
| |
| | |
| ===Google Summer of Code===
| |
| | |
| *[[GSOC/2008|Google Summer of Code 2008]] (Helen)
| |
| | |
| ===If you want to lead a discussion on something, please add it here!===
| |
| | |
| | |
| ==Other stuff==
| |
| * 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. --[[User:Dan Poltawski|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)
| |
| | |
| [[Category:Developer]]
| |