From Fedora Project Wiki
Spin SIG meeting information
Current schedule
Meetings weekly on Mondays at 21:00 UTC.
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
- Spins status
- Spins jumped around 25-30 MB between the 13th and 14th.
- broffice appears to be oversize
- xfce appears to be oversize
- Design team says Design Suite is targeting 1 GB USB devices, so is NOT oversize.
- Target sizes should get tracked somewhere. Probably on the spin release page, since those are the ones we want to worry about.
- This is just waiting for Bruno to complete.
- Target sizes should get tracked somewhere. Probably on the spin release page, since those are the ones we want to worry about.
- Meego will not be a publish spin for F14. There will probably be a remix at some point before F15.
- Spins jumped around 25-30 MB between the 13th and 14th.
- Should owners be required to sign off on an RC of their spin before GA?
- Bruno still doesn't have a proposed set yet.
Future Agenda
- Getting a review of Dan Walsh's changes proposed for live-base to make maintaining his sandbox spin simpler.
- I think this could be useful for other custom spins as well.
- Having a way to add users when running livecd-iso-to-disk might also be useful, though maybe not practical.
- Process updates noted in Paul's message.
- Kevin did a rough draft, Bruno will review and we will take up at the next meeting.
- This needs to be checked to make sure the relevant information has been captured.
- 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?