Re: Simple Solution to Ruby Licensing Issues/Misunderstandings

< :the previous in number ^ :the list in numerical order > :the next in number P :the previous (in thread) N :the next (in thread) |<:the top of this thread >|:the next thread ^ :the parent (reply-to) _:the child (an article replying to this) >:the elder article having the same parent <:the youger article having the same parent ---:split window and show thread lists | :split window (vertically) and show thread lists ~ :close the thread frame .:the index ..:the index of indices

Aredridel wrote:

> #5: Get OSI to list the license.
> 
> 

That doesn't solve the problem of people not understanding the license 
or people not being sure if it is "commercial-use friendly".

The most effective solution is to use one that is already widely used 
and known to be commercial-use friendly.

EMPLOYEE: we'd like to use ruby programming language. the ruby license 
seems friendly and meets our needs.

CORPORATION: We've pre-approved Artistic, BSD and MIT licenses.  GPL or 
LGPL requires special approval from your project manager.  All others 
need to  be submitted to our legal department by the CIO or CTO and that 
could take weeks.

EMPLOYEE: ummm....never mind, we'll just use perl.