[cloud] #65: crucial questions on Docker image deliverable
by Fedora Cloud Trac Tickets
#65: crucial questions on Docker image deliverable
-----------------------------------+--------------------------------
Reporter: mattdm | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 21 (Branch)
Component: Docker Base Container | Keywords: meeting
-----------------------------------+--------------------------------
Adam W asks some excellent questions here:
https://lists.fedoraproject.org/pipermail/devel/2014-June/199579.html
> What "Fedora" exactly is the image going to contain? Fedora Server?
> Fedora Cloud? Will it be a part of either of those products? If not,
> what is its status, exactly? Who's responsible for it? Is it considered
> a primary or frontline or whatever Fedora deliverable? Who's going to
> test it? How's it going to be promoted in relation to all our other
> deliverables?
I gave some tentative answers, but let's get them answered definitively.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/65>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
9 years, 7 months
Fedora Cloud (Atomic) & Infra meeting 26 August 2014
by Joe Brockmeier
Apologies for being tardy in sending this out.
===============
#atomic Meeting
===============
Meeting started by jzb at 20:09:50 UTC. The full logs are available at
http://meetbot.fedoraproject.org/atomic/2014-08-26/atomic.2014-08-26-20.0...
.
Meeting summary
---------------
* F21 composes (jzb, 20:10:17)
* looks like there is a TC4 for Atomic (jzb, 20:10:42)
* LINK:
http://dl.fedoraproject.org/pub/alt/stage/21-Alpha-TC4/Cloud/Images/x86_64/
(jzb, 20:10:47)
* ACTION: nirik when we have a viable Atomic TC nirik will make sure
it's announced. (jzb, 20:13:44)
* ACTION: jzb once we have a viable Atomic TC jzb will try to arrange
a test day (jzb, 20:14:12)
* ACTION: jzb research test case possibilities for Atomic (jzb,
20:21:00)
* any new business? (jzb, 20:24:35)
Meeting ended at 20:29:20 UTC.
Action Items
------------
* nirik when we have a viable Atomic TC nirik will make sure it's
announced.
* jzb once we have a viable Atomic TC jzb will try to arrange a test day
* jzb research test case possibilities for Atomic
Action Items, by person
-----------------------
* jzb
* jzb once we have a viable Atomic TC jzb will try to arrange a test
day
* jzb research test case possibilities for Atomic
* nirik
* nirik when we have a viable Atomic TC nirik will make sure it's
announced.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jzb (37)
* dustymabe (11)
* nirik (10)
* stickster (4)
* zodbot (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
9 years, 8 months
Re: Proposal for every WG to send a short summary *to other WGs directly*
by Josh Boyer
On Tue, Aug 26, 2014 at 10:46 AM, Honza Horak <hhorak(a)redhat.com> wrote:
> Hi working groups members,
>
> since we have learned on Flock that new Fedora working groups do not
> communicate with each other much (or enough), I'd like to propose the
> following:
>
> Every working group will time to time (e.g. weekly) send short summary about
> what they did / were talking about directly to mailing lists of other
> working groups + to devel(a)fp.o. Really only a short summary with links where
> one can find details.
>
> I tried to collect such info from the meeting logs and mailing lists for the
> last few weeks for Env and Stacks WG:
> https://lists.fedoraproject.org/pipermail/env-and-stacks/2014-August/0004...
>
> I found many notes are really worth spreading beyond groups' borders, but it
> takes too much time for one person to collect all the information. Thus,
> proposing to "do a summary once per group and share with other groups".
>
> Another benefit would be that Matt would have better content for his 5tiftw.
>
> I don't think we need to sync about date or frequency, just remembering to
> send a direct mail if anything interesting is done/discussed should work
> fine.
>
> List of proposed MLs to send this summary to:
> server(a)lists.fedoraproject.org
> desktop(a)lists.fedoraproject.org
> cloud(a)lists.fedoraproject.org
> env-and-stacks(a)lists.fedoraproject.org
> devel(a)lists.fedoraproject.org
>
> Comments, ideas or better solutions are welcome as usually, but I might be
> offline until Sunday, so do not expect any answers from me in that time :)
I don't have any major objections to this, but I will note that
reports stopped being sent to FESCo because at some point they were
kind of redundant. "Still working on thing X" every week isn't really
something that needs to be sent. So I would avoid a weekly deadline
and maybe just post minutes/summaries of the meetings the groups have
when there is actually something to communicate.
josh
9 years, 8 months
Regrets to today's meeting
by Joe Brockmeier
Hi all,
At LinuxCon Chicago this week, will not be able to make today's IRC
meeting.
I did send the RFC to the cloud list for updates to the Docker images,
have had some offline feedback, but need more.
No travel after this week until the second or third week of October, so
I expect to be getting a lot more items cleared during that time.
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
9 years, 8 months
