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

Clear guidance and visibility #21

Open
gcharest opened this issue Sep 28, 2018 · 3 comments
Open

Clear guidance and visibility #21

gcharest opened this issue Sep 28, 2018 · 3 comments
Labels
guidance security Security related issue

Comments

@gcharest
Copy link
Member

Examples of times where we could have used an OSS alternative

@gcharest
Copy link
Member Author

Ashley Casovan

Policy will help clarify direction on use, contribution, create OSS.

Need to make sure that existing policies are known and are realigned towards the direction of the GC

Digital Standards will lead to Digital Policy (upcoming) as a reference point: coming from Minister and states that we need to work in the open, use open standards and open source software.

@KingBain
Copy link
Contributor

Would this become a TBS ITPIN ? I'd say TBS needs to push this down as a policy.

@swill
Copy link

swill commented Sep 28, 2018

Ideally, the end users who wants to use an open source tool would be able to link the source repo they want to use (github). This tool would scan the repo, determine the license, potentially do security scanning, etc... The result would be a report card which would act as a litmus test of risk. It would be ideal if there was an auto-approval for low risk projects. If something comes back with some flags, the report card could be used to escalate to the people who need to review for approval.

Automate as much as possible...

@gcharest gcharest added security Security related issue guidance labels Nov 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guidance security Security related issue
Projects
None yet
Development

No branches or pull requests

3 participants