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.

Sign up for GitHub

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 6 additions & 12 deletions governance/CHARTER.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This Charter sets forth the responsibilities and procedures for
technical contribution to, and oversight of, the Servo open source
project, which has been established as a project of Linux Foundation
Europe, a Belgian private stichting headquartered at Kunstlaan 56,
Brussels (“LF Europe”). All contributors (including
Brussels ("LF Europe"). All contributors (including
committers, maintainers, and other technical positions) and other
participants in the Project (collectively, "Collaborators") must comply
with the terms of this Charter.
Expand All @@ -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.

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.


> i. Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project;
>
> ii. Committers are Contributors who have earned the ability to modify ("commit") source code, documentation or other technical artifacts in a project's repository; and
>
> iii. A Contributor may become a Committer by a majority approval of the existing Committers. A Committer may be removed by a majority approval of the other existing Committers.

d. Participation in the Project through becoming a Contributor and Committer is open to anyone so long as they abide by the terms of this Charter.
d. Participation in the Project through becoming a Collaborator, Contributor or Maintainer is open to anyone so long as they abide by the terms of this Charter.

e. The TSC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Committer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Committers, and create new roles, and publicly document any TSC roles, as it sees fit.
e. The TSC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Collaborators to Contributor status or Contributors to Maintainer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Maintainers, and create new roles, and publicly document any TSC roles, as it sees fit.

f. The TSC will annually elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC. The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact and any funding effort supporting the Project.

Expand All @@ -51,7 +45,7 @@ g. Responsibilities: The TSC will be responsible for all aspects of oversight r
>
> vi. establishing community norms, workflows, issuing releases, and security issue reporting policies;
>
> vii. approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with LF Europe to resolve matters or concerns that may arise as set forth in Section 7 of this Charter;
> vii. approving and implementing policies and processes for contributing (to be published in the [`README.md` file](README.md)) and coordinating with LF Europe to resolve matters or concerns that may arise as set forth in Section 7 of this Charter;
>
> viii. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and
>
Expand Down