Falco's repo lifecycle doesn't mention forks and it seems it's more targeted for "big projects" something that we would be expecting to see for things like hubble, tetragon, cilium-cli. However, we might need to define a process for smaller projects similar to https://github.com/cilium/scruffy, https://github.com/cilium/fake, and https://github.com/cilium/json-mock for example or even forks such as https://github.com/cilium/controller-tools

We should also add how handle experimental and unmaintained/archived repos.

And we might want to do something like a sandbox open-telemetry/oteps#231

Hi @xmulligan
I liked the lifecycle structure of falcosecurity

We can add more information about the repositories for better understanding of contributors

Something else that I think would help with this discussion is: What do we need beyond just having a maintainer create the repo? What expectations or obligations are there that we need to satisfy for any new repo (whether freshly created due to contributions within the Cilium organization, or as a fork from an external repo for Cilium organization usage).

Hello Everyone!
I would like to work on this issue as part of the LFX Mentorship.

Please apply through the platform https://mentorship.lfx.linuxfoundation.org/project/eeaec4a9-5a9c-4cae-945d-f99265e85275

Hi @xmulligan! I'm Abhay. First and foremost, the project is thriving. I have successfully applied to the mentorship program and completed all the pre-tasks. I am eagerly awaiting the opportunity to work with you, learn more about the projects, and delve into interesting challenges.

Hi there! I am Rudraksh, the project on Cilium governance documentation looks pretty interesting to me. I am willing to work on it as LFX Mentee. While considering the points mentioned by @xmulligan @joestringer & @aanm. I performed a data analysis on the repos under Cilium project using Pandas. I came up with some figures with Cilium as:

I am looking forward to leveraging it further, to get more details about the individual projects which can help while defining lifecycle. While I found the Falco project repo lifecycle structure to be an excellent reference, I understand that we may need to make certain adjustments in the context of Cilium. I also came across CNCF governance templates which has been incredibly helpful in learning about governance in open source.

In the latest, review of Cilium governance the essence of contributor ladder was one of the major feedback/reviews by TOC, is this an aspect we should prioritize in the context of the Cilium governance project?

It might also be useful to include some guidelines https://github.com/istio/community/blob/master/ONBOARDING-TECH-TO-ISTIO.md