Skip to content

The JSON Schema Charter #325

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

Open
wants to merge 86 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
Show all changes
86 commits
Select commit Hold shift + click to select a range
0b8d59b
Initial commit of charter template Copy from OpenJS Foundation CPC repo
Relequestual Feb 7, 2023
4666a22
Add comments to heading for people who might edit the file, and a lin…
Relequestual Feb 7, 2023
3cc72d2
Add content for Guiding Principles
Relequestual Feb 7, 2023
b7de5e1
Add content for Scope section
Relequestual Feb 7, 2023
a4bf147
Modified version of Scope
Relequestual Feb 7, 2023
327b09e
Add sections 1.1 and 1.2 re scope In-scope does not yet have any sugg…
Relequestual Feb 7, 2023
cdc7cf5
Add Relationship with OpenJS Foundation CPC section
Relequestual Feb 7, 2023
d60d388
Add Other Formal Project Relationships section Left blank
Relequestual Feb 7, 2023
ece5e53
Add Governing Body (TSC) section
Relequestual Feb 7, 2023
2d38695
Add Roles and Responsibilities section
Relequestual Feb 9, 2023
29ed1a5
Add Project Operations and Management section
Relequestual Feb 9, 2023
c9a6006
Add Decision-making and Voting section
Relequestual Feb 10, 2023
d0d58ba
Add Definitions section
Relequestual Feb 10, 2023
0c0f97c
Add footer with links to resources
Relequestual Feb 10, 2023
557c0a2
Fix typos
Relequestual Feb 20, 2023
5abe1bd
Add note about how testing for agreement is not the same as voting.
Relequestual Feb 21, 2023
9ba125a
Refine consensus model
Relequestual Feb 23, 2023
9301be9
Tidy up and break out section for ADRs
Relequestual Feb 23, 2023
e3ecb1e
Add definition of TSC
Relequestual Mar 3, 2023
f6ac84c
Recognize other project roles to be defined
Relequestual Mar 3, 2023
a2af3ba
Add detail about signal based voting at the Test for Agreement stage …
Relequestual Mar 8, 2023
3fc951e
Spacing
Relequestual Mar 8, 2023
df8930a
Amend decision making process in charter
Relequestual Mar 14, 2023
cfa2ae9
Fix inconsistent name for repos
Relequestual Mar 14, 2023
a6bc2a8
Add details for project scope in the charter
Relequestual Mar 14, 2023
d30322d
Add line about non-technical conflicts to the charter
Relequestual Mar 16, 2023
fea1163
Update CHARTER.md
Relequestual Mar 20, 2023
14d7ca2
Fix using upper case inside bracket
Relequestual Mar 24, 2023
90896a9
Remove specific mention of linting tooling.
Relequestual Mar 28, 2023
dc3785a
Add time limits to some stages of consensus process
Relequestual Mar 30, 2023
c35d423
Provide blocker fallback
Relequestual Apr 6, 2023
c1f0fa4
Add details to ADR for consensus based TSC
Relequestual Apr 11, 2023
42e1c54
Remove comments not intended for final document
Relequestual Apr 13, 2023
1b31445
Fix typo
Relequestual Apr 13, 2023
9634a60
Remove additional comment and mention governance document is to be cr…
Relequestual Apr 13, 2023
8f1df0f
Remove (optional) from headings in charter
Relequestual Apr 13, 2023
f5dd0f5
Add initial TSC members list
Relequestual Apr 13, 2023
d083f46
Fix grammar
Relequestual Apr 13, 2023
6653e46
Fix typo in charter
Relequestual Apr 13, 2023
c84610a
Apply grammar and typo fixes to charter from PR review
Relequestual Apr 13, 2023
a4943cd
Remove specific TSC member requirement about meetings
Relequestual Apr 17, 2023
94d1801
Fix double typo with thanks to @mwadams
Relequestual Apr 17, 2023
c9ab2dd
List names and links for the TSC members
Relequestual Apr 18, 2023
b5f0e85
Fix typo and quotes in charter
Relequestual Apr 18, 2023
b2efdce
Fix typos and quotes in charter
Relequestual Apr 18, 2023
d2f853c
Fix grammar in charter
Relequestual Apr 18, 2023
035ab9b
Remove 'section' from titles
Relequestual Apr 18, 2023
dc3e685
Fix language specific spellings in charter
Relequestual Apr 18, 2023
631db8c
Specifically mention specifications we use and that use us as out of …
Relequestual Apr 18, 2023
8eb9883
Do not reference 'JSON Schema Org'
Relequestual Apr 24, 2023
341ecef
Do not define what the OpenJS Foundation does, per feedback from the …
Relequestual Apr 25, 2023
f4e35ff
Remove mention of fund and budgeting, as the charter is about the fou…
Relequestual Apr 25, 2023
e94c0cb
Remove mention of finances as per last commit
Relequestual Apr 25, 2023
9e1ad26
Remove mention of special interest groups in favour of noting the com…
Relequestual Apr 25, 2023
52bedb3
Loosen TSC meeting expectations
Relequestual Apr 26, 2023
4a2ad4a
Intro section better reflects the JSON Schema projects relationship w…
Relequestual Apr 25, 2023
397a8d1
Don't use 'we' and use proper pronouns
Relequestual May 3, 2023
d79198e
Move the list of initial TSC members outside of the charter document
Relequestual May 3, 2023
59deddb
Use 'private' as opposed to 'non-public'
Relequestual May 3, 2023
f1974e2
Remove the explicit mention of ingesting tooling into the project
Relequestual Jun 15, 2023
c872a5f
Note what kinds of discussions and votes can and should be made private
Relequestual Jun 16, 2023
a974117
Move the paragraph about TSC period of leave to membership section
Relequestual Jun 16, 2023
86ff12e
Create governance document and move governance and process related co…
Relequestual Jun 23, 2023
55aa9b3
Refined definition of TSC in context
Relequestual Jun 23, 2023
75542a8
Move content about voting and additional project roles from charter t…
Relequestual Jun 26, 2023
aea0b80
Add interoperability to list of in scope concerns
Relequestual Jun 26, 2023
fbe8b54
Change 'JSON data' to 'JSON-compatible data' in charter
Relequestual Jun 27, 2023
63cf673
Use more inclusive phrasing
Relequestual Jul 10, 2023
a996e13
Remove content which is mostly a duplication of section 2
Relequestual Jul 10, 2023
2a92249
Simplify out of scope sction. Add engaging with upstream and downstre…
Relequestual Jul 11, 2023
58d942b
Move TSC policy elements to charter from governance document
Relequestual Jul 13, 2023
8b2ed66
Add that TSC meetings should have an agenda
Relequestual Jul 13, 2023
be38006
Move roles and responsibilities section back to charter document with…
Relequestual Jul 25, 2023
4c92fc6
Migrate some content regarding process out of the governance document…
Relequestual Jul 25, 2023
507246b
Remove governance document for the Charter PR
Relequestual Jul 25, 2023
26f9265
Improve phrasing for out of scope
Relequestual Aug 2, 2023
31d5f6e
Tighten phrasing
Relequestual Aug 2, 2023
47a0d79
Note that updates to the charter must be approved by the OpenJS Found…
Relequestual Aug 2, 2023
37eccb2
Include the CPC
Relequestual Aug 2, 2023
bea5924
Strive to be open, always!
Relequestual Aug 2, 2023
91d5133
Remove initial included license and add CC-BY 4.0
Relequestual Aug 3, 2023
cdce30b
Fix posession
Relequestual Aug 3, 2023
06240f9
Fix grammar
Relequestual Aug 9, 2023
ad35025
Remove mention of the OpenJS Foundation
Relequestual Jun 17, 2025
ddf82c4
Fix grammar
Relequestual Jun 17, 2025
573ad4e
Remove mention of OpenJS Foundation from ADR
Relequestual Jun 17, 2025
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
Prev Previous commit
Next Next commit
Add Governing Body (TSC) section
  • Loading branch information
