Confirm
610
edits
Changes
Change education.mozilla.org acronym from EMO to EDMO
=== education.mozilla.org ===
The [[Foundation:Planning:Education:EMOEDMO|education.mozilla.org]] (EMOEDMO) initiative will create a Mozilla Education library as a special section on mozilla.org. This would make it easy to find resources like:
* The Real World Mozilla and Mozilla Developer Resource Kit materials developed at Seneca.
* Do we have agreement on plans and institutional commitments from Seneca and URJC? If 'no', ask why and potentially reconsider partnership.
* Do we have people, content and web infrastructure ready to roll for at least one Mozilla Community Course? If 'no', is the problem one of resources or enthusiasm for the project? If the problem is lack of enthusiasm, drop this idea.
* Are we able to gather compelling and useful content for EMOEDMO? If 'no', what is missing? Where do we need to look? Is the idea viable?
* Do we have shared versions of basic Seneca tools for use by others, especially the prototype student project pool web site and the updated Real World Mozilla course?
* Do we have the materials and people in place to have a successful first course at URJC? Are students registered?
* How many people participated in the first Mozilla community courses? Did the participating Mozilla projects get useful outcomes? If 'no', do we need to improve our approach or kill this idea?
* Are we starting to see traffic and use on the EMO EDMO site? If 'no', does this indicate a lack of interest or a need for improvements?
=== September 30, 2009 (end of Q3) ===
* Do we see actual courses or individual student projects starting up with Seneca-provided resources? If 'yes', do we have the capacity to handle them? If 'no', assess why and adjust future plans accordingly.
* Is the pace of Mozilla community courses meeting the needs of the potential audience? What do we need more of? Less of?
* How useful is the new EMO EDMO functionality? If it is not useful, can it be fixed?
=== December 31, 2009 (end of Q4) ===
* Did the URJC Mozilla Technology summer course generate good learning outcomes for participants? Was URJC happy with the outcomes? Did we produce re-usable course materials? If 'yes' on most, consider a second phase. If 'no', question whether this is worthwhile to do again.
* Do any major tweaks need to be made to the Mozilla community courses for 2009? Should we bring all instructor duties in-house (as part-time or full-time staff)?
* Is EMO EDMO important enough to evolve into a "first-class object" (e.g., comparable to SUMO, QMO, AMO, MDC) during 2010? If 'yes', this needs to be fully addressed in the 2010 budget.
* What is our overall assessment of Mozilla Education activities in 2009? What are the answers to our core design and thesis questions? In 2010, should we expand, evolve our experiments or kill the program?
* Hold an [[Events/EduCamp@FOSDEM2009|EduCamp]] meeting in association with [http://www.fosdem.org/2009/ FOSDEM] in early February to discuss Mozilla and other open source education initiatives in Europe. (February)
* Get a definitive go/no-go decision on URJC participation and plans for a Mozilla Technology course, and begin content development. (January)
* Deploy an initial EMO EDMO prototype as a page on mozilla.org or WikiMo with a basic set of links and resources. (February and March)
* Develop shared versions of core Seneca resources, especially student project pool web site and updated Real World Mozilla course. (January to March)
* Make contacts and have discussions with the OSS Watch FOSS Education project, the institutions involved in the "Integrating FOSS into undergraduate curriculum" activities, and others involved in general "teaching open source" activities. (throughout)
* Develop content and recruit students for Mozilla Technology course, making sure it's ready to go live in Q3.
* Deliver at least one Mozilla community courses, ideally more.
* Evaluate the usefulness of the EMO EDMO prototype (e.g., based on traffic, content, comparison with related sites) and plan how it might evolve. In particular: should it remain a simple portal or take on other functions?
* Make decisions on where and how we might work together with others involved in "teaching open source" activities and commit to a set of plans.
* Mozilla Technology course begins.
* Hold three Mozilla community courses (one per month)
* Work on the next phase of EMOEDMO.
=== Q4 2009 ===
