Commit text as provided by LF in https://github.com/mindersec/minder/pull/4834

[evankanderson]

Check in the official LF governance docs, as per mindersec/minder#4834. Check in the files as markdown, such that it is easier to track future edits. Per request in that file, limit approvals for governance changes to require approval by @thelinuxfoundation explicitly.

It appears that some of the suggested Stacklok changes didn't make it into the official LF document. Adding @riaankleinhans to suggest what to do:

1. The maintainers preferred the name "Steering Committee" to "Technical Steering Committee", as the responsibilities including maintaining and updating committer and community roles and non-technical processes.
2. The project is keeping governance documents, including the maintainers list, in the community repository, rather than in "the project's code repository" (as the project has several code repositories).
3. The maintainers preferred to resolve all votes with electronic voting, removing the "majority-of-quorum" voting option for in-person voting (it seemed more likely to cause confusion and strife, and is less async-friendly).

[riaankleinhans]

mindersec/minder#4834 (comment)

[riaankleinhans]

@evankanderson I can submit a request to the Linux Foundation formation team to update the Minder charter.
Are these 3 items the only points from the project? or should we wait for more feedback?

- The maintainers preferred the name "Steering Committee" to "Technical Steering Committee", as the responsibilities including maintaining and updating committer and community roles and non-technical processes.
- The project is keeping governance documents, including the maintainers list, in the community repository, rather than in "the project's code repository" (as the project has several code repositories).
- The maintainers preferred to resolve all votes with electronic voting, removing the "majority-of-quorum" voting option for in-person voting (it seemed more likely to cause confusion and strife, and is less async-friendly).

[evankanderson]

@evankanderson I can submit a request to the Linux Foundation formation team to update the Minder charter. Are these 3 items the only points from the project? or should we wait for more feedback?

- The maintainers preferred the name "Steering Committee" to "Technical Steering Committee", as the responsibilities including maintaining and updating committer and community roles and non-technical processes.
- The project is keeping governance documents, including the maintainers list, in the community repository, rather than in "the project's code repository" (as the project has several code repositories).
- The maintainers preferred to resolve all votes with electronic voting, removing the "majority-of-quorum" voting option for in-person voting (it seemed more likely to cause confusion and strife, and is less async-friendly).

The only other changes I see seem to be cosmetic or against the LF legal requirements:

• The project description is slightly different
• The SC description makes the SC responsible for updating this charter, but it sounds like LF legal is the final responsible authority, so removing that sentence seems fine.

(the - lines are the ones that we committed before the LF legal process was complete and the PDF documents created. The + lines are the new lines the LF document contained. The words moving from line to line is an unfortunate consequence of line-wrapping.)

Thanks!

[riaankleinhans]

@evankanderson I have clarified with the formation team. The changes are expectable, but need to be traceable.
Please add the charter to the repo in .md format as a exact copy of PDF in mindersec/minder#4834 and merge that as the base document.

Then please make a second PR with the changes and tag me in it. Also get the required community approval for the changes, then we can get the formation team to review and approve that changes.

One comment from their side about changing TSC to SC:
"We generally recommend that they keep TSC (vs. SC) to be consistent with the nomenclature of all of the other projects (as it is a well understood term in these communities), but, I'm not going to fight that point if this is what they really want."

[evankanderson]

This PR does step 1, with the following rendering changes. I can try to avoid them if needed / desired:

1. The top-level bolded numbered sections (e.g. "1. Mission and Scope of the Project") are translated to markdown headings, and the numbers have been removed.
2. The "a", "b", etc ordered lists under the numbered sections are now top-level ordered lists, which use "1", "2", etc as sequence numbers in markdown.

Beyond those two differences, I've spot checked all the sequence numbers and word-for-word about half the paragraphs in the rendered version of the new file against the PDF from mindersec/minder#4834.

This will become the new baseline for governance, and then we can use the governance laid out in the PDF / this markdown to propose new changes on top of it.

[evankanderson]

(Also, once this change is committed, only @thelinuxfoundation will be able to approve PRs to update the file)

[riaankleinhans]

/cc @thelinuxfoundation @tbenzies