From Fedora Project Wiki

(Add Release Checklist)
 
(39 intermediate revisions by 11 users not shown)
Line 9: Line 9:
  
 
* Get running with Fedora in the cloud here: [https://getfedora.org/en/cloud/download/ https://getfedora.org/en/cloud/download/]
 
* Get running with Fedora in the cloud here: [https://getfedora.org/en/cloud/download/ https://getfedora.org/en/cloud/download/]
* Pre-release software (alphas, betas) can be found at [https://getfedora.org/en/cloud/prerelease/ https://getfedora.org/en/cloud/prerelease/]
+
* Pre-release software (Rawhide) can be found in [https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Cloud/ Cloud Rawhide nightlies].
  
 
= Our Goals =
 
= Our Goals =
Line 34: Line 34:
  
 
Let's keep track of how things work here so that we can help integrate new folks more easily.
 
Let's keep track of how things work here so that we can help integrate new folks more easily.
 +
 +
[[Cloud/Release_Checklist |  Production Release Checklist ]]
  
 
[[Cloud/Atomic_Runbooks | Atomic SOPs and Runbooks]]
 
[[Cloud/Atomic_Runbooks | Atomic SOPs and Runbooks]]
 +
 +
[[Cloud/Atomic_2wk_Release_Criteria | Atomic 2 week Release Criteria]]
  
 
== RFCs ==
 
== RFCs ==
Line 47: Line 51:
 
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.
 
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, https://lists.fedoraproject.org/mailman/listinfo/cloud. Members also regularly are available in the <tt>#fedora-cloud</tt> IRC channel on FreeNode.
+
Our primary forum for discussion is the Cloud SIG mailing list, https://lists.fedoraproject.org/mailman/listinfo/cloud. Members also regularly are available in the <tt>#fedora-cloud</tt> IRC channel on libera.chat.
  
 
The Cloud SIG will work with other groups (Base WG, QA, Rel-eng, etc.) as needed to help deliver the final cloud products.
 
The Cloud SIG will work with other groups (Base WG, QA, Rel-eng, etc.) as needed to help deliver the final cloud products.
Line 57: Line 61:
 
== IRC ==
 
== IRC ==
  
<nowiki>#fedora-cloud</nowiki> on [https://freenode.net/ Freenode].
+
<nowiki>#fedora-cloud</nowiki> on [https://libera.chat/ 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.
  
== Points of Contact ==
+
General:
 +
* [[User:Walters | Colin Walters ]]
 +
* [[User:sinnykumari | Sinny Kumari ]] (Multi-Arch)
  
 
Testing:
 
Testing:
Line 67: Line 77:
 
* [[User:Sayan | sayan ]]
 
* [[User:Sayan | sayan ]]
 
* [[User:Roshi | roshi ]]
 
* [[User:Roshi | roshi ]]
 +
* [[User:davdunc | davdunc ]]
 +
* [[User:miabbott | miabbott ]]
 +
* [[User:sinnykumari | Sinny Kumari ]]
  
 
Release Engineering:
 
Release Engineering:
Line 81: Line 94:
 
== Meetings ==
 
== Meetings ==
  
The Fedora Cloud Working Group has a weekly meeting. The meeting usually happens in #fedora-meeting-1 on irc.freenode.net and the schedule for the meeting can be found here: https://apps.fedoraproject.org/calendar/cloud/
+
The Fedora Cloud Working Group has a weekly meeting. The meeting usually happens in fedora-meeting-1@irc.libera.chat and the schedule for the meeting can be found here: https://calendar.fedoraproject.org/cloud/
 +
 
 +
You can find Meeting Minutes on the [https://meetbot.fedoraproject.org/ 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 [https://calendar.fedoraproject.org/cloud/ Cloud Fedocal]. To subscribe to the calendar and receive changes automatically, you can import "From URL" in Google Calendar (and others) with this link: <code>https://calendar.fedoraproject.org//ical/cloud/</code>
 +
 
 +
=== Quorum Voting Policy ===
  
You can find Meeting Minutes on the [https://meetbot.fedoraproject.org/ Fedora møte: meeting wrangler]. Meetings are currently held every Wednesday at 17:00 UTC.
+
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 [[Cloud#Working_Group_Members_and_Points_of_Contact | 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 ===
 
=== Steps to run the meeting ===
  
* #startmeeting fedora_cloud_wg
+
* #startmeeting fedora_atomic_wg
 
* #topic Roll Call
 
* #topic Roll Call
  
Line 95: Line 116:
 
* #topic Action items from last meeting
 
* #topic Action items from last meeting
  
^^ Find the last meeting log from https://meetbot-raw.fedoraproject.org/teams/fedora_cloud_wg
+
^^ Find the last meeting log from https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg (cloud_wg_logs: https://meetbot-raw.fedoraproject.org/teams/fedora_cloud_wg)
  
* After they are done move to each ticket from https://fedorahosted.org/cloud/report/9
+
* After they are done move to each ticket from https://pagure.io/atomic-wg/issues?status=Open&tags=meeting
  
 
Do the following for each ticket
 
Do the following for each ticket
Line 108: Line 129:
  
 
* #endmeeting
 
* #endmeeting
 
 
=== Upcoming Meetings, Agendas, and Chairs ===
 
 
Ideally we should have an agenda prior to each meeting that consists of any urgent business, action items from the last meeting (carry over if not completed!), and Trac tickets marked with the "meeting" tag. ([https://fedorahosted.org/cloud/report/9 See the Meeting report in Trac].)
 
 
We need someone to chair the meeting each week, and it's a good idea to come prepared to run the meeting rather than playing "who's the chair this week?" To that end, here's a list of upcoming meetings. Please call a spot if you're interested in chairing:
 
 
* 20 April 2016: Chair - Josh Berkus
 
* 27 April 2016: Chair
 
* 4 May 2016: Chair - Scott Collier (scollier)
 
* 11 May 2016: Chair - Josh Berkus
 
* 18 May 2016: Chair
 
* 25 May 2016: Chair - Scott Collier (scollier)
 
* 01 June 2016: Chair -
 
* 08 June 2016: Chair - Joe Brockmeier (jzb)
 
* 15 June 2016: Chair - Sayan Chowdhury (sayanchowdhury)
 
* 22 June 2016: Chair - Joe Brockmeier (jzb)
 
* 29 June 2016: Chair - Sayan Chowdhury (sayanchowdhury)
 
* 06 July 2016: Chair - Dusty Mabe (dustymabe)
 
* 13 July 2016: Chair - Josh Berkus (jberkus)
 
* 20 July 2016: Chair -
 
* 27 July 2016: Chair - Josh Berkus (jberkus)
 
* 03 Aug 2016: NO MEETING - FLOCK CONFERENCE
 
* 10 Aug 2016: Chair - Scott Collier (scollier)
 
* 17 Aug 2016: Chair -
 
* 24 Aug 2016: Chair -
 
 
== Physical Meetings ==
 
 
[[Cloud SIG Meeting - Flock 2015 - 14 August 2015 - Rochester]]
 
 
[[Category:Cloud]]
 
[[Category:Cloud SIG]]
 

Latest revision as of 15:51, 3 February 2022

The Fedora Cloud Special Interest Group


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 Working group leads the design and production of Fedora's Cloud edition.

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

Cloud/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

Atomic SOPs and Runbooks

Atomic 2 week Release Criteria

RFCs

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

RFC: Rebuild Policy for Fedora Docker Trusted Images

Communications

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, https://lists.fedoraproject.org/mailman/listinfo/cloud. Members also regularly are available in the #fedora-cloud IRC channel on libera.chat.

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

https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org/

IRC

#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.

General:

Testing:

Release Engineering:

Documentation/Marketing:

Meetings

The Fedora Cloud Working Group has a weekly meeting. The meeting usually happens in fedora-meeting-1@irc.libera.chat and the schedule for the meeting can be found here: https://calendar.fedoraproject.org/cloud/

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: https://calendar.fedoraproject.org//ical/cloud/

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 https://meetbot-raw.fedoraproject.org/teams/fedora_atomic_wg (cloud_wg_logs: https://meetbot-raw.fedoraproject.org/teams/fedora_cloud_wg)

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