Implementation process
Development policies
Communication
FIXME
- decisions
- project modifications: APIs, documentations, teams, ...
- medias: IRC, mail, mailing-lists, web site, ...
Code conventions
Design by contract
FIXME
In debugging mode, always assert the contract.
Code indentation
FIXME
Language specific notes
C
FIXME
Function names are lower case.
Validation process
Make it just work
Audit
Optimize
Audit
Think about possible features
If globally accepted, add selected features
Audit
Development tasks
It seems reasonable, if not obvious, to determine independant tasks within the huge work described before in this document. There follows a proposal.
Global tasks
Communication
Project frontmatter
The project main access is its web site, hosted at http://www.defora.org/ . Its content management system is nearly finished, and will allow desiring members to contribute to its maintainance. The rules for membership and privileged access will be available when the portal is ready.
Important announces and debates
Though it has not been setup yet, one or more mailing-lists will be available. Their use is dedicated to announces and discussions, that deserve to be read by their subscribers. They will be archived on the project website. Please use the IRC channel below, until a list has been setup.
General discussions
An IRC channel has been registered on the freenode network: #DeforaOS. This channel is dedicated to discussions related to the DeforaOS system. The preferred language is english, and the preferred charset is either ISO-8859-1 or ISO-8859-15. The rules are basically to be social, there won't be any moderation unless complaints are filed to the project appropriate members, say the mailing-list as a start.
Programming interfaces
The common APIs have to be decided and accepted by the project members, at the appreciation of the project leader. They are then presented in this reference paper.
Cooperation tasks
Documentations
FIXME
Low-level applications
Assembler
FIXME
C compiler
FIXME
Micro-kernel
FIXME
C library
FIXME
System applications
General purpose services
These applications only require their application engines. For an easy and safe configuration, or monitoring, they may provide user interfaces though.
Text mode toolkit
FIXME
End-user applications
Every application that fits on a desktop: file browser, web browser, mail and news reader, messaging application, images viewer, audio and video viewer, and optionaly games, etc.
Graphics
Graphical server
FIXME
Graphical mode toolkit
FIXME
Services
General purpose daemons
FIXME
Networking daemons
FIXME
User interfaces
The only essential part of these services is their application engines.
POSIX environment
At the moment it is not yet known if the system will be based on, or provide a native POSIX development environment.
It may be possible to write an application engine providing the POSIX system and library calls, on which the POSIX utilities would connect as usual application interfaces. We could even imagine them with a graphical interface, which would fallback as the regular UNIX commands if the graphical toolkit is denied (using stdin, stdout and stderr as usual).