From Fedora Project Wiki

(livecd-tools)
(Remove some stuff that's no longer relevant.)
Line 18: Line 18:


== Current Agenda ==
== Current Agenda ==
* Bruno and Kevin also have trac admin access
** Getting some more relevant milestones set up and maybe cleaning up the old ones is a task.
* Push livecd-tools 033 to F13 and F12 now to allow build rawhide/F14 images?
* Nightly composes
** Status?
* 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?
* When should we change repo's in the spins?
Line 37: Line 26:
*** 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.
*** 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.
** The answer to these needs to be added to the schedule.
 
** Bruno is going to write up a proposal taking into account nirik's suggestion.
 
* Late proposal for music spin
** We agreed to defer it, so unless David wants to discuss this, we shouldn't need to. But I want to leave the pointers just in case.
** https://fedoraproject.org/wiki/Music_Creation_Lite_Spin
** http://members.iinet.net.au/~timmsy/spin/fedora-livecd-music-creation.ks
** Issues noted:
*** http://lists.fedoraproject.org/pipermail/spins/2010-July/001324.html


* Should owners be required to sign off on an RC of their spin before GA?
* Should owners be required to sign off on an RC of their spin before GA?
Line 50: Line 32:
** Possibly discuss recommend minimum test plans to execute
** 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.
** 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 [http://lists.fedoraproject.org/pipermail/spins/2010-May/001101.html Dan Walsh's changes] proposed for live-base to make maintaining his sandbox spin simpler.
* Getting a review of [http://lists.fedoraproject.org/pipermail/spins/2010-May/001101.html Dan Walsh's changes] proposed for live-base to make maintaining his sandbox spin simpler.

Revision as of 21:56, 16 August 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

  • 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.
    • Bruno is going to write up a proposal taking into account nirik's suggestion.
  • 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.
  • 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?