F21 Beta release announcement
by Jaroslav Reznik
Hi marketing team/WGs,
me again - we're getting closer to Beta release. The readiness
meeting is just one week away from now, it would be great to have
at least draft prepared.
I see, Joe already created Beta announcement page.
https://fedoraproject.org/wiki/F21_Beta_release_announcement
Btw. it was excellent work on Alpha, with WGs and everyone else
being involved! I expect we don't need much updates from Alpha,
just a bit extend it with more features, more details.
Thanks
Jaroslav
9 years, 6 months
Self Introduction
by Neependra Khare
Hi All,
I work with Red Hat in performance engineering team from Bangalore, India.
I am also one of the co-organizer of Banglaore Docker meetup group.
http://www.meetup.com/Docker-Bangalore/
I met few of you during the LinuxCon NA in Chicago few months back.
I am interested in testing, developing of Fedora Atomic.
During the last Docker meetup in Bangalore I asked if members would be
interesting in testing Atomic and there were few guys who showed interest.
http://neependra.net/?p=1221
Regards,
Neependra
www.neependra.net
@neependra
9 years, 6 months
[DRAFT] Changes to Working Group structure
by Joe Brockmeier
Hi all,
As discussed last week, we need to make some changes to the language
about choosing members of the CWG.
Current:
Membership
----------
The Fedora Cloud Working Group has nine voting members, one selected by
the Fedora Engineering Steering Committee as the liaison to FESCo, and
the others initially selected by the FESCo liaison.
Because continuity is important, Working Group members serve as long as
they are able and willing. Each voting member of the working group will
confirm their continued membership every six months. When a position in
the group becomes available, that position will be filled by unanimous
consent of the existing members.
Suggested Change:
-----------------
The Fedora Cloud Working Group will have a minimum of five voting
members, one selected by the Fedora Engineering Steering Committee
(FESCo) as the liaison to FESCo, and the others to be approved by a lazy
majority of the existing Working Group members.
Because continuity is important, Working Group members serve as long as
they are able, willing, and active. There is no upper cap on Working
Group Members, but members may be removed from active status after
sustained inactivity or on majority vote of the rest of the Working Group.
Current:
Making Decisions
----------------
Because Fedora is a global project, members of the working group may be
distributed across multiple timezones. It may be possible to have a
real-time IRC meetings, but in general we will conduct business on the
Fedora Cloud mailing list.
Many of our decisions can be made through "lazy consensus". Under this
model, an intended action is announced on the mailing list, discussed,
and if there is no controversy or dissenting views with a few days,
simply done.
For bigger issues, where there may be disagreement, or where there is
long-term impact, or where an action may not easily be undone, we will
use a ticketing system for voting https://fedorahosted.org/cloud/.
Working group members can vote +1 to approve, -1 to disagree, or 0 to
abstain; five +1 votes are necessary for a measure to pass. Non-members
may comment on the ticket and (of course) discuss on the mailing list,
but are asked to refrain from putting votes in the ticket.
Suggested Change:
Making Decisions
----------------
Because Fedora is a global project, members of the working group are
distributed across multiple timezones. While the Working Group does have
real-time IRC meetings, these are used as working sessions and policy or
major technical decisions will be conducted on the Fedora Cloud
(cloud(a)lists.fedoraproject.org) mailing list.
When possible, we will try to take decisions through "lazy consensus."
Under this model, an intended action is announced on the mailing list,
discussed, and if there is no controversy or dissenting views with a few
days, simply done.
In some cases a vote may be required if:
- Consensus cannot be reached through discussion.
- There's a long-term impact.
- An action cannot easily be undone.
When a vote is required, we will use the Trac ticketing system for
voting at https://fedorahosted.org/cloud/. Working group members can
vote +1 to approve, -1 to disagree, or 0 to abstain; a majority of +1
votes are necessary for a measure to pass. Non-members may comment on
the ticket and (of course) discuss on the mailing list, but are asked to
refrain from putting votes in the ticket.
# # #
Thoughts, comments, flames?
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
9 years, 6 months
Friday meeting agenda [Draft]
by Joe Brockmeier
Hi all,
Will be out tomorrow, but promised to send a draft agenda to help run
the meeting. Here's the action items and tickets for tomorrow:
* jzb to draft changes to Fedora Cloud Working Group Governance
Structure and sent to list [DONE]
* mattdm to take changes in Fedora Cloud Working Group Governance
Structure to FESCo once accepted.
* roshi to update fedocal once a date is set
* jzb continue planning Atomic image test days. Wait for new date. [IN
PROGRESS]
* jzb Continue to work on a runbook for having Atomic and other cloud
images updated out of band. [IN PROGRESS]
* roshi wait until next week for feedback on ticket 77 then move
forward.
* kushal and roshi to work on Ticket 38 on Automatic Smoketests on Image
Build w/an eye towards completion for Fedora 22.
* roshi remind Cloud SIG about blocker review meetings.
* number80 set a poll to change WG meeting date
Tickets tagged with meeting:
https://fedorahosted.org/cloud/report/9
Note on Ticket 74 - also see my AI above. In progress, but nothing to
report this week.
Note on Ticket 75 - still in progress, waiting for beta. Nothing to
report this week.
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
9 years, 6 months
