Open PhilippWendler opened 7 years ago
Requirements added to description.
@PhilippWendler What is the procedure here? I would be happy to contribute the information for the missing float-* (BSD license), but I don't know how to take action.
@tautschnig Just add a PR with a LICENSE.txt in the respective directories.
ce25410 of #239 adds license files for floats-cbmc-regression, floats-cdfpl, pthread-wmm (and busybox, but that wasn't essential).
Those license fixes have now been moved into #243.
What is the status of this issue? Is there still help wanted? Probably we need to update the list with folders that were added in the meanwhile, though those should not be a problem since we always look for a README and a LICENSE in the PRs.
Yes, help would still be great. The list above should be correct, the most important point would be to contact original submitters of those directories that are not checked above.
I recently did #1098 and also have some info on pthread tasks for which I will create a PR soon.
@dopelsunce you added the Apache 2.0 license to eca-programs
in 040cc22ed5107d03948994241e0fd286538f5aaf, where in the README it claims that these were derived from the RERS 2012 tasks. Do you know that the RERS 2012 tasks are under Apache 2.0 license or does this just refer to your changes? You added this license also to the eca-rers2012
folder, which would indicate that you were able to determine the license for them. If so, we could tick eca-rers2012
off the list in this issue
@MartinSpiessl The license of eca-programs
and eca-rers2020
were actually added in 8693853c2dfa932c9df2826165d2b89922b9f72b (#601) and we have confirmation from Bernhard Steffen that Apache 2.0 is correct. So we can indeed tick eca-rers2020
.
040cc22ed5107d03948994241e0fd286538f5aaf seems to contain lots of content from other branches that should not have been part of it, probably because of a merge commit was incorrectly squashed together with other commits (https://github.com/sosy-lab/sv-benchmarks/pull/584#issuecomment-428352015). The diff of #584 shows what was actually added.
We should discuss what licenses are acceptable for benchmarks, i.e., what kind of rights to we need to be granted in the license.
I would list at least the following requirements:
__VERIFIER_*
specifics)When this is answered, it should also be added to the documentation.
Furthermore, we should check for all existing directories whether their license grants the necessary rights: