From Fedora Project Wiki
About the Spins SIG
The Spins SIG develops, releases and maintains the Fedora Spins as available on http://spins.fedoraproject.org, and develops, releases and maintains the utilities used to create spins.
Who's Who in the Spins SIG?
- Joe Sixpack
- Chair
- John Doe
- Secretary
- Jane Doe
- Developer
- Max Imum
- Developer, Infrastructure liaison
- Min Imum
- Quality Assurance liaison
- Joe Average
- Release Engineering liaison
Who Does What?
- Chair
- Calls and organizes meetings, (co-)maintains schedules, approves guideline and process changes
- Secretary (also called Wrangler)
- Applies the Spins processes, (co-)maintains schedules
- Developer
- Develops and maintains the utilities required
- Infrastructure liaison
- The Spins SIG interface to the Infrastructure team, tasked with, amongst others, build and compose facilities
- Quality Assurance liaison
- The Spins SIG interface to the Quality Assurance team, tasked with, amongst others, organizing test days and test-case development and maintenance.
- Release Engineering liaison
- The Spins SIG interface to the Release Engineering team, tasked with, amongst others, the various composing tasks and maintaining and applying release criteria.
Spins Development and Release Cycle
- First, a spin is proposed.
- After review by the Spins SIG developers, it is included in the spin-kickstarts'
custom/directory - Should the spin be released by and through the Fedora Project, Infra, QA and Rel-Eng together with the spin maintainer determine a feasible schedule conform the release schedule guidelines
Spin Proposal
- A spin is proposed by submitting the kickstart for the new spin and a description to the Spins SIG. See also: Action Items for a new Spins Proposal
- For the person proposing the new spin, attendance at the next Spins SIG meeting is mandatory, or the new spin defaults to being rejected.
Spin Release Schedule
- The release schedule for any given spin is to be whipped up by the Release Engineering liaison, in conjunction with the spin maintainer and the Quality Assurance liaison. This is what meetings and Fedora Talk are for.
Spin Proposal: Action Items
- Include the kickstart in the spin-kickstarts repository, under the
custom/directory. - Make the necessary changes to the Makefile.am, .spec.in, etc.
- Launch a livecd compose task against koji for the latest current release. (Note: rawhide may be too volatile for this item)
- Put a review task on the meeting agenda for the first upcoming Spins SIG meeting.