Skip to content

Commit 33c1088

Browse files
fujitatomoyaclalancette
authored andcommitted
one sentence per line.
Signed-off-by: Tomoya.Fujita <[email protected]>
1 parent 5fc458b commit 33c1088

File tree

1 file changed

+54
-22
lines changed

1 file changed

+54
-22
lines changed

source/Governance/ros2-tsc-charter.rst

Lines changed: 54 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -18,49 +18,64 @@ Charter
1818
Guiding Principles & Rationale
1919
---------------------------------
2020

21-
The ROS 2 Project (“ROS 2” or “the project”) operates openly, such that plans, decisions, and processes are freely available to the general public in a timely manner. All interested parties should have access to information about the project direction and timeline, from casual observers to companies planning product releases.
21+
The ROS 2 Project (“ROS 2” or “the project”) operates openly, such that plans, decisions, and processes are freely available to the general public in a timely manner.
22+
All interested parties should have access to information about the project direction and timeline, from casual observers to companies planning product releases.
2223

2324
Responsibilities of the TSC
2425
---------------------------
2526

26-
The ROS 2 Technical Steering Committee (“TSC”) is responsible for the technical direction that the project takes. The TSC makes decisions on the project roadmap, developer policies and process, release schedule, and other matters that require technical supervision in ROS 2. It is intended that these decisions be final and authoritative, but successful implementation of any decision depends on commitment of the necessary resources from the organizations represented on the TSC.
27+
The ROS 2 Technical Steering Committee (“TSC”) is responsible for the technical direction that the project takes.
28+
The TSC makes decisions on the project roadmap, developer policies and process, release schedule, and other matters that require technical supervision in ROS 2.
29+
It is intended that these decisions be final and authoritative, but successful implementation of any decision depends on commitment of the necessary resources from the organizations represented on the TSC.
2730

2831
The TSC aims to ensure the following characteristics of the project:
2932

30-
#. **Independent and transparent governance​.**
33+
#. **Independent and transparent governance​**
34+
3135
The project is driven by the community that contributes to and uses the resulting software, with Open Robotics as the founding project sponsor.
3236

33-
#. **Coordination.**
37+
#. **Coordination**
38+
3439
Those individuals and organizations that are contributing the labor and other resources to develop the project are in regular contact with each other to coordinate their plans and activities.
3540

36-
#. **Pace & quality.**
41+
#. **Pace & quality**
42+
3743
The project advances as quickly as possible given the available resources and without sacrificing quality in the resulting software.
3844

39-
#. **Policies.**
45+
#. **Policies**
46+
4047
Contributions to the project are received, reviewed, and tested in a manner that is consistent with the requirements for widespread adoption of the resulting software in industry.
4148

4249
Establishment of the TSC
4350
------------------------
4451

45-
The TSC is made up of individuals who contribute materially to the project and/or individuals who represent organizations that contribute materially to the project. The TSC seeks to coordinate the contributions that members and their organizations are voluntarily making to the project. The TSC cannot compel or oblige any action on the part of a member, his or her organization, or that organization’s employees.
52+
The TSC is made up of individuals who contribute materially to the project and/or individuals who represent organizations that contribute materially to the project.
53+
The TSC seeks to coordinate the contributions that members and their organizations are voluntarily making to the project.
54+
The TSC cannot compel or oblige any action on the part of a member, his or her organization, or that organization’s employees.
4655

47-
#. Material contribution is the commitment of a minimum level of effort toward developing software and/or documentation that is contributed to the project under the appropriate open source license. This contribution may be in the form of in-kind labor and/or outsourced work. No fees or payments beyond material contribution to the project are required for TSC membership.
56+
#. Material contribution is the commitment of a minimum level of effort toward developing software and/or documentation that is contributed to the project under the appropriate open source license.
57+
This contribution may be in the form of in-kind labor and/or outsourced work.
58+
No fees or payments beyond material contribution to the project are required for TSC membership.
4859

49-
#. The minimum level of effort commitment required to qualify for TSC membership is **​1 full-time equivalent (FTE)**. This level may be changed by the TSC via a standard TSC motion and vote.
60+
#. The minimum level of effort commitment required to qualify for TSC membership is **​1 full-time equivalent (FTE)**.
61+
This level may be changed by the TSC via a standard TSC motion and vote.
5062

5163
#. The TSC must have at least three members.
5264

5365
#. TSC membership is not time-limited.
5466

55-
#. The size of the TSC is limited to **30​ members**. This limit may be changed by the TSC via a standard TSC motion and vote.
67+
#. The size of the TSC is limited to **30​ members**.
68+
This limit may be changed by the TSC via a standard TSC motion and vote.
5669

57-
#. The TSC may add additional members to the TSC by a standard TSC motion and vote. When considering the addition of a new member, the TSC is responsible for determining whether that potential member’s material contributions to the project are appropriate and sufficient to qualify for membership.
70+
#. The TSC may add additional members to the TSC by a standard TSC motion and vote.
71+
When considering the addition of a new member, the TSC is responsible for determining whether that potential member’s material contributions to the project are appropriate and sufficient to qualify for membership.
5872

5973
#. A TSC member may be removed from the TSC by voluntary resignation, by a standard TSC motion and vote, or in accordance with the following participation rule:
6074

6175
* In the case where an individual TSC member -- within any three-month period -- attends fewer than 1⁄3 of the regularly scheduled meetings, does not participate in TSC discussions, and does not participate in TSC votes, the member shall be automatically removed from the TSC.
6276

63-
#. The TSC will periodically review the material contributions of TSC members to ensure that they continue to meet the minimum level of effort established by the TSC for TSC membership. In the case where a TSC member’s material contributions fall below that minimum level, the TSC may decide to remove that TSC member by a standard TSC motion and vote.
77+
#. The TSC will periodically review the material contributions of TSC members to ensure that they continue to meet the minimum level of effort established by the TSC for TSC membership.
78+
In the case where a TSC member’s material contributions fall below that minimum level, the TSC may decide to remove that TSC member by a standard TSC motion and vote.
6479

6580
#. With the exception of Open Robotics, there may be at most one TSC member from any single employer.
6681

@@ -79,44 +94,61 @@ The TSC meets regularly in-person and/or via an electronic means.
7994

8095
#. A minimum of three TSC members is required to establish a quorum to hold a TSC meeting.
8196

82-
#. Participation in a TSC meeting is open to current members. Other organizations or individuals may be invited by Open Robotics to observe a TSC meeting. TSC members may suggest to Open Robotics the names of individuals or organizations for consideration as potential observers.
97+
#. Participation in a TSC meeting is open to current members.
98+
Other organizations or individuals may be invited by Open Robotics to observe a TSC meeting.
99+
TSC members may suggest to Open Robotics the names of individuals or organizations for consideration as potential observers.
83100

84-
#. Minutes from each TSC meeting are published by Open Robotics shortly after the meeting. TSC meetings are not broadcast or recorded verbatim, but they should be treated as public discussions.
101+
#. Minutes from each TSC meeting are published by Open Robotics shortly after the meeting.
102+
TSC meetings are not broadcast or recorded verbatim, but they should be treated as public discussions.
85103

86104
Working Groups
87105
--------------
88106

89107
The TSC may establish one or more working groups (“WGs”) to discuss specific topics in greater detail than is practical for the TSC as a whole.
90108

91-
#. A WG may be established by the TSC via standard TSC motion and vote. At the time of such establishment, the TSC is responsible for deciding the name, scope, and initial chair of the new WG.
109+
#. A WG may be established by the TSC via standard TSC motion and vote.
110+
At the time of such establishment, the TSC is responsible for deciding the name, scope, and initial chair of the new WG.
92111

93112
#. A WG may be dissolved by the TSC via standard TSC motion and vote.
94113

95-
#. Each WG must be chaired by a TSC member. The chair of a WG is responsible for all aspects of that WG’s operation, including membership, meeting schedule, and decision-making.
114+
#. Each WG must be chaired by a TSC member.
115+
The chair of a WG is responsible for all aspects of that WG’s operation, including membership, meeting schedule, and decision-making.
96116

97117
#. A WG may bring findings and/or recommendations to the TSC for discussion and/or decision.
98118

99119
Voting
100120
------
101121

