From Fedora Project Wiki

No edit summary
 
(91 intermediate revisions by 2 users not shown)
Line 2: Line 2:


== Current schedule ==
== Current schedule ==
 
We have ceased meetings again.
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 ==
== How this page is used ==
Line 12: Line 9:


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.
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 ==
[http://meetbot.fedoraproject.org/sresults/?group_id=spins-sig&type=team Meetbot logs]


== Current Agenda ==
== Current Agenda ==


* Advertise for a new Spins Wrangler
== Future Agenda ==
 
* Leader or at least a chair?


* 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.
** I think this could be useful for other custom spins as well.
** Having a way to add users when running livecd-iso-to-disk might also be useful, though maybe not practical.


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


* New meeting time?
* It has [http://lists.fedoraproject.org/pipermail/spins/2010-June/001176.html 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.
* Schedule for F14?
** Is this something we would do ourselves, or would docs or design team do it?
** 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?

Latest revision as of 23:15, 29 July 2015

Spin SIG meeting information

Current schedule

We have ceased meetings again.

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

Future Agenda

  • Getting a review of Dan Walsh's changes proposed for live-base to make maintaining his sandbox spin simpler.
    • I think this could be useful for other custom spins as well.
    • Having a way to add users when running livecd-iso-to-disk might also be useful, though maybe not practical.
  • 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?