sadly, i don't have an actionable response for your question. i have been considering something similar for the kubemark provider. in our case, we do not have an abundance of users currently, so i have been considering proposing a monthly office hours/project meetup. for CAPOCI, you might consider your users and also the cadence of change to the project. if you plan on moving fast, then it would be beneficial to have meetings on a more frequent basis to ensure that people are not getting "left behind". on the other hand, if you feel that the cadence of change will be slower, or your user community smaller, having a less frequent meeting will make it easier for the maintainers (less meeting load).
i think it would be cool to capture some of these factors to help project communities make a good decision. as i see it there are three really strong options:
1. weekly meeting. good for high cadence, and/or high user community size. gives many opportunities for issues and discussion.
2. bi-weekly meeting. good for high, or medium, cadence with a smaller user community size. gives regular opportunity for issues and discussion, but also places lower demand on the maintainers
3. monthly meeting. good for low, or medium, cadence with a small user community size. lowest demand on maintainers at the cost of infrequent public meetings.
it's a difficult question to answer in general, but those are my thoughts, hope it helps =)
peace o/
Thanks,
Paul
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-cluster-lifecycle" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-cluster...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/8af28f20-50a5-4f19-973b-946df75f417en%40googlegroups.com.