Fortran-FOSS-Programmers / Fortran-FOSS-Programmers/Best_Practices

Fortran software project licensing considerations

Open
#8 13 comments 0 reactions 0 assignees View on GitHub
help wanted question
Dominant language
No language data
Stars
70
Forks
10
PR merge metrics
No merged PRs in 30d

Description

While I feel that there is no one-size-fits-all choice for an appropriate license for new Fortran software projects, and trying to reach a consensus and trying to make a specific recommendation is beyond the scope of Fortran-FOSS-Programmers/Best_Practices, I think that a **discussion** of various licenses, their pros and cons, and implications for Fortran and scientific computing projects would be useful. This is the appropriate location to discuss such considerations, to be included in a ["licensing discussion" document](https://github.com/Fortran-FOSS-Programmers/Best_Practices/blob/master/License-considerations.md). The goals of this document should be (open for further discussion here):
1. Be as neutral as possible; we all prefer certain licensing schemes but let's try to discuss the different licenses as factually as possible
2. Describe open source software licenses in plain english
3. Enumerate their properties and requirements
4. Discuss theoretical and practical implications for choosing a given license
5. Discuss their pros and cons in different contexts
6. Let me know if there are other topics you want to see included and I'll add them here

Here is an incomplete list of licenses I think we should cover/discuss:
1. MIT
2. GPL
3. LGPL
4. BSD2
5. BSD3
6. CC (probably shouldn't be used for code)
7. The ["unlicense"](http://unlicense.org)
8. I'm sure there are others I am forgetting.

See the now locked #7 for some previous discussion history.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.