Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Envoy security team membership #6591

Closed
htuch opened this issue Apr 15, 2019 · 1 comment
Closed

Envoy security team membership #6591

htuch opened this issue Apr 15, 2019 · 1 comment
Assignees

Comments

@htuch
Copy link
Member

htuch commented Apr 15, 2019

Related to #6586, we currently have all Envoy maintainers as a subset of the Envoy security team.

Should we maintain this going forward, or shift to a set of dedicated folks with active bandwidth?

Does maintainership confer the ability for sponsoring organizations to receive early bug fixes?

Action item for CVE-2019-9900
Action item for CVE-2019-9901

@htuch htuch self-assigned this Apr 15, 2019
@htuch
Copy link
Member Author

htuch commented Apr 25, 2019

Based on discussion at the postmortem, it seems that there is no good reason to remove maintainers or their sponsoring organization (further reasoning to be provided in #6586). So, I'll close this one out (and reopen if #6586 takes a turn).

@htuch htuch closed this as completed Apr 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant