Meeting:Board meeting 2008-02-26

From FedoraProject

Jump to: navigation, search

Contents

Fedora Project Board Meeting :: Tuesday 2008-02-26

Roll Call

Attendees: Paul Frields, Steve Dickson, Bill Nottingham, Matt Domsch, Dennis Gilmore, Chris Aillon, Seth Vidal, Spot Callaway, John Poelstra

Regrets: Jef Spaleta, Karsten Wade, Bob McWirther


Followup to Previous Business

Secondary Arch Hosting (2008-02-19)

  • Can Fedora host binaries for secondary architectures?
  • Change from original proposal
  • makes it easier to get new mirrors and use mirror manager
  • DECISION: board approves of Fedora hosting binaries for secondary architectures
  • FOLLOWUP 2008-02-26
  • Infrastructure group raising issue with lack of space
  • Are distribution methods a concern for growing secondary architectures?
  • OWNERS: Seth and Matt; Spot also assisting
  • ACTIONS: reach out to existing relationships and pursue storage opportunities

fedoraproject.org mail (2008-01-29)

  • Take steps to approach changes that were requested in the past
  • Could we create a better start and search page for Fedora mailing list?
  • ACTION: check back on status in one month
  • OWNER: Dennis Gilmore
  • FOLLOWUP 2008-02-26
  • Dennis has spoken with some people inside RHT IS
  • should have no issues making a fedora branded interface to Red Hats mailman instance and having a @fedoraproject.org alias for fedora lists
  • existing lists will stay where they are
  • could migrate all mailing lists to fedoraproject.org in time time if so desired
  • driving forces here is:

1. making everything run Fedora 1. break ties to RHT IS which does not make Fedora a priority

  • fedoraproject.org email addresses lost four days of email a week ago and RHT did nothing to try and remedy the problem
  • ACTION: check back on status in one month


Job of the Fedora Board (2008-01-29)

  • Discussion resulted from fedora-advisory-board-list thread
  • Clarify roles and responsibilities of the board and make wiki pages more specific
  • ACTION: check back on status in one month
  • OWNER: Paul Frields
  • FOLLOWUP 2008-02-26
  • Paul updated some of the wiki pages.
  • Key issues:

1. Keep decision making as much as possible in the community 1. Board is responsible for three types of issues a. escalated issues a. issues not covered by any committee in Fedora a. sensitive legal or personnel issues that need to be covered in private


LWN 10th Birthday (2006-02-12)

  • Board voted to make contribute to LWN in commemoration of its 10th birthday
  • Contribution went toward purchasing 75 subscriptions which start on March 1, 2008
  • In the future (when there is more lead time) look into ways to use things like this as rewards for strong Fedora leadership and community participation
  • OWNER: Jef Spaleta
  • ACTION: Jef to followup Max Spevack who made original arrangements and then post to fedora-advisory-board list soliciting feedback on the best way to create a lottery to give these out to Fedora people who can use them.
  • FOLLOWUP 2008-02-26
  • Requests are rolling in and Jef is handling lottery


Trademark Usage By Non-Profit Organizations (2006-02-19)

  • Use of Fedora trademark by non-profit organizations
  • Fedora ambassadors in Europe are working on setting up a non-profit
  • Board would prefer detailed reporting on a quarterly basis
  • Board would ask people not to flood the board requests for six months so that existing requests and be addressed
  • OWNER: Paul Frields
  • ACTIONS:

1. Send draft policy to fedora-board-list 1. Collaboratively modify draft on list and reach consensus vote 1. Upon approval post to fedora-advisory-board list and fedora-ambassadors-list as public notice 1. Inform Fedora EMEA Ambassadors of the "yes" vote

  • FOLLOWUP 2008-02-26
  • Approved and email sent: https://www.redhat.com/archives/fedora-advisory-board/2008-February/msg00157.html
  • NPO is responsible; Max will likely be point person for quarterly reports
  • Use of Fedora trademark is being requested for an organization in India
  • DECISIONS:
  • As requested at last meeting would like wait to six months until reviewing further requests
  • Board wants to arrive at a governance model that works and makes sense; will take some time to confirm what works best
  • Want to give some time to see how things work with EMEA

New Business

Status of PPC

  • Request from RHEL Engineering to Fedora for the current status of PPC as primary or secondary architecture
  • Spot Callaway spoke to issue
  • There are no changes from its current status which is understood to be:

1. PPC will remain a primary architecture until there is at least one other building secondary architecture; this has not been happened yet 1. PPC SIG remains responsible for all release engineering responsibilities around PPC


Summer of Coding

  • What do we want to pursue for 2008?
  • What do we want to achieve?
  • Start collecting project ideas on the mailing list and wiki
  • Separate Red Hat paid positions from Google Summer of Code
  • OWNER: Karsten Wade
  • ACTIONS: Move discussion to fedora-advisory-board@redhat.com and split out between Red Hat and Summer of Code work


Trademark Cease & Desist

  • Brief recap of what happened with Data Portability
  • Putting procedures in place so that board reviews Trademark issues going forward
  • OWNER: Paul Frields
  • ACTIONS:
  • Paul Frields and Spot Callaway meeting with RHT Legal to make sure board is consulted first in actions such as this that involve Fedora


Codeina

  • Still not comfortable that we are pointing people to content that is not "Free and Open Source software"
  • Cannot suitably fix codeina in the Fedora 9 time frame
  • ACTIONS:

1. Review email thread: https://www.redhat.com/archives/fedora-advisory-board/2007-November/msg00050.html 1. Move discussion to fedora-advisory-board list to formulate a solution there 1. Propose patching out other for sale non-free plugins 1. Bill Nottingham to make sure that live spin includes codeina correctly


Future Business (discuss at a future meeting)

Post-release updates of custom spins (2008-01-29)

  • Should the board have to approve them?
  • We will hosts as many spins as we have space for
  • Need to determine the hosting requirements and limits
  • How long will spins stay around?
  • http://fedoraproject.org/wiki/RahulSundaram/SpinsProcess
  • ACTION: Jef to review Rahul's proposal and report back to board
  • OWNER: Jef Spaleta
  • FOLLOWUP on 2008-02-12
  • Jef is waiting for feedback from Jeremy Katz on release engineering's perspective
  • Reference: http://fedoraproject.org/wiki/ReleaseEngineering/Meetings/2008-feb-11
  • People are still not clear on exactly what is required to create an official "Fedora Spin"
  • Need a clear list of guidelines of what a spin owner is responsible for and what they are required to test
  • Hoping a test will come from Jeremy Katz as part of feedback from release engineering
  • We are only talking about spins that use GA packages, thus testing for GA should have given us enough comfort that risk is minimized
  • We only need to be concerned with new combination of packages that a spin would present
  • ACTIONS & OWNERS:
  • Paul Frields--followup with Fedora Release Engineering and QA contingent to discuss testing requirements
  • Jef Spaleta to formulate specific guidelines for review prior to or at next board meeting (dependent on feedback from release engineering)
  • FOLLOWUP on 2008-02-19
  • Crux of issue right now is figuring out exactly what input release engineering is supposed to be giving
  • Jef will have a writeup to the board by next meeting
  • Paul will be at the Red Hat office in Westford, MA next week and can sit down and work out any of the remaining details with Jeremy, Jesse, Will, etc.
  • FOLLOWUP on 2008-02-26
  • releng has created http://fedoraproject.org/wiki/JeremyKatz/SpinChecklist
  • Jef has input from Rahul and plans to start writing a draft

Next Meeting

  • IRC meeting on #fedora-board
  • Date: 2008-03-04
  • Time: 14:00 EST (1900 UTC)
  • OWNER: Paul Frields
  • ACTIONS:

1. Paul send to to fab and fedora-announce 1. Set up two IRC channels; one for dialog with board and one to collect questions