Difference between revisions of "Individual Project 01"
| Line 5: | Line 5: | ||
all rights of this project work or other outcomes belongs to OpenOffice.org<br> | all rights of this project work or other outcomes belongs to OpenOffice.org<br> | ||
get help and info were you want<br> | get help and info were you want<br> | ||
| + | <br> | ||
| + | start basics:<br> | ||
| + | 1. site: give the group a name and create a wiki site (like the calling cards)<br> | ||
| + | 2. work diary: on this site write a weekly (at the end of every week, means sunday) progress of the week (in few pregnant words)<br> | ||
| + | 3. monthly resumee: after four weeks write a small resumee (approx. 1000 words) and present your work<br> | ||
---- | ---- | ||
| + | '''Project discription: create a musik database (for handling musik files, cover, info etc.) with a form frontend (ui) by using the OOo internal HSQL db.'''<br> | ||
<br> | <br> | ||
| + | 1 month: orientation, ideas, concept, design, Spec (itterative)<br> | ||
| + | 2 month: realisation (must be ready inside this month)<br> | ||
| + | 3 month: TCS and Documentation (2 weeks), QA a foreign project and write a buglist (1 week), bugfixing with buglist (1 week)<br> | ||
| + | ! afterwards a jury of sun experts (qa, ux, dev) and the OOo community will have a look at the results and comment them.<br> | ||
<br> | <br> | ||
Revision as of 13:30, 19 May 2009
Music Database
(individual project start: 25 May 2009 for 3 months)
2-3 person groups (organizes themselves) – GL arrange and support the group
all rights of this project work or other outcomes belongs to OpenOffice.org
get help and info were you want
start basics:
1. site: give the group a name and create a wiki site (like the calling cards)
2. work diary: on this site write a weekly (at the end of every week, means sunday) progress of the week (in few pregnant words)
3. monthly resumee: after four weeks write a small resumee (approx. 1000 words) and present your work
Project discription: create a musik database (for handling musik files, cover, info etc.) with a form frontend (ui) by using the OOo internal HSQL db.
1 month: orientation, ideas, concept, design, Spec (itterative)
2 month: realisation (must be ready inside this month)
3 month: TCS and Documentation (2 weeks), QA a foreign project and write a buglist (1 week), bugfixing with buglist (1 week)
! afterwards a jury of sun experts (qa, ux, dev) and the OOo community will have a look at the results and comment them.
Please do not change the logical content of this site without acknowledge of the author, the Database Docu Coordinator or the OOo QA Project Lead/Co-Leads.
