[DOCS] Rename LLVM Security Group to LLVM Security Response Group. #116986
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rename LLVM Security Group to LLVM Security Response Group. Take the opportunity to canonicalise security group and Security Group to LLVM Security Response Group. At the 2024-11-19 LLVM Security Group meeting [1] we discussed that in practice the LLVM Security Group was performing an incident response role, but it was not proactively adding additional testing, fuzzing and hardening. We do not want projects that use LLVM to see the LLVM Security Group as guaranteeing security for LLVM. We decided that it would be useful to rename the group to LLVM Security Response Group as that reflects the work that it is doing. There may be a case for a proactive security group with a different remit, but this is out of scope of this commit. [1] https://discourse.llvm.org/t/llvm-security-group-public-sync-ups/62735/32
smithp35
requested review from
kbeyls,
ahmedbougacha,
cuviper,
tuliom,
ormris,
serge-sans-paille,
emaste,
gburgessiv,
yroux,
DimitryAndric and
mrragava
|
I've added all the security group members on the pick-list provided by Github. There is a related PR #116980 for removing the one bullet point on the security group page that implies we do anything more than incident response. We thought keeping the PRs separate was preferential as changing the LLVM Security Group name may need further consultation. |
cuviper
approved these changes
Nov 20, 2024
dimitry-unified-streaming
approved these changes
Nov 20, 2024
DimitryAndric
approved these changes
Nov 20, 2024
ormris
approved these changes
Nov 20, 2024
yroux
approved these changes
Nov 21, 2024
tuliom
approved these changes
Nov 22, 2024
gburgessiv
approved these changes
Nov 23, 2024
This was referenced Jun 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rename LLVM Security Group to LLVM Security Response Group. Take the opportunity to canonicalise security group and Security Group to LLVM Security Response Group.
At the 2024-11-19 LLVM Security Group meeting [1] we discussed that in practice the LLVM Security Group was performing an incident response role, but it was not proactively adding additional testing, fuzzing and hardening. We do not want projects that use LLVM to see the LLVM Security Group as guaranteeing security for LLVM.
We decided that it would be useful to rename the group to LLVM Security Response Group as that reflects the work that it is doing.
There may be a case for a proactive security group with a different remit, but this is out of scope of this commit.
[1]
https://discourse.llvm.org/t/llvm-security-group-public-sync-ups/62735/32