Thank you all very much! So most people are ok with 9/1 (Fri) one hour in 2~6 PM at UTC+8. Let's meet on 9/1 (Fri) 2:00 ~ 3:00 PM at UTC+8.
I'll send an announcement with detailed information to the mailing list later. On Fri, Aug 25, 2023, at 00:17, Jun Ouyang wrote: > I can present at 9/1 one hour in 2~6 PM at UTC+8. > > Suyan <[email protected]> 于2023年8月24日周四 11:09写道： >> >> All of these time slots are ok for me. >> >> Sincerely, >> Suyan >> >> Xuanwo <[email protected]> 于2023年8月23日周三 14:14写道： >> > >> > We didn't hold the meeting because no one replied to this email. Let's >> > schedule a new time for the testing meeting. Please respond to this email >> > with your availability so that we can have an idea of how many people will >> > attend in advance. >> > >> > In this meeting, we will simply greet each other. All relevant information >> > will be shared via the mailing list, so there is no need to worry about >> > missing any updates regarding the event. >> > >> > There are some possible time to pick up: >> > >> > - 8/31 (Thu) 10~11 AM at UTC+8 >> > - 8/31 (Thu) one hour in 2~6 PM at UTC+8 >> > - 9/1 (Fri) one hour in 2~6 PM at UTC+8 >> > >> > For time zone convert: https://time.is/compare >> > >> > On Thu, Jul 20, 2023, at 18:32, Xuanwo wrote: >> > > Community Over Code will happen at 8/18~8/20, maybe we can pick a time >> > > before that for test. And start a formal one after that (three weeks >> > > later). >> > > >> > > How about 8/3 (Thu) 4~5 PM at UTC+8? (That's a random time picked, >> > > welcome for better choice) >> > > >> > > On Thu, Jul 20, 2023, at 16:17, Chojan Shang wrote: >> > >> Hello everyone! >> > >> >> > >> I am pleased to share our results with you. With the participation of >> > >> Xuanwo and Suyan, we tested Discord and Google Meet, and I'm glad to >> > >> say that they both work well, despite some minor setup issues I >> > >> encountered. They both support audio and video, allow access from a >> > >> browser, and their limitations are fully sufficient for our current >> > >> needs. >> > >> >> > >> However, there are some things worth noting. Google Meet has a larger >> > >> quota and can accommodate up to 100 people. Also, since we are >> > >> non-native English speakers, live captioning seems more important as it >> > >> will be a bridge for communication. As for recording meetings, it seems >> > >> that Google Meet requires a paid account to do so but I don't think >> > >> this will be a key factor in troubling us; at least we can try saying >> > >> hi. >> > >> >> > >> Overall, we have chosen Google Meet as our preferred option for >> > >> meetings at the moment. Next time - which may be next month - we plan >> > >> on having a relatively open test where everyone can join the meeting >> > >> together to test devices and greet the community. >> > >> >> > >> Looking forward to seeing you all soon. >> > >> >> > >> PsiACE >> > >> >> > >> On 2023/07/20 01:58:37 Xuanwo wrote: >> > >>> Hello, everyone! >> > >>> >> > >>> I believe it's worth discussing whether hosting OpenDAL Community Sync >> > >>> on a regular basis is a good idea. While I've shared this concept with >> > >>> individuals on [discord], I think the mailing list would be a more >> > >>> appropriate forum for discussion. >> > >>> >> > >>> Here my current idea for this sync meeting: >> > >>> >> > >>> - Style: text or video meeting >> > >>> >> > >>> Attending, recording, and archiving text meetings is easier. However, >> > >>> I believe that video meetings are more appealing and can help >> > >>> establish connections between developers. The [Iceberg Community Sync] >> > >>> serves as a good example. It's important to consider that most of the >> > >>> OpenDAL PPMC members and committers are not native English speakers. >> > >>> >> > >>> - Time: two/three/four weeks >> > >>> >> > >>> The meeting will last at least one hour for all attendees. However, we >> > >>> want to ensure that we do not overburden our participants. So two >> > >>> weeks is two heavy for a small community like OpenDAL. >> > >>> >> > >>> Four weeks is too long and may coincide with the same time of the >> > >>> month when some members of OpenDAL are unable to attend, such as >> > >>> during the first or last week. >> > >>> >> > >>> So I perfer to have three weeks like Iceberg does. >> > >>> >> > >>> - Content >> > >>> >> > >>> From my experience with the Iceberg community, their sync meetings >> > >>> typically include highlights since the last meeting, release updates, >> > >>> and discussions. It appears that we can directly adopt these ideas. >> > >>> >> > >>> - Tools >> > >>> >> > >>> I feel like Google Meet is a good choice (based iceberg experience, >> > >>> haha). But using discord seems easier for us. Maybe we need to have a >> > >>> try first. I plan to have a private meeting with @psiace first and >> > >>> share the feedback here. >> > >>> >> > >>> - Process >> > >>> >> > >>> All our meeting will be recorded, in english, and with AI generated >> > >>> summary. We will share the summary with maillist, and maybe in blog >> > >>> (I'm not sure). >> > >>> >> > >>> Please feel free to ask any additional questions. I am very excited to >> > >>> meet with you! >> > >>> >> > >>> [discord]: >> > >>> https://discord.com/channels/1081052318650339399/1081052319342407715/1130816807809327234 >> > >>> [Iceberg Community Sync]: https://www.youtube.com/watch?v=DhvRg0oEdwU >> > >>> >> > >>> Xuanwo >> > >>> >> > > >> > > -- >> > > Xuanwo >> > >> > -- >> > Xuanwo > > > > -- > GPG public key: 4A6D297E6F74638E4D5F8E99152AC7B5F7608B26 > Thanks, > Jun Ouyang -- Xuanwo
