[tracking] cleanup inactive maintainers

[jasondellaluce]

Motivation

As part of the preparations for our graduation submission, this issue tracks the process of reviewing and cleaning up the OWNERS files of each repository. This is a step for falcosecurity/falco#2106 and follows the community call discussion of 2022-06-29.

The OWNERS files of each repository will be updated to remove maintainers that have been inactive for the past 6 months as for the criteria of our governance (see: https://github.com/falcosecurity/.github/blob/master/GOVERNANCE.md#project-inactivity).

Developer activity is reviewed from the https://devstats.cncf.io/ API (ref: https://github.com/cncf/devstatscode/blob/master/API.md, https://github.com/cncf/devstatscode/blob/master/devel/api_dev_act_cnt.sh). Inactivity means having recorded zero or very little devstats over the past 6 months (2022-01-01 - 2022-07-01).

Inactive maintainers will be moved from approvers to emeritus_approvers (see: https://www.kubernetes.dev/docs/guide/owners/#emeritus) so that they will have the possibility to step up again in the future.

If any of the maintainers involved wishes to continue with their role, or to become active again, this issue (or any of its linked PRs) is the right place of discussion.

These repositories are excluded from the rewiew:

• Special repositories (see: [tracking] cleanup inactive maintainers #157 (comment))
  • falcosecurity/community
  • falcosecurity/evolution
  • falcosecurity/.github
  • falcosecurity/template-repository (see: Archive falcosecurity/template-repository #154)
• Repositories opened less than 6 months ago
  • falcosecurity/deploy-kubernetes
  • falcosecurity/kernel-crawler
  • falcosecurity/plugin-sdk-cpp
  • falcosecurity/falco-aws-terraform
  • falcosecurity/libs-sdk-go
• Repositories that had no activity (or very little) in the past 6 months
  • falcosecurity/katacoda-scenarios
  • falcosecurity/client-py
  • falcosecurity/client-rs
  • falcosecurity/kilt
  • falcosecurity/pdig

Repositories where inactive owners need to be updated

• falcosecurity/falco - cleanup(OWNERS): remove inactive approvers falco#2116, update(OWNERS): move inactive approvers to emeritus_approvers falco#2134
• falcosecurity/libs - cleanup(OWNERS): remove inactive approvers libs#460, update(OWNERS): move inactive approvers to emeritus_approvers libs#489
• falcosecurity/charts - cleanup(OWNERS): remove inactive approvers charts#360, update(OWNERS): move inactive approvers to emeritus_approvers charts#368, update(falco/OWNERS): move inactive approvers to emeritus_approvers charts#369
• falcosecurity/falco-website - cleanup(OWNERS): remove inactive approvers falco-website#642, update(OWNERS): move inactive approvers to emeritus_approvers falco-website#655
• falcosecurity/plugins - cleanup(OWNERS): remove inactive approvers plugins#129, update(OWNERS): move inactive maintainers to emeritus plugins#133
• falcosecurity/plugin-sdk-go - cleanup(OWNERS): remove inactive approvers plugin-sdk-go#58, update(OWNERS): move inactive maintainers to emeritus plugin-sdk-go#64
• falcosecurity/client-go - cleanup(OWNERS): remove inactive approvers client-go#57, update(falco/OWNERS): move inactive approvers to emeritus_approvers client-go#59
• falcosecurity/driverkit - cleanup(OWNERS): remove inactive approvers driverkit#179, update(OWNERS): move inactive approvers to emeritus_approvers driverkit#188
• falcosecurity/event-generator - cleanup(OWNERS): remove inactive approvers event-generator#73, update(OWNERS): move inactive approvers to emeritus_approvers event-generator#76
• falcosecurity/falco-exporter - cleanup(OWNERS): remove inactive approvers falco-exporter#73
• falcosecurity/falcoctl - cleanup(OWNERS): remove inactive approvers falcoctl#111, update(OWNERS): move inactive approvers to emeritus_approvers falcoctl#113
• falcosecurity/falcosidekick - cleanup(OWNERS): remove inactive approvers falcosidekick#342, chore(OWNERS): remove duplicates in reviewers falcosidekick#343
• falcosecurity/falcosidekick-ui - cleanup(OWNERS): remove inactive approvers falcosidekick-ui#56, chore(OWNERS): remove duplicates in reviewers falcosidekick-ui#57
• falcosecurity/test-infra - cleanup(OWNERS): remove inactive approvers test-infra#751, update(OWNERS): move inactive approvers to emeritus_approvers test-infra#768
• falcosecurity/evolution - update(OWNERS): move inactive maintainers to emeritus approvers #155
• falcosecurity/community - update(OWNERS): move inactive maintainers to emeritus approvers community#151
• falcosecurity/.github - update(OWNERS): move inactive maintainers to emeritus approvers .github#84

[jasondellaluce]

@bencer, @developer-guy, @fntlnz, @jonahjon, @KeisukeYamashita, @kris-nova, @ldegio, @leodido, @leogr, @lucperkins, @markyjackson-taulia, @mfdii, @mstemm, @nestorsalceda, @nibalizer, @radhikapc, @Rajakavitha1, @sreedaum

[markjacksonfishing]

Ack @jasondellaluce

[fntlnz]

Citing our governance:

If they decide to step down they open a pull request to be removed from the OWNERS files.

I did not decide to step down. It’s important for me to keep being a maintainer of Falco to ensure that our community has a different voice out there than employees of a single company. When I will see a diverse pool of maintainers I will think about stepping down. Even in that case, it’s a decision I will take based on the status of the project. I’m continuing to serve the community by making sure that the project is openly governed.

Please make sure to not remove my name from the approver files.

[leodido]

Citing our governance:

If they decide to step down they open a pull request to be removed from the OWNERS files.

I did not decide to step down. It’s important for me to keep being a maintainer of Falco to ensure that our community has a different voice out there than employees of a single company. When I will see a diverse pool of maintainers I will think about stepping down. Even in that case, it’s a decision I will take based on the status of the project. I’m continuing to serve the community by making sure that the project is openly governed.

Please make sure to not remove my name from the approver files.

Likewise. Same for me.

[nestorsalceda]

Citing our governance:

If they decide to step down they open a pull request to be removed from the OWNERS files.

I did not decide to step down. It’s important for me to keep being a maintainer of Falco to ensure that our community has a different voice out there than employees of a single company. When I will see a diverse pool of maintainers I will think about stepping down. Even in that case, it’s a decision I will take based on the status of the project. I’m continuing to serve the community by making sure that the project is openly governed.

Please make sure to not remove my name from the approver files.

I do agree with @fntlnz and @leodido

Same for me.

[maxgio92]

IMHO there is an ambiguity in this sentence:

If they decide to step down they [1] open a pull request to be removed from the OWNERS files.

1. Active maintainers or inactive maintainers?

[fntlnz]

@maxgio92 no ambiguity, please read the whole thing

Any existing maintainer that does not show significant activity on the project they maintain can be removed. Periodically, maintainers review the list of maintainers and their activity during the past six months.
In case the maintainer involvement in the past six months doesn't meet the requirements in this file they will be contacted to ask wether they want to continue being a maintainer. If they decide to step down they open a pull request to be removed from the OWNERS files.

Again, In my case I don't consider myself inactive. I'm less active than others but it's no justification to single-handedly
remove me from a project that I know like my pockets and where I am and will be always useful - because I'm here to help.

[leodido]

IMHO there is an ambiguity in this sentence:

If they decide to step down they [1] open a pull request to be removed from the OWNERS files.

1. Active maintainers or inactive maintainers?

I think there's no ambiguity at all. ⬇️

they will be contacted to ask whether they want to continue being a maintainer. If they ...

[fntlnz]

@leodido

they will be contacted to ask whether they want to continue being a maintainer.

No evidence of being contacted from my side as well.

[markjacksonfishing]

I can also say other than being tagged in this, there has been no contact with me.
I was originally removed under the same circumstances previously and aired my concerns over that.
I would like to remain as well.

[maxgio92]

I agree on the fact that the contact is a requirement. I wasn't aware it has been missed.

Maybe a clarification on what is considered inactivity can help on the governance?
Also, how a maintainer should be contacted, to avoid mistakes (e.g. maintainer email?).

[leodido]

This is not the place to discuss changes to the governance (there's a process for that in the governance itself).

[krisnova]

Please see falcosecurity/falco#2132 where I believe we can migrate some of the existing approvers to a new role.

[jasondellaluce]

As @leogr suggested in some of the related PRs and issues, I agree on moving this discussion to falcosecurity/evolution.

Quoting the readme of the evolution repository:

This repo aims to document the evolution process of The Falco Project.

Since this issue covers many PRs across the organization, and not just the falco repository, I'd ask @leogr or some other maintainer of both repositories to move this issue to falcosecurity/evolution.

[leogr]

Since this issue covers many PRs across the organization, and not just the falco repository, I'd ask @leogr or some other maintainer of both repositories to move this issue to falcosecurity/evolution.

Sure 👍

Moving it right now.

[jasondellaluce]

Closing this issue as the checklist is now complete.

/close

[poiana]

@jasondellaluce: Closing this issue.

In response to this:

Closing this issue as the checklist is now complete.

/close

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.