search

stan-dev / posteriordb

Database with posteriors of interest for Bayesian inference
163 stars 26 forks source link

Add license requirements for contributions #186

Closed avehtari closed 3 years ago

avehtari commented 3 years ago

Add to contributions doc information what licences we accept for Stan code to be included in posteriordb

MansMeg commented 3 years ago

Ok. What licences do we accept? I guess that as long as they are open? Or should we focus on MIT?

avehtari commented 3 years ago

It's better to be flexible, but the license should be permissive (free to distribute and modify, no commercial restrictions etc). I don't think we need to have explicit list, but maybe say something like "To get Stan code included in posteriordb git repo, the license for the code needs to be permissive such as BSD3, MIT, GPL, etc"

It seems posteriordb itself is currently missing LICENSE file. We could use the same as for posterior https://github.com/stan-dev/posterior/blob/master/LICENSE.md

MansMeg commented 3 years ago

I think it will be hard to have separate licenses for different code in the same project. I suggest that we use the same as posterior and then say that of they supply code it will have that licence? That should be more simple, or?

avehtari commented 3 years ago

We can encourage BSD3, but it's not hard to have different licenses. Each file can have their own license, and we just don't accept licenses that are too restrictive to be compatible.

avehtari commented 3 years ago

I would not like to stop adding a model that has compatible license but that just is different than the license for the package code.

MansMeg commented 3 years ago

Alright. This seems reasonable. We will just add an additional slot in the model code info and data info json objects.

MansMeg commented 3 years ago

Now done by adding this to the CONTRIBUTING.md file