usegalaxy-eu / workflow-testing

Automated testing of workflows against Galaxy
10 stars 20 forks source link

Could you add a license? #54

Open simleo opened 4 years ago

simleo commented 4 years ago

Since this repo does not have a license, it falls into the no license category, i.e., an exclusive copyright that forbids almost everything. A license allowing to copy/redistribute and modify the contents of the repo would be really nice, since it provides complete examples of workflows together with their test suites.

bgruening commented 4 years ago

Hi @simleo, are you referring to the workflows or the code, so the simple bash script?

simleo commented 4 years ago

Mainly to the workflows (and associated test suites).

bgruening commented 4 years ago

The workflows are mirrored from the Galaxy Training Network to a large degree and fall under the GTN license. Maybe we should add license information for workflows into the workflows.

simleo commented 4 years ago

The readme on https://github.com/galaxyproject/training-material says the license is CC BY 4.0 for website content and MIT for infrastructure code, but I'm not sure which one covers the workflows. Moreover, the workflows in this repo seem different (I guess they're older versions). In addition, this repo also contains non-training workflows, so it's a bit confusing. I think explicit licensing information on the workflows as they are in this repo would be great.

A bit of context: one of the scenarios we are considering for the EOSC-Life workflow testing service is the monitoring of tests that run externally, for instance in a Jenkins server as is the case here. One of the interaction models we're exploring involves monitoring the status of external tests for workflows stored in a registry (such as the EOSC-Life Workflow Hub), so we need to know if we can take workflows from here and upload them to the registry, and under which license. That's why we're interested in licensing for the exact versions of the workflows that appear in this repo.

hexylena commented 4 years ago

I'd say the workflows are cc-by since they're more tutorial+tutorial content.

Given some of our hopeful future directions with workflows/tutorials, cc-by makes more sense, even if it feels a bit strange to me.