Relequestual committed Feb 10, 2023
commit ece5e53040a5f56112d8123eefa49e762cfd3fff
28 changes: 22 additions & 6 deletions CHARTER.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,14 +43,30 @@ Most large, complex open source communities have both a business and a technical

Section Intentionally Left Blank

## Section 3: ${PROJECT TSC} Governing Body
## Section 3: JSON Schema Org Governing Body (TSC)
<!-- https://github.com/json-schema-org/community/discussions/286#discussioncomment-4391284 -->

_directions: describe the structure of the group responsible for managing_
_the project and its respective organization and repositories. If there are_
_specific rules for membership or participation in the group, list them here or_
_by reference to a governance.md document._
The TSC is initially established from the observed major contributors who are currently active and in good standing.

ex. [Node.js TSC Charter](https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md#section-3-establishment-of-the-tsc)
There is no maximum TSC membership size. The TSC must have a minimum of four members.

Changes to TSC membership should be posted in the agenda, and may be suggested as any other agenda item.

TSC memberships are not time-limited.

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 exclusivly on the open source project). While at this time there is 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.

TSC members are expected to regularly participate in TSC activities.

The TSC will meet regularly using virtual conferencing tools. The meeting will be directed by the TSC Chairperson(s). Responsibility for directing individual meetings may be delegated by a TSC Chairperson to any other TSC member. Minutes or an appropriate recording will be taken and made available to the community through accessible public postings.

