korg: add audit command

[palnabarun]

Implements the audit command

Top level logic

1. Fetch all users from the org configuration
2. Fetches contribution statistics from devstats
3. Parses an exception file (in CSV format), if specified
4. Filters out members with contributions exceeding a threshold or present in the exceptions file. Note: The filtered-out members are active contributors, and inactive members are the ones left.
5. Checks if the users are owners.
6. Print the data to a Markdown file or to stdout.

Example

Running the following with this exceptions file after checking out this branch will give this table of users to be removed.

go run ./cmd/korg/... audit --org kubernetes,kubernetes-sigs,kubernetes-client,kubernetes-csi --activity-threshold 0 --output-file removals.md --exceptions-file exceptions.csv --check-teams --check-owners

Follow-ups

• Post the data to Cleanup Inactive Org Members #3094
• Implement the remove command

[palnabarun]

/hold

[nikhita]

/assign
for final review and lgtm

/assign @MadhavJivrajani @Priyankasaggu11929
can you take an initial pass?

[MadhavJivrajani]

Just a few minor suggestions and questions.
Overall, looks great! Thank you @palnabarun, this is going to be very handy ❤️

[Priyankasaggu11929]

Also — it would be useful to include this example exceptions file as well in the PR.

Both for format reference and maybe as a default entries for bot accounts?

(k8s-release-robot is appearing in the output table for usernames to remove. Perhaps we could add that to the exceptions list too. )

[pacoxu]

There is a special case that not sure if we want to make a flag.

https://go.k8s.io/owners/liu-cong is in the owner file but is emeritus. For such cases, we don't need an owner cleanup.
For others, he/she may be in the owner file and need a cleanup. (But hard to know if one is an emeritus as emeritus_approvers will not be commented with #.🤣 )

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale

[palnabarun]

[...] would it make sense to have "if a username is still a valid GH username or not?" as a default filtering predicate? [...]

@MadhavJivrajani The idea is good. I think it is taken care of already. Peribolos occasionally fails to reconcile if an invalid user exists in our manifests. Wondering if that is a sufficient lazy check.

---

@Priyankasaggu11929 @MadhavJivrajani @pacoxu I resolved all your pending comments and regenerated the lists.

Functionality diff from previous version:

• Removed the output type. Rendering to the terminal doesn't provide much value.
• The script now computes all teams that the users are part of.
• Takes care of case agnostic behavior of GitHub usernames. The repo has entries for the same user in correct case and lower case.

[palnabarun]

/remove-lifecycle stale

[MadhavJivrajani]

A few non-blocking comments, LGTM otherwise!

[MadhavJivrajani]

The idea is good. I think it is taken care of already. Peribolos occasionally fails to reconcile if an invalid user exists in our manifests. Wondering if that is a sufficient lazy check.

I think this should suffice, thanks for reminding me about that 👍🏼

[MadhavJivrajani]

/lgtm

[Priyankasaggu11929]

/lgtm
/approve

/hold

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MadhavJivrajani, palnabarun, Priyankasaggu11929

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [MadhavJivrajani,Priyankasaggu11929,palnabarun]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[palnabarun]

/hold cancel

[pacoxu]

Good job.

My last run two months ago resulted in a long list.