(→Summary of Work: Taiga is dead) |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
* [[BaseRuntime/Development_and_Testing|Development and Testing]] | * [[BaseRuntime/Development_and_Testing|Development and Testing]] | ||
* [[BaseRuntime/Architecture|Architecture]] | * [[BaseRuntime/Architecture|Architecture]] | ||
* [[BaseRuntime/ | * [[BaseRuntime/Container_Base_Image|Container Base Image Definition]] | ||
* [[BaseRuntime/Fedora_26_MVP|Base Runtime Fedora 26 MVP]] | |||
== Background == | == Background == | ||
| Line 15: | Line 16: | ||
Besides the BaseRuntime module itself, the team is responsible for a number of additional low level modules that define the platform, such as software management and configuration tools or buildroots. | Besides the BaseRuntime module itself, the team is responsible for a number of additional low level modules that define the platform, such as software management and configuration tools or buildroots. | ||
== Presentations == | |||
* [https://psabata.fedorapeople.org/brt/presentation/Generational%20Core%20FOSDEM%202017%20presentation%20-%20February%204,%202017.pdf Generational Core] — Petr's FOSDEM 2017 presentation | |||
* [https://psabata.fedorapeople.org/brt/presentation/Generational%20Core%20DevConf%202017%20presentation%20-%20January%2027,%202017.pdf Generational Core] — Petr's DevConf.cz 2017 presentation | |||
== Blog Posts == | == Blog Posts == | ||
* Stephen's high-level overview of [https://communityblog.fedoraproject.org/base-runtime-generational-core/ Base Runtime and the Generational Core] | |||
* Stephen's introductory tutorial on [https://sgallagh.wordpress.com/2017/05/30/sausage-factory-an-introduction-to-building-modules-in-fedora/ Building modules in the Module Build Service] | |||
== Summary of Work == | == Summary of Work == | ||
The team's currently working on the first prototype of the BaseRuntime module, creating a self-hosted module that would later be minimized and split into multiple pieces as necessary. | The team's currently working on the first prototype of the BaseRuntime module, creating a self-hosted module that would later be minimized and split into multiple pieces as necessary. | ||
== Get Involved == | == Get Involved == | ||
Latest revision as of 10:46, 30 June 2017
Summary
A project closely linked to the Modularity Initiative, BaseRuntime is about the defining the common shared package and feature set of the operating system, providing both the hardware enablement layer and the minimal application runtime environment other modules can build upon. Besides the BaseRuntime module itself, the project also focuses on delivery of additional low-level modular content, such as distribution management and configuration utilities, basic system services or infrastructure build environments.
BaseRuntime subsections
- FAQ
- Getting Started
- Development and Testing
- Architecture
- Container Base Image Definition
- Base Runtime Fedora 26 MVP
Background
With the Modularity infrastructure gradually becoming available, it is time to focus on the modular content as well. The goal of the BaseRuntime project is to define the minimal shared core of the operating system that would light up the hardware (where applicable) and provide runtime environment for other, more complex and feature-rich modules. The idea is to deliver this functionality as a set of modules or a module stack.
Besides the BaseRuntime module itself, the team is responsible for a number of additional low level modules that define the platform, such as software management and configuration tools or buildroots.
Presentations
- Generational Core — Petr's FOSDEM 2017 presentation
- Generational Core — Petr's DevConf.cz 2017 presentation
Blog Posts
- Stephen's high-level overview of Base Runtime and the Generational Core
- Stephen's introductory tutorial on Building modules in the Module Build Service
Summary of Work
The team's currently working on the first prototype of the BaseRuntime module, creating a self-hosted module that would later be minimized and split into multiple pieces as necessary.
Get Involved
See Modularity WG.
Get in touch with us on the devel mailing list and our IRC channel, #fedora-modularity.