-
Notifications
You must be signed in to change notification settings - Fork 225
Expand file tree
/
Copy pathCREDITS
More file actions
64 lines (56 loc) · 1.97 KB
/
CREDITS
File metadata and controls
64 lines (56 loc) · 1.97 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
We gratefully acknowledge all those who reviewed or helped develop the
badging criteria and/or the software to implement it.
That includes everyone who provided comments via the mailing list,
issue tracker, or via pull requests.
Alphabetically by family (last) name, contributors include:
* Wang Anyu
* Mark Atwood
* Tod Beardsley
* Doug Birdwell
* Alton(ius) Blom
* Hanno Böck
* enos-dandrea
* Jason Dossett *
* David Drysdale
* Andrew Fader *
* Karl Fogel
* Tony Hansen
* Alex Jordan (strugee)
* Sam Khakimov
* Greg Kroah-Hartman
* Dan Kohn
* Yannick Moy
* Charles Neill (cneill)
* Mark Rader
* Emily Ratliff
* Tom Ritter
* Christopher "CRob" Robinson
* Toine Siebelink
* Nicko van Someren
* Daniel Stenberg (curl)
* Marcus Streets
* Trevor Vaughan
* Dale Visser
* Kevin W. Wall
* Florian Weimer
* David A. Wheeler *
(Apologies in advance for anyone we've accidentally omitted.)
We especially recognize Dan Kohn (1972-2020), who was instrumental
in starting this project. He is deeply missed.
Those marked with a "*" have all the necessary rights to
create and close issues, accept proposed changes,
and release versions of software, as well administrate the production system.
This meets the "access_continuity" criterion.
See the TSC.md document for the current Technical Steering Committee
(TSC) members.
We currently don't have any security vulnerabilities that have been
found externally by others. If someone *has* done so, and would like to
be credited, we will gladly do so! If we've accidentally forgotten to give
you credit, our apologies; please let us know so we can quickly fix that.
We *want* people to report any vulnerabilities our system has, so that
we can quickly fix them. Please see our information on
[how_to_report_vulnerabilities](CONTRIBUTING.md#how_to_report_vulnerabilities).
Karl Fogel not only provided us helpful inputs, but his book
"Producing Open Secure Software" <http://producingoss.com/>
was an important basis for identifying many project best practices.
Thank you!