From Fedora Project Wiki

Page title matches

Page text matches

  • = Distribution of Spins, the problem = ...ere's constraints as to how much data the Fedora Project can distribute to it's mirrors.
    1 KB (215 words) - 20:13, 26 June 2009
  • ...live spin serves as a way to try OpenShift Origin, demo it or even develop it. ...and use. The installation will be all-in-one with possiblity of extending it by adding new application nodes.
    2 KB (265 words) - 20:41, 22 November 2013
  • = Spins repo directives = ** This is included by spins (often indirectly).
    549 bytes (84 words) - 16:44, 29 June 2013
  • The Spins Special Interest Group reviews, tests and approves Fedora Spins. Participants in this SIG are delegates from QA, Release Engineering, the F == What is it we do? ==
    5 KB (730 words) - 19:17, 8 August 2018
  • <!-- When your spins page is completed and ready for review, remove Category:Spins_in_Development and change it to Category:Spins_Ready_For_Wrangler
    2 KB (318 words) - 13:18, 16 January 2015
  • ...an OpenStack enabled Fedora out of the box, providing a Cloud on one node. It's intended as demo material. Deploying OpenStack based on this spin to seve <!-- When your spins page is completed and ready for review,
    2 KB (322 words) - 08:23, 28 November 2012
  • It could be used in Uni CS labs, etc and by people who want a portable Haskell <!-- When your spins page is completed and ready for review,
    2 KB (377 words) - 07:05, 29 October 2010
  • This page describes the DOs and DONTs for Spins being submitted for review to the [[Spins_SIG|Spin SIG]] . ...nclude guidelines with regards to the snippet layout as proposed in [[SIGs/Spins/KickstartPool|Kickstart Pool]] .
    3 KB (427 words) - 05:40, 18 April 2021
  • It is intended for users who want to easily do smaller custom installations by should be more stable during the development cycle than larger spins.
    4 KB (614 words) - 10:02, 23 January 2012
  • {{admon/important|If you would like to improve this content, it is recommended to find fact from here. http://fedoraproject.org/wiki/Featur == Spins ==
    2 KB (234 words) - 14:08, 18 September 2016
  • * anyone to learn about what spins are and how to use them * users to be able to browse, download, and start using spins
    4 KB (590 words) - 20:38, 27 October 2013
  • ** Policy on spins-list membership for spin maintainers. ...squashfs patches to the kernel list on December 7th. So effectively larger spins may be doable for F13.
    1 KB (242 words) - 02:05, 15 December 2009
  • ...edora {{FedoraVersionNumber|next}}, and so forth, fall under the Recurring Spins process. ...jor changes to the spin from going unnoticed. It is not like all recurring spins will have to go through the entire review process step-by-step once more.
    3 KB (482 words) - 00:29, 29 August 2016
  • === Are spins required to have SELinux enabled? === * FESCo would like the Spins SIG to work on a proposal to make their guidelines(1) meet the QA Release C
    1 KB (197 words) - 08:02, 18 September 2016
  • ...rt Pool] . This does not imply inclusion in the official release, nor does it include being mirrored, tracked or seeded by the Fedora Project. = Live Spins =
    2 KB (308 words) - 01:00, 11 June 2009
  • It corresponds to the @basic-desktop-environment group in comps. ...arketing your product to the end user. This ends up on the details page on spins.fedoraproject.org, and may be used in the release notes. -->
    4 KB (678 words) - 07:42, 16 January 2013
  • ** biertie said the QA Test Day spin page looked OK. But wondered if it was necessary. ...p at a later meeting. Probably pages are both for the target group and the spins SIG, but maybe not.
    842 bytes (141 words) - 22:13, 5 October 2009
  • ...d to create a page for your spin at [http://spins.fedoraproject.org http://spins.fedoraproject.org]. What you'll need before you start creating these graphi ...pins directory on the front page of [http://spins.fedoraproject.org http://spins.fedoraproject.org]
    7 KB (1,047 words) - 06:20, 9 July 2011
  • = Discontinued Spins Process = When a spin is no longer being maintained the Spins SIG needs to do some clean up.
    1 KB (241 words) - 17:47, 11 July 2010
  • {{admon/important|This page is currently under review. It may contain incomplete or misleading data. ETA for the final version is Thu ...ead of time (we added this point to the Change process as releng requested it)
    9 KB (1,183 words) - 14:49, 31 January 2017
  • {{admon/important|This page is currently under review. It may contain incomplete or misleading data. ETA for the final version is Thu ...ead of time (we added this point to the Change process as releng requested it)
    9 KB (1,217 words) - 14:51, 31 January 2017
  • ...erse environment of packages, contributors, and spins. In most situations, it is possible for these elements to coexist without conflict, however, on occ * The opportunity to create almost infinite spins off of the Fedora packageset
    5 KB (826 words) - 15:29, 9 July 2009
  • ...ead of time (we added this point to the Change process as releng requested it) ...ven non-blocking), please use Fedora Change Management process and propose it ahead of time, so the community is prepared for such release.
    12 KB (1,660 words) - 13:44, 18 March 2019
  • ...pins Wrangler (check Wiki page Category Spins_Ready_for_SIG, and who moved it there) ...ny changes to application configuration files should therefore be motived (Spins page) and audited (risk, impact, feasibility, maintainability and motivatio
    3 KB (532 words) - 13:56, 30 June 2013
  • ...his spin is and what it will do. This information is used for the overall spins summary page for each release. --> ...arketing your product to the end user. This ends up on the details page on spins.fedoraproject.org, and may be used in the release notes. -->
    5 KB (895 words) - 04:44, 16 November 2013
  • === "Permanent" Spins === === Official Fedora Spins ===
    4 KB (538 words) - 00:30, 17 November 2009
  • = Fedora 11 Official Spins = ...re-installed, pre-configured, system images. This Spin is intended to make it easier for anyone (ISVs, developers, OEMS, etc) to create and deploy virtua
    2 KB (329 words) - 09:08, 18 September 2016
  • ...ill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before m <!-- All fields on this form are required to be accepted by the Spins SIG
    6 KB (957 words) - 16:10, 11 March 2014
  • <!-- All fields on this form are required to be accepted by the Spins SIG ...his spin is and what it will do. This information is used for the overall spins summary page for each release. -->
    6 KB (959 words) - 14:42, 20 August 2011
  • {{admon/important|This page is currently under review. It may contain incomplete or misleading data. ETA for the final version is Thu ...ead of time (we added this point to the Change process as releng requested it)
    16 KB (2,042 words) - 15:41, 1 June 2017
  • ...ead of time (we added this point to the Change process as releng requested it) ...ven non-blocking), please use Fedora Change Management process and propose it ahead of time, so the community is prepared for such release.
    15 KB (2,030 words) - 19:52, 10 September 2018
  • Moving to F16 target, the spin did not make it into Fedora 12 due to the current level of blacklisting.( RPM/file system b ...d like to get integrated with Fedora's Release Engineering and incorporate it into Koji.
    3 KB (533 words) - 10:08, 8 October 2011
  • ...ead of time (we added this point to the Change process as releng requested it) ...ven non-blocking), please use Fedora Change Management process and propose it ahead of time, so the community is prepared for such release.
    8 KB (1,070 words) - 14:53, 31 January 2017
  • ...ead of time (we added this point to the Change process as releng requested it) ...ven non-blocking), please use Fedora Change Management process and propose it ahead of time, so the community is prepared for such release.
    15 KB (1,849 words) - 13:32, 3 May 2018
  • {{Admon/caution|Use the change process| The spins now follow the [[Changes/Policy|standard change process]]. The information ...s]] to the Spins SIG mailing list at [mailto:spins@lists.fedoraproject.org spins@lists.fedoraproject.org], and creates a Spin Page (from the [[Spins_New_Spi
    9 KB (1,448 words) - 20:01, 20 August 2019
  • ...ead of time (we added this point to the Change process as releng requested it) ...ven non-blocking), please use Fedora Change Management process and propose it ahead of time, so the community is prepared for such release.
    14 KB (1,782 words) - 08:25, 25 September 2017
  • ...ists.redhat.com.au. Preferably link to the gmane.org archive as this makes it easier to read the threads. === Spins Info ===
    2 KB (251 words) - 21:31, 17 September 2016
  • <!-- All fields on this form are required to be accepted by the Spins SIG ...his spin is and what it will do. This information is used for the overall spins summary page for each release. -->
    5 KB (915 words) - 20:10, 10 April 2021
  • ...t a defining vision for the Project and enable other groups to work toward it, without excluding those who want to do other things * (Combined) Issues with spins (Can spins change enough of the distro, "target audience")
    2 KB (370 words) - 09:20, 18 September 2016
  • <!-- This anchor doesn't need to change, since the page title says it all. ...ection are all for the creation and maintenance of docs relating to custom spins of Fedora. This includes docs about livecd-tools, pungi and Revisor.
    2 KB (236 words) - 21:36, 19 September 2016
  • Build new releases of Anaconda to support the creation of LiveCDs and Spins for currently supported Fedora releases (f12, f13, f14 at this time). It will not:
    1 KB (203 words) - 18:55, 29 September 2013
  • ...anding agenda items. Stuff will be added when it comes up and removed when it has been dealt with. [http://meetbot.fedoraproject.org/sresults/?group_id=spins-sig&type=team Meetbot logs]
    2 KB (271 words) - 23:15, 29 July 2015
  • <!-- All fields on this form are required to be accepted by the Spins SIG ...his spin is and what it will do. This information is used for the overall spins summary page for each release. -->
    7 KB (1,206 words) - 19:30, 5 December 2012
  • ...('''Kate''') is an open-source text editor developed by the KDE community. It has several advanced text editor features, but no IDE-specific features lik ...on (which utilizes the GNOME desktop environment) one will need to install it manually, by running:
    605 bytes (85 words) - 12:03, 8 January 2017
  • <!-- All fields on this form are required to be accepted by the Spins SIG ...suite alternative that includes OpenOffice.org, Thunderbird and Lightning. It will be based on the Fedora Desktop Spin but with a revised package list.
    6 KB (1,060 words) - 18:57, 17 July 2010
  • <!-- All fields on this form are required to be accepted by the Spins SIG ...pin is now available at [https://spins.fedoraproject.org/cinnamon/ https://spins.fedoraproject.org/cinnamon/]
    5 KB (791 words) - 04:03, 23 November 2015
  • <!-- All fields on this form are required to be accepted by the Spins SIG ...his spin is and what it will do. This information is used for the overall spins summary page for each release. -->
    6 KB (976 words) - 22:14, 17 September 2016
  • ...Spins SIG is pleased to announce the availability of the following Fedora Spins. These Spins have met technical requirements and been approved by Fedora Release Enginee
    3 KB (445 words) - 09:11, 18 September 2016
  • * It will better to break this into sub-modules targeting different audiences. G * Spins are good for every audience, so that's a keeper.
    3 KB (511 words) - 21:02, 15 March 2010
  • [[File:Spins-banner_security.png]] <!-- All fields on this form are required to be accepted by the Spins SIG
    4 KB (526 words) - 19:53, 26 July 2022
View (previous 50 | ) (20 | 50 | 100 | 250 | 500)