Confirmed users
656
edits
Foundation:Planning:Education:Seneca: Difference between revisions
Foundation:Planning:Education:Seneca (view source)
Revision as of 15:53, 7 January 2009
, 7 January 2009→Products / stuff we'll create
| Line 63: | Line 63: | ||
* an actively maintained list of potential projects (bugs) for students and others looking to get involved. | * an actively maintained list of potential projects (bugs) for students and others looking to get involved. | ||
* a retrospective look at bugzilla in order to data mine knowledge in the community about Mozilla development best practices. Every day patches are reviewed, and knowledge recorded about what to do, and what not to do. This information should be gathered so that new students/faculty can be more effective with their work right away. Also, this would help to make Mozilla seem less intimidating for outsiders: it's a real strength of Mozilla that so much of the knowledge is embedded in the community; but it also sets up an "inside" and "outside." Many faculty and students want to get engaged quickly to do a project, and may or may not want to commit to staying around long term. | * a retrospective look at bugzilla in order to data mine knowledge in the community about Mozilla development best practices. Every day patches are reviewed, and knowledge recorded about what to do, and what not to do. This information should be gathered so that new students/faculty can be more effective with their work right away. Also, this would help to make Mozilla seem less intimidating for outsiders: it's a real strength of Mozilla that so much of the knowledge is embedded in the community; but it also sets up an "inside" and "outside." Many faculty and students want to get engaged quickly to do a project, and may or may not want to commit to staying around long term. | ||
* a living example of what it means to teach Mozilla at the post-secondary level, but continuing to offer the Mozilla courses at Seneca. This will insure a steady supply of students, updates to materials, constant improvement of process, etc. and give interested faculty elsewhere a model to follow. | |||
== Use cases == | == Use cases == | ||