102-
The TSC aims to operate by consensus. When consensus cannot be reached, decisions should in most cases be made by resource commitment: e.g., if a member wants to include a feature on the roadmap but the rest of the TSC is uninterested, then that member can choose to commit his or her organization’s contribution to development of the desired feature and thereby have it included in the roadmap. In cases where consensus cannot be reached and resource commitment is insufficient or inappropriate, simple majority voting is used, with each member having one vote.
122+
The TSC aims to operate by consensus.
123+
When consensus cannot be reached, decisions should in most cases be made by resource commitment: e.g., if a member wants to include a feature on the roadmap but the rest of the TSC is uninterested, then that member can choose to commit his or her organization’s contribution to development of the desired feature and thereby have it included in the roadmap.
124+
In cases where consensus cannot be reached and resource commitment is insufficient or inappropriate, simple majority voting is used, with each member having one vote.
103125

104126
Project Roles
105127
-------------
106128

107-
TSC membership does not influence the handling of code contributions, which continues to follow the established federated development model in which contributions are made by pull request and reviewed and approved by the appropriate maintainer(s) prior to merging. Commit rights and maintainer status are earned through code contributions to the relevant package(s).
129+
TSC membership does not influence the handling of code contributions, which continues to follow the established federated development model in which contributions are made by pull request and reviewed and approved by the appropriate maintainer(s) prior to merging.
130+
Commit rights and maintainer status are earned through code contributions to the relevant package(s).
108131

109132
Confidentiality
110133
---------------
111134

112-
The TSC is set up to transparently guide the community. However, to facilitate effective communication, the ability to have some confidential discussions is important. TSC members should share confidential information within the TSC and other members are expected to respect that confidentiality. The following are rules regarding confidentiality in TSC communications, events, and meetings. All other communications may be made freely available to the broader community for transparency. Breaking the rules in this section is sufficient, but not necessary, causality for expulsion of the representative or member company, depending on the nature of the infraction, from the TSC by a standard motion and vote.
135+
The TSC is set up to transparently guide the community.
136+
However, to facilitate effective communication, the ability to have some confidential discussions is important.
137+
TSC members should share confidential information within the TSC and other members are expected to respect that confidentiality.
138+
The following are rules regarding confidentiality in TSC communications, events, and meetings.
139+
All other communications may be made freely available to the broader community for transparency.
140+
Breaking the rules in this section is sufficient, but not necessary, causality for expulsion of the representative or member company, depending on the nature of the infraction, from the TSC by a standard motion and vote.
113141

114142
#. Statements made by individuals in discussions surrounding a vote or topic of contention which are not reflected in the publicly posted minutes should be considered confidential.
115143

116-
#. Statements made by individuals regarding companies, research groups, individuals, or other entities for which they are not also members should be considered confidential. This is exempt when the entity in question is a member and in attendance to the TSC meeting or event.
144+
#. Statements made by individuals regarding companies, research groups, individuals, or other entities for which they are not also members should be considered confidential.
145+
This is exempt when the entity in question is a member and in attendance to the TSC meeting or event.
117146

118147
#. Statements made in obvious confidence or explicitly stated as confidential regarding their own entity or opinions should remain confidential.
119148

120-
#. Rule a-c may be waived by the TSC member who made the statement only by explicit verbal or written approval. If the existence of a waiver is put into question by either party, this waiver is considered nullified.
149+
#. Rule a-c may be waived by the TSC member who made the statement only by explicit verbal or written approval.
150+
If the existence of a waiver is put into question by either party, this waiver is considered nullified.
121151

122-
#. Affiliates of TSC member organizations or guests of TSC events privy to confidential information will be held to the same standards set out in this section. It is the responsibility of the TSC member issuing invitations or sharing information to inform relevant parties of these confidentiality requirements. If this policy is broken, the TSC member is in full responsibility for the disclosure.
152+
#. Affiliates of TSC member organizations or guests of TSC events privy to confidential information will be held to the same standards set out in this section.
153+
It is the responsibility of the TSC member issuing invitations or sharing information to inform relevant parties of these confidentiality requirements.
154+
If this policy is broken, the TSC member is in full responsibility for the disclosure.

0 commit comments

Comments
 (0)