Difference between revisions of "Education Courses"
(→Contents) |
|||
| Line 2: | Line 2: | ||
'''FIXME: DRAFT, define a better look, sort every point .. add missing ''' | '''FIXME: DRAFT, define a better look, sort every point .. add missing ''' | ||
| + | |||
| + | ==== Introduction ==== | ||
| + | |||
| + | Original links : | ||
| + | |||
| + | The Courses idea is based on Franck Hecker blog : | ||
| + | |||
| + | [[http://hecker.org/mozilla/seneca-college-and-open-source-education]] | ||
| + | |||
| + | Mozilla University : | ||
| + | |||
| + | [[http://www.mozilla.org/university/ Mozilla University]] | ||
| + | |||
| + | [[http://www.mozilla.org/university/courses.html Mozilla courses ]] | ||
| + | |||
| + | '''Let's try ? :-)''' | ||
Revision as of 16:19, 20 November 2007
Return to Education Project
FIXME: DRAFT, define a better look, sort every point .. add missing
Introduction
Original links :
The Courses idea is based on Franck Hecker blog :
[[1]]
Mozilla University :
Let's try ? :-)
Rules
We must know, as preliminary, what is teached in the most common situations in most of the schools
FIXME : TABS
- Chinese education system for computing
- US System education system for computing
- French system education system for computing
- Other ...
Who will help, contribute for the courses
How present them
Courses must have pre requisites
Courses must follow objectives :
- knowledge
- know how
- experimental know how
Authors of courses must be visible
A clear progression must be defined
Define, for every courses, developers who can be contacted as technical contacts
Create applications illustrating the courses, including code sample
Contents
1) not project / applications dependant
- Structure of the project
Projects, organisation, life, decisions .. etc
- Tools:
source code: checkout (cvs / git / svn ) , extract infos ( cvs log ..etc ) , organisation
cwstools: cwsquery, create a cws, cws life: QA, validate, resync a cws
Build OpenOffice.org: dependencies, configure time, needs for every OS, architecture
examples: AquaBuild
- Source Code
extract cws, create patches, apply them, propose patches
- interactions with tools:
buildtime, dependencies management (build.lst) , solver (d.lst)
- Build issues: acquire skills, share and teach them
- known typical issues: typical build issues ( makefile relevant); code issues: fix warnings
- how find info: IssueZilla, IRC
- provide a buildfix (patch)
- rules for commiting
- avoid general build breaker(s): portability rules
- Writing code
- Coding Guidelines
- source code distribution: where find what
- rules for code review
- become a Domain Developer
Source code analyze ( + examples ) :
- vcl content and design -> use Mac OS X port as example
- svx content and design
- scp2: content and design
Feature implementation: how write specs, the process, integration process
Example of feature implementation: Native FilePicker on Mac OS X, for Aqua version of OpenOffice.org
Work in progress: new print dialog box
Manage a new feature implementation
