Workstation/AtomicWorkstation/SIG/Notes: Difference between revisions

Revision as of 19:01, 19 February 2018

Notes from the call on Feb 19, 2018

Agenda: Workstation/AtomicWorkstation/SIG/Agenda

Participants:

Sanja Bonic
Owen Taylor
Matthias Clasen
Jeff Ligon
Jonathan Lebon
Suraj Narwade
Micah Abbott
Steve Milner
Kalev Lember
Allan Day

Topic: Meeting time and venue

Decision: Future meetings will be on irc, same time, bi-weekly. Well aim for 45 minutes since some of us have another meeting at 9:45
No recording, we'll take notes

Topic: Fedora 28 goals

The big feature in Fedora 28 will be rpm-ostree support in GNOME software
We'll also have proper website for FAW (as part of the Project Atomic website)
Future topic: release planning:
- how do we go from alpha to beta to final ?
- make sure we have a FAW release at GA time, not delayed
- how frequently do we want composes ?
- is there any form of gating for the images ?

In discussion around update frequency, Kalev points out that it would be good to synch the OSTree updates with package repo metadata updates. See this: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/MFXURKYAIMHU27JR36GENXLCKL2QML6R/

The experimental jigdo transport for rpm-ostree also came up in this discussion as a possible solution for 'split package version' situations. This is not aimed at F28 though, more likely F30.

Topic: Status of composes

Is there a person responsible for FAW composes in rel-eng ? Not particularly :-(
This page tracks it somewhat: https://www.happyassassin.net/nightlies.html - Workstation dvd-ostree on that page is the FAW installer image
Rawhide composes have not been working for quite some time, recently fixed: https://pagure.io/atomic-wg/issue/409
F27 composes have been happening though

In discussion of composes, the question of the two branches (f27 and updates) came up. The branches work slightly differently from the package repos of the same name: the f27 package repo is frozen in time, while the f27 branch in OSTree still moves forward, just at a more granular pace than updates (at least in theory, we were not exactly clear if any gating happens for this currently).

Future topic that came up here: How do we determine the package set ? Do we differentiate more from FAH or move closer to the regular workstation ? Installing default apps as flatpaks helps for this.

Topic: Status of Flatpaks from rpms in Fedora

Everything is lined up
New person on the rel-eng side is starting
Still a few weeks away from seeing the first flatpak produced in this way

Topic: Website

Currently here: http://new.projectatomic.io
Will have a section on FAW
Will replace www.projectatomic.io soon

Topic: Issue tracking

Currently, we have a very non-obvious pagure project for it
Owen suggests that we create an empty project for it. Atomic wg does that: https://pagure.io/atomic-wg/issues
Decision: we will do the same

@@ Line 7: / Line 7: @@
 * Owen Taylor
 * Matthias Clasen
-* Jeffro Ligon
+* Jeff Ligon
 * Jonathan Lebon
 * Suraj Narwade
 * Micah Abbott
-* Steve Milne
+* Steve Milner
 * Kalev Lember
 * Allan Day
@@ Line 21: / Line 21: @@
 ==== Topic: Fedora 28 goals ====
 * The big feature in Fedora 28 will be rpm-ostree support in GNOME software
-* We'll also have proper website for FAW (as part of the project atomic website)
+* We'll also have proper website for FAW (as part of the Project Atomic website)
 * '''Future topic:''' release planning:
 ** how do we go from alpha to beta to final ?
@@ Line 32: / Line 32: @@
 The experimental jigdo transport for rpm-ostree also came up in this discussion as a possible
-solution for 'spit package version' situations. This is not aimed at F28 though, more likely F30.
+solution for 'split package version' situations. This is not aimed at F28 though, more likely F30.
 ==== Topic: Status of composes ====

Search