Spins SIG: Difference between revisions

Latest revision as of 19:17, 8 August 2018

The Spins Special Interest Group reviews, tests and approves Fedora Spins. Participants in this SIG are delegates from QA, Release Engineering, the Fedora Project Board, Infrastructure and FESCo as well as spin owners.

What is it we do?

The purpose of the Spins SIG is to oversee the development of an evolving set of technical best practices to be applied to all community spin concepts. The Spins SIG will also oversee the continued maintenance of approved community spins in the Kickstart Pool, and will regulate the use of any infrastructure as it becomes available for use for the Spins SIG. For example, webspace at http://spins.fedoraproject.org/ will be made available for spin descriptions. New spin concepts first come to the Spins SIG for discussion and technical review. Once the Spins SIG comes to a consensus as to technical merit, the benefit to Fedora, and the overall feasibility of a proposed spin, that spin concept is passed to the Board for final trademark approval.

Trackers

Tracker Pages:

README Documents

These are the pages the Spins SIG maintains.

Spins Guidelines - Guidelines for people to submit spin concepts.
Kickstart Pool - A draft proposal for a kickstart pool.
Spins Process - A draft on the Community Spin Submission Process.
Localized Spins - A draft on how Localized Spins should be composed.
Test Plans - Test Plans for Spins in general
Spins_SIG_Review_Checklist - More guidelines for kickstart files
Recurring Releases - The process of recurring releases of a given Spin
New Spin Page Template - A template for new Spins to help create their Spins page
Discontinued Spins Process - How to deal with discontinued spins.
Rebuilding Spins Packages - How and when to rebuild the spin-kickstarts packages
Spins repo directives - When to adjust repo directives in base spins
Spins Wrangler - About the spins wrangler position
Spins release page - List of spins for the upcoming release
Spins Lead - Need to write a job description for this position
Spin Owners - Need to write expectations for Spin Owners

Tracking Spins SIG tasks

We keep track of some of our outstanding tasks and issues using the spins-kickstarts trac instance.
There is also a spins-specific part of the schedule for the upcoming release.

Test spins

Nightly builds from the kickstart files in the git repository. These are what will be available for the alpha and beta release for alternate spins (those under the Spins SIG).
Kickstart files are available from the spin-kickstarts git repository.

Meetings

We had been meeting at 2000 UTC in #fedora-meeting-2, but we seem to have stopped again.

Mailing List

spins (Archives)
- Low traffic
- Commit notices for spin-kickstarts git repo are posted
- Trac ticket change messages are posted

Wish List

A way to install spins into an existing install.
- What exactly this would mean needs to be worked out first.
  - Just packages and no special setup?
  - Would this just add packages to the current install, or possibly remove some?
  - Would there be any way to remove a spin once it was installed?

@@ Line 3: / Line 3: @@
 == What is it we do? ==
-The purpose of the Spins SIG is to oversee the development of an evolving set of technical best practises to be applied to all community spin concepts.  The Spins SIG will also oversee the continued maintenance of approved community spins in the Kickstart Pool, and will regulate the use of any infrastructure as it becomes available for use for the Spins SIG. For example webspace at http://spins.fedoraproject.org/ will be made available for spin descriptions. New spin concepts first come to the Spins SIG for discussion and technical review. Once the Spins SIG comes to a consensus as to technical merit, the benefit to Fedora, and the overall feasibility of a proposed spin, that spin concept is passed to the Board for final trademark approval.
+The purpose of the Spins SIG is to oversee the development of an evolving set of technical best practices to be applied to all community spin concepts.  The Spins SIG will also oversee the continued maintenance of approved community spins in the Kickstart Pool, and will regulate the use of any infrastructure as it becomes available for use for the Spins SIG. For example, webspace at http://spins.fedoraproject.org/ will be made available for spin descriptions. New spin concepts first come to the Spins SIG for discussion and technical review. Once the Spins SIG comes to a consensus as to technical merit, the benefit to Fedora, and the overall feasibility of a proposed spin, that spin concept is passed to the Board for final trademark approval.
 == Trackers ==
@@ Line 13: / Line 13: @@
 * [[:Category:Spins_Ready_For_SIG | Spins Ready for SIG]]
 * [[:Category:Spins_Ready_For_Board | Spins Ready for Board]]
+* [[:Category:Spins_Fedora_24 | Accepted Spins for Fedora 24]]
 * [[:Category:Spins_Fedora_23 | Accepted Spins for Fedora 23]]
 * [[:Category:Spins_Fedora_22 | Accepted Spins for Fedora 22]]
@@ Line 55: / Line 56: @@
 * [http://dl.fedoraproject.org/pub/alt/nightly-composes/ Nightly builds] from the kickstart files in the git repository. These are what will be available for the alpha and beta release for alternate spins (those under the Spins SIG).
-* Kickstart files are available from the [http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=summary spin-kickstarts git repository] .
+* Kickstart files are available from the [http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=summary spin-kickstarts git repository].
 == Meetings ==
@@ Line 62: / Line 63: @@
 == Mailing List ==
-* {{fplist|spins}} ([http://lists.fedoraproject.org/pipermail/fedora-spins/ Archives])
+* {{fplist|spins}} ([https://lists.fedoraproject.org/archives/list/spins@lists.fedoraproject.org/ Archives])
 ** Low traffic
 ** Commit notices for spin-kickstarts git repo are posted

Search