FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

LinkBack Thread Tools
Old 06-02-2008, 12:59 PM
Jeroen van Meeuwen
Default Spin SIG meeting (Tue Jun 10, 18:00 UTC)

Hello there,

I would like the Spin SIG members, current spin maintainers and other
enthusiasts to get together in #fedora-meeting at Tuesday, June 10th, at
18:00 UTC, so you are hereby invited to join us.

There's several items on the Agenda.

- How come we did not have Fedora 9 Spins of:
- Electronic Lab
- Games
- Developer

The Electronic Lab does have a certain amount of people interested but
no one "accountable" maintainer, while there was a lot of exposure,
whereas the Developer spin did not get any maintenance, afaics.
Regardless, we will need to contact maintainers during the Alpha-Beta
time-frame to update their spins, or come up with a policy/guideline for
the maintainers to hold on to.

- Drafted policies

I've submitted the drafted policies[1] for the Spin SIG to -devel, but
they did not get much feedback. We need to determine if they are
sufficient to enter the F10 development/release cycle with.

- The release process / spin process

Right now, we put in a request at the Release Engineering Team[2] to
have certain spins spun. This may or may not be "golden" spins, but
regardless, I think we prefer to trigger building our own spins, and
then hand one over to Release Engineering, that can be released. Let's
talk about this at our meeting.

- Updates to kickstarts are submitted... where?

I think the spin-kickstarts GIT repository at fedorahosted.org[3] needs
to have the latest kickstarts, whereas now developments still take place
in the livecd-tools GIT repository at fedorahosted.org[4]. I've tried to
come up with a branching policy that makes development go into the
master branch, which we branch off for maintenance purposes every
release. I've also been thinking about a commit access policy, and I
think having commit access for at least the primary maintainers of each
spin makes the most sense.

- kickstarts RPM package for "Home Use"

A review request has been submitted for a "spin-kickstarts" package[5],
which I'd like you to look at and give some feedback on. This is to
enable people getting approved (by Spin SIG and Board) kickstarts to
their own computers in a controllable fashion.

If you have any other topics you want to discuss at the meeting, please
let me know; there's a bunch of kickstarts from Rahul that need
reviewing as well[6].

I hope to see you all so that we can accomplish something (and a little
more). I'm also planning to have a HackFest/BarCamp session at FUDCon in
Boston[7], in two weeks.

Kind regards,

Jeroen van Meeuwen

[1] http://fedoraproject.org/wiki/SIGs/Spins
[2] https://fedorahosted.org/rel-eng/ticket/24
[3] http://git.fedorahosted.org/git/?p=spin-kickstarts.git
[4] http://git.fedorahosted.org/git/?p=livecd
[5] https://bugzilla.redhat.com/show_bug.cgi?id=448072
[6] http://fedoraproject.org/wiki/SIGs/Spins/Agenda
[7] http://fedoraproject.org/wiki/FUDCon/FUDConF10

fedora-devel-list mailing list

Thread Tools

All times are GMT. The time now is 09:47 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org