-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
The JSON Schema Charter #325
Open
Relequestual
wants to merge
83
commits into
json-schema-org:main
Choose a base branch
from
Relequestual:charter
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
83 commits
Select commit
Hold shift + click to select a range
0b8d59b
Initial commit of charter template Copy from OpenJS Foundation CPC repo
Relequestual 4666a22
Add comments to heading for people who might edit the file, and a lin…
Relequestual 3cc72d2
Add content for Guiding Principles
Relequestual b7de5e1
Add content for Scope section
Relequestual a4bf147
Modified version of Scope
Relequestual 327b09e
Add sections 1.1 and 1.2 re scope In-scope does not yet have any sugg…
Relequestual cdc7cf5
Add Relationship with OpenJS Foundation CPC section
Relequestual d60d388
Add Other Formal Project Relationships section Left blank
Relequestual ece5e53
Add Governing Body (TSC) section
Relequestual 2d38695
Add Roles and Responsibilities section
Relequestual 29ed1a5
Add Project Operations and Management section
Relequestual c9a6006
Add Decision-making and Voting section
Relequestual d0d58ba
Add Definitions section
Relequestual 0c0f97c
Add footer with links to resources
Relequestual 557c0a2
Fix typos
Relequestual 5abe1bd
Add note about how testing for agreement is not the same as voting.
Relequestual 9ba125a
Refine consensus model
Relequestual 9301be9
Tidy up and break out section for ADRs
Relequestual e3ecb1e
Add definition of TSC
Relequestual f6ac84c
Recognize other project roles to be defined
Relequestual a2af3ba
Add detail about signal based voting at the Test for Agreement stage …
Relequestual 3fc951e
Spacing
Relequestual df8930a
Amend decision making process in charter
Relequestual cfa2ae9
Fix inconsistent name for repos
Relequestual a6bc2a8
Add details for project scope in the charter
Relequestual d30322d
Add line about non-technical conflicts to the charter
Relequestual fea1163
Update CHARTER.md
Relequestual 14d7ca2
Fix using upper case inside bracket
Relequestual 90896a9
Remove specific mention of linting tooling.
Relequestual dc3785a
Add time limits to some stages of consensus process
Relequestual c35d423
Provide blocker fallback
Relequestual c1f0fa4
Add details to ADR for consensus based TSC
Relequestual 42e1c54
Remove comments not intended for final document
Relequestual 1b31445
Fix typo
Relequestual 9634a60
Remove additional comment and mention governance document is to be cr…
Relequestual 8f1df0f
Remove (optional) from headings in charter
Relequestual f5dd0f5
Add initial TSC members list
Relequestual d083f46
Fix grammar
Relequestual 6653e46
Fix typo in charter
Relequestual c84610a
Apply grammar and typo fixes to charter from PR review
Relequestual a4943cd
Remove specific TSC member requirement about meetings
Relequestual 94d1801
Fix double typo with thanks to @mwadams
Relequestual c9ab2dd
List names and links for the TSC members
Relequestual b5f0e85
Fix typo and quotes in charter
Relequestual b2efdce
Fix typos and quotes in charter
Relequestual d2f853c
Fix grammar in charter
Relequestual 035ab9b
Remove 'section' from titles
Relequestual dc3e685
Fix language specific spellings in charter
Relequestual 631db8c
Specifically mention specifications we use and that use us as out of …
Relequestual 8eb9883
Do not reference 'JSON Schema Org'
Relequestual 341ecef
Do not define what the OpenJS Foundation does, per feedback from the …
Relequestual f4e35ff
Remove mention of fund and budgeting, as the charter is about the fou…
Relequestual e94c0cb
Remove mention of finances as per last commit
Relequestual 9e1ad26
Remove mention of special interest groups in favour of noting the com…
Relequestual 52bedb3
Loosen TSC meeting expectations
Relequestual 4a2ad4a
Intro section better reflects the JSON Schema projects relationship w…
Relequestual 397a8d1
Don't use 'we' and use proper pronouns
Relequestual d79198e
Move the list of initial TSC members outside of the charter document
Relequestual 59deddb
Use 'private' as opposed to 'non-public'
Relequestual f1974e2
Remove the explicit mention of ingesting tooling into the project
Relequestual c872a5f
Note what kinds of discussions and votes can and should be made private
Relequestual a974117
Move the paragraph about TSC period of leave to membership section
Relequestual 86ff12e
Create governance document and move governance and process related co…
Relequestual 55aa9b3
Refined definition of TSC in context
Relequestual 75542a8
Move content about voting and additional project roles from charter t…
Relequestual aea0b80
Add interoperability to list of in scope concerns
Relequestual fbe8b54
Change 'JSON data' to 'JSON-compatible data' in charter
Relequestual 63cf673
Use more inclusive phrasing
Relequestual a996e13
Remove content which is mostly a duplication of section 2
Relequestual 2a92249
Simplify out of scope sction. Add engaging with upstream and downstre…
Relequestual 58d942b
Move TSC policy elements to charter from governance document
Relequestual 8b2ed66
Add that TSC meetings should have an agenda
Relequestual be38006
Move roles and responsibilities section back to charter document with…
Relequestual 4c92fc6
Migrate some content regarding process out of the governance document…
Relequestual 507246b
Remove governance document for the Charter PR
Relequestual 26f9265
Improve phrasing for out of scope
Relequestual 31d5f6e
Tighten phrasing
Relequestual 47a0d79
Note that updates to the charter must be approved by the OpenJS Found…
Relequestual 37eccb2
Include the CPC
Relequestual bea5924
Strive to be open, always!
Relequestual 91d5133
Remove initial included license and add CC-BY 4.0
Relequestual cdce30b
Fix posession
Relequestual 06240f9
Fix grammar
Relequestual File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd also add "Format registry" - since OpenAPI has one, and it really should be part of the JSON Schema project for more compatibility.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What value have you seen come from the OpenAPI format registry?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It provides a reference for applications so they can provide a consistent implementation of formats -- which is why we have specifications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be noted (and I imagine Karen is aware from the OpenAPI side of things) that were looking at importing the format registry from OpenAPI.