Open IPvSean opened 1 year ago
(If internal content) Content has been or is being migrated into the redhat-cop Github org
Is this something we have to do? This would take quite a bit of unscoped work where I need to go into ansible/workshops and instruqt and point to the new repo and test... why can't the content just stay here?
FYI around ansible-lint, I have some concerns here: https://github.com/ansible/ansible/pull/80746
unclear what I am needed to do with the OpenSSF Best Practices. It seems to run some sorta lint tool, but doesn't tell me "what" to do to fix the ?
Picking up this issue again! @IPvSean The ABU has taken a pretty firm stance on requiring internal content to migrate into redhat-cop, for governance reasons.
For OpenSSF standards, @ericzolf may be able to give guidance and recommendations.
IPvSean for a network collection, how sweet... There isn't a lint tool as far as I know, it's more or less just a self-assessment questionnaire, where a question mark is the default state until you give a proper answer to the question. If you click on Edit at the top, you can simply click yourself through the questionnaire. Feel free to chat me if you have a specific question.
Candidate Name
network.toolkit
Link to Github Repo
toolkit
Review Due By
no timeline for me yet
CHECKLIST
Business Checks:
Content Viability
Content Duplication
Technical Checks:
Content Conformity
Content Compliance
Content Testing/Validation
ansible-lint
“Production” profile in an active Github workflow on the repositoryansible-lint
“Production” profile