codecheckers / codecheckers/discussion
Badge metadata
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This recent NISO report about badges gives some recommendations about what badge metadata should be made available in a structured form. We should revisit if all the information is available via the `codecheck.yml`, and think about how badge and YAML file could be connected.
https://doi.org/10.3789/niso-rp-31-2021
Also, the idea to add a crpytographic hash in the image header for authentication of the badge source is interesting, but would require an own badge server.
It's a pity that they have `ROR-R` (reproduced) only as an extension of `ROR` (reviewed), whereas CODECHECK does reproduction without too much code review.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked NISO report and inspecting codecheck.yml to compare its available metadata with the report's recommendations. Clarify how badge data should connect to the YAML file and whether authentication is in scope; done would be an agreed, actionable specification for the metadata and badge-server work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100