This page describes the process for creating a new Spin or adopting an abandoned Spin.
There are a few steps you’ll need to do first. Some of these may seem obvious, but it’s best to be clear.
To start a new Spin, you’ll need to file a Self-Contained Change proposal. Since Release Engineering will need to start building the Spin, you’ll need to submit a ticket with Release Engineering. If you want the Spin to have a non-descriptive name (for example: "Fedora Llamanator" instead of "Fedora Llama Herder Spin"), file a trademark issue with the Fedora Council. But before you do any of that…
In order to be successful, there are a few things you should do as you’re starting the process.
Find helpers. Whether it’s a single co-maintainer or a full team, having help will lighten the load. It gives you the ability to step away when you need to. And if you’re working with someone else, you can make each other’s ideas better.
Set your goals. You can make a Spin for just about any reason. But if you don’t identify the reason, you’ll have a hard time building a solution for it. Who are you trying to serve? What problem will you solve for them? How will you solve it?
Make sure a Spin is the right solution. Is a software group in repo a better solution?
Great! Your proposal is approved. Now it’s time to make it happen.
Work with Release Engineering to build the Spin. See the Maintaining a Spin docs for more about this.
Open a ticket with the Websites & Apps team. You’ll need to get your Spin added to the website if you want people to be able to find it. The Websites & Apps team can help you get ready.
Open a ticket with the Design team. At a minimum, you’ll want a header image for the website. You may also want additional art for the website, stickers, etc. The Design team repo is your starting point for those requests.
If a Spin is abandoned and you want to take it over, it doesn’t take much beyond raising your hand. If the Program Manager has announced that the Spin is abandoned, just reply to their email. For a Spin that has been retired, first make sure there’s a good use case for bringing it back. If there is, submit a Self-Contained Change proposal as if it were a new Spin.