Open IanLee1521 opened 7 years ago
We should see about adding something like https://github.com/cfpb/open-source-checklist into our best practices so that we can make sure whatever is released and pushed out is, and stays, "clean" for however we end up defining that.
Some things to watch out for include:
API tokens :)
Further resource, pointed out to me by @benbalter https://opensource.guide
You may want to consider suggesting a scan for licenses with https://github.com/nexB/scancode-toolkit I maintain this
Content from #13
CI options:
Code Coverage:
Static Analysis:
Patch Review/Management:
We should see about adding something like https://github.com/cfpb/open-source-checklist into our best practices so that we can make sure whatever is released and pushed out is, and stays, "clean" for however we end up defining that.
Some things to watch out for include: