From Fedora Project Wiki
(Add releng ticket)
No edit summary
Line 128: Line 128:
-->
-->


[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAnnounced]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Revision as of 09:39, 17 February 2018

FedoraScientific VagrantBox

Build and Release Vagrant boxes for Fedora Scientific

Summary

Fedora Scientific is currently delivered as ISOs. Shipping vagrant boxes will give potential users a friendlier option to try out Fedora Scientific while keeping their current operating system.

Owner

  • Name: Amit Saha
  • Email: amitsaha.in@gmail.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 29
  • Last updated: 2018-02-17
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Vagrant boxes for Fedora Scientific will allow users to easily run Fedora Scientific in a virtual machine. This can be useful for users who are using another operating system as their host operating system and not have to manually download the ISO, and go through the installation process which can be unfamiliar or unnecessary hassle for users who may be new to Fedora or Linux.


Benefit to Fedora

This will lower the barrier of entry to potential Fedora Scientific and Fedora users.


Scope

  • Proposal owners: This will require creating pungi configuration as well as new kickstarts to be able to build the vagrant boxes for Fedora Scientific.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: #7324 (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes