On Wed, Jun 15, 2016 at 10:55 PM, Joe Brockmeier wrote:
> Do we have any system-wide changes we need to propose for F25?
>
> Also, seems weird to have this deadline looming before we even release
> F24... :-)
It is strange for me as well :-)
The first reason is that F25 has been
Matthew Miller (mat...@fedoraproject.org) said:
> 3. Pick a name! I know, it's bikeshed painting to some degree, but it
>really is actually important. Possibilities include:
>
>- Fedora Container Cluster Edition
>- Fedora OpenShift Edition
>- Fedora Atomic Cluster Edition
>-
On 14/06/16, Josh Berkus wrote:
> https://hub.docker.com/_/fedora/
>
> This seems like a big loss, especially for getting folks to test Fedora 24.
>
We push there only after GA. You can see the latest nightly build at
[1].
[1]
On Wed, Jun 15, 2016 at 05:04:08PM -0400, Matt Micene wrote:
> I can also see the potential argument that Atomic Host on it's own wasn't
> compelling enough for a full Edition. So, I hope if we do move toward an
> Atomic+Origin as primary deliverable, we don't lose focus on Atomic Host
>
On Wed, Jun 15, 2016 at 02:09:51PM -0400, Josh Boyer wrote:
> > Thanks — that's good feedback. One possibility — especially as Fedora
> > Server does its own rethink — is for the Fedora Cloud Base to migrate
> > to Fedora Server WG. Another would be for it to continue as a Spin (or
> > the analog
>
> We've decided that, like Workstation, we want to focus on deliverable,
> complete OS environments for users instead of "parts". For Container
> Cloud, that looks a lot like Fedora+OpenShiftOrigin, rather than just
> Atomic Host.
>
I feel like I've not been out of the loop (aside from the
Do we have any system-wide changes we need to propose for F25?
Also, seems weird to have this deadline looming before we even release
F24... :-)
-- Forwarded message --
From: Jan Kurik
Date: Tue, Jun 14, 2016 at 2:31 AM
Subject: REMINDER: Submission deadline
#162: Milestones, components need updating
-+
Reporter: jberkus | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Keywords:
-+
The components
HTML Version:
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-06-15/fedora_cloud_wg.2016-06-15-17.03.html
Full Log:
https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2016-06-15/fedora_cloud_wg.2016-06-15-17.03.log.html
==
#fedora-meeting-1:
On Wed, Jun 15, 2016, at 02:09 PM, Josh Boyer wrote:
>
> To me it is. As I said originally, something that might be
> self-evident to the WG likely isn't to someone that is following the
> IRC meetings, etc. It's a case of "we said we were going to do thing
> X on the list, suddenly on the list
On 06/15/2016 11:09 AM, Josh Boyer wrote:
> On Wed, Jun 15, 2016 at 1:51 PM, Matthew Miller
> wrote:
>> On Wed, Jun 15, 2016 at 01:17:34PM -0400, Josh Boyer wrote:
steps. But, it turned out that everyone in the room (and
teleconferenced in) felt pretty strongly
On Wed, Jun 15, 2016 at 1:51 PM, Matthew Miller
wrote:
> On Wed, Jun 15, 2016 at 01:17:34PM -0400, Josh Boyer wrote:
>> > steps. But, it turned out that everyone in the room (and
>> > teleconferenced in) felt pretty strongly that we actually should go
>> > even further —
#154: make Fedora Atomic download page clearer
---+-
Reporter: jberkus| Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Docker Host Image | Resolution:
#153: design, deploy and document Fedora OpenShift Playground (FOSP)
-+---
Reporter: goern| Owner: jberkus
Type: task | Status: assigned
Priority: normal | Milestone: Future
Component: --- | Resolution:
Keywords:
On Wed, Jun 15, 2016 at 01:17:34PM -0400, Josh Boyer wrote:
> > steps. But, it turned out that everyone in the room (and
> > teleconferenced in) felt pretty strongly that we actually should go
> > even further — not just a single container host, but a full container
> > cluster solution based on
#161: NTP should be enabled by default on Atomic Host
---+
Reporter: jberkus| Owner:
Type: defect | Status: new
Priority: normal | Milestone: Future
Component: Docker Host Image |
#148: Container "Packager" Guildelines and Naming Conventions
-+-
Reporter: maxamillion | Owner:
Type: task | Status: closed
Priority: normal | Milestone: Future
Component: --- | Resolution: fixed
#115: Fedora Cloud FAD (late 2015/early 2016)
---+
Reporter: dustymabe | Owner: dustymabe
Type: task | Status: closed
Priority: normal | Milestone: Future
Component: Planning | Resolution: fixed
Keywords:
On 06/15/2016 09:07 AM, Matthew Miller wrote:
> 3. Pick a name! I know, it's bikeshed painting to some degree, but it
>really is actually important. Possibilities include:
>
>- Fedora Container Cluster Edition
>- Fedora OpenShift Edition
>- Fedora Atomic Cluster Edition
>-
On Wed, Jun 15, 2016 at 12:07 PM, Matthew Miller
wrote:
> Previously (at last year's Flock and after), we've talked about
> replacing the Fedora Cloud Edition with Fedora Atomic Edition. (See
> previous discussion on this list if you're unfamiliar with this
> decision
On 06/15/2016 11:07 AM, Matthew Miller wrote:
Previously (at last year's Flock and after), we've talked about
replacing the Fedora Cloud Edition with Fedora Atomic Edition. (See
previous discussion on this list if you're unfamiliar with this
decision and its rationale.)
We hadn't actually had
Previously (at last year's Flock and after), we've talked about
replacing the Fedora Cloud Edition with Fedora Atomic Edition. (See
previous discussion on this list if you're unfamiliar with this
decision and its rationale.)
We hadn't actually had much movement on _doing_ that, though, so one of
22 matches
Mail list logo