Governance 1.0 complete draft for discussion #107

quaid · 2021-12-08T19:36:54Z

Merging together ideas and content from Kubernetes, OpenInfra
This commit is the raw first draft of the Governance 1.0 section
The outline for Governance 1.1 section is included in this commit

Signed-off-by: Karsten Wade kwade@redhat.com

- Merging together ideas and content from Kubernetes, OpenInfra - This commit is the raw first draft of the Governance 1.0 section - The outline for Governance 1.1 section is included in this commit Signed-off-by: Karsten Wade <kwade@redhat.com>

quaid · 2021-12-08T20:34:34Z

We are keeping this PR open for discussion, so I'm putting a hold on it to make sure it's not prematurely merged.
/hold

quaid · 2021-12-08T20:48:12Z

How to comment on this document:

You must be logged into GitHub.
At the top of this "Conversation" are three other menu tabs: "Commits", "Checks", and "Files Changed". Clicking on "Files changed" takes you here
Within the "Files changed" tab is one file governance.md, with a grey column on the left because it's a new file, and the green column on the right showing all the new content.
Read through the green column, which is marked in the attached image with a dark purple right angle large brushstroke.
If you have a comment about a particular line, click the + symbol next to the line number and a comment field will open, as marked by the dark purple vertical brushstroke in the attached image.
Every sentence that is part of a paragraph should be on it's own line, making it easier to comment on a part of a paragraph.
Overall comments can be left back at the main PR#107; if you are having troubles leaving detailed comments in the file view, let us know here in a comment and we can see what else can be done to include your feedback.

In this way we can engage in discussions about different parts of the file, right where the content exists.

governance.md

durandom

This is a great start. Just some minor nit-picks

governance.md

stefwalter

Nice stuff! Wonderful to see. Left a few comments, I hope they are helpful.

governance.md

stefwalter

Added one more comment about AGPL

governance.md

akrawczy · 2021-12-09T14:34:10Z

governance.md

+These are the Op1st community principles we adhere to:
+1. **Open Source** : Any content we create is released under an open source license. Content includes software, documentations, configuration files, and training materials.
+  - This is crucial to fulfilling our mission around open sourcing operations
+2. **Welcoming and respectful** : We intend to be an open, welcoming, and inclusive community.


Should we mention equity here, as well?

Thanks for thinking of this and suggesting it. I'm going to provide all my context here so everyone can understand, add to, and share the reasoning.

I pulled the three-item turn of phrase together out of a sort-of modern sentiment—it's similar to wording used in projects perceived as inclusive. The general approach is to focus on being as inclusive as possible when designing an architecture for making a more diverse and equitable community. When people come to the community and find it accessible, regardless of who they are, they can more easily and willingly bring their voices to the common table.

But recently I've been thinking about how to bring equitability into these processes, statements, and outcomes, especially since the All In Open Source project started with the goal of open sourcing diversity, equity, and inclusion. I figure one of the first steps is to talk about equity, and I appreciate you seeing it here as an ideal we put forth. That means it's something we talk about in the SIGs—how to be more equitable, how to measure our success at that, how to improve—and thus something we can improve on over time as the project grows more diverse.

We can swap the words around in any order, but the order does have impact. Even more so is picking one word to modify "community" directly. Here are some ideas:

Suggested change

2. **Welcoming and respectful** : We intend to be an open, welcoming, and inclusive community.

2. **Welcoming and respectful** : We intend to be an open, welcoming, equitable, and inclusive community.

Suggested change

2. **Welcoming and respectful** : We intend to be an open, welcoming, and inclusive community.

2. **Welcoming and respectful** : We intend to be an open and welcoming community that is equitable and inclusive.

Suggested change

2. **Welcoming and respectful** : We intend to be an open, welcoming, and inclusive community.

2. **Welcoming and respectful** : We intend to be an equitable community that is open, welcoming, and inclusive.

Suggested change

2. **Welcoming and respectful** : We intend to be an open, welcoming, and inclusive community.

2. **Welcoming and respectful** : We intend to be an inclusive community that is open, welcoming, and equitable.

@akrawczy do you have any preferences of these variations?

governance.md

- As per: operate-first/community#107 (comment) Signed-off-by: Karsten Wade <kwade@redhat.com>

durandom · 2021-12-15T08:31:38Z

@quaid either in the first version or the next iteration of the governance doc, can we have some language about how we work with other communities?
So we can capture that we request or require open transparent processes, etc. and the reasoning why.

quaid · 2021-12-17T00:37:07Z

governance.md

+
+This document contains a work in progress (WIP) draft of the initial governance of the Op1st project (Governance 1.0).
+
+It also has a roadmap for additions coming in the next iteration of governance (Governane 1.1).


Suggested change

It also has a roadmap for additions coming in the next iteration of governance (Governane 1.1).

It also has a roadmap for additions coming in the next iteration of the governance (Governance 1.1).

