|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| <!-- Self Contained or System Wide Change Proposal?
| |
| Use this guide to determine to which category your proposed change belongs to.
| |
|
| |
|
| Self Contained Changes are:
| |
| * changes to isolated/leaf package without the impact on other packages/rest of the distribution
| |
| * limited scope changes without the impact on other packages/rest of the distribution
| |
| * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
| |
|
| |
| System Wide Changes are:
| |
| * changes that does not fit Self Contained Changes category touching
| |
| * changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
| |
| * changing system defaults
| |
|
| |
| For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
| |
| improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).
| |
|
| |
| We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
| |
| -->
| |
|
| |
| <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->
| |
|
| |
| <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->
| |
| = Fedora Media Writer as Primary Downloadable =
| |
|
| |
| == Summary ==
| |
| The new Fedora Media Writer that is being finished has an overhauled, more user friendly interface. Because USB sticks are the most common way to install Fedora, it should be the primary download option. It cover the whole installation media creation, it lets the user pick the right flavor of Fedora, downloads its image, and copies it to a USB drive.
| |
|
| |
| == Owner ==
| |
| <!--
| |
| For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
| |
| This should link to your home wiki page so we know who you are.
| |
| -->
| |
| * Name: [[User:mbriza| Martin Briza]], [[User:eischmann| Jiri Eischmann]]
| |
| <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
| |
| * Email: mbriza redhat com, eischmann redhat com
| |
| * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
| |
| <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
| |
| * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
| |
| -->
| |
| <!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
| |
| * Product:
| |
| * Responsible WG:
| |
| -->
| |
|
| |
| == Current status ==
| |
| * Targeted release: [[Releases/25 | Fedora 25 ]]
| |
| * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
| |
| <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
| |
| Bugzilla states meaning as usual:
| |
| NEW -> change proposal is submitted and announced
| |
| ASSIGNED -> accepted by FESCo with on going development
| |
| MODIFIED -> change is substantially done and testable
| |
| ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)
| |
| CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
| |
| -->
| |
| * Tracker bug:
| |
|
| |
| == Detailed Description ==
| |
|
| |
| Fedora Media Writer is a new tool that be much easier to use than the existing tools (see [https://github.com/gnome-design-team/gnome-mockups/tree/master/USB-boot-creator mockups]). It should cover the complete work flow of creating an installation media. It provides information (descriptions, screenshots,...) about flavors and variants of Fedora to help the user to pick the right one for their usage, downloads the ISO, and copies it to a USB flash disk. The goal of this change is to provide this tool as the primary download option on getfedora.org and create a mechanism to store and update information (descriptions, screenshots,...) for the tool. This requires work not only from the change owners, but also from other groups (websites, design, marketing, releng teams).
| |
|
| |
| == Benefit to Fedora ==
| |
|
| |
| It will provide an easy-to-use tool for all major platforms (Linux, Windows, Mac OS X) which will be offered to users as the primary download option. That should generally lower the barrier for potential users to try and install Fedora.
| |
|
| |
| <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
| |
|
| |
| == Scope ==
| |
| * Proposal owners:
| |
| ** Fedora Media Writer for Linux (Copr and Flatpak coming soon, should we create a deb package, too?)
| |
| ** Fedora Media Writer for Windows
| |
| ** Fedora Media Writer for Mac OS X
| |
| <!-- What work do the feature owners 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?-->
| |
|
| |
| * Other developers: the websites team has to update the download page to make FMW the primary download option. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| <!-- What work do other 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?-->
| |
|
| |
| * Marketing and design:
| |
| ** the design team has to work with websites team on necessary changes to the download page.
| |
| ** the marketing has to provide information for FMW including descriptions and screenshots (screenshots of Workstation are currently missing)
| |
|
| |
| * QA:
| |
| ** adjust tests and test result matrices
| |
|
| |
| * Release engineering:
| |
| ** Plan the process of building Windows and MacOS packages
| |
| ** Handle the distribution of the releases
| |
| ** (Probably) estabilish a way how to pass Fedora release data to the tool - related to the release information from Marketing
| |
|
| |
| <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here.
| |
| Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
| |
| ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: ?? <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
| |
|
| |
| * Policies and guidelines: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
|
| |
| The Media Writer tool is helping with new installations. Existing installations are not affected.
| |
|
| |
| <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. -->
| |
|
| |
| * Trademark approval: N/A (not needed for this Change)
| |
| <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
| |
|
| |
| == Upgrade/compatibility impact ==
| |
|
| |
| The Media Writer tool is helping with new installations. Existing installations are not affected.
| |
| <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
| |
|
| |
| == How To Test ==
| |
|
| |
| # Go to getfedora.org
| |
| # Go for the default download option
| |
| # Download it
| |
| # Use the tool on {Fedora, Windows, OS X} to create a live USB using the F24 or F25 workstation
| |
| # Verify that the created live USB works
| |
| # Also try creating live USBs with some of the other available images
| |
|
| |
| == User Experience ==
| |
| <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. -->
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| Hopefully this change will improve user experience of trying and installing Fedora a lot.
| |
|
| |
| == Dependencies ==
| |
| <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change 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 change)? -->
| |
|
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| No dependecies.
| |
|
| |
| == Contingency Plan ==
| |
|
| |
| <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
| |
| * Contingency mechanism: if Fedora Media Writer is not ready to be the primary download option, it can only be mentioned on the download website as a tool to create a live USB stick. If the new FMW is not ready at all to replace the old version, we can still keep linking the old version or alternative tools.
| |
| <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. -->
| |
| * Contingency deadline: beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
| |
| * Blocks release? Yes, it will be such a visible change that it should block a release if it's not ready.
| |
| * Blocks product? All
| |
|
| |
| == Documentation ==
| |
| <!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. -->
| |
|
| |
|
| |
|
| |
| [[How_to_create_and_use_Live_USB]] should be updated.
| |
|
| |
|
| |
|
| |
| <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| TBD
| |
|
| |
| Repo: [https://github.com/MartinBriza/FedoraMediaWriter Github]
| |
|
| |
| == Release Notes ==
| |
| <!-- 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 change, indicate them here. A link to upstream documentation will often satisfy this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release.
| |
|
| |
| Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
| |
| -->
| |
|
| |
| [[Category:ChangeReadyForWrangler]]
| |
| <!-- When your change proposal page is completed and ready for review and announcement -->
| |
| <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
| |
| <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
| |
| <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
| |
|
| |
| <!-- Select proper category, default is Self Contained Change -->
| |
| [[Category:SystemWideChange]]
| |