The TSC may, at its discretion, invite any number of non-voting observers to participate in the public portion of TSC discussions and meetings.
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd encourage you to make those sessions public all the time.

Copy link
Member Author

Choose a reason for hiding this comment

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

That's the intent! Public as much as possible!
I note that the CPC has a private portion of the call on occasion, for whatever reason.

Copy link
Contributor

Choose a reason for hiding this comment

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

Whereby I meant that the session should be public by default (with an agenda and videoconf link made available upfront), not that it is private by default and that the TSC may decide to open it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Agreed. That is what is intended. If it doesn't come across that way, it needs revising.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think this sentence is correct. It should be specified somewhere else that there might a private portion of the meeting.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think this sentence is correct. It should be specified somewhere else that there might a private portion of the meeting.

Well, but the problem of making allowing access to the TSC meeting at the discretion of the TSC, is that this makes the meeting private by default, and requires action by the TSC to make it public.

Copy link
Member Author

Choose a reason for hiding this comment

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

It doesn't say that. It says the TSC may invite people to the public portion of the meeting. You're reading into it something which isn't there.

Technically, as it is public, and the details of how to access it will be public, anyone could invite anyone. But I wanted to make it explicit that TSC may invite guests.

I don't recall specifically where I borrowed the phrasing from, but I agree it is not clear and can be improved.

Copy link
Contributor

Choose a reason for hiding this comment

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

You're reading into it something which isn't there.

I dont doubt your intentions. I’m stating that the text doesn’t match them. ;)


A TSC member may be removed by vote from the TSC if, during a 3-month period, all of the following are true:

Copy link
Member

Choose a reason for hiding this comment

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

Any restrictions on the maximum percentage of Governing Body members that can be employed by the same company? The risk of one company exerting undue influence over the direction of the project is real.

Copy link
Member

Choose a reason for hiding this comment

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

We looked at this before, I but I don't remember (or necessarily agree with) why it was removed.

Copy link
Member Author

@Relequestual Relequestual Aug 18, 2023

Choose a reason for hiding this comment

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

This clause was seen more as a governance concern than a charter related concern, and was moved out to #456, specifically this line. (This also allows us to update it without having to go back to the OpenJS Foundation for their approval.)

The risk of one company exerting undue influence over the direction of the project is real.

I hear you. Regardless of what anyone in such a position reports, such as no to little influence, that doesn't mean things can't change, or it shouldn't be a concern.

We are trying to start addressing this by engaging more with implementers: #412 - Comments and suggestions welcome.

Additionally, we are looking to encourage users to self report: #441

Further, there are plans to create a stakeholders group: Community and DevRel Plan (view) (Although these are a little vague currently).

Open to thoughts, suggestions, comments, on all of this and anything else that comes to mind as to how we can expand our TSC. @karenetheridge your voice carries weight here =]

Copy link
Member

Choose a reason for hiding this comment

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

I don't think this presents an immediate problem anymore, but I do think it's still a good idea to have such a limitation.

- They attend fewer than 25% of the regularly scheduled meetings
- They do not participate in any TSC votes
- They do not provide any form of excuse or no excuse is known for their absence

## Section 4: Roles & Responsibilities

Expand Down