This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
Phase out "pledge" feature #162
Assignees
Comments
|
Very much in favor of deleting those code paths. Prior to launch, we'd anticipated that orgs with poor scoring would want a stopgap solution to communicate "We're working on it!", thus the pledge functionality. After launch, response was quite positive, and we've seen a large uptick in adoption since then. Much more interested in ramping up integration of additional sites and regions (#143), as well as expanding the grading rubric (#128) than promoting, or even maintaining, the pledge feature. |
|
Alright, I'll take a crack at this one. |
eloquence
changed the title
eloquence
added a commit
that referenced
this issue
Jun 8, 2018
eloquence
added a commit
that referenced
this issue
Jun 8, 2018
4 tasks
SaptakS
pushed a commit
that referenced
this issue
Sep 30, 2019
SaptakS
pushed a commit
that referenced
this issue
Sep 30, 2019
SaptakS
pushed a commit
that referenced
this issue
Sep 30, 2019
harrislapiroff
pushed a commit
that referenced
this issue
Oct 29, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We've been showing 0 pledges on https://securethe.news/ (AFAICT forever), if the pledge feature is not actually being used, we should probably disable it.
The text was updated successfully, but these errors were encountered: