Spin SIG meeting information
Current schedule
Meetings weekly on Mondays at 21:00 UTC.
In the recent past we haven't had real meetings, but sometimes have provided some status updates.
How this page is used
Since we haven't had real meetings for a while, I think we are better off using this page to keep a list of outstanding agenda items. Stuff will be added when it comes up and removed when it has been dealt with.
Meeting results will be in the meetbot area. Previous meetings mostly pre-date being able to name meetings so will probably be hard to find, but going forward should be easy to link to.
Previous Meeting Logs
Current Agenda
- Note that Bruno will be unable to attend the August 2nd meeting and is highly likely to not be able to attend the August 9 meeting as well. (Due to vacation travel.)
- Starting approving spins for F14.
- Note that there are conflicts breaking some of the spin builds right now.
- MeeGo
- Added @meego-netbook (was @moblin-desktop)
- Includes mesa-dri-drivers-experimental which isn't allowed for release. Is it needed now?
- Is the trademark issue settled? (Thread: http://lists.fedoraproject.org/pipermail/advisory-board/2010-July/008651.html)
- SoaS
- Added pygame
- Games
- Dropped tremulous due to its orphan status
- Other high level ones didn't change, though at some point we need to look at the mini stuff
- livecd-desktop ks removes packages in post. This is bad.
- Should owners be required to sign off on an RC of their spin before GA?
- Report from the releng meeting
- Process doc. (Status if it isn't done yet.)
- Possibly discuss recommend minimum test plans to execute
- Review categories for ready states and 13 to make sure spins are properly categorized.
- Make sure 13 entries and any new ones we know of are in development.
- Getting a review of Dan Walsh's changes proposed for live-base to make maintaining his sandbox spin simpler.
- Process updates noted in Paul's message.
- Kevin did a rough draft, Bruno will review and we will take up at the next meeting.
- It has been suggested that we better document how to use the spins with USB drives.
- With USB drives becoming more common and being a lot better because they don't have large seek times, this seems like good advice.
- Is this something we would do ourselves, or would docs or design team do it?