Spins SIG Meetings

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

Until we have something better you need to start at http://meetbot.fedoraproject.org/fedora-meeting/ and then look for Spins meetings on Mondays.

Current Agenda

• Review draft spins wrangler page.

• Starting clearing spins for F14.

• Should owners be required to sign off on an RC of their spin before GA?
  • What should happen if we require this, but an owner fails to sign off?
  • If we go down this route we need to talk to releng about details.

• Make sure Security Lab actually got trademark approval.
  • See https://fedoraproject.org/wiki/Meeting:Board_meeting_2010-02-18#Trademark_approval_for_Security_spin

• How did Security Lab get published if it wasn't in the category for F13?
  • There is a separate wiki page for the spins with published ISOs.

• We might try to cover the releng GA handoff depending on when Jesse wants to do the makeup meeting.

• 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.

• Create a 14 category landing page.

• spins commits getting bounced from spins list

• FYI livecd-creator patches

• Advertise for a new Spins Wrangler
  • Kevin started doing some of this.
  • We hope to have a page with description of their duties soon. This might help.

• 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.

• Schedule for F14?
  • Branch ks repo for F14?
    • This will happen near release
  • When to use rawhide, release an updates as repos in each branch?
  • When to update package for the release?
    • Do we want the initial one to not use updates and then push one to updates after the release that uses updates?
    • How does all of this affect nightly builds and releng composes?
      • Nightly builds uses head of master branch of git repo
  • Deadlines for process milestones
  • Some suggestions from Kevin.
  • We will probably go with proposed and track issues for adjustments for F15. This item should be closed after verifying there is an official schedule page.

• How to document which spins get iso's made by releng (and possibly nightly builds)
  • We think they base off of a wiki page.

• Team tasks for making sure Spins look OK and releng has what they need?
  • I.e. what could we have done to have prevented missing the Moblin spin?
    • We think a wiki page needed to be updated when we decided to go forward with Moblin.
    • Need to make sure this ends up in process document with ownership.

• Do we need some sort of review process for changes to the live base ks?
  • For now changes will start being gated to the spins list.

• Do something with the Spins SIG membership list on our wiki page. It includes a number of people that haven't actively participated in a long time.
  • Maybe remove it?
  • Maybe reset it and let interested people add themselves back?
  • Maybe develop some critera for who is on that list?
• At one time an earlier version of the content at http://docs.fedoraproject.org/en-US/Fedora/13/html-single/Fedora_Live_Images/index.html was packaged and as part of the live image build was placed on the desktop. The file stopped being packaged a while ago and the cp command to put it on the desktop was recently removed because it was resulting in an error message during the compose process. Is this something we want included on the live desktop?
  • I asked about this and was told it was no longer packaged, but could be again if it was desired.

• 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?