You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 28, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 28, 2018. It is now read-only.
The HTTPS Everywhere documentation at https://www.eff.org/https-everywhere is out of sync with this Git repository. For example, the current version of the "Development" page in this repo says:
Please work off of the "3.0" branch if you're submitting changes to the latest stable release and use "master" if you're submitting changes to the latest development release.
Please could the EFF website's documentation pages for HTTPS Everywhere be automatically built from this Git repository (or better still, the code repository), or otherwise kept in sync with it?
As you suggested here and in #3, we want to close and archive this repo, and de-duplicate the docs in EFForg/https-everywhere, and welcome your continued participation there. So I'm going to put a bit of time into figuring this out, porting useful prose from these documents into https://github.com/EFForg/https-everywhere/tree/master/docs/en_US/ , before we archive this repository. I'd welcome your help.
It sounds like EFForg/https-everywhere#14423 is going to be a step on the way to you making a good diff between these two sets of docs, @sampablokuper -- is that right? Thanks!
Activity
brainwane commentedon Jan 24, 2018
You're right -- thanks, @sampablokuper .
As you suggested here and in #3, we want to close and archive this repo, and de-duplicate the docs in EFForg/https-everywhere, and welcome your continued participation there. So I'm going to put a bit of time into figuring this out, porting useful prose from these documents into https://github.com/EFForg/https-everywhere/tree/master/docs/en_US/ , before we archive this repository. I'd welcome your help.
brainwane commentedon Feb 8, 2018
It sounds like EFForg/https-everywhere#14423 is going to be a step on the way to you making a good diff between these two sets of docs, @sampablokuper -- is that right? Thanks!
Hainish commentedon Feb 28, 2018
@sampablokuper thanks for looking into this. I don't have ownership of this repo, I've requested from the organization owners that it be archived.