For Regularly Scheduled Meetings

Oct 13, 2025 by magicalceylontours.com 85 views

Meeting Notes

The Fedora CoreOS (FCOS) meeting is held every week on Wednesdays at 16:30 UTC. The meeting is held in the #meeting-1:fedoraproject.org channel on Matrix. The meeting is logged, and the logs are available on the Meetbot website.

Required Concepts

Voting

On some topics, we will need to vote. The following rules apply to the voting process:

A quorum for the meeting is 5 people, or 51% of the members of the WG listed below, whichever is lower.
Voting items must pass with a majority of the members voting at the meeting.

Working Group Members and Points of Contact

Please see the meeting-people.txt file for a list of working group members and points of contact.

Meeting Host Requirements

The meeting host needs to have a Matrix account (an example is an account on the Fedora Matrix Server). The host needs to have access to the following channels on Matrix:

#coreos:fedoraproject.org
#meeting-1:fedoraproject.org

The host needs to have a Fedora account and be able to post discussion topics to the Fedora Project.

For Regularly Scheduled Meetings

A quorum for the meeting is 5 people, or 51% of the members of the WG listed below, whichever is lower. Voting items must pass with a majority of the members voting at the meeting.

For General Ad-Hoc Votes

All ad-hoc votes will be held via tracker issues.
Ad-hoc votes must be announced on the current primary mailing list for Fedora Atomic (atomic-devel).
Ad-hoc votes must be open for at least three working days (see below) after the announcement.

At least 5 people must vote, or 51% of the WG membership, whichever is less. Votes are "+1" (in favor), "-1" (against), or +0 (abstain). Votes pass by a simple majority of those voting.

For Urgent Ad-Hoc Votes

All ad-hoc votes will be held via tracker issues in the fedora-coreos-tracker repository.
Ad-hoc votes must be announced on the current primary mailing list for Fedora CoreOS.
Ad-hoc votes must be open for at least three hours after the announcement.

At least 5 people must vote, or 51% of the WG membership, whichever is less. Votes are "+1" (in favor), "-1" (against), or +0 (abstain). Votes pass by a 2/3 majority of those voting (round up).

Meeting Steps

Join the #meeting-1:fedoraproject.org channel on Matrix and copy the following commands:
- !startmeeting fedora_coreos_meeting
- !topic roll call
Switch to the #coreos:fedoraproject.org channel on Matrix and post the following notification:

@aaradhak:matrix.org @apiaseck:matrix.org @bri:transfem.dev @davdunc:fedora.im @dustymabe:matrix.org @guidon:guidon.ems.host @gurssing:matrix.org @jaimelm:fedora.im @jbtrystram:matrix.org @jbrooks:matrix.org @jdoss:fedora.im @jlebon:fedora.im @jmarrero:matrix.org @lorbus:matrix.org @marmijo:fedora.im @miabbott:fedora.im @quentin9696:matrix.org @ravanelli:fedora.im @walters:fedora.im @ydesouza:fedora.im @yves:siegrist.io

FCOS community meeting in #meeting-1:fedoraproject.org If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt

3.  Switch back to the `#meeting-1:fedoraproject.org` channel and wait for people to join.
4.  After 2-4 minutes pass, start the action items from the last meeting:
    *   `!topic Action items from last meeting`
    *   `Failed: to get action items, check the last meeting notes.`
5.  Discuss the current Fedora Release Schedule to see if any actions need to be addressed:
    *   `!topic Review Fedora 42 Release Schedule`
    *   `!link https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html`
6.  After the action items are covered, start the topics from the tracker:
    *   Cover the below topics from the tracker repository:
    *   `!topic tracker: F42 Test Week`
    *   `!link https://github.com/coreos/fedora-coreos-tracker/issues/1885`
7.  Once all the topics are covered, start the open floor:
    *   `!topic Open Floor`
8.  Once the time limit is reached or the open floor is quiet, end the meeting:
    *   `!endmeeting`

**Housekeeping**
--------------

