Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add initial bootstrap governance #4

Merged
merged 1 commit into from
Jan 17, 2022

Conversation

afrittoli
Copy link
Contributor

Add an initial governance.md to define the bootstrap governance
committee

Signed-off-by: Andrea Frittoli andrea.frittoli@gmail.com

Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title should be CD Events not Tekton

As discussed at the CD Events SIG, it might make sense to have this file in .github so that it can be referenced from all repositories.

governance.md Outdated Show resolved Hide resolved
governance.md Outdated Show resolved Hide resolved
governance.md Show resolved Hide resolved
@m-linner-ericsson
Copy link
Contributor

As discussed at the CD Events SIG, it might make sense to have this file in .github so that it can be referenced from all repositories.

I don't know if it was @oleg-nenashev or @sbtaylor15 who mentioned this.

When looking again at the .github repository I didn't find any good reason for putting the governance there. I know it's good for code of conduct and contributor guidelines as GitHub automatically links it, but I can't see any purpose with the governance. Am I missing something here?

@oleg-nenashev
Copy link
Member

It is basically style topic. As you prefer. I just do not want to have governance being version along with the spec tags. Sorry moving it to a separate repo makes sense to me

@afrittoli
Copy link
Contributor Author

afrittoli commented Dec 16, 2021

It is basically style topic. As you prefer. I just do not want to have governance being version along with the spec tags. Sorry moving it to a separate repo makes sense to me

The governance docs are not really versioned, so I'm not sure I see the issue?

We could have a dedicated repo for community / governance type of documents, owned by the project governance team, but that seemed a bit of an overhead to just get started - I wanted to avoid spending too much time in managing a lot of repos :P

@oleg-nenashev I you feel strongly about using the .github repo for this, it works for me.

@afrittoli
Copy link
Contributor Author

I addressed all comments.
I also made a PR to the .github repo: cdevents/.github#1
We can decide next time we meet which of the two to merge, or if we shall create a new repo to host this.

Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Time to merge it? All the text looks reasonable to me. IMHO there are too many lists planned, maybe some of them could be moved to GitHub Issues or discussions. The Code of Conduct escalations handing could be also directly delegated to the CDF, but no strong opinion here

@e-backmark-ericsson
Copy link
Contributor

Merging this as a base for our govenance model

@e-backmark-ericsson e-backmark-ericsson merged commit c6ec5fd into cdevents:main Jan 17, 2022
@xibz xibz mentioned this pull request Aug 25, 2023
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants