GarmanGroup / RABDAM

Identification of specific radiation damage in MX structures using the BDamage and Bnet metrics
GNU Lesser General Public License v3.0
5 stars 2 forks source link

Licensing #12

Closed kls93 closed 7 years ago

kls93 commented 7 years ago

Hi All,

It might be a good idea to add a license to RABDAM before the paper is submitted. Does anyone have any preferences? From the available options https://choosealicense.com/, and based upon what others in the group have chosen previously, I was thinking either an MIT license or a GNU General Public License, but I'm not sure what's best. (From what I can gather, most CCP4 programs tend to use either the GPL or a variant.)

Thanks, Kathryn

td93 commented 7 years ago

HI Kathryn,

That's probably a good idea. I don't know much about this myself but I wonder if the Gnu LGPLv3 would be best?

"Permissions of this copyleft license are conditioned on making available complete source code of licensed works and modifications under the same license or the GNU GPLv3. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights.

However, a larger work using the licensed work through interfaces provided by the licensed work may be distributed under different terms and without source code for the larger work." Sounds like what might be the case if it is to be incorporated into CCP4...

Best, Tom

On 1 August 2017 at 11:59, Kathryn Shelley notifications@github.com wrote:

Hi All,

It might be a good idea to add a license to RABDAM before the paper is submitted. Does anyone have any preferences? From the available options https://choosealicense.com/, and based upon what others in the group have chosen previously, I was thinking either an MIT license or a GNU General Public License, but I'm not sure what's best. (From what I can gather, most CCP4 programs tend to use either the GPL or a variant.)

Thanks, Kathryn

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GarmanGroup/RABDAM/issues/12, or mute the thread https://github.com/notifications/unsubscribe-auth/AOffxKWESxBYKuAddNj3-TTJEYMDl9Kaks5sTwUVgaJpZM4OpkEd .

JonnyCBB commented 7 years ago

Great idea!

I too am not very clued up about licenses. I mostly come across MIT licenses but typically these are used for library packages.

Here's a very good resource that explains things simply for a few licenses. Namely:

  1. MIT: The MIT License is a permissive license that is short and to the point. It lets people do anything they want with your code as long as they provide attribution back to you and don’t hold you liable.
  2. GNU GPLv3: The GNU GPLv3 is a copyleft license that requires anyone who distributes your code or a derivative work to make the source available under the same terms, and also provides an express grant of patent rights from contributors to users.

Importantly it notes:

FYI, the major difference between GNU GPLv3 and GNU LGPLv3 (from here) is:

The LGPL is similar to the GPL, but is more designed for software libraries where you want to allow non-GPL applications to link to your library and utilise it. If you modify the software, you still have to give back the source code, but you are allowed to link it with proprietary stuff without giving the source code to all of that back.

I guess it's ultimately one for Elspeth but I would think of it like this:

Perhaps that's oversimplified a little but it helps me. With that in mind, I would agree with @td93 and go for GNU LGPLv3. As much as I would love for everyone to share all of their code, I think GNU GPLv3 could prevent things like CCP4 using it for example (whether they would is another question) because CCP4 is not free for non-academic institutions (if I remember rightly). But again, I would check with Elspeth.

kls93 commented 7 years ago

Thanks for the replies. I agree that the GNU LGPLv3 license is the best option (and Elspeth is happy with this), so I've added it in.

(Note however that currently the GitHub page is displaying GPL rather than LGPL - I will work out how to fix this without removing the GPL text file (which apparently I am supposed to include) later.)