Are you interested in how we organize and run the Operate First project? Do you want to participate in getting things done? SIG Community has the charter to figure that out, one step at a time. Come join us in all the work and fun! Step one is having our first (virtual) meeting, see who is interested in being involved, and decide on which subprojects and new SIGs those people are interested in running.[1] https://doodle.com/poll/phwviunxrerrkba2 The time windows I selected include NA/Western Europe-centric ones, but I also put in a window that is more friendly for folks in Asia and around the Pacific Rim. My thinking is: when we have more SIGs, subprojects, and working groups, we want to have folks participating from wherever they are. Let's be inclusive from the start, and figure out accommodations that are needed to make it work. Maybe we even have two meeting times, every other week? See you there! - Karsten [1] This is the PR for the SIG Community charter, I anticipate it being merged before next week. We can always make changes to it, but this gives us a place to start the meeting from. https://github.com/operate-first/community/pull/124 -- Karsten Wade [he/him/his] | Senior Community Architect | @quaid Red Hat Open Source Program Office (OSPO) : @redhatopen The Open Source Way : https://theopensourceway.org Operate First : https://operate-first.cloud

Hey Karsten, no worries - life happens! You mean this week Thursday for the inaugural meeting? The invite starts march 3rd. I would love to start this week though On Mon, Feb 14, 2022 at 4:58 AM Karsten Wade <kwade(a)redhat.com&gt; wrote: > OK, so last week fell off the rollercoaster tracks for me and I couldn't > get this organized in time for a popular slot. Shall we try for this week > instead? Following is calendar information and a draft agenda. > > Calendar > ======= > From the poll, Thursdays at 10:00 PT/18:00 UTC was the most popular time, > with 7 out of 9 votes (or 8 out of 10 if you count me.) > > If this works for folks, I made an entry in the group Google Calendar ( > operate.first.community(a)gmail.com): > > > https://calendar.google.com/calendar/embed?src=operate.first.community%40... > iCal: > https://calendar.google.com/calendar/ical/operate.first.community%40gmail... > > SIG Community weekly call > Thursday, March 3 · 10:00 – 10:50 > Every Thursday following > Google Meet joining info > Video call link: https://meet.google.com/gxo-obbe-oha > > Agenda (proposed) > =============== > * Introductions, administrivia > * Confirm consensus on new SIG Community charter > * Form any new SIGs > * What ideas are there for subprojects, and who wants to do them? > - No bare ideas: subproject proposals don't go forward unless people > want to work on the subproject > * Closing, administrivia > > > On Thu, Feb 3, 2022 at 10:33 AM Karsten Wade <kwade(a)redhat.com&gt; wrote: > >> Are you interested in how we organize and run the Operate First project? >> Do you want to participate in getting things done? >> >> SIG Community has the charter to figure that out, one step at a time. >> Come join us in all the work and fun! >> >> Step one is having our first (virtual) meeting, see who is interested in >> being involved, and decide on which subprojects and new SIGs those people >> are interested in running.[1] >> >> https://doodle.com/poll/phwviunxrerrkba2 >> >> The time windows I selected include NA/Western Europe-centric ones, but >> I also put in a window that is more friendly for folks in Asia and around >> the Pacific Rim. >> >> My thinking is: when we have more SIGs, subprojects, and working groups, >> we want to have folks participating from wherever they are. Let's be >> inclusive from the start, and figure out accommodations that are needed to >> make it work. Maybe we even have two meeting times, every other week? >> >> See you there! >> >> - Karsten >> >> [1] This is the PR for the SIG Community charter, I anticipate it being >> merged before next week. We can always make changes to it, but this gives >> us a place to start the meeting from. >> >> https://github.com/operate-first/community/pull/124 >> -- >> Karsten Wade [he/him/his] | Senior Community Architect | @quaid >> Red Hat Open Source Program Office (OSPO) : @redhatopen >> The Open Source Way : https://theopensourceway.org >> Operate First : https://operate-first.cloud >> > > > -- > Karsten Wade [he/him/his] | Principal Community Architect | @quaid > Red Hat Open Source Program Office (OSPO) : @redhatopen > The Open Source Way : https://theopensourceway.org > Operate First : https://operate-first.cloud > _______________________________________________ > Community mailing list -- community(a)lists.operate-first.cloud > To unsubscribe send an email to community-leave(a)lists.operate-first.cloud > _______________________________________________ Community mailing list -- community(a)lists.operate-first.cloud To unsubscribe send an email to community-leave(a)lists.operate-first.cloud

On Mon, Feb 14, 2022 at 3:08 AM Jeremy Choi <jechoi(a)redhat.com&gt; wrote: > Hi Karsten, > > Just wondering if the meeting recording will be provided? If so, that > would be much appreciated! > Hi Jeremy, that's a great and important question. We definitely will record all these meetings. Recorded meetings should really be the rule, saving non-recorded meetings for discussions that need to be private. But we may need to make that explicit in the Governance, and definitely should say it in the meeting invite (and as part of the introduction in the meeting itself), so it's also not a surprise to attendees. Thanks! _______________________________________________ Community mailing list -- community(a)lists.operate-first.cloud To unsubscribe send an email to community-leave(a)lists.operate-first.cloud

On Mon, Feb 14, 2022 at 3:08 AM Jeremy Choi <jechoi(a)redhat.com&gt; wrote: > Hi Karsten, > > Just wondering if the meeting recording will be provided? If so, that > would be much appreciated! > Hi Jeremy, that's a great and important question. We definitely will record all these meetings. Recorded meetings should really be the rule, saving non-recorded meetings for discussions that need to be private. But we may need to make that explicit in the Governance, and definitely should say it in the meeting invite (and as part of the introduction in the meeting itself), so it's also not a surprise to attendees. Thanks!

Hey Karsten, no worries - life happens! You mean this week Thursday for the inaugural meeting? The invite starts march 3rd.