January 2018 - Atomic Working Group (ARCHIVED)

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 09 Jan '18

09 Jan '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-01-10 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.or… Source: https://apps.fedoraproject.org/calendar/meeting/6952/

1 0

[atomic-wg] Issue #356: Article For F27: Fedora 27 Atomic Features
by Josh Berkus 09 Jan '18

09 Jan '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Article Title: Fedora 27 Atomic Feature Roundup Deadline: October 30 Priority: Normal Publication: Fedora Community Blog This should be a round-up of the features in Fedora 27 Atomic, for a general audience that hasn't followed Atomic for the last 6 months. Should cover features from the talking points briefly and link off to other articles. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/356

2 5

[atomic-wg] Issue #357: Article for F27: Updated Installing Kubernetes Doc
by Josh Berkus 09 Jan '18

09 Jan '18

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Title: Installing Kubernetes on Fedora 27 Atomic Deadline: November 15 Publication: Project Atomic Blog, Docs Priority: Low This should be based on the F26 article from Jason Brooks, updated to show the correct options and terminal sessions for F27. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/357

3 3

[fedora-atomic] PR #102: Use boot_location: new
by Colin Walters 08 Jan '18

08 Jan '18

walters opened a new pull-request against the project: `fedora-atomic` that you are following: `` Use boot_location: new `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/102

2 2

[fedora-atomic] Issue #94: Migrate to boot_location: new
by Colin Walters 08 Jan '18

08 Jan '18

walters reported a new issue against the project: `fedora-atomic` that you are following: `` See https://github.com/projectatomic/rpm-ostree/pull/959#issuecomment-325780234 Right now we have: ``` [root@localhost ~]# ostree ls -R -X -C fedora-atomic:fedora/27/x86_64/atomic-host /boot|grep initramfs -00600 0 0 52565370 7e6c941d0eefc5760917b300bade10e107d99c89fd0f627b7d9e1cf03068b9bd { [(b'security.selinux', b'system_u:object_r:boot_t:s0')] } /boot/initramfs-4.13.9-300.fc27.x86_64.img-850b4ded439b2151106725e7b522d8485d312c9ed80aee65c818c9f99c2c1701 [root@localhost ~]# ostree ls -R -X -C fedora-atomic:fedora/27/x86_64/atomic-host /usr/lib/ostree-boot|grep initramfs -00600 0 0 52565370 79acadd126fcb5a02142119dfab6bd35fd5bfb46606adeab23f89cb04c4afc2a { [(b'security.selinux', b'system_u:object_r:lib_t:s0')] } /usr/lib/ostree-boot/initramfs-4.13.9-300.fc27.x86_64.img-850b4ded439b2151106725e7b522d8485d312c9ed80aee65c818c9f99c2c1701 [root@localhost ~]# ostree ls -R -X -C fedora-atomic:fedora/27/x86_64/atomic-host /usr/lib/modules|grep initramfs -00600 0 0 52565370 f70d77da922263abc7e4f4e9fc92e178b051df8e10bd3105ebbb642ca5748f4b { [(b'security.selinux', b'system_u:object_r:modules_object_t:s0')] } /usr/lib/modules/4.13.9-300.fc27.x86_64/initramfs.img ``` Which means 3 physically distinct copies of the initramfs, and with `/boot` as its own partition, that brings it to 4. Using `boot_location: new` should bring us to 2 copies in the tree, and at that point I think we should change the SELinux policy to bring that to 1. I still need to verify that everything works for Anaconda with that set. `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/issue/94

1 2

[fedora-atomic] PR #101: post: Strip glibc_post_upgrade.x86_64
by Colin Walters 04 Jan '18

04 Jan '18

