-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Community Meeting Plan #17
Comments
It seems we created an maintainer type in our initial maintainers doc that claims to be "community". |
IMHO the project needs to document how meetings are managed, including hosting responsibilities that need to be assigned. |
I would like to ask for folks (particularly maintainers) who are interested in hosting to sign up, but as far as I understand, there is no requirement for this for CNCF incubation project level and different projects vary. For example, in istio, we don't assign people but people holds leadership role in the project usually steps up. |
A couple of takeaways from our first meeting which should probably shape the early direction:
|
Since the meeting infra will change if/when the project is accepted by CNCF, +1 to hold off on recording. |
As much as I love to develop a plan to run a community mtg, we can start to keep things simple for now. I'd expect maintainers are leaders of the project. At the beginning of the meeting, we'll ask if any maintainer wants to host the meeting (or someone can volunteer to host without ask.). This is pretty much what Istio does too, which requires no planning effort. |
Develop a plan for running the community meeting, i.e. How will host rotation work? Will a meeting scribe be a required role? The results should be documented in this repo and linked to the k8sgw repo.
The text was updated successfully, but these errors were encountered: