From Fedora Project Wiki
m (internal link cleaning) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 10: | Line 10: | ||
== Proposed Approach == | == Proposed Approach == | ||
* | * [[User:Pfrields/Drafts/Roles]] | ||
== Possible Role of FESCo == | == Possible Role of FESCo == | ||
| Line 38: | Line 38: | ||
# what their current focus areas are | # what their current focus areas are | ||
* FESCo will lay out what they want to be responsible for going forward | * FESCo will lay out what they want to be responsible for going forward | ||
[[Category:Board meetings]] | |||
Latest revision as of 08:21, 18 September 2016
Fedora Project Board & FESCo Meeting :: Monday 2008-06-09
- Attendees: Seth Vidal, Dennis Gilmore, Chris Aillon, Spot, Bill Nottingham, Karsten Wade, Jeff Spaleta, Matt Domsch, Máirín Duffy, Paul Frields, Jesse Keating, Jason Tibbits, Jeremy Katz, Josh Boyer, Christian Iseli, and John Poelstra
Background
- Both boards met in a joint session to discuss the future of FESCo
- Meeting called as a result of FESCo's query to the board as to what its purpose is
- History on feature process and FESCo: https://www.redhat.com/archives/fedora-advisory-board/2007-June/msg00022.html
Proposed Approach
Possible Role of FESCo
- Software in Fedora--"if you affect the distro"
- Features
- Oversight of SIGs
- No common agreement on this
SIGS
- Example of a SIG: KDE, Robotics, Astronomy, Python, $LANG
- Not a SIG: Artwork, Ambassadors, Infrastructure
- No Governance Model
- Outreach-Oriented Groups
- Nuts & Bolts Tech-Oriented
Meeting Outcome
Fedora Board Actions
- The board has not changed its stance that FESCo owns the feature process
- The board will meet to determine the other things that FESCo should be responsible for
- The board define roles that it has for FESCo going forward
FESCo Actions
- FESCo to provide the following to the Fedora Board
- summary of their other ongoing work
- what their current focus areas are
- FESCo will lay out what they want to be responsible for going forward