From Fedora Project Wiki

No edit summary
No edit summary
Line 15: Line 15:
== Current Agenda ==
== Current Agenda ==


* Advertise for a new Spins Wrangler
* Pick a name for our meetbot area (probably fedora-spins)


* Leader or at least a chair?
* Leader or at least a chair?
* New meeting time?
* Advertise for a new Spins Wrangler


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


* Process updates noted in [http://lists.fedoraproject.org/pipermail/spins/2010-May/001143.html Paul's message].
* Process updates noted in [http://lists.fedoraproject.org/pipermail/spins/2010-May/001143.html Paul's message].
* New meeting time?


* Schedule for F14?
* Schedule for F14?

Revision as of 18:08, 2 June 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.

Current Agenda

  • Pick a name for our meetbot area (probably fedora-spins)
  • Leader or at least a chair?
  • New meeting time?
  • Advertise for a new Spins Wrangler
  • Getting a review of Dan Walsh's changes proposed for live-base to make maintaining his sandbox spin simpler.
  • Schedule for F14?
    • Branch ks repo for F14?
    • Branch ks repo for F15?
    • 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?
    • Deadlines for process milestones
  • Documenting make spin-kickstart releases from the git repo.
  • How to document which spins get iso's made by releng (and possibly nightly builds)
  • 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?