On Sun, Apr 18, 2021 at 12:43 AM sebb <seb...@gmail.com> wrote: > How do you ensure that a specific Google account is authorised to view > a particular project?
This is exclusively governed by the project's "project.yaml" [1]. An example of such a file is [2]. [1] https://google.github.io/oss-fuzz/getting-started/new-project-guide/#projectyaml [2] https://github.com/google/oss-fuzz/blob/master/projects/openssl/project.yaml > > We also need to ensure continuity of access should an existing Google > user leave the project or be unavailable. How is that managed? This is usually managed through pull requests to the OSS-Fuzz repo, which are usually swiftly acted upon. If not performed by the "primary_contact" for a project directly, they are contacted to verify such changes. AFAIK that is the only difference between a "primary_contact" and an "auto_ccs" member. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
