No edit summary |
|||
Line 27: | Line 27: | ||
* {{check}} Do test the release thoroughly before submitting it to ReleaseEngineering | * {{check}} Do test the release thoroughly before submitting it to ReleaseEngineering | ||
* {{check}} Do try to establish yourself with a SIG (Special Interest Group) before submitting a respin | * {{check}} Do try to establish yourself with a SIG (Special Interest Group) before submitting a respin | ||
* {{Template:Warning}} Don't assume you can change your spin more | * {{Template:Warning}} Don't assume you can change your spin more than once per release | ||
* {{Template:Warning}} Don't assume your spin will get accepted, make it a worthwhile, compelling spin | * {{Template:Warning}} Don't assume your spin will get accepted, make it a worthwhile, compelling spin | ||
* {{Template:Warning}} Don't be discouraged if your respin is rejected, especially if your SIG is new, establish yourself first | * {{Template:Warning}} Don't be discouraged if your respin is rejected, especially if your SIG is new, establish yourself first |
Revision as of 03:08, 23 July 2010
Custom Spins
A custom spin of Fedora is a community release that has been created using one of the Fedora remixing tools, preferably either Pungi (regular images) or livecd-creator (Live CD/DVD's). Custom spins should be strict subset's of packages available in the official Fedora repositories. The iso images created during the build process are hosted at http://spins.fedoraproject.org/. Unlike the official releases (http://torrent.fedoraproject.org/), custom re-spins are created and maintained by Fedora's SIGs .
Some re-spins are officially supported by Fedora. An example of this is the standard GNOME and KDE spins.
Approval Process
The approval process for having Fedora host a spin and being allowed to use the Fedora trademarks are as follows.
- Submit your spin proposal to ReleaseEngineering for technical approval.
- Submit your spin proposal to the Board for approval to use the Fedora trademarks.
- Submit your final kickstart script to ReleaseEngineering to be built and uploaded to http://spins.fedoraproject.org/
Guidelines for Success
Official Fedora spins must only contain bits that are in Fedora. Those wanting a special theme or package must have it in the official Fedora repositories or it will not be considered. The respin can then install it as a default.
Do's and Don'ts
- Do include only Fedora bits
- Do test the release thoroughly before submitting it to ReleaseEngineering
- Do try to establish yourself with a SIG (Special Interest Group) before submitting a respin
- Don't assume you can change your spin more than once per release
- Don't assume your spin will get accepted, make it a worthwhile, compelling spin
- Don't be discouraged if your respin is rejected, especially if your SIG is new, establish yourself first