From Fedora Project Wiki
Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

Objective: Fedora Modularization, Prototype Phase

Also known as: the Let's Get Real Phase, or, Less Talk, More... Modules

Goal

The goal of this phase is to deliver a functional implementation of modular Fedora. We will be able to create, demonstrate, and deploy Fedora-based solutions made from independent modules which can move at their own paces yet still be trusted to work together and to be kept secure.

Logic Model

The basic idea: planning flows from right to left, and actual effort back from left to right. To the left of the double line is stuff we can actually do; to the right of that line, stuff we expect to be true as a result. See this blog post for more on this planning tool.


Modularization-phase3-logicmodel-v3-20160309.png

Todo: expand Activities, fill out Resources

More Details

See Modularization for background and oh so many details.

Deliverables

(outputs go here; connect to outcomes)

New Charter for Working Groups

(preamble)

Base Working Group

(describe)

  • Define the base / core module
  • Develop a fedora minimal spin?
    • as a way to provide a goal
    • container
    • bootable
    • ongoing maintenance of this
  • Maximum size of base is 50mb (semi-arbitrary target) -- “because reasons!”
    • 50mb installed size
    • Requires dependency minimization work to be done across the package set
    • Constant vigilance against dependency creep
  • Members? TBD

Some specifics:

  1. Create pagure repo for experimentation with specs and rpms should
  2. COPR build repo
  3. Specific changes proposed to and ratified by FESCo (FPC?)
  4. Proven packagers to make changes to all affected packages in Rawhide
  5. Monitor changes to packages to ensure no “growth”


Environments and Stacks Working Group

(describe)


  • Change WG to require a member of Fedora Rel-Eng and Fedora Security Team
  • Phase 1 (3 months)
    • Figures out what a “module” actually is in practice
    • Required stakeholders
      • Fedora Release Engineering
      • Fedora Security Team
      • Base WG
    • Creates whatever tools needed to produce and use modules
      • using existing tooling and systems where possible
      • rely on Fedora Release Engineering for changes to infrastructure where required
      • Fedora Infrastructure may also need changes
    • Defines & creates demo modules other than base
  • Phase 2 (ongoing)
    • Defines guidelines for module definition
    • Defines guidelines for new technologies as they emerge
    • Approved and ratified by FeSCO

Objective Lead

Timeframe

History

(link to previous phases, note any big updates here)