You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
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.
The text was updated successfully, but these errors were encountered: