From 23000b708d967cdeafa6b86305e3db25ae8ecf9a Mon Sep 17 00:00:00 2001
From: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date: Sep 24 2020 00:22:19 +0000
Subject: Add "Spins" page


---

diff --git a/fesco/modules/ROOT/nav.adoc b/fesco/modules/ROOT/nav.adoc
index f56ad4f..3d601c7 100644
--- a/fesco/modules/ROOT/nav.adoc
+++ b/fesco/modules/ROOT/nav.adoc
@@ -4,6 +4,7 @@
 ** xref:Updating_Fedora_Engineering_Steering_Committee_Members.adoc[Updating FESCo members]
 ** https://fedoraproject.org/wiki/FESCo_meeting_process[FESCo meeting process]
 * Policy documents
+** xref:Spins.adoc[Spins]
 ** xref:Bundled_Software_policy.adoc[Bundled software policy]
 ** xref:Mass_package_changes.adoc[Mass package changes]
 ** xref:Package_maintainer_responsibilities.adoc[Package maintainer responsibilities]
diff --git a/fesco/modules/ROOT/pages/Spins.adoc b/fesco/modules/ROOT/pages/Spins.adoc
new file mode 100644
index 0000000..93a1286
--- /dev/null
+++ b/fesco/modules/ROOT/pages/Spins.adoc
@@ -0,0 +1,34 @@
+= Spins
+
+Spins must obey the
+link:https://fedoraproject.org/wiki/Legal:Main[Fedora Legal] guidelines and
+link:https://docs.fedoraproject.org/en-US/project/code-of-conduct/index.html[Code of Conduct].
+
+== Adding new Spins
+
+Addition of new Spins follows the standard link:https://docs.fedoraproject.org/en-US/program_management/changes_policy/[Change process].
+
+A new variant must be proposed as a
+link:https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_system_wide_changes[System-wide Change],
+subject to discussion with the community and various stakeholders and approval by FESCo.
+The change page must describe the motivation for the new Spin,
+governance and ownership,
+and the differences in design from other Spins and Editions
+(link:https://pagure.io/fesco/issue/1972[FESCo #2418]).
+
+Bold and novel designs are encouraged, even if it is not possible to
+say with certainty at the time of the approval whether they can be
+delivered successfully or if users will find them useful.
+
+== Keepalive check
+
+In each release cycle, the Fedora Program Manager will send a request to the owners of all Spins
+to confirm that they should be built for the next release
+(link:https://pagure.io/fesco/issue/1972[FESCo #1972]).
+
+If there is no response from Spin owners, Program Manager will announce the intent to drop the Spin.
+If nobody takes it over, that Spin will be dropped for that release.
+
+Responses to the keepalive check must be made sufficiently in advance of branching
+to allow Release Engineering to react to the results.
+See the schedules for individual releases for details.