From Fedora Project Wiki

Revision as of 21:03, 1 November 2022 by Davdunc (talk | contribs) (→‎Quick Links: Add a link to the Cloud Sig)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This is the home for the Fedora Cloud Working Group, where we are developing Fedora's next-generation cloud product. You may also be interested in the Cloud SIG, which has a broader, more loosely defined mission covering all things related to Fedora and cloud computing.

Fedora Cloud Working Group

Quick Links

Our Goals

The Fedora Cloud Edition allows users to work across multiple virtual environments at scale by focusing engineering efforts on supplying a base disk images, rpms, and container-based tooling of various architectures for working in and around public and private cloud environments. The Cloud Edition Working Group targets efforts towards the facilitation and improvement of continuous delivery by ensuring that Fedora project solutions support cloud native workflow without forcing users to understand all of the environments in which they require enablement.

Role in Fedora

The Fedora Cloud Working Group is a subset of the Fedora Cloud SIG, one of the many teams working on Fedora.

The Working Group is responsible for initial and ongoing development of the Product Requirements Document, and for coordinating production of the Fedora Cloud operating system.

We work with existing groups across the greater Fedora Project, and may delegate particular members to take responsibility for working with certain other teams. For example, a working group member may act as a coordinator for quality assurance or for release engineering.

Charter / Governance


Product Requirements Document

Cloud PRD

Runbooks / Standard Operating Procedures

Let's keep track of how things work here so that we can help integrate new folks more easily.

Production Release Checklist


This section lists the RFCs in progress or RFCs that have been accepted by the Cloud Working Group.

RFCs for Review

RFCs Recently Accepted

Guidelines for Changing Fedora Cloud Images


It is our policy to default to open; wherever possible, all communications will be held in the open and archived for future public reference. In some rare cases, it may necessary for some members of the group to enter into non-disclosure agreements (for example, when working with public cloud vendors) but such circumstances should be minimal and not impact core decisions of the group.

Our primary forum for discussion is the Cloud SIG mailing list, Members also regularly are available in the #fedora-cloud IRC channel on

The Cloud SIG will work with other groups (Base WG, QA, Rel-eng, etc.) as needed to help deliver the final cloud products.

Mailing List

Real-time Communications

Matrix on


#fedora-cloud on Libera.Chat.

Working Group Members and Points of Contact

At a later date we will likely establish a formal on-boarding process for new community members but at this time if you're interested in joining, simply add your name below either in the "General" section or under a specific sub topic and then reach out via the irc channel and mailing list to introduce yourself.



Release Engineering:



The Fedora Cloud Working Group has a weekly meeting. The meeting usually happens in and the schedule for the meeting can be found here:

You can find Meeting Minutes on the Fedora møte: meeting wrangler. Meetings are currently held every other Thursday at 14:00 UTC.

Upcoming Meetings

Meetings are announced on the Cloud SIG mailing list. The Fedora Cloud SIG and Working Group meeting schedule is also found on the Cloud Fedocal. To subscribe to the calendar and receive changes automatically, you can import "From URL" in Google Calendar (and others) with this link:

Quorum Voting Policy

At minimum 51% of the voting members of the Atomic WG must be in attendance in order to make decisions on meeting items. The definition of voting members is that of those who have self identified themselves as participants of the Working Group by adding their name here. A quorum vote is required to approve a decision on behalf of the working group, not simply the majority vote of those in attendance of any particular meeting.

Steps to run the meeting

  • #startmeeting fedora_atomic_wg
  • #topic Roll Call

Wait for 2 minutes for the roll call.

  • #chair all the people present for the meeting
  • #topic Action items from last meeting

^^ Find the last meeting log from (cloud_wg_logs:

Do the following for each ticket

  • #topic Ticket subject link_to_the_ticket

When all the tickets are over, go for Open floor

  • #topic Open Floor
  • #endmeeting