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.

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

Core: Add section to define expectations for proposals #1569

Open
gregsdennis opened this issue Jan 7, 2025 · 3 comments
Open

Core: Add section to define expectations for proposals #1569

gregsdennis opened this issue Jan 7, 2025 · 3 comments
Labels

Comments

@gregsdennis
Copy link
Member

We need a section in Core that defines what we expect from tooling around support for feature proposals.

Basically, proposals are OPTIONAL but RECOMMENDED.

Tooling must also specify in their docs which proposals they support and the latest date or some kind of proposal version that they support.

@abhayymishraa
Copy link

can i work on this issue ?

@gregsdennis
Copy link
Member Author

gregsdennis commented Jan 7, 2025

@abhayymishraa if you have ideas, simply state them. You don't need permission to participate in discussion. However, as you can see under the "Projects" header to the right, this is still in discussion; it's not ready to be worked on.

Secondly, spec changes require in-depth knowledge of JSON Schema and experience with specification authorship. That generally means TSC members and other experts who have been working with JSON Schema for a long time and have proven their understanding of the spec and knowledge of its uses. While anyone may contribute their ideas to discussions, contribution to the documents is not generally open.

@abhayymishraa
Copy link

got it...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Discussion
Development

No branches or pull requests

2 participants