Skip to content

Code license #15

@willian-m

Description

@willian-m

If we plan to make the code public soon, a license should be applied, even if it is open source. Some popular are:

Also relevant, there is a UIUC-license.

As an example of common software used by the community, MUSIC uses GPL-v2.0 license, Kompost and Trento uses MIT license and SMASH uses a GPL v3 for the code and BSD for the cmake scripts. The Cabana lib (which I am integrating on the code) uses 3-clause BSD and Kokkos uses the Apache license.

My personal opinion: We should use the UIUC license. Not just because we are all based here, but it is more precise than the MIT while being simpler to understand than the GPL one. 3-clause BSD is very similar to it.

If anyone wants to go down this rabbit hole, here here is a good resource that lists many options that we could use.

Metadata

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