# F21 Blocker Review meeting
# Date: 2014-09-10
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
It's everyones favorite time of the week! Our next blocker review meeting will
be this Wednesday (as usual). As of right now, we have 2 proposed blockers
All,
At the last SIG meeting I agreed to have a go at fixing up the cloud
spin and the associated kickstarts. As I understand it, this means:
* Changes to comps - Specifically adding a group that carries the
necessary enabling packages that need to be in the cloud image
* Changes to the cloud
On 09/08/2014 10:17 AM, Dusty Mabe wrote:
On Mon, Sep 08, 2014 at 09:28:20AM -0400, Adam Young wrote:
On 09/07/2014 11:22 PM, Dusty Mabe wrote:
Hi All,
Per discussion in the #fedora-cloud meeting last Friday I would like to
start a thread about the names of the Docker and Atomic deliverables f
On Mon, Sep 08, 2014 at 09:28:20AM -0400, Adam Young wrote:
> On 09/07/2014 11:22 PM, Dusty Mabe wrote:
> >Hi All,
> >
> >Per discussion in the #fedora-cloud meeting last Friday I would like to
> >start a thread about the names of the Docker and Atomic deliverables for F21.
> >
> >I know of at leas
On Mon, Sep 08, 2014 at 09:29:12AM -0400, Colin Walters wrote:
> On Sun, Sep 7, 2014, at 11:22 PM, Dusty Mabe wrote:
> >
> > In a nutshell, it would be great if we added "Container" to references we
> > make to the container image (in conversation and docs).
>
> I tend to say "Docker Base Image"
On Sun, Sep 7, 2014, at 11:22 PM, Dusty Mabe wrote:
>
> In a nutshell, it would be great if we added "Container" to references we
> make to the container image (in conversation and docs).
I tend to say "Docker Base Image" - that's the terminology upstream
Docker uses: https://docs.docker.com/arti
On 09/07/2014 11:22 PM, Dusty Mabe wrote:
Hi All,
Per discussion in the #fedora-cloud meeting last Friday I would like to
start a thread about the names of the Docker and Atomic deliverables for F21.
I know of at least a few cases where there has been confusion regarding
what deliverable has be