New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding packages #259
Adding packages #259
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked everything and it looks good, I think it passes our criteria.
However, there might be a license issue. The MUMPS package is under the CeCILL-C license and I don't see it here in the list of OSI approved licenses:
https://opensource.org/licenses/alphabetical
The only one I can see is CECILL-2.1, the full text is here:
https://opensource.org/licenses/CECILL-2.1
Compared to the CeCILL-C text:
https://cecill.info/licences/Licence_CeCILL-C_V1-en.html
there are some slight differences and I don't know if that matters or not.
I strongly think we should only allow OSI approved licenses. @milancurcic, @LKedward, @scivision and others, what do you think?
This precedent:
seems to suggest that the CeCILL-C license might not be OSI approved... Here is another similar issue: pypi/legacy#679 |
Ok, so according to this: The CECILL-C license is not OSI approved. Here is what I suggest we do:
I suggest to only allow OSI (https://opensource.org/licenses/alphabetical) approved licenses to be allowed in the main section. Should we have another section that allows non OSI approved software written in Fortran? In this section we could list all kinds of commercial codes also, such as VASP. We could put MUMPS there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me to merge as is.
Yes I think it will be necessary to have a second list for non-OSI software. Given a few factors such as the long lifetime of Fortran, and the nature of the aerospace and other such government and research organizations that make Fortran code. To protect (perhaps misguidedly) their IP and commercial relicensing ability they have what are open source but not necessarily free licenses. Some recently released software has some of the most restrictive licenses I've seen on open source packages. But the software is essential for a range of geospace research. |
Thanks! Yes, there will be quite a few packages that we could list there. I created fortran-lang/webpage#79 to discuss that. |
Ondrej requested I add Gemini3D. I added / updated a few more packages.