The wider OpenCost community identified work that falls into the categories of contributor experience, advocacy and communications, community management as integral to its success. This document outlines the responsibilities of the Community Maintainers, and links to OpenCost community resources.
See https://github.com/opencost/opencost/blob/develop/MAINTAINERS.md#community-maintainers
As opposed to defining a big overarching burden of responsibilities the team would have a hard time to actually realise, we want to slowly and carefully add tasks as we build out the team.
- Project communications
- Monthly blog post
- Social media
- Mailing list
- Slack
- Events and Advocacy
It is important to us to create a space for our community to meet, engage, collaborate and learn from each other. Over the past months, we have participated in CloudNativeCon / KubeCon and at various meetups.
If you want to join the planning effort, please come and talk to us!
Also, if you would like to speak about OpenCost, do reach out - we are happy to help you find a speaking slot soon. The more the world hears about this, the better!
We as a project want to make it a priority to inform our community and the wider world of developments well. It's what helps new contributors get up to speed, enables collaboration, integrations and more.
The Community team helps with communication channels, including:
Add news-worthy items to our community meeting notes, so that our community maintainers can broadcast them appropriately!
- Check the community meeting notes and see if there are items that still need doing.
- We would like to get monthly updates out to our community, so writing up content, getting quotes from relevant people, etc
Talk to us in #opencost on Slack and let us know if you're interested in contributing.
We would love to have you part of the team.
In case you need access to a particular OpenCost resource to fulfil your role as team member, please file an issue on this repository and tag some of the folks in the previous section.
Below we list resources that are not tied to GitHub permissions. You can assume that the core OpenCost maintainers have access, community maintainers and sometimes CNCF staff as backup.
For people listed below we made exceptions:
TODO
TODO
TODO
https://youtube.com/@CNCFOpenCost
Credit to the Flux project for their structure and contents of this file, and expectations of community maintainers - https://github.com/fluxcd/community/blob/main/COMMUNITY.md