Welcome all to the first and central new mailing list for the Operate First community! This mailing list is the central location to start, find, conduct, and conclude the types of discussions and decisions an active open source community makes on a daily basis. This list is now fully open and transparent for subscriptions and archives. <http://goog_1223256055> - Send email to: community(a)lists.operate-first.cloud - Subscribe/manage: https://lists.operate-first.cloud/admin/lists/community.operate-first.cloud/ - Forum interace: https://lists.operate-first.cloud/archives/list/community@lists.operate-f... Read on to find out how we'll use this mailing list. You can also scroll to the end for some instructions on how to unsubscribe. Using this list ========== With so much going on across different platforms, such as GitHub <https://github.com/operate-first> and Slack <https://operatefirst.slack.com/>;, we need a single location that serves the core open source tenet of having a culture of transparency <https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html#_...;. Email is a reliable, low-barrier, and accessible way to communicate across the globe. When it comes to using an open source mailing list, many people think of "The Apache Way" from the Apache Software Foundation: “If it didn’t happen on the mailing list, it didn’t happen. <http://theapacheway.com/on-list/>” But how do you actually practice that? My recommendation is to let conversations arise where they already do, but make sure to start (and finish!) a thread on this mailing list. The thread closer should include a link to the concluding discussion and a recommendation of a decision that is about to go into effect. Then lazy consensus principle <https://community.apache.org/committers/lazyConsensus.html> says, let people have a few days (72 hours) to notice the thread about the decision/recommendation and raise any comments, questions, or concerns. If necessary, changes can be rolled back, so progress doesn't have to always stop. This is about being inclusive and overall doesn't slow the process of getting things done. In fact, it typically makes all things go faster by reducing surprises and the risks of accidental-obscurity. Your account ========== We are using Mailman 3, which includes a new web forum interface for interacting with threaded discussions, in addition to the usual email delivery. Your email address has been subscribed but your user account was not created for you. So the instructions in the welcome email to get your password will require you to create the account associated with your subscribed email address. If you wish to unsubscribe right now, you can email me and I will take care of it without you needing to create an account. To create an account, today we have one method, the Mailman 3 login system. We are working on adding <https://github.com/operate-first/community/issues/77> Operate First community SSO that allows you to use your GitHub login. We are also looking at other auth services, such as GitHub and Google. If you are interested in that, check out the details in the tracking issue. When you click `Sign Up`, you can create an account using the regular Mailman login, tying it to the email address you have subscriptions for. Then you can manage your account, including unsubscribing, setting options, and interacting with threaded discussions via the web interface. If you wish to wait until we have the SSO to create your account, there is nothing you need to do to remain subscribed. If you have any questions, don't hesitate to contact me. If you would like to help administer this mailing list, definitely contact me ASAP. :) Kind regards, - Karsten -- 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