From Fedora Project Wiki
No edit summary
Line 1: Line 1:
{{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 "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
<!-- 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 -->
= Let's Encrypt client now in Fedora =
= Let's Encrypt client now in Fedora =


Line 34: Line 10:
-->
-->
* Name: [[User:nb| Nick Bebout]]
* Name: [[User:nb| Nick Bebout]]
<!-- 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. -->
* Name: [[User:jhogarth| James Hogarth]]
* Name: [[User:noodles| Nick Le Mouton]]
* Email: nb@fedoraproject.org
* Email: nb@fedoraproject.org
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->

Revision as of 01:22, 9 February 2016

Let's Encrypt client now in Fedora

Summary

The Let's Encrypt client is now packaged in Fedora. This will allow Fedora users to easily install the Let's Encrypt client (letsencrypt) and generate free SSL certificates for their websites (or other services which use SSL)

Owner

Current status

  • Targeted release: Fedora 24
  • Last updated: 2016-02-09
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The Let's Encrypt client is now packaged in Fedora. This will allow Fedora users to easily install the Let's Encrypt client (letsencrypt) and generate free SSL certificates for their websites (or other services which use SSL)

Benefit to Fedora

Having the Let's Encrypt client in Fedora is in keeping with the foundations of Features and First. I believe we are the only distro that has the Let's Encrypt client in our base distro currently. This is making it easy for people to use Fedora to get certificates from Let's Encrypt without having to install the client manually.


Scope

  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • 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