Difference between revisions of "Education Project"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Courses)
(Contents)
Line 125: Line 125:
  
 
==== Contents ====
 
==== Contents ====
 +
 +
 +
1) not project / applications dependant
  
 
* Structure of the project  
 
* Structure of the project  
  
Projects, organisation, life, decisions ..  etc  
+
Projects, organisation, life, decisions ..  etc
  
  
Line 137: Line 140:
 
cwstools: cwsquery, create a cws, cws life
 
cwstools: cwsquery, create a cws, cws life
  
Build OpenOffice.org
 
  
 +
Build OpenOffice.org: dependencies, configure time, needs for every OS, architecture
 +
 +
examples: AquaBuild
  
 
* Source Code
 
* Source Code
  
 
extract cws, create patches, apply them, propose patches
 
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: build typical issues ( makefile relevant); code issues: fix warnings
 +
 +
- how find info: IssueZilla, IRC
 +
 +
- provide a buildfix (patch)
 +
 +
- avoid general buildbreaker: portability rules
 +
 +
 +
* Writing code
 +
 +
- Coding Guidelines
 +
 +
- source code distribution: where find what
 +
 +
Source code analyze ( + examples ) :
 +
 +
- vcl content and design -> use Mac OS X port
 +
 +
- svx content and design
 +
 +
- scp2: content and design
 +
 +
 +
 +
-
  
 
===  Whatever ===
 
===  Whatever ===

Revision as of 14:25, 12 November 2007

[Education project]

Categories:

Education project: the official site


Todo

( Brainstorming in progress )

  • Revamp http://education.openoffice.org
  • Statisticize the site
  • Organize the wiki page
  • Create new entries : locales ? / tools ? / Success stories ? / Partners ?
  • Resources : ask an entry for every school present on the site ? (annually ?)
  • QA : define default owner for education project issues
  • Be present and visible (please complete the list) :


European events :

  • OOoCon 2008 (supposed occuring in Europa, not sure .. )
  • FOSDEM 2008
  • RMLL 2008 (France, Mont de Marsan, probably 1st or 2nd week of July )
  • Educatice ( France, Paris )
  • Apple Expo

US events :

WWDC (San Francisco) / AppleLiveExpo (Köln) / Mac World (San Francisco)


Asian events :


African events :


Oceanian events :

List of schools

Define tabs for every country ?

French schools already contacted :

Work in progress (this week)  :


please complete the list, and define/add contacts

Projects in progress

Volunteers to revamp the site

  • Raphael Bircher

IRC channel

All informations are now available at Education_IRC_meetings wiki page.


Proposal : have regular IRC meetings ?

First IRC meeting scheduled for the week 12th - 17th of November 2007


Proposed :

server : irc.freenode.net Channel : #education.openoffice.org

Done :

Register the channel : Chanserv is set as guard , mode secure On, Topiclock is on, ops are ericb2, lgodard, rbircher louis_to ( new volunteers are welcome )

Define operators / tasks / Action Items

+ complete the list on OpenOffice.org wiki page

Courses

Rules =

We must know, as preliminary, what is teached in the most common situations

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


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: build typical issues ( makefile relevant); code issues: fix warnings

- how find info: IssueZilla, IRC

- provide a buildfix (patch)

- avoid general buildbreaker: portability rules


  • Writing code

- Coding Guidelines

- source code distribution: where find what

Source code analyze ( + examples ) :

- vcl content and design -> use Mac OS X port

- svx content and design

- scp2: content and design


-

Whatever

FIXME : complete :-)

Personal tools