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

Update charter #118

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update charter #118

wants to merge 1 commit into from

Conversation

mrego
Copy link
Member

@mrego mrego commented Dec 4, 2024

This is a patch to update the Servo project charter after the agreements on the TSC regarding the project governance: https://github.com/servo/project/blob/main/governance/README.md

This is a patch to update the Servo project charter after
the agreements on the TSC regarding the project governance:
https://github.com/servo/project/blob/main/governance/README.md

Signed-off-by: Manuel Rego Casasnovas <[email protected]>
@@ -21,19 +21,13 @@ b. The scope of the Project includes collaborative development under the Projec

a. The Technical Steering Committee (the "TSC") will be responsible for all technical oversight of the open source Project.

b. The TSC voting members are initially the Project's Committers. At the inception of the project, the Committers of the Project will be as set forth within the "CONTRIBUTING" file within the Project's code repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the CONTRIBUTING file. Any meetings of the Technical Steering Committee will be open to the public, and can be conducted electronically, via teleconference, or in person.
b. The TSC voting members are as set forth within the [`README.md` file](README.md) within this repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the [`README.md` file](README.md). Any meetings of the Technical Steering Committee will be open to the public, and can be conducted electronically, via teleconference, or in person.
Copy link
Member Author

Choose a reason for hiding this comment

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

I'm removing the "are initially the Project's Committers" as I guess that was from when the TSC was initially setup and it's no longer needed.

@@ -21,19 +21,13 @@ b. The scope of the Project includes collaborative development under the Projec

a. The Technical Steering Committee (the "TSC") will be responsible for all technical oversight of the open source Project.

b. The TSC voting members are initially the Project's Committers. At the inception of the project, the Committers of the Project will be as set forth within the "CONTRIBUTING" file within the Project's code repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the CONTRIBUTING file. Any meetings of the Technical Steering Committee will be open to the public, and can be conducted electronically, via teleconference, or in person.
b. The TSC voting members are as set forth within the [`README.md` file](README.md) within this repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the [`README.md` file](README.md). Any meetings of the Technical Steering Committee will be open to the public, and can be conducted electronically, via teleconference, or in person.
Copy link
Member

Choose a reason for hiding this comment

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

within this repository

Is this text hosted/included on any other website (e.g. included on some LF EU webpage, where it might be unclear what "this repository" might refer to?

Copy link
Member Author

Choose a reason for hiding this comment

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

AFAIK, it's only here. While it's linked from other places, all of them point to here.

We might reword to "the servo/project repository" or something like that.


c. TSC projects generally will involve Contributors and Committers. The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented:
c. TSC projects generally will involve Collaborators, Contributors and Maintainers. The TSC may adopt or modify roles so long as the roles are documented in the [`README.md` file](README.md).
Copy link
Member

Choose a reason for hiding this comment

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

This allows the TSC to add new roles, without needing to amend the charter, right?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think that was allowed before already, but I'm fixing the name of the file as that's not in the CONTRIBUTING file, actually that file has been moved to the book.

So TSC could already do that in the CONTRIBUTING file, and if we didn't do it then the other rules would apply. I'm removing the other rules as it doesn't look like something needed, as we'll have now the process documented somewhere else. I was doing that to simplify the charter, but I'm fine keeping those lines if we think it's better.

Copy link
Member

Choose a reason for hiding this comment

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

Just to clarify, I'm not opposed to this - on the contrary, I would have suggested that we add a line that allows us to define roles in the Readme through regular TSC meetings, since we still need to define some existing roles like Organization admin or infrastructure maintainers.

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.

2 participants