1.  Navigate to the [tickets that were discussed](https://github.com/coreos/fedora-coreos-tracker/labels/meeting) and remove the `meeting` label.
2.  Add any relevant information to the ticket.
3.  Email a meeting summary to the following addresses:
    *   `coreos@lists.fedoraproject.org`
    *   `devel@lists.fedoraproject.org`
    The subject of the email should be `Fedora CoreOS Community Meeting Minutes YYYY-MM-DD`. The body of the email should include the following:
    *   A header with the following information:
        ```text
Minutes: <this-meetings-notes>.html
Minutes (text): <this-meetings-notes>.txt
Log: <this-meetings-notes>.log.html

*   A body with the contents of the `<this-meetings-notes>.txt` file.

Post to the Fedora Project with the following information:
- Subject: Fedora CoreOS Community Meeting Minutes YYYY-MM-DD
- Category: Project Discussion
- Tags: coreos-wg
- Body: Copy and paste the output of the fcosmeetinghtml command.

fcosmeetinghtml Command

The fcosmeetinghtml command is used to generate the meeting summary. The command takes the summary URL as an argument and generates the meeting summary in HTML format. The command can be used as follows:

fcosmeetinghtml <this-meetings-notes>.html

Q: What is the purpose of the FCOS meeting?

A: The purpose of the FCOS meeting is to discuss and decide on various topics related to the Fedora CoreOS project. The meeting is held every week on Wednesdays at 16:30 UTC.

Q: Where is the FCOS meeting held?

A: The FCOS meeting is held in the #meeting-1:fedoraproject.org channel on Matrix.

Q: Who is required to attend the FCOS meeting?

A: All members of the Fedora CoreOS working group are required to attend the meeting. However, anyone interested in participating in the discussion is also welcome to join.

Q: What is the quorum for the FCOS meeting?

A: A quorum for the meeting is 5 people, or 51% of the members of the WG listed below, whichever is lower.

Q: How are votes cast in the FCOS meeting?

A: Votes are cast by typing "+1" (in favor), "-1" (against), or +0 (abstain) in the chat window.

Q: What is the voting process for ad-hoc votes?

A: Ad-hoc votes are held via tracker issues in the fedora-coreos-tracker repository. The vote must be announced on the current primary mailing list for Fedora Atomic (atomic-devel) and must be open for at least three working days after the announcement.

Q: What is the voting process for urgent ad-hoc votes?

A: Urgent ad-hoc votes are held via tracker issues in the fedora-coreos-tracker repository. The vote must be announced on the current primary mailing list for Fedora CoreOS and must be open for at least three hours after the announcement.

Q: How do I join the FCOS meeting?

A: To join the FCOS meeting, simply log in to the #meeting-1:fedoraproject.org channel on Matrix and type !startmeeting fedora_coreos_meeting.

Q: What is the format of the FCOS meeting?

A: The format of the FCOS meeting is as follows:

Join the #meeting-1:fedoraproject.org channel on Matrix and copy the following commands:
- !startmeeting fedora_coreos_meeting
- !topic roll call
Switch to the #coreos:fedoraproject.org channel on Matrix and post the following notification:

FCOS community meeting in #meeting-1:fedoraproject.org If you don't want to be pinged remove your name from this file: https://github.com/coreos/fedora-coreos-tracker/blob/main/meeting-people.txt

3.  Switch back to the `#meeting-1:fedoraproject.org` channel and wait for people to join.
4.  After 2-4 minutes pass, start the action items from the last meeting:
    *   `!topic Action items from last meeting`
    *   `Failed: to get action items, check the last meeting notes.`
5.  Discuss the current Fedora Release Schedule to see if any actions need to be addressed:
    *   `!topic Review Fedora 42 Release Schedule`
    *   `!link https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html`
6.  After the action items are covered, start the topics from the tracker:
    *   Cover the below topics from the tracker repository:
    *   `!topic tracker: F42 Test Week`
    *   `!link https://github.com/coreos/fedora-coreos-tracker/issues/1885`
7.  Once all the topics are covered, start the open floor:
    *   `!topic Open Floor`
8.  Once the time limit is reached or the open floor is quiet, end the meeting:
    *   `!endmeeting`

**Q: What is the purpose of the housekeeping tasks?**
---------------------------------------------------

A: The housekeeping tasks are performed after the meeting to ensure that all necessary steps are taken to document the meeting and follow up on any action items.

**Q: How do I perform the housekeeping tasks?**
------------------------------------------------

A: To perform the housekeeping tasks, follow these steps:

1.  Navigate to the [tickets that were discussed](https://github.com/coreos/fedora-coreos-tracker/labels/meeting) and remove the `meeting` label.
2.  Add any relevant information to the ticket.
3.  Email a meeting summary to the following addresses:
    *   `coreos@lists.fedoraproject.org`
    *   `devel@lists.fedoraproject.org`
    The subject of the email should be `Fedora CoreOS Community Meeting Minutes YYYY-MM-DD`. The body of the email should include the following:
    *   A header with the following information:
        ```text
Minutes: <this-meetings-notes>.html
Minutes (text): <this-meetings-notes>.txt
Log: <this-meetings-notes>.log.html

*   A body with the contents of the `<this-meetings-notes>.txt` file.

Post to the Fedora Project with the following information:
- Subject: Fedora CoreOS Community Meeting Minutes YYYY-MM-DD
- Category: Project Discussion
- Tags: coreos-wg
- Body: Copy and paste the output of the fcosmeetinghtml command.

Q: What is the `fcosmeetinghtml` command?

A: The fcosmeetinghtml command is used to generate the meeting summary. The command takes the summary URL as an argument and generates the meeting summary in HTML format. The command can be used as follows:

fcosmeetinghtml <this-meetings-notes>.html

The output of the command should be copied and pasted into the post body.