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

Create v1 project governance #28

Merged
merged 3 commits into from
Feb 3, 2023
Merged

Create v1 project governance #28

merged 3 commits into from
Feb 3, 2023

Conversation

theadactyl
Copy link
Member

@theadactyl theadactyl commented Dec 14, 2022

Proposing a project governance model for OpenXLA.

Please see slides from the 12/13/2023 community meeting to get an overview of the goals and principles we are hoping to achieve with this model.

This document is a draft (hence many TODOs), and this PR is open for community review and feedback until Jan 13, 2023. Outstanding comments and planned revisions will be discussed in the OpenXLA community meeting on Jan 17, 2023.

/cc @burmako @joker-eph

Copy link
Contributor

@joker-eph joker-eph left a comment

Choose a reason for hiding this comment

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

Thanks :)

Copy link
Contributor

@burmako burmako left a comment

Choose a reason for hiding this comment

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

LGTM!

@theadactyl theadactyl marked this pull request as draft December 14, 2022 17:39
@theadactyl
Copy link
Member Author

Converting to draft to make it unmergeable during RFC

GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
GOVERNANCE.md Outdated Show resolved Hide resolved
@ManfeiBai
Copy link

Proposing a project governance model for OpenXLA.

Please see slides from the 12/13/2023 community meeting to get an overview of the goals and principles we are hoping to achieve with this model.

This document is a draft (hence many TODOs), and this PR is open for community review and feedback until Jan 13, 2023. Outstanding comments and planned revisions will be discussed in the OpenXLA community meeting on Jan 17, 2023.

/cc @burmako @joker-eph

Do we have meeting recording link to share about the OpenXLA community meeting on Jan 17, 2023?

@theadactyl theadactyl marked this pull request as ready for review February 2, 2023 00:48
@theadactyl
Copy link
Member Author

@ManfeiBai the meeting actually happened a week later than normal. I'll be uploading the video shortly and linking to the meeting directory ASAP.

Copy link
Contributor

@burmako burmako left a comment

Choose a reason for hiding this comment

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

I think this is a great initial version of OpenXLA governance.

The core values are compelling, the decision-making process looks sound, and the overall spirit of the proposal sounds good to me. I especially like the proposed hierarchical structure because it makes it clear what groups are involved in what decisions.

There are some rough edges in the proposal, e.g. there are some TODOs and some implementation details may need additional work. However, as Mehdi mentioned in one of the threads, there is a clear process for updating this document if needed, so I am confident that we'll figure out these things together as a community as we go.

GOVERNANCE.md Outdated

OpenXLA favors a consensus-driven approach to development. Contributors are expected to engage in discussions and attempt to resolve all blockers raised by other contributors, either through RFCs or during code reviews discussions. We are using blocking consensus to ensure “equal footing” and to act as a forcing-function to keep the community whole.

Consensus is employed by many other projects, some like LLVM don’t define a structure around it and operate like a do-ocracy. We recognize that there are limits to consensus with respect to scaling a project, and as such we also adopt a technical governance structure that is hierarchical. This will:
Copy link
Contributor

Choose a reason for hiding this comment

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

Recommend quotes around "do-ocracy"

Copy link
Contributor

@joker-eph joker-eph left a comment

Choose a reason for hiding this comment

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

Thanks for driving this Thea!
I trust you took good notes of the comments to be addressed incrementally, this is an important stepping stone we will be able to build on top of, so I am very supportive of landing this to unblock the governance structure to start getting formalized.

@theadactyl theadactyl merged commit 15b928d into main Feb 3, 2023
@theadactyl
Copy link
Member Author

Thanks to all the reviewers & community feedback -- excited to move forward on this!

@GMNGeoffrey GMNGeoffrey deleted the theadactyl-patch-6 branch May 2, 2023 21:04
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.

8 participants