Add a proposed mechanism for tracking known "quality" implementations. #554
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 slight overlap here with our existing list of implementations on the web page -- 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: #418
This was referenced Nov 28, 2023
Closed
gregsdennis
approved these changes
Nov 29, 2023
|
Any other comments on this one? |
|
GitHub now have top programming languages for 2023, but not as a stand alone page/post: https://github.blog/2023-11-08-the-state-of-open-source-and-ai/ |
Relequestual
approved these changes
Jan 9, 2024
There was a problem hiding this comment.
Looks good to me. Thanks for this work.
We might end up making all the data live in https://github.com/json-schema-org/ecosystem, but this here is fine for now. We will update if/when required.
|
OCWM Agenda: Looks like this is good to merge (or may be merged). We should create 1-3 reports by hand, then invite the community to join in adding and/or automating data collection. We can also invite the community to create some sort of rendering of this data for the website. |
|
Cool! Thanks! Sounds good. |
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.
There is obvious slight overlap here with our existing list of implementations on the web page -- 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.
Do you think resolving this issue might require an Architectural Decision Record (ADR)? (significant or noteworthy)
No
(What's here is provisional, and ultimately informational).