Cloud Native Runtime Security.

---

Falco Community

The Falco community owns and maintains all aspects of The Falco Project. Every repository in the falcosecurity GitHub org belongs to the community.

Table of Contents

• Falco Community
  • Community Calls
  • Running a call
  • Slack Channel
  • Mailing List
  • How to contribute
  • Project Evolution

Resources

• Governance
• Code Of Conduct
• Maintainers Guidelines
• Maintainers List
• Repositories Guidelines
• Repositories List
• Adopters List
• Contributing
• Security policy
• Join the Community

Community Calls

These are the primary calls for The Falco Project. If you are unsure where to get started, this is the place to join.

When: Biweekly Community Calls, every 2 weeks on Wednesday at 4pm UTC.

You can see the Falco Calendar here .

If you want to subscribe to the Falco calendar, you can use this ics feed.

https://lists.cncf.io/g/cncf-falco-dev/ics/7639482/1350118793/feed.ics

Where: Zoom call

Falco Community calls gives the Falco community a common time to come together to discuss any open issues or PRs, new features, rules, upcoming releases, etc.

Each session is composed of 3 parts:

• Latest news of the project and its ecosystem
• A 5min lightning talk from anyone in the community, maintainers, contributors and users, about any topic they would like to present. It can be an existing feature, a POC for a new feature, a specific use case, a useful tip, etc.
• The remaining time is free for the users to ask for help to the present maintainers. Having created the issue on GitHub before will help.

The MC can be every community member willing to help run the call. The MC should be chosen in advance so that they have enough time to prepare the Agenda.

To give a lightning talk or discuss any topic in the upcoming meeting, please book the slot by adding an item in the hackmd.

After every release of Falco, the minutes of the community calls since the previous release are published in this repository.

Minutes: We use the same hackmd document every week to track our minutes.

History: Check out the YouTube channel

All of our calls are documented and posted to the YouTube channel.

Running a call

Regardless if you are interested in starting a new call, or running an existing call we have some structure in place to drive these calls.

• All new calls should include a calendar invite sent to the mailing list's email address cncf-falco-dev@lists.cncf.io, as well as a short description of the call and the goals.
• All calls should be recorded and published to the Falco YouTube Channel
  • Note: Please contact a maintainer for access to the channel if you need to upload a video.
• All calls should have written minutes using hackmd.io. Ideally the minutes are posted in advance to give collaborators a chance to add items before the meeting. After the meeting the notes should be closed, and uploaded to this repository.
  • Note: The template used for the Falco Community Calls can be found here
• All calls must adhere to the CNCF Code of Conduct

Slack Channel

Join the #falco channel on Kubernetes Slack. We will be thrilled to meet you!

Mailing List

Join the Falco mailing list to keep you posted on important news and announcements.

How to contribute

See the contributing guide and the code of conduct.

Project Evolution

The falcosecurity/evolution repository is the official space for the community to work together, discuss ideas, and document processes. It is also a place to make decisions. Check it out to find more helpful resources.