[Community] Re: Getting it started-up: Community SIG

Hi all: So we get to instantiate a new special interest group focused on all of the aspects of using, participating in, and contributing to an open source project: the Community SIG or `sig-community`.[1] I propose we have an instantiating meeting this week and decide on some clear proposals to take back to this list, including figuring out a plan for when the Community SIG meets and how. But this meeting-to-decide-when-to-have-a-meeting should be as accessible as possible. Instead of real time voice or video, how about a semi-live discussion over a block hours in Slack? I propose we meet in Slack on Wednesday 19 January in the now-renamed #sig-community channel. We can have a real-time and asynchronous discussion, recorded in the channel with the logs archived and sent to this list. 19 January 2022 13:30 UTC - 19:30 UTC (05:30 - 11:30 PST) https://join.slack.com/t/operatefirst/shared_invite/zt-o2gn4wn8-O39g7sthT... https://operatefirst.slack.com/ Who is planning to come? I can add you to a calendar invite. Can I get some facilitating help? I don't plan to be there for maybe the first hour, but I will be there ahead of time seeding the agenda. If one or two of you are there at the opening, welcome people with The Spiel*, and lurk or guide. You can do this alongside other work, etc. Looking forward to seeing you all then! - Karsten * The Spiel is the kind and useful welcoming message you'll give a few times, and it should include relevant links for the meeting. [1] The new governance instantiates only two SIGs, Community and Operations. The Operations SIG scope is all the things running the prototype Operate First community cloud environment. Therefore, anything not in that is in the purview of the Community SIG: user and contributor experience, training, marketing, social media, organizing and building the community, etc. _______________________________________________ Community mailing list -- community(a)lists.operate-first.cloud To unsubscribe send an email to community-leave(a)lists.operate-first.cloud