Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

do closed source / non-OSI licensed computational models meet OMF standards? #88

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

Closed
jedbrown opened this issue May 18, 2020 · 4 comments
Assignees
Labels
OMF discussion an issue to be raised for community discussion standards - accessibility Suggestions for accessibility standards standards - reusability Suggestions for reusability standards

Comments

@jedbrown
Copy link

By way of example, NSF's MolSSI Community Code Partners includes Gaussian and VASP, both of which have non-open licenses that forbid publishing benchmarks (cf, Banned by Gaussian). A purist would mandate OSI-approved licenses in hopes of incentivizing transparency and reproducibility, but that will exclude significant research sectors. Alternatively, it could be tiered and best-effort, allowing the status quo to persist, though that undermines some of the objectives of OMF.

@jedbrown jedbrown added the standards - accessibility Suggestions for accessibility standards label May 18, 2020
@alee alee added the OMF discussion an issue to be raised for community discussion label May 19, 2020
@alee
Copy link
Member

alee commented May 19, 2020

IMO we should take a strong stance as the Open Modeling Foundation that requires transparency in any blessed digital artifacts - no room for closed source anything that would meet the minimal standards guidelines..

@alee alee added the standards - reusability Suggestions for reusability standards label Oct 6, 2020
@alee alee changed the title Non-OSI license considerations do closed source / non-OSI licensed computational models meet OMF standards? Oct 6, 2020
@alee
Copy link
Member

alee commented Oct 6, 2020

related to #90

@cmbarton
Copy link
Contributor

cmbarton commented Oct 6, 2020

I strongly agree. This will make some people uncomfortable. But as one participant reiterated today, if you are doing science, you need to be transparent. That means that we may not have a lot to offer industry. But maybe more than it seems.

@platipodium
Copy link
Contributor

While I personally agree with @cmbarton, I fell that as on organization we should not exclude non-OSI codes. Some thoughts

  1. We might require the metadata to be FAIR and open, this would make many non-OSI codes at least FAIRer
  2. we have the problem of open but not OSI codes that cannot be relicensed
  3. some closed source is still "fair" and interacting with open source codes. That's one of the reasons we have the LGPL

@alee alee closed this as completed May 12, 2021
@openmodelingfoundation openmodelingfoundation locked and limited conversation to collaborators May 12, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
OMF discussion an issue to be raised for community discussion standards - accessibility Suggestions for accessibility standards standards - reusability Suggestions for reusability standards
Projects
Status: Done
Development

No branches or pull requests

4 participants