Copyright Headers #3881
SudharakaP
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
That would be a tedious practice to enforce, and a big change to enforce it for existing files. I understand that it can be needed for some projects (ie. libraries with advanced algorithms) but our code is so tied to Open Collective's business that I don't think we need to be too protective with it. Are there arguments in favor of this practice that I'm missing? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@opencollective/core : I just had this idea while working on another projects copyright notices. So, I was wondering if we should insert a copyright header notice on all files in OpenCollective (at least in the main reops such as the front end and api)? 🤔
Reference: https://reuse.software/spec/
Beta Was this translation helpful? Give feedback.
All reactions