From Fedora Project Wiki
(Created page with "{{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 re...")
 
(The Change is not needed: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/WX7KYP7CKPQORSVX4CNUJTEIBBO3IVZR/#WX7KYP7CKPQORSVX4CNUJTEIBBO3IVZR)
 
(7 intermediate revisions by 2 users not shown)
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.'''}}
= Let's Encrypt client now in Fedora =
 
<!-- 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 -->
= Change Proposal Name <!-- The name of your change proposal --> =


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
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 ==
== Owner ==
Line 33: Line 9:
This should link to your home wiki page so we know who you are.  
This should link to your home wiki page so we know who you are.  
-->
-->
* Name: [[User:FASAcountName| Your Name]]
* 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. -->
* Email: nb@fedoraproject.org
* Email: <your email address so we can contact you, invite you to meetings, etc.>
 
* Name: [[User:jhogarth| James Hogarth]]
* Email: jhogarth@fedoraproject.org
 
* Name: [[User:noodles| Nick Le Mouton]]
* Email: noodles@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> -->
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
Line 46: Line 28:


== Current status ==
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
* Targeted release: [[Releases/24 | Fedora 24 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* 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  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 60: Line 42:
== 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. -->
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 ==
== 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.
    
    
<!-- 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?-->
<!-- 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 ==
== Scope ==
* Proposal owners:
* Proposal owners: To implement this Change
<!-- 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?-->
<!-- 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?-->


Latest revision as of 14:23, 15 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

  • Release notes owner:

Current status

  • Targeted release: Fedora 24
  • Last updated: 2016-02-15
  • 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

  • Proposal owners: To implement this Change
  • 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

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/LetsEncrypt&oldid=434189"