-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
Build a JSON Schema Landscape #144
Comments
This is the repo provided by CNCF for creating new landscapes: https://github.com/cncf/landscapeapp |
I think we're quickly gonna run into the fact that basically no tools have logos, no? That repo says:
Which I can believe, but even worse yeah e.g. my implementation is 15 years old and has no logo (though I'd love one at some point) -- but yeah I bet the norm is the vast majority not having them. What would we do there? |
Agreed on your concerns regarding logos. As an alternative we can use something like this Inner-source Portal Patterns to show projects and search on them. This is what Data on Kubernetes Community did: https://dok.community/landscape/ |
Now that we launched adopters, this issues is going to be replaced by #160 |
Reopening. I think eventually we might use a single data source, but that will take some time. |
Hello @benjagm i have seen similar landscapes in https://landscape.cncf.io/ cncf project list as well |
can i start working on this?? |
Please do! |
Hi @praveen-rikhari, I am going to leave this issue free for other contributors. If you finally prefer to continue working on it let me know. |
Hi, I'd like to take this up |
@benjagm I already started working on it. Please reassign this to me. |
Of course @praveen-rikhari ! |
Making this issue available for others as there as been no progress in the last weeks |
I'd be happy to work on this issue. Let me know if I can take it on. |
Can I collab on this with you if you don't mind |
I love to collaborate on building JSON-schema landscape, and I believe it requires a significant amount of time and effort. I checked out the CNCF landscape and found out that we need a diverse range of people in different technology stacks, including frontend, backend, and DevOps, to create a comprehensive landscape. |
Let's create a working group to work together on this. Please thumbs up/down if you are interested. |
I would also like to collabrate on this : D |
I would love to collaborate on this as well, It looks amazing as an approach. Can contribute with Technical Writing Docs and Frontend. Would love to get added to the group |
Hey, I'd love to join too.✌️ |
Hi folks! I just created our pilot working group here: json-schema-org/community#701 Please join the JSON Schema Slack server and join the wg-landscape channel so we can sync for our first meeting. We are so excited about working on this together. As per your interest I am adding to the Working group this group of people:
|
Closed as completed: https://landscape.json-schema.org/ Now the work will continue here: https://github.com/json-schema-org/landscape |
It's great that we have the implementations and tooling page but that is just a portion of JSON Schema ecosystem. There are other players like adopter organizations or maybe partners that need's to be mapped.
It would be great to have a JSON Schema Landscape web space to visualize the real dimension of JSON Schema and the linux foundation actually provide a tool for that: https://lfx.linuxfoundation.org/tools/landscape/
We can make it very simple like the GraphQL Landscape:
https://landscape.graphql.org/
I'd essentially have these categories:
Resources:
Work Detail:
The text was updated successfully, but these errors were encountered: