Modularity

    • What is Modularity:
    • Quick Introduction
    • Architecture
      • Building Software
      • Consuming Software
      • Stream Expansion
      • Upgrade Paths
    • Basic usage:
    • Using Modules
      • Installation and Discovery
      • Switching Streams
    • Making Modules — Guides
      • Adding New Modules
      • Updating Existing Modules
      • Defining Modules in modulemd
      • Building Modules
      • Managing Defaults
      • Inspecting Build Failures
      • Building Modules Locally
    • Making Modules — Policies
      • Packaging Policy
      • Naming Policy
    • Reporting Module Bugs
    • FAQ
    • Advanced:
    • Creating Modular Repositories
    • Using Other Build Systems
    • NSVCA (Module ID)
      • Version Prefix
      • NSVCA Definition
    • Community:
    • Communication
    • Teams and Working Groups
    • Project Tracking
    • Reporting Project Issues
    • Other:
    • References
    • Archive
      • DNF Behavior
Modularity master
  • Modularity
    • master
  • Home
  • Modularity
  • Teams and Working Groups
en English
Edit this Page

Working Groups and Teams

Modularity is driven by the Modularity Working Group

However, Modularity couldn’t happen without other working groups contributing a significant portion of effort into it, i.e.:

  • Server Working Group

  • Fedora Release Engineering

  • Fedora Infrastructure

Want to help? Learn how to contribute to Fedora Docs.

All Fedora Documentation content available under CC-BY-SA 3.0 or, when specifically noted, under another accepted free and open content license.

Last build: