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
I've seen some unlicensed research code being published, which makes reuse hard and increases friction. Usually that was not the intent, but a result from a lack of knowledge of the legal implications.
Would it make sense to add a section with a short explanation why adding a software license is important, as well as a recommendation? MIT and APACHE 2.0 seem to be favored and a short explanation of their mechanics could be included.
If that is something that is wanted, I can open a PR.
The text was updated successfully, but these errors were encountered:
I've seen some unlicensed research code being published, which makes reuse hard and increases friction. Usually that was not the intent, but a result from a lack of knowledge of the legal implications.
Would it make sense to add a section with a short explanation why adding a software license is important, as well as a recommendation? MIT and APACHE 2.0 seem to be favored and a short explanation of their mechanics could be included.
If that is something that is wanted, I can open a PR.
The text was updated successfully, but these errors were encountered: