License?

[IPetrik]

Hi Evan,

I noticed there is no explicit license for this repository. Am I to assume that this code is not open-source? If it is open-source, please add an open source license. If it is copyrighted, it might benefit users to add a line in the readme stating this and how they can obtain a license to use this software.

Thanks!

[EvanBaugh]

Hi, I intend this code to be open-source although it was developed in motivation to be used with copyrighted software (Rosetta), and indeed it is little more than a wrapper around this code (technically there are use cases without it but it is intended for use with that software). The main script mentions this but I will update the README to clarify. It is complicated since Rosetta is "open for academic use" which as far as I know, is not a clear legal classification but all Rosetta users are manually approved and any academic or not-for-profit users are effectively given free access. If you have any tips or suggestions for how to clarify this please let me know. Most software associated with Rosetta is simply subsumed by it however I wanted the methodology, wrapper, and specific parameters used by my repository (VIPUR) to remain open. Thanks, Evan

[IPetrik]

Thanks for the explanation Evan!

There are two major simple open-source licenses:

• MIT (allows others to make closed source derivatives)
• GNU GPLv3 (prohibits closed-source derivatives of your content)

My recommendation based on your stated desire would be to add to the README file or a separate LICENSE file something along the lines of the following (e.g. MIT):

"The contents of this repository are made available under MIT License (see below). The contents of this repository depend on additional software to function (see README) which may be distributed under different licenses; it is the user's responsibility to obtain licenses for these dependencies.

===
MIT License

Copyright (c) 2018 Evan Baugh

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE."

Thanks and good luck!

• Igor

[tz-rrze]

Hi Evan,

I'd like to bring the license issue up again. Did you come to any final decision?

Thanks
thomas