Opened 5 years ago

Last modified 5 years ago

#6278 new enhancement

HTTPS-E: Include webdocs in git

Reported by: grarpamp Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords:
Cc: micahlee, mfb@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Try to include the HTTPS-E pages and docs available under this url:

https://www.eff.org/https-everywhere

in the repo:

https://gitweb.torproject.org/https-everywhere.git

Child Tickets

Change History (2)

comment:1 Changed 5 years ago by pde

Cc: micahlee mfb@… added

Those pages are in a content management system. Maybe there's a way to use a git backend for a subset of the CMS pages, so I'm not marking this WONTFIX straight away, but we'd have to be pretty convinced that the benefits were worth the headaches.

comment:2 Changed 5 years ago by grarpamp

Concerned the complete lack of rule writing docs and 'official' 'best style' rule templates/examples in git is leading to poor quality rulesets as writers inherit and copy/paste each others poor forms. Surveying and linting the rule files shows that some regex knowledge is low, and this copying is infecting things. 00README in git points to web, for which a writer, already working in the same dir, may not fork browser and just copies a random xml instead.

Rather than deal with CMS to git, or git to CMS...
try dumping the CMS content to git once, then replacing the CMS content with weblink to the content in the browseable git repo.

Certainly and primarily only for this page, as its real consumer is writers (in git) not
end users (surfing web). And such writers are better position to update it as needed,
than general EFF account holders in CMS.
https://www.eff.org/https-everywhere/rulesets

And perhaps for most of this page too...
https://www.eff.org/https-everywhere/development

This might relate to #2160.

Note: See TracTickets for help on using tickets.