Skip to content

Commit 6e4aba4

Browse files
committed
Modify TSC membership by employer conditions
As suggested by @benjagm
1 parent 979c719 commit 6e4aba4

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

GOVERNANCE.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,7 @@ For context, see https://github.com/json-schema-org/community/pull/325
99
<!-- This document is managed in the json-schema-org/community GitHub repository. Please do NOT modify this file in another repository as changes may be overridden. -->
1010

1111
## JSON Schema Governing Body (TSC)
12-
13-
While the project is not looking to obtain "Impact" project status within the OpenJS Foundation, there is no requirement set out to limit the number of TSC members by employer. It is in some cases considered difficult or even unhelpful for the project to limit the number or percentage of TSC members by employer (especially when an employer has employed individuals already active in the community to work exclusively on the open source project). While at this time there are no limits on TSC membership by employer, the TSC will strive to keep to at least less than 50%, ideally 33% (One third, one in three). The TSC will re-evaluate this specific clause at least every six months, and aim to revise it within one year to meet the "no more than 1/3 employer member affiliation" mandate.
12+
It is in some cases considered difficult or even unhelpful for the project to limit the number or percentage of TSC members by employer (especially when an employer has employed individuals already active in the community to work exclusively on the open source project). While at this time there are no limits on TSC membership by employer, as soon as the TSC reach 10 members a rule will be enabled to set the limit to at least less than 50%, ideally 33% (One third, one in three).
1413

1514
TSC members are expected to regularly participate in TSC activities.
1615

0 commit comments

Comments
 (0)