Welcome to the Fedora CoreOS issue tracker. This tracker will be used
to discuss new features for Fedora CoreOS and also important bugs that
are affecting the project. Tickets with the meeting label will be
taken as agenda items during the meetings. This repo is to be used primarily
for development purposes. If you are a user and have questions please use
the forum or the mailing list.
Fedora CoreOS is an automatically updating, minimal, monolithic, container-focused operating system, designed for clusters but also operable standalone, optimized for Kubernetes but also great without it. It aims to combine the best of both CoreOS Container Linux and Fedora Atomic Host, integrating technology like Ignition from Container Linux with rpm-ostree and SELinux hardening from Project Atomic. Its goal is to provide the best container host to run containerized workloads securely and at scale.
The Fedora CoreOS Working Group works to bring together the various technologies and produce Fedora CoreOS.
- Main mailing list: [email protected]
- Status mailing list: [email protected] (announcements/important messages)
- Chat room:
#coreos:fedoraproject.orgon Matrix - Forum at https://discussion.fedoraproject.org/tag/coreos
- Feature planning and important issue tracking at github.com/coreos/fedora-coreos-tracker
- Website at https://getfedora.org/coreos/
- Documentation at https://docs.fedoraproject.org/en-US/fedora-coreos/
- Twitter: @fedoracoreos
Fedora CoreOS is available for general use and no longer in preview. We're continuing to add more platforms and functionality, fix bugs, and write documentation. Please try out Fedora CoreOS and give us feedback!
We often find people asking for a particular package to be added to the base set of packages included in Fedora CoreOS. One of the goals of Fedora CoreOS is to remain as lean as possible, without impacting overall usability for our users. Thus, new package requests are carefully scrutinized to weigh the benefits and drawbacks of adding an additional package.
If you would like to propose the inclusion of a new package in the base set of packages, please file a new package request.
See RELEASES.md.
The Fedora CoreOS Working Group has a weekly meeting. The meeting usually
happens in
#meeting-1:fedoraproject.org
on Matrix and the schedule for the meeting can be found here:
https://calendar.fedoraproject.org/CoreOS/ Currently, meetings are at
16:30 UTC on Wednesdays.
As the Matrix bridge to Libera Chat is shutdown, you can not attend the meeting from IRC and you have to join using Matrix.
The fedora meeting host can follow the guide which is curated by the fcos-meeting-action repo. Every Wednesday a new checklist will be available in the form of a issue in the fcos-meeting-action repo, which can be used to run the meeting.
If the action meeting repo is not available for some reason, the host can follow the below steps to run the meeting.
Legacy Meeting steps
cdto a local checkout of this repo andgit pull- Ping meeting people in
#fedora-coreoson libera.chatbash meeting-people.txt- copy lines of output and paste into
#coreos:fedoraproject.orgon Matrix
- Navigate to
#meeting-1:fedoraproject.orgon Matrix - Type:
!startmeeting fedora_coreos_meeting!topic roll call
Wait for 2-4 minutes for people to check in for the roll call.
!topic Action items from last meeting
Find the last meeting log from meetbot and post the action items in the meeting for people to update the status of.
- After they are done move to each
meetingticket from this tracker
Do the following for each ticket
!topicTicket subject!link <link_to_the_ticket>
During the meeting, you can give people action items for them to complete:
!action <nickname>description of what needs to be done
When all topics are over, go for open floor:
!topic Open Floor
After open floor, end the meeting.
!endmeeting
Then, when convenient:
-
Remove
meetinglabels from tickets that were discussed -
Send an email to [email protected] with the details of the meeting from meetbot page. Minutes in textual format are directly available using
.txtas URL extension. It's easiest to get the Minutes/Minutes (text)/Log URLs by copying the footer that Meetbot prints after#endmeeting. You can see examples in the archives; the usual format follows:
Subject: Fedora CoreOS Meeting Minutes year-mm-dd
Body:
Minutes: <URL to meetbot .html>
Minutes (text): <URL to meetbot .txt>
Log: <URL to meetbot .log.html>
<Copy/paste content of meetbot .txt>
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, which ever is lower. Voting items must pass with a majority of the members voting at the meeting.
- 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.
- All ad-hoc votes will be held via tracker issues in the fedora-coreos-tracker repo.
- 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).
Working days: non-holiday weekdays. Relevant holidays are the national holidays of the USA, Western Europe, and India.
Please see meeting-people.txt.