Just in case this doesn't end up as planned because of cross-commits I made here, I'm reopening this discussion so it appears when looking after the merge is complete.

governance.md

program-management-tracker.md

We can either have our own document that explains this or push an explanation to https://theopensourceway.org as an upstream. Co-authored-by: Marcel Hild <hild@b4mad.net>

- discussion operate-first/community#107 (comment) Signed-off-by: Karsten Wade <kwade@redhat.com>

If this doesn't work immediately, it may take some experimentation to get the correct GitHub Flavored Fix.

I'm committing this fix as I believe it is good enough for the 1.0. This conversation thread is open for review, ideas welcome.

- Many types of contributions - Reference outward for canonical content about contributors and roles Signed-off-by: Karsten Wade <kwade@redhat.com>

@mscherer

These incorporate or address the various comments and questions left here by @mscherer, @rbown, @schwesig, and @pilhuhn. Thanks folx!

@AmarRich

thanks @AmarRich

- Couldn't get it to work from this discussion so doing it here: https://github.com/operate-first/community/pull/107/files/092e770de008cf2c8ccfd95f528b3326618d2baa#r771014862 Signed-off by: Karsten Wade <kwade@redhat.com> <quaid@iquaid.org>

durandom · 2022-01-12T17:02:09Z

/lgtm

quaid · 2022-01-12T17:02:12Z

/unhold

quaid · 2022-01-12T17:04:13Z

/approve

