Fedora Board Recap 2009-06-11
[Posted June 12, 2009 by ris]
| From: |
| "Paul W. Frields" <stickster-AT-gmail.com> |
| To: |
| fedora-advisory-board-AT-redhat.com |
| Subject: |
| Fedora Board Recap 2009-06-11 |
| Date: |
| Thu, 11 Jun 2009 15:34:46 -0400 |
| Message-ID: |
| <20090611193446.GA25419@localhost.localdomain> |
https://fedoraproject.org/wiki/Board/Meetings/2009-06-11
== Roll Call ==
* Board Members: Harald Hoyer, Dimitris Glezos, Chris Tyler, Chris
Aillon, Paul W. Frields
* Regrets: Tom 'spot' Callaway, Matt Domsch, Bill Nottingham, Jesse
Keating, Seth Vidal
* Secretary: N/A
Spent a couple minutes at the top of the meeting on Fedora 11 release
'Yeehaa!!'s.
== What is Fedora ==
* last discussion:
http://fedoraproject.org/wiki/Meeting:Board_meeting_2009-...
* Chris is still chasing it down
* Desktop team meeting today covered this in part
* Nothing in writing yet
** ACTION: Chris Aillon to have something ready June 25
== Status of sponsorship work ==
* last discussion:
http://fedoraproject.org/wiki/Meeting:Board_meeting_2009-...
* Spot has design proposals from Mo Duffy & Ricky Zhou
* Paul to kick the general proposal part in the posterior
* Proposal on wiki, run by Infrastructure, then FAB
== Fedora 11 Release Follow-up ==
* Anything emergent that we need to address right away?
** Looks solid from a board pov
** Awesome job by infra team
** record breaking release
** Fedora moves about **24 Petabytes** every release via all channels
* ACTION: Dimitris -- ticket to website to add very brief summary of
current BT stats to the download page
** Ticket created:
https://fedorahosted.org/fedora-infrastructure/ticket/1456
* release wide retrospective on Tuesday:
** Paul described the logistics for the meeting
(https://www.redhat.com/archives/fedora-advisory-board/200...)
** Paul will get one extra Board member to attend, email Paul or John
Poelstra to be included
== Security notification plan ==
* Status of security proposal from Mike McGrath to be ready after the
release of Fedora 11
** CSI pages describe best practices for an open source project based
on our experiences
** Draft posted --
http://pfrields.fedorapeople.org/documents/csi-securitypo...
* ACTION: Board to review and discuss next week in full
== PPC as a secondary arch ==
* Use of the existing ppc builders for a secondary arch effort
* last discussion:
https://fedoraproject.org/wiki/Meeting:Board_meeting_2009...
** Does this create a chicken/egg problem? How does PPC proceed if we
*don't* use these hardware pieces?
** It doesn't seem like there's any point in *not* providing them
** Need more information from Board members who have intimate
knowledge of the hardware and/or other priorities the current
call-in group doesn't know about
* ACTION: Paul to ask on list for input from missing Board members
== Postponed / Future Business ==
=== Toxicity--follow-ups ===
* establishing a list for moderators to record what they're doing
* assignment of actual moderators
* announcement on FAB about those names
=== Security notification plan ===
* Review and discuss plan as it exists now in CSI docs
=== Seating of next Board ===
* Establish first meeting date, and set meeting day/time with new members.
== Next Meeting ==
* Date: 2009-06-18
* Time: 1700 UTC
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board