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 discourse 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.
Future Link to download page
- main mailing list: coreos@lists.fedoraproject.org
- status mailing list: coreos-status@lists.fedoraproject.org (announcements/important messages)
- #fedora-coreos on IRC (Freenode)
- forum at https://discussion.fedoraproject.org/c/coreos
- feature planning and important issue tracking at github.com/coreos/fedora-coreos-tracker
- website at https://coreos.fedoraproject.org/
- Twitter: @coreos (specific to CoreOS and containers) and [@fedora](https://twitter.com/fedora] (all Fedora and other relevant news)
The Fedora CoreOS 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/CoreOS Currently, meetings are at 16:30 UTC on Wednesdays.
- Navigate to #fedora-meeting-1 on freenode
- Type
#startmeeting fedora_coreos_meeting - #topic roll call
Wait for 2-4 minutes for people to check in for the roll call.
- #chair all the people present for the meeting
- #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
- #topic Ticket subject
- #link link_to_the_ticket
When all the tickets are over, go for Open floor
- #topic Open Floor
After open floor, end the meeting.
- #endmeeting
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.
TBD