synchronize https://www.operate-first.cloud/sre/README.html and https://github.com/operate-first/community/blob/main/sigs.yaml

[goern]

SSIA

[goern]

and in relation to SIG/SRE, why does https://www.operate-first.cloud/sre/ADRs/RH/SIG-SRE/README.html exist? is red hat making decisions on behalf of the SIG?

[quaid]

and in relation to SIG/SRE, why does https://www.operate-first.cloud/sre/ADRs/RH/SIG-SRE/README.html exist? is red hat making decisions on behalf of the SIG?

We have a work-in-progress situation — the SIG doesn't really exist yet.

At the end of 2021 an internal Red Hat group was created called SIG-SRE, and they began publishing work done in internally/privately into Operate First. This group did not ever propose an active SIG within Operate First, rather, they began publishing into the sre repo at the direction of SIG-Ops.

This was when I adjusted that README a little to make it clear the intention to work Openly with others. But there was never work done to connect this as a formal SIG to the governance. This is evident in the empty charter.md file:

https://github.com/operate-first/sre/blob/main/charter.md

At the end of 2022 the internal SIG-SRE group let me know they were interested in having the Red Hat Open Source Program Office (OSPO) go forth with making an external SIG. Since then I have been working on a plan that I can propose, including getting alignment with people before making the proposal.

I intend to send my proposal to community@lists.operate-first.cloud by the start or middle of next week. That will include a call to organize a first meeting, get some folks to help with organizing the SIG, etc.