From Fedora Project Wiki

(livecd-tools)
 
(33 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 15: Line 12:
== Previous Meeting Logs ==
== Previous Meeting Logs ==


[http://meetbot.fedoraproject.org/teams/spins-sig/ Meetbot logs]
[http://meetbot.fedoraproject.org/sresults/?group_id=spins-sig&type=team Meetbot logs]


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


* Nightly composes
== Future Agenda ==
** Spins are building again.
** Games spin is very close to max size.
** Desktop CD is still oversize, but perl is still being dragged in until we get a new anaconda.
 
* Install ks repo directives question?
** The install ks does some things differently in order to provide sources and updates aren't wanted. But it is using --excludes on the repo commands. I think this to to block anything that drags in certain packages, rather than excluding packages that might be listed in a group.
** Is there any issue with install doing this (though it's in releng's area)?
** Is this something we want to allow for live images?
 
* 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.
** The repo commands in the ks files that use them aren't consistent. This should also be fixed.
** The proposal is at: https://fedoraproject.org/wiki/Spins_repo_directives
 
* FYI - Bruno will be looking at getting a new livecd-tools release out within a week. Some bug fixes and a couple of new scripts.
 
* 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 has not finished this yet.


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

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?