-
Notifications
You must be signed in to change notification settings - Fork 22
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
Genomad license in Galaxy tools #127
Comments
@bernt-matthias i actually asked and received permission to deploy on major servers with additional links to the license file and a text caveat asking anyone who wants to use commercially to read the license. I can send over the email correspondence |
If approved we can add this here https://github.com/Helmholtz-UFZ/galaxy-tools/tree/main/tools/genomad |
As I mentioned to @astrovsky01, we ourselves provide geNomad as a webapp. To me, making it more accessible to a broader audience would be amazing. I think that a small text mentioning the license for commercial users would be enough. |
How about adding a boolean where users have to agree (I think one extra click is fine) and a small extra text in the tools help: I implemented this here: Helmholtz-UFZ/galaxy-tools#54 |
That works. But I don't think the extra click is necessary as long as the notice is shown like this. Up to you, really. |
* add licence boolean to genomad apcamargo/genomad#127 * add validator * agree to license for test
I recently created a tool wrapper for genomad for the Galaxy platform: Helmholtz-UFZ/galaxy-tools#29 and have a question regarding the license.
While using the tool on the private Galaxy server of our research institute should be fine, we were wondering how to deal with the license on public Galaxy servers (usegalaxy.eu, usegalaxy.org, ...). Would it be sufficient to add a boolean switch to the tool where users need to actively agree with your license in order to use the tool (plus linking the license at this boolean)?
Would be great to have this tool in Galaxy.
Ping @bgruening @astrovsky01
The text was updated successfully, but these errors were encountered: