Add a proposed mechanism for tracking known "quality" implementations. #222
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is obvious overlap here with our existing list of implementations -- note though that we have loose (or no) criteria for listing implementations on the page. Here instead we wish to specifically raise languages for which we know no good implementation to exist, despite the language being popular or widespread, if any. What's here does *not* yet render this data anywhere, nor does it implement the dynamic API calling mentioned in the body (for retrieving statistics from any listed repository). What it does do is identify a simple initial list of languages (from TIOBE and GitHub's own lists), and propose a format for tracking data points about implementations meeting the proposed criteria. The initial goal is to get feedback on this template, and to solicit help in filling it in for these languages. Refs: json-schema-org/community#418
7 tasks
Deploying with
|
| Latest commit: |
6de5a04
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f93fe3d3.website-2v2.pages.dev |
| Branch Preview URL: | https://quality-list.website-2v2.pages.dev |
|
Do we need this to appear in the website? |
Good question. It could just as easily live in the community repo. Let's discuss. |
3 tasks
|
Superceded (as per the OWCM call) via json-schema-org/community#554 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a file for us to add data on "quality" implementations, for some defined characteristics of how we maight characterize such a thing. The file is nearly fully stubbed out -- so essentially the key content is the comment here, which we can use to farm this out hopefully.
Overall I tried to stress we're exposing data points here, not trying to (hopelessly) define a metric for what good and bad code/projects are.
There is obvious overlap here with our existing list of implementations -- note though that we have loose (or no) criteria for listing implementations on the page. Here instead we wish to specifically raise languages for which we know no good implementation to exist, despite the language being popular or widespread, if any.
What's here does not yet render this data anywhere, nor does it implement the dynamic API calling mentioned in the body (for retrieving statistics from any listed repository).
What it does do is identify a simple initial list of languages (from TIOBE and GitHub's own lists), and propose a format for tracking data points about implementations meeting the proposed criteria.
The initial goal is to get feedback on this template, and to solicit help in filling it in for these languages.
Refs: json-schema-org/community#418