From Fedora Project Wiki

(evolution)
 
(20 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.


== How this page is used ==
== How this page is used ==
Line 13: 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 ==


* How is new livecd-tools working?
== Future Agenda ==
** Seems OK in F14.
** Some people are trying it in F13 to build F14 and it seems to help.
 
* Other issues affecting Spin builds?
** Design hasn't built since 2010-09-08. [https://bugzilla.redhat.com/show_bug.cgi?id=635833 gnome-python2-evolution - libcamel  dependency issue]. A new version of gnome-python2-evolution is available in testing. Can we get this moved to stable soon? (Possibly related is other evolution updates requiring the latest gnome-panel build. The whole set may need to move at once?)
** Some of the spins targeting a CD are oversize.
*** Design was oversize on its last build.
*** Xfce is still oversize, though I have from them in the last week that they are aware of this and are working on it.
** AOS i686 build failed.
*** Looks like the build occurred during a repo update which broke things.
** Meego x86_64 build failed.
*** Probably a repo update during build.
 
* 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 [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?