Skip to content

Software License Recommendation #15

Open
@degregat

Description

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.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions