From c282941b9d0995af327f712e99e731a7d65d04ee Mon Sep 17 00:00:00 2001 From: Justin Cormack Date: Tue, 16 Oct 2018 15:29:29 +0100 Subject: [PATCH] Tweak the organizations Signed-off-by: Justin Cormack --- reviews/tuf-graduation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/reviews/tuf-graduation.md b/reviews/tuf-graduation.md index 6f298d5..0fad2ea 100644 --- a/reviews/tuf-graduation.md +++ b/reviews/tuf-graduation.md @@ -6,7 +6,7 @@ The Update Framework (TUF) helps developers maintain the security of a software ### Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope. -* TUF is used in production by Docker, IBM, VMware, Cloudflare, Kolide, DigitalOcean, RedHat, Datadog, and many others. [Uptane](https://uptane.github.io/), the automotive variant of TUF, is sold by major automotive vendors and is being adopted by automakers with over 1/3 of the cars on US roads in their forthcoming cars. Uptane is included as part of [Automotive Grade Linux](https://www.automotivelinux.org/), another Linux Foundation project. +* TUF is used in production by Docker, IBM, VMware, Cloudflare, Kolide, DigitalOcean, RedHat, Microsoft, Datadog, and many others. [Uptane](https://uptane.github.io/), the automotive variant of TUF, is sold by major automotive vendors and is being adopted by automakers with over 1/3 of the cars on US roads in their forthcoming cars. Uptane is included as part of [Automotive Grade Linux](https://www.automotivelinux.org/), another Linux Foundation project. * More detail about adoption, including some of the in progress adoptions, can be found here: https://theupdateframework.github.io/adoptions.html ### Have a healthy number of committers. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project. The committers should come from at least two organizations. @@ -19,7 +19,7 @@ As an intentionally minimal security specification / framework, we deliberately * Notary (8 committers, 3 organizations) - * Ying Li (Docker), Diogo Mónica (Docker), Evan Cordell (RedHat / CoreOS), David Lawrence (Docker), HuKeping (Huawei), Justin Cormack (Docker), Nathan McCauley (Docker), Riyaz Faizullabhoy (Docker) + * Ying Li, Diogo Mónica, Evan Cordell (RedHat / CoreOS), David Lawrence, HuKeping (Huawei), Justin Cormack (Docker), Nathan McCauley, Riyaz Faizullabhoy ### Demonstrate a substantial ongoing flow of commits and merged contributions. @@ -36,7 +36,7 @@ The 5 accepted TAPs have authors from 5 different organizations: There are 2 TAPs that are currently under consideration (both of which are likely to be accepted) with authors from 4 organizations: * [TAP5](https://github.com/theupdateframework/taps/blob/master/tap5.md) by Trishank Karthik Kuppusamy (Datadog / NYU), Sebastien Awwad (NYU), Evan Cordell (CoreOS / RedHat), Vladimir Diaz (NYU), Jake Moshenko (CoreOS / RedHat), Justin Cappos (NYU) -* [TAP8](https://github.com/theupdateframework/taps/blob/master/tap8.md) by Hannes Mehnert (OCaml / Mirage), Justin Cappos (NYU) +* [TAP8](https://github.com/theupdateframework/taps/blob/master/tap8.md) by Hannes Mehnert (OCaml / Cambridge University), Justin Cappos (NYU) These demonstrate the breadth of contributions from different adopters and the way in which contributions are merged into the specification.