sesheta · 2022-01-12T17:04:31Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: durandom, quaid

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [durandom,quaid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

- Content was ratified in operate-first/community#107 - These changes make it clear to the reader this is the actual formal docuemnt Signed-off-by: Karsten Wade <kwade@redhat.com>

- Content was ratified in #107 - These changes make it clear to the reader this is the actual formal docuemnt Signed-off-by: Karsten Wade <kwade@redhat.com>

- discussion operate-first/community#107 (comment) Signed-off-by: Karsten Wade <kwade@redhat.com>

This is a draft for discussion

092e770

- Merging together ideas and content from Kubernetes, OpenInfra - This commit is the raw first draft of the Governance 1.0 section - The outline for Governance 1.1 section is included in this commit Signed-off-by: Karsten Wade <kwade@redhat.com>

sesheta requested review from durandom and ipolonsk December 8, 2021 19:37

sesheta added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 8, 2021

quaid mentioned this pull request Dec 8, 2021

Governance 1.0 discussion draft #105

Closed

sesheta added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 8, 2021

quaid commented Dec 8, 2021

View reviewed changes

governance.md Show resolved Hide resolved

quaid commented Dec 8, 2021

View reviewed changes

governance.md Show resolved Hide resolved

jeremyeder reviewed Dec 9, 2021

View reviewed changes

governance.md Show resolved Hide resolved

quaid changed the title ~~This is a complete draft for discussion~~ Governance 1.0 complete draft for discussion Dec 9, 2021

anishasthana reviewed Dec 9, 2021

View reviewed changes

governance.md Outdated Show resolved Hide resolved

governance.md Outdated Show resolved Hide resolved

governance.md Outdated Show resolved Hide resolved

governance.md Show resolved Hide resolved

governance.md Show resolved Hide resolved

durandom reviewed Dec 9, 2021

View reviewed changes

stefwalter reviewed Dec 9, 2021

View reviewed changes

mscherer reviewed Dec 9, 2021

View reviewed changes

governance.md Outdated Show resolved Hide resolved

mscherer reviewed Dec 9, 2021

View reviewed changes

governance.md Show resolved Hide resolved

stefwalter reviewed Dec 9, 2021

View reviewed changes

governance.md Outdated Show resolved Hide resolved

akrawczy reviewed Dec 9, 2021

View reviewed changes

governance.md Outdated Show resolved Hide resolved

akrawczy reviewed Dec 9, 2021

View reviewed changes

governance.md Outdated Show resolved Hide resolved

rbowen reviewed Dec 9, 2021

View reviewed changes

governance.md Show resolved Hide resolved

rbowen reviewed Dec 9, 2021

View reviewed changes

governance.md Outdated Show resolved Hide resolved

tumido reviewed Dec 14, 2021

View reviewed changes

governance.md Outdated Show resolved Hide resolved

governance.md Show resolved Hide resolved

governance.md Outdated Show resolved Hide resolved

Adding missing sections

d1adfd2

- As per: operate-first/community#107 (comment) Signed-off-by: Karsten Wade <kwade@redhat.com>

quaid commented Dec 17, 2021

View reviewed changes

governance.md Show resolved Hide resolved

durandom approved these changes Dec 17, 2021

View reviewed changes

governance.md Outdated Show resolved Hide resolved

governance.md Outdated Show resolved Hide resolved

program-management-tracker.md Outdated Show resolved Hide resolved

sesheta added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 17, 2021

quaid and others added 16 commits January 12, 2022 08:49

Link to our canonical & upstream CoC

9ffdbdf

linking to explanation for now

248ec6d

We can either have our own document that explains this or push an explanation to https://theopensourceway.org as an upstream. Co-authored-by: Marcel Hild <hild@b4mad.net>

Clarifying these are placeholders for Community SIG work to-be-done

c7d29ab

- discussion operate-first/community#107 (comment) Signed-off-by: Karsten Wade <kwade@redhat.com>

adding in-file links to sections

f7b2e2a

If this doesn't work immediately, it may take some experimentation to get the correct GitHub Flavored Fix.

Making clear intentions around CoC

0cc01c9

I'm committing this fix as I believe it is good enough for the 1.0. This conversation thread is open for review, ideas welcome.

Clarifying wide range of types of contributions

f4f4fae

- Many types of contributions - Reference outward for canonical content about contributors and roles Signed-off-by: Karsten Wade <kwade@redhat.com>

using permalink for all CoC references

e849a22

Lightweight consensus process clarification

67a8871

Deeper clarity on time window to make decisions

8e48cc2

These incorporate or address the various comments and questions left here by @mscherer, @rbown, @schwesig, and @pilhuhn. Thanks folx!

clarifying Community SIG owns these decisions

210fdb9

grammar fix

ed3dc8a

thanks @AmarRich

Fixing naming confusions

b59d773

Opening the definition of our canopy

6486e2d

opening the canopy of our definition of "open source"

82547ce

widen canopy for meaning of "open community"

83dc55c

Spelling fix

dcc2288

- Couldn't get it to work from this discussion so doing it here: https://github.com/operate-first/community/pull/107/files/092e770de008cf2c8ccfd95f528b3326618d2baa#r771014862 Signed-off by: Karsten Wade <kwade@redhat.com> <quaid@iquaid.org>

quaid force-pushed the main branch from af3ff20 to dcc2288 Compare January 12, 2022 16:58

sesheta removed the lgtm Indicates that a PR is ready to be merged. label Jan 12, 2022

sesheta added the lgtm Indicates that a PR is ready to be merged. label Jan 12, 2022

sesheta removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 12, 2022

durandom merged commit b1bbd37 into operate-first:main Jan 12, 2022

quaid mentioned this pull request Jan 12, 2022

Completion of draft stage, no longer WIP #113

Merged

sesheta pushed a commit that referenced this pull request Jan 12, 2022

Completion of draft stage, no longer WIP (#113)

ecb15af

- Content was ratified in #107 - These changes make it clear to the reader this is the actual formal docuemnt Signed-off-by: Karsten Wade <kwade@redhat.com>

quaid added a commit to quaid/community that referenced this pull request Jan 19, 2022

Clarifying these are placeholders for Community SIG work to-be-done

47c1668

- discussion operate-first/community#107 (comment) Signed-off-by: Karsten Wade <kwade@redhat.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Governance 1.0 complete draft for discussion #107

Governance 1.0 complete draft for discussion #107

quaid commented Dec 8, 2021

quaid commented Dec 8, 2021

quaid commented Dec 8, 2021

durandom left a comment

stefwalter left a comment

stefwalter left a comment

akrawczy Dec 9, 2021

quaid Dec 17, 2021 •

edited

Loading

quaid Jan 11, 2022

durandom commented Dec 15, 2021

quaid Dec 17, 2021 •

edited

Loading

quaid Jan 3, 2022

durandom commented Jan 12, 2022

quaid commented Jan 12, 2022

quaid commented Jan 12, 2022

sesheta commented Jan 12, 2022

	2. Welcoming and respectful : We intend to be an open, welcoming, and inclusive community.
	2. Welcoming and respectful : We intend to be an open, welcoming, equitable, and inclusive community.


		This document contains a work in progress (WIP) draft of the initial governance of the Op1st project (Governance 1.0).

		It also has a roadmap for additions coming in the next iteration of governance (Governane 1.1).

Governance 1.0 complete draft for discussion #107

Governance 1.0 complete draft for discussion #107

Conversation

quaid commented Dec 8, 2021

quaid commented Dec 8, 2021

quaid commented Dec 8, 2021

durandom left a comment

Choose a reason for hiding this comment

stefwalter left a comment

Choose a reason for hiding this comment

stefwalter left a comment

Choose a reason for hiding this comment

akrawczy Dec 9, 2021

Choose a reason for hiding this comment

quaid Dec 17, 2021 • edited Loading

Choose a reason for hiding this comment

quaid Jan 11, 2022

Choose a reason for hiding this comment

durandom commented Dec 15, 2021

quaid Dec 17, 2021 • edited Loading

Choose a reason for hiding this comment

quaid Jan 3, 2022

Choose a reason for hiding this comment

durandom commented Jan 12, 2022

quaid commented Jan 12, 2022

quaid commented Jan 12, 2022

sesheta commented Jan 12, 2022

quaid Dec 17, 2021 •

edited

Loading

quaid Dec 17, 2021 •

edited

Loading