From Fedora Project Wiki
< Extras | SteeringCommittee
Fedora Extras Steering Committee
14 October 2005
Present
- Adrian Reber
- Greg DeKoenigsberg
- Thomas Vander Stichele
- Warren Togami
- Thorsten Leemhuis
- Elliot Lee
- Michael Schwendt
- Dams Nade
- Ville Skytta
- Jose Pedro Olivia
Action items
- Legal requirements for Extras licensing in packages, should be incorporated into general packaging guidelines as appropriate SHOULDs and MUSTs; by spot
- Eric Meyer has done work on comps, Elliot will look into it. Jeremy has done new work, and comps.xml won't match anymore. Eric should wait before he moves on further.
- No new sponsors for this week
- Warren brings up how elvis CVS accounts and migration of the many translator accounts are happening. Elliot tells us someone is working on it, let them do good
- Seth brings us great tidings in the form that Dell is shipping two (2) new machines to the Fedora Project. Now thats new boxes, that will sit at Duke, and be torrent.fedoraproject.org and fedoraproject.org. For
all the tech heads, its: "dual 2850s 2.8ghz - 2GB ram 2x36GB disk in a raid1 and 3x146GB disks in a raid5". We will have a Dell logo at the bottom of fp.o
- Warren will revoke cvsextras to anyone approved via the blanket process, only after sending details to FESCO
Brainstorming
- laptop-project to list working laptops - maybe we can use Pooty
Pedia.sf.net - Single sign on for account requests... Fedora Directory Server
- Extras CDs and splitting it into groups
- We need tools for any user to create combinations of Core/Extras by themselves. This could be done via a yum-util, that takes a set of repos (using Core tree, with nice 2nd stage stuff), and build a set.
- Yarrr was a research project, thats not being worked on any longer
- LiveCD. We need one. Kadischi is what we should focus energies on. Stateless never landed, but there might be some rework for FC5 to get this going.
- Michael asks: Do we have concrete plans on how to make sure that FE5 is ready with the release of FC5? (For instance, to document whether and when to rebuild packages without a central mass-rebuild like last time.
To coordinate rebuilding of dependency chains. To document who is permitted to trigger rebuilds.). Greg suggests an FE Release Engineer :)
- We need people, instead of plans. Or maybe people *and* plans. Or heck, plans to get people.
- We need policy on how rebuilds happen. Assuming we don't have packagers that are responsive, allow "leaders" to rebuild away. This is like Core.
- Sopwith is focusing on QA, and making it more user driven (with more user-friendly tools)
- Statistics, for top ten package reviewers:
tcallawa redhat com 76.0 rc040203 freenet de 32.0 jpo di uminho pt 20.0 wtogami redhat com 12.0 jamatos fc up pt 10.0 petersen redhat com 10.0 bugs michael gmx net 9.0 dkl redhat com 8.0 steve silug org 8.0 paul city-fan org 7.0
- kernel-modules in Extras?
- repoclosure in Extras?