1,774
edits
Changes
m
[''This section is '''VERY DRAFT'''[More detailed roadmaps are included on specific pages related to the pilot program activities outlined above. Much discussion still needed.]'']
''[More detailed roadmaps for each experiment / pilot will be included on the related pages.]''=== Q1 2009 ===
=== Q1 2009 ===* Do we still have confidence in proposed activities now that we have plans and budgets in place? If 'no' for any activity, kill it.* 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 enthusiasm, drop this idea.* Are we able to gather compelling and useful content for EMO? 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 student project pool web site and updated Real World Mozilla course?
* Present proposed plan to the Mozilla Foundation board.* Revise plan as necessary based on board or other feedback.* Select projects to execute on, prepare final proposals, and secure commitments for funding and/or staff time.'''Activities'''
* Hold an [[Events/EduCamp@FOSDEM2009|EduCamp]] meeting in association with [http://www.fosdem.org/=== Q2 2009/ FOSDEM conference] in early February to discuss Mozilla and other open source education initiatives in Europe.* 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.===
=== Q2 2009 ===* To what extent did we achieve the goal of expanding Seneca activities to include and/or support non-Seneca institutions and people (e.g., per the checklist above)?* Is everything in place to have a successful first course at URJC?* What worked with the first Mozilla community courses, and should be repeated for subsequent courses? What needs to be changed, and how?* Do we have a solid plan for evolving EMO, including detailed budget and task lists? (Or, if we decide EMO is not the way to go, do we have a solid plan for how to meet the need we thought we were meeting with EMO?) '''Activities'''
End of quarter checks:
* To what extent did we achieve the goal of expanding Seneca activities to include and/or support non-Seneca institutions and people (e.g., per the checklist above)?
* Is everything in place to have a successful first course at URJC?
* What worked with the first Mozilla community courses, and should be repeated for subsequent courses? What needs to be changed, and how?
* Do we have a solid plan for evolving EMO, including detailed budget and task lists? (Or, if we decide EMO is not the way to go, do we have a solid plan for how to meet the need we thought we were meeting with EMO?)
* Work on Seneca initiatives in preparation for new academic year. * Mozilla Technology course begins.* Hold three Mozilla community courses (one per month)* Work on the next phase of EMO. '''End of quarter checks:check points'''
* Evaluate the achieved scope '''End of the Seneca program in the 2008-2009 academic year thus far vs. what was accomplished in the 2007-2008 academic year.* Evaluate the success of the Mozilla Technology course and plan follow-on projects.* Evaluate the success of Mozilla community courses, including the popularity of particular topics and whether the basic model of academic instructor plus mentor is working OK.quarter check points'''
End of quarter checks:
→Roadmap
== Roadmap ==
''[Open question: Is a roadmap process tied to the Foundation's fiscal year and the calendar year going to work for projects done in cooperation with institutions working to an academic year calendar? How much lead time will we need to have significant influence over what an institutions rolls out in the fall semester?]End of quarter check points'''
* Prepare Present plan to the Mozilla Foundation board, revise plan as necessary. Finalize commitments for funding and staff time. (January)* Finalize a detailed task list and timeline for Seneca activities.(January)* Generate a list of course topics for Mozilla community courses, recruit instructors and mentors for Mozilla community courses, begin course design. (January and February)* 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 prototype as a page on www.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)
'''End of quarter checks:* Do we have detailed plans and budgets for all proposed activities?* Do we have agreement on plans and institutional commitments at Seneca and URJC?* Do we have qualified people committed to work on the Mozilla community courses?check points'''
* Do an academic year-end review of Seneca program, including
* Evaluate the usefulness of the EMO prototype (e.g., based on traffic, content, comparison with related sites) and plan how it might evolve. (In particular, whether it remains a portal only or should 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.
=== Q3 2009 ===
* Have all Seneca-related issues identified the earlier review been addressed going into the 2008-2009 academic year?
* 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 functionality?
'''Activities'''
* Work on Seneca initiatives in preparation for new academic year.
* Mozilla Technology course begins.
* Hold three Mozilla community courses (one per month)
* Work on the next phase of EMO.
=== Q4 2009 ===
* Seneca: See above.
* What further is needed from Mozilla and URJC to achieve Seneca-like success? Are there any quick wins? What needs to be done in order to achieve a significant step up in activity for 2009?
* Do any major tweaks need to be made to the Mozilla community courses for 2009? Should we bring all instructor duties inhouse (as part-time or full-time staff)?
* Is EMO important enough to evolve into a "first-class object" (e.g., comparable to SUMO, QMO, AMO, MDC) during 2009?
'''Activities'''
* Evaluate the achieved scope of the Seneca program in the 2008-2009 academic year thus far vs. what was accomplished in the 2007-2008 academic year.
* Evaluate the success of the Mozilla Technology course and plan follow-on projects.
* Evaluate the success of Mozilla community courses, including the popularity of particular topics and whether the basic model of academic instructor plus mentor is working OK.
=== Beyond ===
