Skip to content
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

Open
danehans opened this issue Nov 19, 2024 · 7 comments
Open

Community Meeting Plan #17

danehans opened this issue Nov 19, 2024 · 7 comments

Comments

@danehans
Copy link

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.

@danehans
Copy link
Author

cc: @ilrudie @linsun

@nfuden
Copy link
Contributor

nfuden commented Nov 19, 2024

It seems we created an maintainer type in our initial maintainers doc that claims to be "community".
Is this something that would fall within that set and therefore we should ask for more people to take on that role or is this more of a thing we would want to share around and have people sign up to host?

@danehans
Copy link
Author

IMHO the project needs to document how meetings are managed, including hosting responsibilities that need to be assigned.

@linsun
Copy link
Contributor

linsun commented Nov 20, 2024

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.

@ilrudie
Copy link
Contributor

ilrudie commented Nov 20, 2024

A couple of takeaways from our first meeting which should probably shape the early direction:

  • With a free account we can't delegate hosting of our meeting. Someone will need to be able to login as k8sgateway in order to start the meeting, I think ideally starting the meeting and hosting the meeting should be considered 2 different roles until we get better infrastructure. Direct access to literally be k8sgateway should probably be a bit more restricted that simply project maintainer but I have no good ideas for how that should be managed in practice. Currently we have no defined "super maintainer" role. Perhaps "community maintainers" have access to be k8sgateway but this makes that role pretty powerful.
  • With a free account we can't record the meetings. Is recording a necessity?
  • With a free account our meeting agenda seems to be a bit odd in terms of granting write access vs having everyone suggest. Could be user error on my part. Happy to huddle up with someone who knows g-suites better than I to take a look at that.

@danehans
Copy link
Author

With a free account we can't record the meetings. Is recording a necessity?

Since the meeting infra will change if/when the project is accepted by CNCF, +1 to hold off on recording.

@linsun
Copy link
Contributor

linsun commented Dec 6, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants