You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Take the example policy rules in ort-config repository as a starting point for your rules set.
Talk a legal counsel about each rule in the example policy rules and create your own set of license classifications maybe based on license-classifications.yml in ort-config.
Find 2-3 software projects of which the maintainers are willing to give ORT a try. Scan their projects with ORT and discuss results together with your legal counsel and selected maintainers - what's good/bad and how to improve
Iterate over the rules until the group is happy with results. Next add new rule updates and start the implement, scan, review iterative loop again.
When writing policy rule we encourage you to reach out to other ORT users on the ORT Slack channel on how to best implement new rules. Try to keep rules simple and the number of exceptions low so the rules are easier
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Would recommend the following:
When writing policy rule we encourage you to reach out to other ORT users on the ORT Slack channel on how to best implement new rules. Try to keep rules simple and the number of exceptions low so the rules are easier
Beta Was this translation helpful? Give feedback.
All reactions