Difference between revisions of "QA reloaded"
| (3 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
[http://blogs.sun.com/GullFOSS/entry/ooo_qa_reloaded1 Introducing blog from Chris Lukasiak (Member of Sun StarOffice/OpenOffice.org QA Team)] | [http://blogs.sun.com/GullFOSS/entry/ooo_qa_reloaded1 Introducing blog from Chris Lukasiak (Member of Sun StarOffice/OpenOffice.org QA Team)] | ||
| − | |||
| Line 27: | Line 26: | ||
[http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-TeamPages.odt Concept: Team Pages] | [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-TeamPages.odt Concept: Team Pages] | ||
| + | |||
| + | |||
| + | [http://blogs.sun.com/GullFOSS/entry/about_one_year_of_ooo About one year of OOo QA Reloaded]<br> | ||
| + | [http://blogs.sun.com/GullFOSS/entry/ooo_qa_reloaded_internship_program OOo QA Reloaded: Internship Program] | ||
Latest revision as of 09:14, 8 July 2009
OOo QA - Strategic Concept Papers
As a result of further opening of the Sun StarOffice/OpenOffice.org QA Team, further involving of bigger parts of the community in their professional process operation methods and last but not least many voices from the community asking for more structure and clearness of the working processes, organizational responsibilities and stabilities, a restructure of the OOo QA project was needed.
To point a new start out on one hand and on the other hand keep the good and proven working processes in the project, the working title 'OOo QA Reloaded' was chosen as a project name, covering several sequencing actions. Under the following links you get the project papers and further info to this topic:
Introducing blog from Thorsten Ziehm (Manager of Sun StarOffice/OpenOffice.org QA Team)
Introducing blog from Chris Lukasiak (Member of Sun StarOffice/OpenOffice.org QA Team)
What QA Community wants (Graphic)
About one year of OOo QA Reloaded
OOo QA Reloaded: Internship Program
Autor: Christoph Lukasiak (Clu) 7 March 2007
Please do not change the logical content of this site without
acknowledge of the author or the OOo QA Project Lead/Co-Leads.
