Skip to content

[Nomination] Add ST representative to Security group #93176

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

Merged
merged 1 commit into from
May 31, 2024

Conversation

yroux
Copy link
Contributor

@yroux yroux commented May 23, 2024

I'd like to nominate myself to join the LLVM Security group as a representative of ST. I work in ST's compiler team contributing to upstream (LLVM and GNU) and several downstream toolchains. We believe that it is important for us to be part of this group to address or report any potential security issues the LLVM project or our toolchains may encounter.

I'd like to nominate myself to join the LLVM Security group as a
representative of ST. I work in ST's compiler team contributing to
upstream (LLVM and GNU) and several downstream toolchains. We believe
that it is important for us to be part of this group to address or
report any potential security issues the LLVM project or our toolchains
may encounter.
@DimitryAndric
Copy link
Collaborator

As with a previous case of "self-nomination", it would be nice if there was a reference from somebody who is already known in this security-related community, who can vouch for @yroux.

@kbeyls
Copy link
Collaborator

kbeyls commented May 23, 2024

I can vouch for @yroux. I've known Yvan as an LLVM and GNU compiler engineer for many years.

Copy link
Collaborator

@smithp35 smithp35 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM too. I also have known Yvan for many years.

Copy link
Member

@emaste emaste left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmation from @kbeyls is good enough for me

Copy link
Collaborator

@pogo59 pogo59 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious what "ST" is? LGTM

Copy link
Collaborator

@DimitryAndric DimitryAndric left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ST is STMicroelectronics, who interestingly have the domain st.com: https://www.st.com/

@mrragava
Copy link
Contributor

LGTM

@kbeyls
Copy link
Collaborator

kbeyls commented May 29, 2024

If I counted correctly, we've got 9 approvals so far.
We currently have 20 people on the security team, so per https://llvm.org/docs/Security.html#choosing-new-members, we'll need another 1 or 2 approvals from existing security group members.

Copy link
Member

@gburgessiv gburgessiv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies for the latency here - LGTM :)

@yroux
Copy link
Contributor Author

yroux commented May 30, 2024

Thanks a lot for your Trust!

I'll merge the PR since the majority is now reached and the 5 business days are passed.

Hope to see you in the next sync meeting

@yroux yroux merged commit ae86278 into llvm:main May 31, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.