Hi Robert, Hi everyone, I am still skeptical about this. Generally, orgs of any kind tend to alternate between "can we do a meeting for this?" and "why don't we do this async?". For anything that goes towards a status update or information sharing, asynchronous, written communication is just more inclusive and efficient. I don't know of why we have the release sync meeting exactly, but would leave this to the release managers. Should the release sync actually be recorded like the Kubernetes community meeting? This seems like a good idea in general.
For an informal get-together, a meeting can be nice, but I would then separate this from the release sync, and clearly manage expectations what this meeting is or isn't about and set it up accordingly. For example, for getting to know each other and informal chatting a big room with more than 6 people becomes awkward very quickly. A series of break-out sessions would be much more useful then. Cheers, Konstantin Am Do., 2. Juni 2022 um 13:03 Uhr schrieb Robert Metzger < metrob...@gmail.com>: > Thanks for your feedback! > > Nobody should feel obliged to attend these meetings, or fear that they are > missing something by not attending. Everything relevant discussed there has > to be reflected on the mailing list, either as a meeting summary, or in > existing discussion threads. > My main motivation is to provide a room for people to get to know each > other, float some ideas and have informal conversations about Flink. > Maybe we should call the meeting "Release Sync & Virtual Get Together" or > something, to manage expectations? > > Looking at other projects, this this not uncommon: > > Apache Cassandra used to have such meetings for some time in 2020: > > https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+Contributor+Meeting > > (also the K8s SIG: > > https://cwiki.apache.org/confluence/display/CASSANDRA/Cassandra+Kubernetes+SIG > ) > > The Kubernetes project seems to have quite many meetings from the various > SIGs: > - Overview: > > https://github.com/kubernetes/community/blob/master/events/community-meeting.md > - Calendar: > https://calendar.google.com/calendar/u/0/embed?src=calen...@kubernetes.io > > Best, > Robert > > > On Tue, May 31, 2022 at 2:04 PM Konstantin Knauf <kna...@apache.org> > wrote: > > > Hi everyone, > > > > can you be more specific what you mean by "current topics in the Flink > > Community"? Shouldn't asynchronous communication be the default, and if > > that doesn't work, we consider a synchronous channel? > > > > Cheers, > > > > Konstantin > > > > Am Di., 31. Mai 2022 um 13:54 Uhr schrieb Jing Ge <j...@ververica.com>: > > > > > +1 > > > Sounds good! Thanks Robert! > > > > > > On Tue, May 31, 2022 at 1:46 PM Márton Balassi < > balassi.mar...@gmail.com > > > > > > wrote: > > > > > > > Hi Robert, > > > > > > > > Thanks for the suggestion +1 from me. You already listed the topic of > > the > > > > timezone on the wiki that I wanted to bring up. > > > > > > > > On Tue, May 31, 2022 at 9:38 AM Robert Metzger <rmetz...@apache.org> > > > > wrote: > > > > > > > > > Hi everyone, > > > > > > > > > > We currently have a bi-weekly release sync meeting on Google Meet > > every > > > > > Tuesday at 9am CEST / 3pm China Standard Time / 7am UTC. > > > > > I would like to propose extending the purpose of the meeting to a > > > general > > > > > "Flink Community Sync" meeting, to discuss current topics in the > > Flink > > > > > community. > > > > > > > > > > I propose that we just collect agenda items on the mailing list in > > the > > > > two > > > > > weeks prior to the meeting. > > > > > I'm happy to take care of prioritizing agenda items and taking > notes > > in > > > > the > > > > > wiki. > > > > > I've created already a page for the next sync: > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/2022-06-14+Community+Sync > > > > > > > > > > Let me know what you think! > > > > > > > > > > Best, > > > > > Robert > > > > > > > > > > > > > > > > > > -- > > https://twitter.com/snntrable > > https://github.com/knaufk > > > -- https://twitter.com/snntrable https://github.com/knaufk