walters opened a new pull-request against the project: `fedora-atomic` that you are following: `` post: Strip glibc_post_upgrade.x86_64 `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-atomic/pull-request/101

3 12

Fedora Atomic WG Meeting Minutes 2018-01-03
by Dusty Mabe 03 Jan '18

03 Jan '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-03/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-03/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by dustymabe at 16:31:32 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-01-03/fedora_atomic… . Meeting summary - --------------- * roll call (dustymabe, 16:31:36) * previous meeting action items (dustymabe, 16:45:52) * Decide strategy for including container runtimes in Atomic Host (dustymabe, 16:49:03) * LINK: https://pagure.io/atomic-wg/issue/360 (dustymabe, 16:49:10) * Overhaul list of members, Quorum Rules (dustymabe, 16:51:09) * LINK: https://pagure.io/atomic-wg/issue/363 (dustymabe, 16:51:16) * LINK: https://pagure.io/atomic-wg/issue/363#comment-485567 (dustymabe, 16:52:42) * LINK: https://fedoraproject.org/wiki/Atomic_WG (sanja, 16:54:44) * Using buildah in Atomic Host (dustymabe, 16:57:58) * LINK: https://pagure.io/atomic-wg/issue/402 (dustymabe, 16:58:04) * open floor (dustymabe, 17:06:24) * LINK: https://src.fedoraproject.org/projects/container/%2A (walters, 17:11:48) * LINK: https://registry.fedoraproject.org/ (puiterwijk, 17:13:50) * LINK: https://github.com/jessfraz/reg/tree/master/server (puiterwijk, 17:16:00) * we are doing a FAH release today (emails should be going out soon) (dustymabe, 17:23:33) * the cloud-utils growpart aarch64 issue is getting closer to being fixed, should be in next release (dustymabe, 17:23:41) * LINK: https://pagure.io/atomic-wg/issue/405 (walters, 17:25:42) Meeting ended at 17:30:41 UTC. Action Items - ------------ Action Items, by person - ----------------------- * **UNASSIGNED** * (none) People Present (lines said) - --------------------------- * dustymabe (139) * puiterwijk (44) * zodbot (19) * jbrooks (13) * walters (11) * sanja (7) * masta (4) * deuscapturus_ (4) * ksinny (4) * miabbott (3) * davdunc (3) * kushal (2) * nirik (1) * misc (1) * markllama (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlpNGDUACgkQMwLb1zlS 5nHm4g//Z2nv1zfvedri7IIits231/O8Uaq+EVmzoireoF1omGcyJth/mZa/XrOl 8UL0Q3EUhvU6Jyi1VkEyHtcEjD3MRsypzJY47kCI9xFvEZWsJ1GjByQy+kVePN6S 3LHhQanBIPcfQMCIDFNxQVeYcsRpFaWmZflakX479WVWtuADp+6Rgjx9DO22CV4f E38+W2ORMyS1r5D2YJdW02BG1noXeTTTwOhXXLkDeZBGWd1ptSoHFmM8g9vCO89o DOOKg9VQeJ1fwhkHMdYTAX6Sp1D0kSOEiOo7HX/bAqUcO4Zhr5TyYQD4I2L8HrXq uLDfkUlAUchsXqMjoLqQe757KhEHu9DQ7tgPosPTDbj8QXOvxlchk7rNSHk1UzgP WLzKW1wp5nfiIW+hBvLaHCQCpOuvwH0pdv7Qv50JPxbcR2aaSyyoEaSqzTlgC6bP g+gmtnIUPCXNVmzhEkIvLtG4HdRj7G8LVI7XV2CLECPp4cEyhtRA3kYsZAHwEzYq rxjHj/5hfQmjxiE+0yzezJWO//GbxYgDWeuH16zjWFJI83nlOjOhwy466FAAFcsp FDiMr8Z582KngMfMdmRWKtt0cqLH9D36wK4zHENEOp3uUzqtGx87jKuJnTg7JrcF RNRPpRzv2xohTjLnEYp6naPCWpcKYtrE9aBCXl6OxW4wfl03S8s= =s7rl -----END PGP SIGNATURE-----

1 0

[atomic-wg] Issue #406: Add ashcrow and sanja to atomic-wg member list
by Sanja Bonic 03 Jan '18

03 Jan '18

sanja reported a new issue against the project: `atomic-wg` that you are following: `` https://fedoraproject.org/wiki/Atomic_WG Would edit page myself but have no permission. If I get the permission, can do. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/406

1 0

2wk atomic release candidate: 20180102
by Dusty Mabe 02 Jan '18

02 Jan '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Tomorrow we will attempt to release the 20180102 images. These images contain the following ostree version/commits from the Fedora-27-updates-20180101.0 updates run: Version: 27.44 Commit(x86_64): b5845ebd002b2ec829c937d68645400aa163e7265936b3e91734c6f33a510473 Commit(aarch64): 76da247f16b7c09d5beb0545387b14f4ddfcb21f869198b2c0243bfd2bb5e650 Commit(ppc64le): d4eb6f890cc2a48aa0bf2dea771c5fb5de64351119a299b6ad44a13de917f652 The atomic host VM images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018010… The ISO images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018010… The AMIs are here: Fedora-Atomic-27-20180102.0.x86_64 EC2 (ap-northeast-1) ami-57c65431 hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (ap-southeast-1) ami-2df98d51 hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (ap-southeast-2) ami-316a9953 hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (eu-central-1) ami-9923b2f6 hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (eu-west-1) ami-699a0f10 hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (sa-east-1) ami-c34704af hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (us-east-1) ami-b64411cc hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (us-west-1) ami-51d2d331 hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (us-west-2) ami-fc0da584 hvm standard Fedora-Atomic-27-20180102.0.x86_64 EC2 (ap-northeast-1) ami-5bc4563d hvm gp2 Fedora-Atomic-27-20180102.0.x86_64 EC2 (ap-southeast-1) ami-3af88c46 hvm gp2 Fedora-Atomic-27-20180102.0.x86_64 EC2 (ap-southeast-2) ami-326a9950 hvm gp2 Fedora-Atomic-27-20180102.0.x86_64 EC2 (eu-central-1) ami-0b27b664 hvm gp2 Fedora-Atomic-27-20180102.0.x86_64 EC2 (eu-west-1) ami-339b0e4a hvm gp2 Fedora-Atomic-27-20180102.0.x86_64 EC2 (sa-east-1) ami-1040037c hvm gp2 Fedora-Atomic-27-20180102.0.x86_64 EC2 (us-east-1) ami-8f4114f5 hvm gp2 Fedora-Atomic-27-20180102.0.x86_64 EC2 (us-west-1) ami-f1d2d391 hvm gp2 Fedora-Atomic-27-20180102.0.x86_64 EC2 (us-west-2) ami-2501a95d hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: a2b80278eea897eb1fec7d008b18ef74941ff5a54f86b447a2f4da0451c4291a ostree diff commit new: b5845ebd002b2ec829c937d68645400aa163e7265936b3e91734c6f33a510473 Upgraded: atomic 1.20.1-6.fc27.x86_64 -> 1.20.1-9.fc27.x86_64 atomic-registries 1.20.1-6.fc27.x86_64 -> 1.20.1-9.fc27.x86_64 audit 2.8.1-1.fc27.x86_64 -> 2.8.2-1.fc27.x86_64 audit-libs 2.8.1-1.fc27.x86_64 -> 2.8.2-1.fc27.x86_64 audit-libs-python 2.8.1-1.fc27.x86_64 -> 2.8.2-1.fc27.x86_64 audit-libs-python3 2.8.1-1.fc27.x86_64 -> 2.8.2-1.fc27.x86_64 ceph-common 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 checkpolicy 2.7-1.fc27.x86_64 -> 2.7-2.fc27.x86_64 cockpit-bridge 155-1.fc27.x86_64 -> 158-1.fc27.x86_64 cockpit-docker 155-1.fc27.x86_64 -> 158-1.fc27.x86_64 cockpit-networkmanager 155-1.fc27.noarch -> 158-1.fc27.noarch cockpit-ostree 155-1.fc27.x86_64 -> 158-1.fc27.x86_64 cockpit-system 155-1.fc27.noarch -> 158-1.fc27.noarch dhcp-client 12:4.3.6-5.fc27.x86_64 -> 12:4.3.6-7.fc27.x86_64 dhcp-common 12:4.3.6-5.fc27.noarch -> 12:4.3.6-7.fc27.noarch dhcp-libs 12:4.3.6-5.fc27.x86_64 -> 12:4.3.6-7.fc27.x86_64 dnsmasq 2.77-9.fc27.x86_64 -> 2.78-1.fc27.x86_64 freetype 2.8-6.fc27.x86_64 -> 2.8-7.fc27.x86_64 glibc 2.26-16.fc27.x86_64 -> 2.26-20.fc27.x86_64 glibc-all-langpacks 2.26-16.fc27.x86_64 -> 2.26-20.fc27.x86_64 glibc-common 2.26-16.fc27.x86_64 -> 2.26-20.fc27.x86_64 glusterfs 3.12.3-1.fc27.x86_64 -> 3.12.4-1.fc27.x86_64 glusterfs-client-xlators 3.12.3-1.fc27.x86_64 -> 3.12.4-1.fc27.x86_64 glusterfs-fuse 3.12.3-1.fc27.x86_64 -> 3.12.4-1.fc27.x86_64 glusterfs-libs 3.12.3-1.fc27.x86_64 -> 3.12.4-1.fc27.x86_64 gnutls 3.5.16-3.fc27.x86_64 -> 3.5.16-4.fc27.x86_64 gssproxy 0.7.0-25.fc27.x86_64 -> 0.7.0-29.fc27.x86_64 info 6.4-5.fc27.x86_64 -> 6.4-6.fc27.x86_64 kernel 4.14.3-300.fc27.x86_64 -> 4.14.8-300.fc27.x86_64 kernel-core 4.14.3-300.fc27.x86_64 -> 4.14.8-300.fc27.x86_64 kernel-modules 4.14.3-300.fc27.x86_64 -> 4.14.8-300.fc27.x86_64 kpartx 0.7.1-8.git847cc43.fc27.x86_64 -> 0.7.1-9.git847cc43.fc27.x86_64 libcephfs2 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 libcrypt-nss 2.26-16.fc27.x86_64 -> 2.26-20.fc27.x86_64 libdb 5.3.28-26.fc27.x86_64 -> 5.3.28-27.fc27.x86_64 libdb-utils 5.3.28-26.fc27.x86_64 -> 5.3.28-27.fc27.x86_64 libgcrypt 1.8.1-1.fc27.x86_64 -> 1.8.1-3.fc27.x86_64 libnfsidmap 1:2.2.1-1.rc1.fc27.x86_64 -> 1:2.2.1-3.rc2.fc27.x86_64 libpkgconf 1.3.10-1.fc27.x86_64 -> 1.3.12-1.fc27.x86_64 librados2 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 libradosstriper1 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 librbd1 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 librgw2 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 libselinux 2.7-2.fc27.x86_64 -> 2.7-3.fc27.x86_64 libselinux-python 2.7-2.fc27.x86_64 -> 2.7-3.fc27.x86_64 libselinux-python3 2.7-2.fc27.x86_64 -> 2.7-3.fc27.x86_64 libselinux-utils 2.7-2.fc27.x86_64 -> 2.7-3.fc27.x86_64 libsemanage 2.7-1.fc27.x86_64 -> 2.7-2.fc27.x86_64 libsemanage-python 2.7-1.fc27.x86_64 -> 2.7-2.fc27.x86_64 libsemanage-python3 2.7-1.fc27.x86_64 -> 2.7-2.fc27.x86_64 libsepol 2.7-1.fc27.x86_64 -> 2.7-2.fc27.x86_64 libsss_idmap 1.16.0-4.fc27.x86_64 -> 1.16.0-5.fc27.x86_64 libsss_nss_idmap 1.16.0-4.fc27.x86_64 -> 1.16.0-5.fc27.x86_64 libsss_sudo 1.16.0-4.fc27.x86_64 -> 1.16.0-5.fc27.x86_64 libzstd 1.3.2-1.fc27.x86_64 -> 1.3.3-1.fc27.x86_64 linux-firmware 20171126-80.git17e62881.fc27.noarch -> 20171215-81.git2451bb22.fc27.noarch lua-libs 5.3.4-6.fc27.x86_64 -> 5.3.4-7.fc27.x86_64 nfs-utils 1:2.2.1-1.rc1.fc27.x86_64 -> 1:2.2.1-3.rc2.fc27.x86_64 openldap 2.4.45-3.fc27.x86_64 -> 2.4.45-4.fc27.x86_64 openssh 7.6p1-2.fc27.x86_64 -> 7.6p1-3.fc27.x86_64 openssh-clients 7.6p1-2.fc27.x86_64 -> 7.6p1-3.fc27.x86_64 openssh-server 7.6p1-2.fc27.x86_64 -> 7.6p1-3.fc27.x86_64 ostree 2017.13-3.fc27.x86_64 -> 2017.15-1.fc27.x86_64 ostree-grub2 2017.13-3.fc27.x86_64 -> 2017.15-1.fc27.x86_64 ostree-libs 2017.13-3.fc27.x86_64 -> 2017.15-1.fc27.x86_64 pkgconf 1.3.10-1.fc27.x86_64 -> 1.3.12-1.fc27.x86_64 pkgconf-m4 1.3.10-1.fc27.noarch -> 1.3.12-1.fc27.noarch pkgconf-pkg-config 1.3.10-1.fc27.x86_64 -> 1.3.12-1.fc27.x86_64 policycoreutils 2.7-1.fc27.x86_64 -> 2.7-4.fc27.x86_64 policycoreutils-python 2.7-1.fc27.x86_64 -> 2.7-4.fc27.x86_64 policycoreutils-python-utils 2.7-1.fc27.x86_64 -> 2.7-4.fc27.x86_64 policycoreutils-python3 2.7-1.fc27.x86_64 -> 2.7-4.fc27.x86_64 python-cephfs 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 python-rados 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 python-rbd 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 python-rgw 1:12.2.1-1.fc27.x86_64 -> 1:12.2.2-1.fc27.x86_64 python2 2.7.14-2.fc27.x86_64 -> 2.7.14-4.fc27.x86_64 python2-libs 2.7.14-2.fc27.x86_64 -> 2.7.14-4.fc27.x86_64 python2-pip 9.0.1-13.fc27.noarch -> 9.0.1-14.fc27.noarch python3-pip 9.0.1-13.fc27.noarch -> 9.0.1-14.fc27.noarch python3-sssdconfig 1.16.0-4.fc27.noarch -> 1.16.0-5.fc27.noarch rpcbind 0.2.4-8.rc2.fc27.x86_64 -> 0.2.4-8.rc3.fc27.x86_64 rpm-ostree 2017.10-3.fc27.x86_64 -> 2017.11-1.fc27.x86_64 rpm-ostree-libs 2017.10-3.fc27.x86_64 -> 2017.11-1.fc27.x86_64 runc 2:1.0.0-11.rc4.gitaea4f21.fc27.x86_64 -> 2:1.0.0-12.rc4.gitaea4f21.fc27.x86_64 sssd-client 1.16.0-4.fc27.x86_64 -> 1.16.0-5.fc27.x86_64 vim-minimal 2:8.0.1360-1.fc27.x86_64 -> 2:8.0.1386-1.fc27.x86_64 Removed: python-enum34-1.1.6-2.fc27.noarch Added: python2-enum34-1.1.6-3.fc27.noarch This was a larger update because of the extra week in the cycle due to the holidays. We have an updated kernel, ostree, rpm-ostree, runc, etc.. Please help us test things out before the release! Dusty -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlpL8BkACgkQMwLb1zlS 5nGzXRAAsJglkxvcvmA+lW4F/oWUGHMJ7UzEJCta8yjW8JB6V7g/wPHsGQA4dAsq tjTK5wawA3D688kwcw4hVBMLwlh01kUvjNkLXFyMMxcWW1DUrh+xJFSMgLN/Xmyr 5ogLbzMhw4q6Ju7/Af4YmXC7D6DuH7gw/IkrkXxzoxO/y5KOaEDb53iqacLwoctl mRV4BBxyVIuCb7Hl24uOBF3pxtmtEac/7vfQ0WGhAgUzmddUZJ9QLaMd0ySqTAUR rDrMQWkkN46Jn4anoQXcgWK6s5swVZgZwabnNAvha4+nDYyHHOUahhil8GQZfpFJ O8+ipKcp8Dh2WpzW0DiSahi64nuES+5Qjv8QklIJS6XfHoyu6nA9Rc5PdzH8XR+B jLE2BKk069yfDvmPXoSLF6/ZtLgkbtgz3Svy37gaPgznY2wrXXLYD4hoLP5l93Lf 9v7LUqHJ0PoQr+GPEOi9rjp2U93CbkUxBAKyJCqce+cdua79gVPwl8Mlv/nGHz2G gxS/F3RHJUtG+/CVHkkuMR+P+hf3Qk3eqZe75urAeMuRVS45T+2yyYa9lrwvALv2 PIT+29oneBCT77P+xBFdvlqnF7wTEavUVWHBZc1FNj+Xw/CfWjSOjqylSWDDJ9Dz V+Efk5Ub10O3VO1siYCWJJoPzGRMzlN5jv1EtZkKxQXcDU8ui6s= =hmYX -----END PGP SIGNATURE-----

2 1

[Fedocal] Reminder meeting : Atomic Working Group Weekly Meeting
by dusty＠dustymabe.com 02 Jan '18

02 Jan '18

Dear all, You are kindly invited to the meeting: Atomic Working Group Weekly Meeting on 2018-01-03 from 16:30:00 to 17:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: This is the meeting for the Fedora Atomic Working Group. We typically go over previous meeting action items and then cover all tickets with the meeting keyword: https://pagure.io/atomic-wg/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/Atomic_WG#Meetings](https://fedoraproject.or… Source: https://apps.fedoraproject.org/calendar/meeting/6952/

1 0

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group (ARCHIVED) January 2018