FAQ development
From Wiki.ooo4kids.org
How is the project developed?
Who supplies the source code of OOo4Kids?
OOo4Kids uses the same source as OpenOffice.org, with changes, while respecting the license associated with OpenOffice.org. So it is a derivative software, also called fork of OpenOffice.org software. This fork is also called "friendly" because the compatibility between licenses is guaranteed (both use the LGPL v3).
OOo4Kids is based on the source code for OpenOffice.org, but what version?
- Source code base: OOO320_m12 for version 1.x and version 2.x for DEV300_mxxx or higher
- Tools used by OpenOffice.org: subversion (3.2.0 branch) and mercurial (DEV300 branch)
- Tools used by OOo4Kids: subversion (version 1.x) and git (for version 2.x and higher)
What tools are used to manage the source code of OOo4Kids?
Compilable on Windows XP (mini), Mac OS X (10.4 mini) Intel and PowerPC, Linux: all architectures (. Deb,. Rpm. Fart. Tar.gz) + development tools associated
Is it possible to consult the source code of OOo4Kids online?
Sites:
- Forge: Adullact
- Project monitoring: Oloh
- Latest commits: CIA.vc OOo4Kids
- Retrieve a given change in the code: Type in a terminal, the command svn diff-c {revision } svn://svn.adullact.net/svnroot/ooo4kids1/trunk
Example, to display the "changeset" between R468 and R469 review, type in a terminal the following command:
svn diff -C469 svn://svn.adullact.net/svnroot/ooo4kids1/trunk
OOo4Kids it follows a quality assurance process?
There is no quality assurance OOo4Kids but beta testers and continuous development punctuated by milestones.
