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

Do you still need commit access? #86826

Open
tstellar opened this issue Mar 27, 2024 · 9 comments
Open

Do you still need commit access? #86826

tstellar opened this issue Mar 27, 2024 · 9 comments

Comments

@tstellar
Copy link
Collaborator

TLDR: If you want to retain your commit access, please comment on this issue. Otherwise, you can unsubscribe from this issue and ignore it. Commit access is not required to contribute to the project. You can still create Pull Requests without commit access.

@jankratochvil @John-Lluch @Keno @kernhanda @kiszk @xndcn @emilio @ColdenCullen @rdwampler @chmeeedalf @bsaleil @vrnithinkumar @hasyimibhar @jberdine @bigboze @mhjacobson @yurydelendik @ArnaudBienner @sgatev @BillyONeal

LLVM has a policy of downgrading write access to its repositories for accounts with long term inactivity. This is done because inactive accounts with high levels of access tend to be at increased risk of compromise and this is one tactic that the project employs to guard itself from malicious actors. Note that write access is not required to contribute to the project. You can still submit pull requests and have someone else merge them.

Our project policy is to ping anyone with less than five 'interactions' with the repositories over a 12 month period to see if they still need commit access. An 'interaction' and be any one of:

  • Pushing a commit.
  • Merging a pull request (either their own or someone else’s).
  • Commenting on a PR.

If you want to retain your commit access, please post a comment on this issue. If you do not want to keep your commit access, you can just ignore this issue. If you have not responded in 6 weeks, then you will move moved from the 'write' role within the project to the 'triage' role. The 'triage' role is still a privileged role and will allow you to do the following:

  • Review Pull Requests.
  • Comment on issues.
  • Apply/dismiss labels.
  • Close, reopen, and assign all issues and pull requests.
  • Apply milestones.
  • Mark duplicate issues and pull requests.
  • Request pull request reviews.
  • Hide anyone’s comments.
@Keno
Copy link
Member

Keno commented Mar 27, 2024

Yes, I'm still active.

@ColdenCullen
Copy link
Member

I'm happy to downgrade to "triage."

@jberdine
Copy link
Contributor

Yes, still active.

@chmeeedalf
Copy link
Contributor

I'm fine being downgraded and using PRs instead. I haven't been really active in several years.

@rdwampler
Copy link
Collaborator

Yes.

@emilio
Copy link
Contributor

emilio commented Mar 29, 2024

Still around, but happy to be downgraded.

@mhjacobson
Copy link
Contributor

I'd like to retain my current access. Thanks.

@BillyONeal
Copy link
Contributor

Given that I'm no longer on the STL team you can revoke all my access. (Crucially, I don't believe I have a reason to retain even triage access)

@tstellar
Copy link
Collaborator Author

tstellar commented May 2, 2024

@jankratochvil @John-Lluch @kernhanda @kiszk @xndcn @bsaleil @vrnithinkumar @hasyimibhar @bigboze @yurydelendik @ArnaudBienner @sgatev Reminder, if you want to retain your commit access, please comment on this ticket in the next week.

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

9 participants