Hi: Yeah, I think adjust the community meeting to two sessions is make sense to me. I can not attend to the community meeting in work day, So the second session can give me opportunities to meet with us. Also, I am strongly agree with office hours, We can host office hour by text meeting in discord or online meeting hours. This will give our contributors and users a direct and immediate opportunity for dialogue.
Xuanwo <[email protected]> 于2023年12月14日周四 17:34写道： > > Hi, all > > The OpenDAL Community Sync takes place every three weeks on Friday at 14:00 > UTC+8. However, some contributors find it difficult to participate. > > For those in or near the UTC+8 time zone, the meeting falls in the middle of > a workday, making attendance challenging. Additionally, contributors outside > this time zone often find the timing inconveniently early or late. > > I suggest we adjust the community sync times to two sessions as follows: one > at 09:00 UTC+8 and another at 19:00 UTC+8. For example, our upcoming meeting > is scheduled for 09:00 UTC+8 on January 5, 2024, and the following meeting > will take place at 19:00 UTC+8 on January 26, 2024. > > Our contributors can choose the most convenient time to participate, ensuring > we accommodate as many time zones as possible. What are your thoughts? > > Besides, I find the cargo office hour [1] is interesting: Some cargo team > members are available to directly mentor contributions to Cargo. Contributors > can talk to committers directly for their problems at office hour. > > I believe this experiment will be a valuable addition to our community sync. > Would you like to discuss with the committers during office hours? > > [1]: https://github.com/rust-lang/cargo/wiki/Office-Hours > > Xuanwo -- GPG public key: 4A6D297E6F74638E4D5F8E99152AC7B5F7608B26 Thanks, Jun Ouyang
