Since there are only voices in support of this, I propose that we hold our meeting on the first Wednesday of the month. This means our first meeting will be May 5th.
I set up a doc for meeting notes, agenda and logistics in our wiki: https://cwiki.apache.org/confluence/x/upaNCg I believe that everyone in the community should be able to use MS Teams. I set up a VMware sponsored MS Teams event for this. Always happy to iterate, if there are ideas for a different platform that feels more aligned with OSS and Apache. I suggest everyone adds their topics as early as possible, to make sure folks can decide if they are going to make to make sure to attend if one of the topics seems very relevant to them See you all on May 5th at 3pm/15:00 UTC (11amEDT/8amPST/17:00 CEST) ________________________________ From: Dan Smith <dasm...@vmware.com> Sent: Monday, April 12, 2021 09:39 To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: [DISCUSS] Monthly, synchronous community meetings Seems like a good idea. I have no preference on video conference platform. -Dan ________________________________ From: Alberto Gomez <alberto.go...@est.tech> Sent: Friday, April 9, 2021 1:25 AM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Re: [DISCUSS] Monthly, synchronous community meetings Hi, This idea sounds great to me. Have you thought about the videoconference platform to host these meetings? Best regards, Alberto ________________________________ From: Alexander Murmann <amurm...@vmware.com> Sent: Friday, April 9, 2021 2:46 AM To: dev@geode.apache.org <dev@geode.apache.org> Subject: [DISCUSS] Monthly, synchronous community meetings Hi everyone, On occasion we see discussions on PRs, here on the mailing list that might be move much quicker if we chatted synchronously about some of these topics and then shared the meetings notes back to the mailing list. Of course, our usual processes for voting and additional discussions would still need to be just as accessible as they are right now on the mailing list to anyone who cannot attend a meeting. However, it might allow us to move these discussions along faster and also create a stronger sense of community. I've seen similar things done in Kubernetes Special Interest Groups (example<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkubernetes%2Fcommunity%2Fblob%2Fmaster%2Fsig-node%2FREADME.md&data=04%7C01%7Camurmann%40vmware.com%7C736cbf2a3fdc4a442e6308d8fdd1a0ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637538424080252391%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=chFVe13gJds6yuvMnaC9shfz49eh9NPrG2kYD3WRJ20%3D&reserved=0>) Meeting Specifics Frequency: monthly Time: It seems like most of our community is distributed between Europe and the US. 3pm/15:00 UTC (11amEDT/8amPST/17:00 CEST) seems like a good compromise. How: We'd have a Confluence page to gather topics ahead of time. Topics should be added with as much lead time as possible, to allow interested community members to plan attendance. We'd use the same page to take meeting notes. Topic examples: RFC discussions, process proposals (like the recent codeowner introduction), show & tells of recent changes, controversial PRs, the sky is the limit till we find certain topics are better in a dedicated meeting. As with everything, I'd expect us to iterate and evolve this Does this sound valuable to everyone? How could this be better?
