From Fedora Project Wiki
(Undo revision 44893 by Renich (Talk))
m (Fix typo)
 
(69 intermediate revisions by 19 users not shown)
Line 1: Line 1:
= Minimal Installation =
+
{{admon/caution|Deprecated template!|From Fedora 20 the Feature process was replaced by the [[Changes | Planning Process]]!. Please, use the new [[Changes/EmptyTemplate | empty template]].}}
<!-- The name of your feature -->
+
 
 +
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill 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 making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
 +
 
 +
{{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
 +
 
 +
{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
 +
 
 +
 
 +
<!-- All fields on this form are required to be accepted by FESCo.
 +
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 +
 
 +
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->
 +
 
 +
= Feature Name <!-- The name of your feature --> =
  
 
== Summary ==
 
== Summary ==
 
+
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. -->
To have a "Minimal Installation" option with full yum support so one can start building a custom distribution from there.
 
  
 
== Owner ==
 
== Owner ==
<!--This should like to your home wiki page.  Your home wiki page should include an email address that you can be reached at should people want to contact you about helping with your feature or to request status -->
+
<!--This should link to your home wiki page so we know who you are-->
 +
* Name: [[User:FASAcountName| Your Name]]
  
* Name: [[User:Renich| Renich Bon Ciric]]
+
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
 +
* Email: <your email address so we can contact you, invite you to meetings, etc.>
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/X | Fedora X ]]  
+
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
 
* Last updated: (DATE)
 
* Last updated: (DATE)
 
* Percentage of completion: XX%
 
* Percentage of completion: XX%
Line 20: Line 34:
 
== Detailed Description ==
 
== Detailed Description ==
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 
This "Minimal Install" option would be very useful for a lot of things and it would let fedora be installed in a PC with minimal requirements and be used in many other areas that it is right now.
 
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
This would expand the range of uses that one can give to Fedora. Not just for installing into minimal requirement PCs but, also, one could build an entire new system from almost scratch and as small as possible (small footprint and all) but, always, with fedora's base support (yum, iptables, lbs, udev, etc) and use revisor or any other tool to make custom distributions.
 
  
 
== Scope ==
 
== Scope ==
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
It requires striping Fedora from any package that is not essential in a practical way and, maybe, a custom kernel. Any GUI or unneeded lib would be omitted and this would make the system much smaller.
+
== How To Test ==
 +
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.  
  
== Test Plan ==
+
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The QA team will turn this information into a more complete test plan.  The more specific you can be, the better the final test plan will be.  
 
  
A good Test Plan should answer these four questions:
+
A good "how to test" should answer these four questions:
  
 
0. What special hardware / data / etc. is needed (if any)?
 
0. What special hardware / data / etc. is needed (if any)?
1. How do you prepare your system to test this feature? What packages
+
1. How do I prepare my system to test this feature? What packages
 
need to be installed, config files edited, etc.?
 
need to be installed, config files edited, etc.?
2. What specific actions do you perform to check that the feature is
+
2. What specific actions do I perform to check that the feature is
 
working like it's supposed to?
 
working like it's supposed to?
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
 
-->
 
-->
 
# Analise the standard installation package list.
 
# make a list of essential packages and their deps.
 
# Analise if the deps are really necessary and do further stripping.
 
# Test install and see if anything else can be stripped or is needed.
 
# Make 3 or 4 kickstart files and let the community vote on them.
 
  
 
== User Experience ==
 
== User Experience ==
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
# The admins would be very happy to make a minimal installation, even if they don't need it, and start adding their own list of packages using yum.
 
# Developers that are interested in making some new Fedora-based distro will love it and use it much.
 
  
 
== Dependencies ==
 
== Dependencies ==
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
No deps... just a kickstart file.
 
  
 
== Contingency Plan ==
 
== Contingency Plan ==
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 
* Use a standard installation.
 
  
 
== Documentation ==
 
== Documentation ==
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
+
*
  
 
== Release Notes ==
 
== Release Notes ==
<!-- The Fedora Release Notes inform end-users how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
+
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
+
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
"Minimal Installation" should be use in the case of minimum requirements, firewall boxes or custom distrobution development. It contains only the essential packages and it will not have the features you'd expect from a standard installation.
+
*
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
 +
* See [[Talk:Features/Your_Feature_Name]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
  
* See [[Talk:Features/YourFeatureName]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
 
 
 
----
 
  
[[Category:FeatureReadyForWrangler]]
+
[[Category:FeaturePageIncomplete]]
 
<!-- When your feature page is completed and ready for review -->
 
<!-- When your feature page is completed and ready for review -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Latest revision as of 14:21, 19 January 2015

Stop (medium size).png
Deprecated template!
From Fedora 20 the Feature process was replaced by the Planning Process!. Please, use the new empty template.
Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed



Feature Name

Summary

Owner

  • Email: <your email address so we can contact you, invite you to meetings, etc.>

Current status

  • Targeted release: [[Releases/<number> | Fedora <number> ]]
  • Last updated: (DATE)
  • Percentage of completion: XX%


Detailed Description

Benefit to Fedora

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion