From Fedora Project Wiki

(remove old stuff and added new stuff)
(repo question)
Line 31: Line 31:
* Creating a branch (or other location) for development of ks files before they have been accepted?
* Creating a branch (or other location) for development of ks files before they have been accepted?
** The Music spin guys would like to have a place where shared development of the ks file can occur. Currently we don't support that, but we probably should.
** The Music spin guys would like to have a place where shared development of the ks file can occur. Currently we don't support that, but we probably should.
* When should we change repo's in the spins?
** rawhide to release?
*** I think just after the development branch, but may depend on compose machine.
*** Certainly by the time we do the kickstart branch.
** release to rawhide?
*** If it ends up changing in master (that depends on the answer to the above), then when we do the kickstart branch we should do it.
** The answer to these needs to be added to the schedule.


* Late proposal for music spin
* Late proposal for music spin

Revision as of 01:54, 31 July 2010

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

Meetbot 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.)
  • Nightly composes
    • Unable to mount ext3 image
      • Other people aren't seeing this when they do builds. What's the difference?
    • Black screen
      • fedora-logos was changed to supposedly match a change in anaconda but it broke live images.
      • generic-logos has been changed to match fedora-logos.
      • A fix has been committed for this and a new livecd-tools rpm is available in rawhide.
  • Creating a branch (or other location) for development of ks files before they have been accepted?
    • The Music spin guys would like to have a place where shared development of the ks file can occur. Currently we don't support that, but we probably should.
  • When should we change repo's in the spins?
    • rawhide to release?
      • I think just after the development branch, but may depend on compose machine.
      • Certainly by the time we do the kickstart branch.
    • release to rawhide?
      • If it ends up changing in master (that depends on the answer to the above), then when we do the kickstart branch we should do it.
    • The answer to these needs to be added to the schedule.


  • Should owners be required to sign off on an RC of their spin before GA?
    • Process doc. (Status if it isn't done yet.)
    • Possibly discuss recommend minimum test plans to execute
    • Bruno is not going to get to this before vacation as a lot of higher priority stuff is outstanding.
  • livecd-tools build coming soon.
  • spin-kickstarts build coming soon.
  • 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?