Consider the future of this repo
Capstan opened this issue · comments
Given there's no active development, and @huggsboson and I have merely been cleaning up as necessary, and that the JSON drafts have progressed, what should become of this project?
https://json-schema.org/implementations.html#validator-java lists two Java alternatives that support up to draft-07. If one (or both) are deemed a suitable successor / replacement, then perhaps this set of repos could be slowly retired (maintenance fixes, then security-only fixes, then closed).
If not, then I think we need some kind of plan to fund bringing it up to date.
/cc @scottbla @thackem @andrei-scripniciuc because of the relevancy on Google imports and dependent services, especially with regard to OpenAPI v3.1 which will use a modern JSON Schema draft.
/cc @Relequestual as we were just discussing this yesterday over email.
Hi Nathan @Capstan ,
This repo has developed for more than 8 years and has helped many users. It would be a pity if it was gradually dead. I am an open source enthusiast and am happy to contribute to this repo. will you consider adding a new maintainer to help you collaborate this repo?
Alan
@Alanscut I can't speak for primary maintainer @huggsboson, but I wouldn't say no to more maintainers. That said, my concern is not whether or not someone will make it work with the next Java or the next CVE that comes down the pike (i.e., maintenance), but that there's a way forward that (1) supports modern JSON schema and (2) is a reasonable application of effort. Certainly someone such as yourself could provide the former, but is that a better approach cost- and ecosystem-wise than migrating/centralizing on an already-modern implementation?
I won't get in the way of people deciding the way forward is improving these repos, but want it to be a considered approach.