From Fedora Project Wiki

No edit summary
Line 55: Line 55:
=== Tooling Prototypes ===
=== Tooling Prototypes ===

* [[Modularity_Working_Group/prototype|pungi]] protoype for modularity - For building composes
* [[Modularity_Working_Group/prototype/pungi|pungi]] protoype for modularity - For building composes
* [[Modularity_Working_Group/prototype|productmd]] protoype for modularity - Compose metadata
* [[Modularity_Working_Group/prototype/productmd|productmd]] protoype for modularity - Compose metadata

=== Status Reports ===
=== Status Reports ===

Revision as of 14:27, 6 April 2016

  • Mailing list: Use the main Fedora Devel, prefixing subject lines with [Modularity]
  • IRC:


  • The Modularity Working Group meets weekly on ? in #fedora-meeting. The meetings are at ??:00 UTC on odd weeks and at ?:00 UTC on even weeks. To get the time for your time zone, use date -d "??:00 UTC" and to get the week number, use date +"%V" .
  • [meeting logs]


  • TBD
  • TBD
  • TBD

This is the home for the Modularity Working Group...

Mission Statement

The goal of the Modularity Working Group is to define and maintain the Fedora Base Module and guidelines and tools for other modules.

This includes releasing the Fedora Base Module in artifact form on a regular schedule — as a Docker base image, as an installable minimal system, and possibly in other ways in the future. This will not be a Fedora Edition, but rather be the thing people constructing custom versions of Fedora can start from — including both advanced end-users and Fedora Spins and Editions. (See interesting background discussion on the Fedora Server mailing list.)

So that modules are useful in the greatest number of situations, are fast to create and to deploy, and have the smallest possible security footprint, the Modularity Working Group will reduce package dependency trees, particularly in the Fedora Base Module.

The Working Group will also produce tooling for module production and maintenance, and guidelines for modules, as the FPC does for RPMs.

The effort will also require help and resources from across Fedora, including Fedora Infrastructure, Release Engineering, QA, Security Team, and more. Representatives of those groups should be included on the new Working Group. Also, proven packagers working as part of this effort will institute weak dependencies in a systematic manner, in cooperation with package maintainers.


Documents and Stuff

See Modularization

How to Get Involved


If you are interested in joining the working group, see Modularity_Working_Group/Initial_Nominations (open until April 18).

We are still working through this, however, if you would like to see where we are or add user stories or issues please check out the Planning page.

IRC Channel: #fedora-modularization

Tooling Prototypes

  • pungi protoype for modularity - For building composes
  • productmd protoype for modularity - Compose metadata

Status Reports

Helpful Information

Commands for chairing a meeting

#startmeeting Modularity (2023-12-14)
#meetingname modularity
#chair .....
#topic Welcomes and Hellos
#topic ...

Don't forget to use #info, #agreed, #link, #idea, #action or other commands often for better meeting minutes. Introduction might be done by .hellomynameis mynick.