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

membership_policy.md misses a definition of what "active" means #255

Closed
dhiller opened this issue Feb 1, 2024 · 2 comments
Closed

membership_policy.md misses a definition of what "active" means #255

dhiller opened this issue Feb 1, 2024 · 2 comments
Labels

Comments

@dhiller
Copy link
Contributor

dhiller commented Feb 1, 2024

What happened:
When looking at the membership_policy I noticed that we are missing a definition of what active means to us.

What you expected to happen:
The membership_policy should contain a definition of "active", i.e. number of contributions required inside a defined timespan expected. All other members should therefore be considered as inactive.

Since there's a set of permissions connected to being a member of KubeVirt org (i.e. run test lanes, rehearsals etc.), we should establish a process to remove inactive members after a while to minimize security risks for the project.

Alternatively we could define "inactive" simply as no contributions over the last 12 months.

How to reproduce it (as minimally and precisely as possible):

Additional context:
Kubernetes has defined a policy for "inactive members"
They are removing inactive members after a period of 12 months from time to time (example).

Environment:

  • KubeVirt version (use virtctl version): N/A
  • Kubernetes version (use kubectl version): N/A
  • VM or VMI specifications: N/A
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): N/A
  • Kernel (e.g. uname -a): N/A
  • Install tools: N/A
  • Others: N/A

/cc @fabiand @aburdenthehand

@dhiller
Copy link
Contributor Author

dhiller commented Mar 22, 2024

/close

Done with #263

@kubevirt-bot
Copy link

@dhiller: Closing this issue.

In response to this:

/close

Done with #263

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants