Ecosystem Critical Projects? #5
Replies: 7 comments 9 replies
-
|
Is the phrasing "ecosystem critical projects" a good representation of the target projects? |
Beta Was this translation helpful? Give feedback.
-
|
How do we identify / classify "critical projects"? |
Beta Was this translation helpful? Give feedback.
-
|
What do critical projects need most? |
Beta Was this translation helpful? Give feedback.
-
|
I think this is the key question worth answering that would drive the rest. But it is a tricky question, and I don't even know what the answer would be for my own projects. Are projects getting stuck because of knowledge? Because of time? |
Beta Was this translation helpful? Give feedback.
-
If we can get a few implementers together, I'd be happy to arrange a workshop session to try and collectivly work through this sort of question. Thumbs up this comment to signal your interst in this! |
Beta Was this translation helpful? Give feedback.
-
|
Very happy to join a workshop on this. A JSONSchema repository app, 'Strands', will come into public beta in the next couple of months (@Relequestual and @jviotti I finally got a bit of funding to kick it over the finish line - or I should probably say "start line"!!). I'll need:
As a more general answer, a couple of years ago what would have been useful (and I suppose still would be) was a much clearer idea of market size - ie number of users and organisations using JSONSchema (I had to wild guess), and traffic sizes I might expect. In general, another thing implementers need help with is technical support on the subtleties of JSONSchema which the slack community is very good at answering, and better documentation and other such things that you already know about and are on the roadmap / under development in GSoC. |
Beta Was this translation helpful? Give feedback.
-
|
How can we best enable and support critical projects? |
Beta Was this translation helpful? Give feedback.
-
|
Hi! go-jsonschema maintainer here :) As a person who's not super knowledgeable about json-schema and maintaining the project in his spare time, maybe something like a maintainer guide (in the shape of a site, or a bunch of markdown files) could be helpful.
I hope it helps! And thank you for the amazing job you folks are doing, jsonschema is possibly the most welcoming community I have ever participated to! 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
I really like the second and third points and would love to participate on those. For example, I wrote the lexical/dynamic scope blog post as a way to do the second. |
Beta Was this translation helpful? Give feedback.
-
|
Also on number 2 and 3, we are doing cool research on GSoC for the upgrade/downgrade project and we'll have a series of research documents as a result (see https://github.com/json-schema-org/upgrade-downgrade-rules/blob/main/research/format.markdown that studies |
Beta Was this translation helpful? Give feedback.
-
|
@omissis thanks for sharing your feedback on this. I'm thinking about more direct / hands-on ways in which we can support such projects. Does this spark any further ideas? |
Beta Was this translation helpful? Give feedback.
-
|
I think my comments on this question are the same as on the previous question ("What do critical projects need most?") which is similar in nature. |
Beta Was this translation helpful? Give feedback.
-
|
Will this be exclusivly for existing projects? |
Beta Was this translation helpful? Give feedback.
-
|
I wouldn't expect so. I imagine any new project that comes along and satisfies whatever conditions we put in place could be considered a "critical" project. I also expect existing projects to eventually lose momentum, as is the way of open source. This will likely be a revolving door of projects, hopefully over the long term only, though. |
Beta Was this translation helpful? Give feedback.
-
|
Should we set general conditions and periodic reviews? |
Beta Was this translation helpful? Give feedback.
-
|
Should we also be able to set project specific conditions or objectives? |
Beta Was this translation helpful? Give feedback.
-
The status of this TSC decision is tracked using #6
This Issue also details the stage of the discussion and what actions are required to progress to the next stage.
Background
During our in person JSON Schema summit last year (2023), one of the items on the agenda was how we allow existing projects into the JSON Schema Github organization.
We concluded that rather than ingesting existing projects, we would look to support and enable them where they were.
We created an Issue to track strategy for engaging implementers: json-schema-org/community#412. And, while this is good, it didn't reflect the need to support specific critical projects.
Since then, we have had some discussions about a "critical projects" program, which is slightly different. Discussion resurfaced on a community call on 2024-01-08. And, @benjagm opened an Issue to kickstart discussion and drive this work forward.
What do we need to decide on?
This is not an exhaustive list and more questions may be added.
(Please also feel free to suggest better phrasing of questions that might lead to more open discussion.)
While this Discussion is labelled
tsc-decisionand is associated with a consensus stage per our governance process, both the community and TSC are welcome to provide their thoughts and comments on these matters.Beta Was this translation helpful? Give feedback.
All reactions