No edit summary |
|||
Line 1: | Line 1: | ||
= 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]] | ||
* 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
- Name: Nick Bebout
- Name: James Hogarth
- Name: Nick Le Mouton
- Email: nb@fedoraproject.org
- Release notes 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
- 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)