From Fedora Project Wiki

(Spin sizes)
(Spin issues)
Line 20: Line 20:


* Other issues affecting Spin builds?
* Other issues affecting Spin builds?
** Some of the spins targeting a CD are oversize.
** Some of the spins targeting a CD are oversize. (KDE, xfce)
** Design hasn't built since 2010-09-08. gnome-python2-evolution - libcamel  dependency issue.


* Meego trademark usage change.
* Meego trademark usage change.

Revision as of 19:54, 20 September 2010

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

  • How is new livecd-tools working?
  • Other issues affecting Spin builds?
    • Some of the spins targeting a CD are oversize. (KDE, xfce)
    • Design hasn't built since 2010-09-08. gnome-python2-evolution - libcamel dependency issue.
  • Meego trademark usage change.
    • Meego won't pass compliance, so we can use the trademark for the spin, but only refer to it in a factual manner. The design team will need to provide Peter with some help, but Spins SIG shouldn't need to do anything special.
    • Once this is resolved, I take it out of needing board approval.
  • 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 still doesn't have a proposed set yet.
  • 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.
    • 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?