[Base] adopting the Docker base image into Atomic WG
by Colin Walters
Now that Cloud -> Atomic and will be focusing on Project Atomic, can we move the
Docker base image into this group from the "Fedora Base" group?
It never really made sense to me in Base; in:
$ git log --format='%ae' fedora-docker-base.ks | sort -u
admiller(a)redhat.com
dennis(a)ausil.us
jpazdziora(a)redhat.com
kevin(a)fedoraproject.org
kushaldas(a)gmail.com
mattdm(a)mattdm.org
maxamillion(a)fedoraproject.org
pbrobinson(a)gmail.com
vpavlin(a)redhat.com
walters(a)verbum.org
Most of the recent committers are outside of the Base group.
And it makes sense to me to have synchronized landing pages/information
for Atomic Host and the Docker base image.
7 years, 6 months
Re: Cloud and Server Q&A
by Adam Williamson
On Thu, 2016-09-29 at 16:51 -0600, Chris Murphy wrote:
> But I don't
> think QA clearly understands what cloud image(s) are release blocking,
> as previously they were just the non-atomic images.
I don't know what's going on with all this crap, but so far as I'm
concerned I understand perfectly well what the release blocking images
are. It's the ones listed on the release blocking images page which
specifically exists for this purpose:
https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/...
(we still need to make the canonical version of this a JSON file
somewhere and generate the human-readable version from the JSON, but
meh, I haven't got around to it yet).
if it doesn't say 'yes' there, it ain't release blocking. Maintaining
that thing is the program manager's problem (i.e. jkurik's), not mine,
but it does somewhat concern me the number of 'TBD's on there. I don't
think the question of what images are 'release blocking' for F25 should
be *remotely* live at this point: it should have been decided weeks
ago, at least by Alpha release. And so far as I remember it, that's
what the protocol was supposed to be, we weren't still supposed to be
kicking around 'is it blocking?' discussions at Beta freeze. I'd
personally be very unhappy with any attempt to significantly change
what that page says right now.
Which images are prominent on the download pages and how much of a
relationship there is between that and 'release blocking' status is
*also* not my problem, but I'd agree with you (Chris) that it'd be
rather strange for the most prominently advertised deliverable for a
given product not to be a release-blocking one.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 6 months
No Two Week Atomic Release
by Adam Miller
Hello all,
I just wanted to post a quick update that there has not been a
compose that passed all AutoCloud testing criteria for release in the
past two weeks. It appears that the Vagrant libvirt images are
failing.
We will try again for a release next Two Week window.
Thank you,
-AdamM
7 years, 6 months
Cloud Meeting Minutes 05-10-2016
by Sayan Chowdhury
==================================
#fedora-meeting-1: fedora_cloud_wg
==================================
Meeting started by sayan at 17:01:16 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-10-05/fedora_clou...
.
Meeting summary
---------------
* Roll Call (sayan, 17:01:23)
* Action items from last meeting (sayan, 17:03:53)
* LINK: https://stg.pagure.io/atomic-wg/issues (kushal, 17:07:29)
* LINK: https://github.com/rtnpro/motdgen (kushal, 17:08:12)
* ACTION: kushal will clean up the wiki next week. (kushal, 17:13:52)
* vagrant boxes fixups https://fedorahosted.org/cloud/ticket/136
(sayan, 17:14:11)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1290659#c42
(kushal, 17:18:36)
* design, deploy and document Fedora OpenShift Playground (FOSP)
https://fedorahosted.org/cloud/ticket/153 (sayan, 17:20:30)
* make Fedora Atomic download page clearer
https://fedorahosted.org/cloud/ticket/154 (sayan, 17:22:41)
* Decide on post-GA update cadence for various deliverables
https://fedorahosted.org/cloud/ticket/155 (sayan, 17:23:50)
* Need complete Kickstart docs for Atomic Host
https://fedorahosted.org/cloud/ticket/156 (sayan, 17:25:29)
* Ship fedora-motd in F24 atomic image
https://fedorahosted.org/cloud/ticket/160 (sayan, 17:27:26)
* Finish new Fedora Cloud PRD https://fedorahosted.org/cloud/ticket/170
(sayan, 17:29:46)
* Open Floor (sayan, 17:38:40)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1290659
(jbrooks, 17:49:05)
Meeting ended at 18:00:28 UTC.
Action Items
------------
* kushal will clean up the wiki next week.
Action Items, by person
-----------------------
* kushal
* kushal will clean up the wiki next week.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* kushal (73)
* sayan (59)
* jberkus (52)
* jbrooks (34)
* zodbot (18)
* scollier (11)
* rtnpro (10)
* maxamillion (9)
* gholms (8)
* dustymabe (7)
* walters (6)
* vvaldez (2)
* trishnag (2)
* tflink (1)
* imcleod (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Sayan Chowdhury <https://sayanchowdhury.dgplug.org/>
Senior Software Engineer, Fedora Engineering - Emerging Platform
GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B
Proud to work at The Open Organization!
7 years, 6 months