Skip to content
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

Levels of success for CODECHECK certificates #12

Open
nuest opened this issue Dec 10, 2020 · 2 comments
Open

Levels of success for CODECHECK certificates #12

nuest opened this issue Dec 10, 2020 · 2 comments
Labels
the check Improvements, discussions about the actual CODECHECK and processes

Comments

@nuest
Copy link
Member

nuest commented Dec 10, 2020

I took a more detailed look at SciGen.Report today together with its founder @amorim-cjs. SciGen.Report has different levels of reproducibility, which might be interesting to capture in the codecheck.yml as proper metadata. The CODECHECK certificates do mentions this kind of information (and the summary in the codecheck.yml might too), but a structured proper field with a set of predefined values could be valuable to intergration and visulisation of search results, for example.

Here is a screenshot of the SciGen.Report options when I want to submit a review and the variants that are relevant to CODECHECK (considering that "negative" CODECHECK certificates are not something that will ever be published in the same way):

  • Yes, within margin, all of it as written
  • Yes, within margin, but extra information was needed (please clarify)
  • Yes, but only partially (please specify)

image

@nuest nuest added the the check Improvements, discussions about the actual CODECHECK and processes label Jan 13, 2021
@nuest
Copy link
Member Author

nuest commented Mar 10, 2021

SciGen.Report now has a new interesting collection of possible terms, which might help us describing the extent of a check:

See https://scigen.report/info/reproducibility for the background.

image

With codecheck, we're staying in the "same/same" quadrant.

@amorim-cjs
Copy link

Thank you for the observation. Do let me know if you or anyone see problems with these terms. For example, in case they don't seem to fit some needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
the check Improvements, discussions about the actual CODECHECK and processes
Projects
None yet
Development

No branches or pull requests

2 participants