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
Adding an issue for a conversation w/ @nickreich (see below). Maybe this issue needs to go elsewhere b/c it involves two repos (see list at end).
(matt) I just spoke briefly with @nick re: [Do not hardcode a list of allowed licenses #56], which we resolved by updating the master csv of licenses, and by updating zoltar's hard-coded list. Nick asked that I post here as a reminder to continue the discussion, esp. desciding where the authoritative list of licenses should live. One option is in the master validations repo, which would put it outside of zoltar, but would need to be duplicated in zoltar. Relatedly, is there an all-encompassing list, or do projects need to constrain to a subset? Sorry if this isn't clear.
(nick) Basically, I think it fits our needs now to have one master list of approved licenses (I think this should live in the master validations repo) and we could add to it as other licenses crop up (as one did in #56).
(nick) And Zoltar may need to duplicate this somehow, but I think it's good to have it also in GitHub.
After a quick look, there are two versions of the file:
Adding an issue for a conversation w/ @nickreich (see below). Maybe this issue needs to go elsewhere b/c it involves two repos (see list at end).
After a quick look, there are two versions of the file:
The text was updated successfully, but these errors were encountered: