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

CII Best Practices Badge Program - "Passing" level #660

Closed
9 tasks done
treiher opened this issue May 10, 2021 · 0 comments · Fixed by #696
Closed
9 tasks done

CII Best Practices Badge Program - "Passing" level #660

treiher opened this issue May 10, 2021 · 0 comments · Fixed by #696
Assignees

Comments

@treiher
Copy link
Collaborator

treiher commented May 10, 2021

To ensure that we follow best practices we should look into the requirements of the CII Best Practices Badge Program and decide if we want to self-certify RecordFlux.

  • Provide information on how to: obtain, provide feedback, and contribute to the software
  • Add requirements for acceptable contributions (coding guide)
  • Reference documentation that describes the external interface
  • Process for reporting vulnerabilities on the project site
  • If private vulnerability reports are supported, the project MUST include how to send the information in a way that is kept private
  • Enable Python security scanner
  • Silver level (fill applicable items)
  • Gold level (fill applicable items)
  • Add badge to README
@treiher treiher added this to To do in RecordFlux Future via automation May 10, 2021
@senier senier removed this from To do in RecordFlux Future Jul 12, 2021
@senier senier added this to To do in RecordFlux 0.5 via automation Jul 12, 2021
@senier senier self-assigned this Jul 12, 2021
@senier senier moved this from To do to In progress in RecordFlux 0.5 Jul 12, 2021
@senier senier changed the title CII Best Practices Badge Program CII Best Practices Badge Program - "Passing" level Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
senier pushed a commit that referenced this issue Jul 13, 2021
@senier senier moved this from In progress to Under review in RecordFlux 0.5 Jul 13, 2021
@senier senier linked a pull request Jul 22, 2021 that will close this issue
RecordFlux 0.5 automation moved this from Under review to Merged Jul 22, 2021
@treiher treiher mentioned this issue Aug 4, 2021
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
RecordFlux 0.5
  
Merged
Development

Successfully merging a pull request may close this issue.

2 participants