From Fedora Project Wiki

Revision as of 16:10, 25 October 2010 by Bruno (talk | contribs) (Update for spin status and the future)

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

Meetbot logs

Current Agenda

  • Bruno to step down as lead after F14 process is complete.
    • I let advisory board know and requested a future of spins meeting.
  • Spins status
    • Modified RC1 built. Seem OK so far.
  • Should owners be required to sign off on an RC of their spin before GA?
    • The LiveCD specific test plans are linked from Category:LiveCD Test Cases. The QA/TestCases/ links are plans. The other two items are for SIGreview. I think we should ask for people to do the tests for both i686 and x86_64 as we have had arch specific issues in the past. The testing would start when RC's start getting built and should use a nightly compose. Owners should report back to the spins list.
      • I sent out a message about this, but it is optional this go around.
      • Starting at RC build time is too late. Should be at TC time. (Plus the recommended monthly.)
  • Future meetings
    • DST -> ST change.
    • Are we done until after the FUDCON?

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?