Make license/licenses field mandatory

Pavol Rusnak prusnak at
Wed Oct 19 09:21:01 EDT 2011

Most of the things you wrote make sense. Thanks Eric!

On 18/10/11 22:34, Eric Hodel wrote:
>> * What if I want to publish my gem with no license?
> put "unlicensed" in the field
>> * ...with a personally crafted license?
> If you can't give a name to your license? ("beer ware" and "WTF" licenses are relatively new licenses that were given clever names.  If you're not creative like me then uou can have the "Eric Hodel license")
>> * the public domain?
> "public domain"

Let me react on this part. Please, please, please do not use "public
domain", your own crafted license or no license. If you think you need
to, please rethink and don't use it! There are plenty of nice licenses
written by lawyers and software experts from which you can choose from.
If you use some "funny" license you are basically blocking your gem from
being used in some areas and my guess is you don't want this.

Some examples:
  - Public domain is not valid outside US
  - Beerware makes your work non-redistributable (as a part of bigger
    FOSS project)
  - etc., etc.

Best Regards / S pozdravom,

Pavol RUSNAK                                       SUSE LINUX, s.r.o
openSUSE Boosters Team                            Lihovarska 1060/12
PGP 0xA6917144                                         19000 Praha 9
prusnak[at]                               Czech Republic

More information about the RubyGems-Developers mailing list