(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...") |
|||
Line 23: | Line 23: | ||
<!-- 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 = | ||
== Summary == | == 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 == | == Owner == | ||
Line 33: | Line 33: | ||
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: | * 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. --> | <!-- 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: | * 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> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
Line 46: | Line 46: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * 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 60: | ||
== Detailed Description == | == 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 == | == 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: [[User: NB | nb - Nick Bebout]] | ||
<!-- 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?--> | ||
Revision as of 21:19, 29 January 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
- Name: Nick Bebout
- Email: nb@fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 24
- Last updated: 2016-01-29
- 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: nb - Nick Bebout
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- List of deliverables: 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)