On Mon, Sep 24, 2018 at 6:03 AM, Stephen De Gabrielle < spdegabrie...@gmail.com> wrote:
> Hi, > > I sometimes see Racket packages on PLaneT or Github, but lack a licence. > > I don’t feel I can redistribute or fork abandoned code if it lacks a > licence. (I can give an example of an 11yo abandoned project that I’d love > to fork but can’t because it lacks a licence) > > With that in mind- what licences should be used when making code available > on the package repository/github in the following situations: > > a) general purpose library that I am happy for the broader community of > evelopers to use without restraint - but is unlikely to ever meet to be > included in Racket e.g. I have an number checksum validator (UK NHS ID > number) > - is dual licence Apache/MIT appropriate? or is it completely up to me. > > b) library, tool or DrRacket plugin that may(or may not) become part of > the Racket distribution > - is dual licence Apache/MIT appropriate or should it also be LGPL? > > c) anything else? > > Kind regards, > > Stephen > It depends very much on what you want to accomplish. If your goal is to help people get things done in the general case then you should choose a liberal license such as BSD or MIT. These will guarantee that you get credit for your work and that the person using that work can make a living off your code or enable someone else (including a company) to make a living off your code. If your goal is to ensure that all users have maximal freedom with their software and you're okay with undermining the system of intellectual property that enables people to make money directly off of selling software (as opposed to indirectly, such as by consulting on open source software), then you should choose a restrictive license such as GPL. If you want to be somewhere in the middle, you could choose a license such as LGPL, which allows people to use your code as part of something from which they make a living, but not to directly make a living off your code. As to things that will be included under DrRacket, the dev team can speak to that better than I, but Racket itself is distributed under an interpretation of the LGPL: https://download.racket-lang.org/license.html Dave > > -- > Kind regards, > Stephen > -- > Ealing (London), UK > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.