Project's ROADMAP
WARNING: This document is only a draft and as such far from being complete. All informations described here are subject to change anytime.
The project will be cut in the four phases described below.
Conception
The first part is to write conception documents about how the system work, both at a high-level (concepts, features, native applications etc.) and low-level (processes management, kernel design...).
This project is currently in this state.
Validation
Once all conception documents are ready, they will be validated one by one, and frozen. Breaking changes after validation are still possible but should be avoided as much as possible.
Implementation
Once all documents have been validated, the different project's pieces can be implemented.
It may happen that, during implementation, some validated documents get modifications in order to improve or fix some specific points. Each modification will need to be validated in order to preserve the stability of these documents.
Below are described the different phases of the implementation.
Phase 1: Unoptimized kernel
The first piece to be implemented will be the kernel. This is required as the kernel is needed in order to implement higher-level pieces like processes. Still, as not everything is needed right from the start, it will developed with no special matter of performances. In this state, it will be referred to as the name of unoptimized kernel.
Phase 2: Low-level implementation
Once the unoptimized kernel is ready, two implementations will start in parallel:
- Kernel optimization (as the unoptimized kernel will be really, really slow)
- System development
The system development will consist in building the following pieces successively:
- The BIOS/UEFI bootloader
- The system bootloader
- The process manager
- The native process manager
Phase 3: Applications & System optimization
The third phase consists in developing the native applications, which are meant to be used by the end user, as well as optimizing the system in parallel and improving its stability.
Starting from this point, all conception documents are definitively validated, which means they cannot receive breaking changes anymore, only new points/features.
This also coincides with the system's first alpha release, which will allow persons who are external to the project to test it and suggest improvements.
Phase 4: Completion
The last phase's purpose is to ensure the system is in a fully usable state, in other words to stabilize it.
The kernel and system will also need to be properly optimized, and once all these things are done a first beta release will be deployed.
Evolution, Optimization & Maintenance
The Evolution, Optimization & Maintenance (EPM) part is pretty explicit: it's all about improving NightOS' existing features, introducing new ones as needed, improving performances and stability, and fixing new bugs.
This part will last forever, as for all operating systems - or until the project dies.