[Meta/Rant] Ownership of schemas hosted by SchemaStore about schemastore

[hyperupcall]

removed properties from the schema and they no longer appear in the IntelliSense in Visual Studio when editing the file

I do apologize for that, I had one key assumption that I probably shouldn't have had when reviewing. I'll revert those changes so the previous schema is restored.

as maintainer for a project, is there a way to declare that I own a specific schema within SchemaStore?

We do have a CODEOWNERS file, but it seems like it only applies to users with write permissions and not read permissions. Would you know of any alternative functionality to work around this?

However, it does reinforce the notion that I don't have control over a schema which nobody outside of my project should have any interest in

I've always viewed this repository as a community-maintained place of JSON schemas. If I ever submit schemas, I would do so under the assumption that it would be modified by other people (cleaning things up, adding properties after releases, etc.). If you do want full 100% control over your schema, that is why catalog.json supports url properties and the like.

[jimmylewis]

We do have a CODEOWNERS file, but it seems like it only applies to users with write permissions and not read permissions. Would you know of any alternative functionality to work around this?

I did find a couple GitHub actions that attempt to accomplish something similar, such as this and this. However, I don't have any experience with them, so no idea how well they'd work for non-Write access.

In the meantime, I'll consider whether to migrate the schema to self-hosted or try to make it more clear how to identify an expert for review (maybe a $comment at the top of the schema).

[hyperupcall]

I'm closing this because the original concerns were addressed and the issue is no longer actionable as an open issue. Additional comments can be added if there are any other concerns