Netlify access audit, cleanup, and next steps.

[divya-mohan0209]

Describe the issue

Per this issue and wider discussions in the Release retrospective + SIG Docs meetings, we have realised that an audit & cleanup of privileged accesses to Netlify is long overdue.

We've initiated a cleanup of Docs emeritus leadership and the efforts are being tracked here.

Since SIG Contribex handles the granting and revoking of access for other areas of the project, this issue has been created for the following purposes in the order mentioned below.

• Seeking consensus around such an initiative
• Establishing a timeframe for periodic review of accesses
• Documenting accesses & access levels in a central document under k/community
• Automating the process of granting access via a GitHub PR (nice-to-have)

cc: @reylejano @natalisucks

[divya-mohan0209]

/sig contribex

[k8s-ci-robot]

@divya-mohan0209: The label(s) sig/contribex cannot be applied, because the repository doesn't have them.

In response to this:

/sig contribex

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[divya-mohan0209]

/sig contributor-experience

[divya-mohan0209]

@cblecker : I don't know if tagging you here would be appropriate. Apologies, if not. This is about the Netlify Access Amendment PR you had commented on earlier and specifically, this issue relates to non-docs accounts.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[reylejano]

/remove-lifecycle rotten