views:

38

answers:

2

What I mean is that it's open source in that the source is viewable, modifiable, and redistributable by anyone, but changes do not have to be contributed back (as is the case with GPL)? I've heard the traditional software licenses are problematic for web applications as well.

I believe I want the web equivalent of the Apache license, but I'm not sure. Any advice would be appreciated. Attribution is not important to me, but it is a very small plus if it comes down to it.

+1  A: 

I believe most BSD/Apache style licenses would work.

The usual problem with web applications only applies when you try to do the opposite - force the recipients to release changes to the users (which is what AGPL tries to do), because a web application does not depend on releasing a binary to the users, which is the usual trigger on which licenses such as the GPL depend on.

Ofir
This was a good answer, thanks.
Andrex
+2  A: 

Consider the MIT license. It is arguably the most used license in Ruby gems.

Swanand
MIT seems to be what I'm going for, thanks.
Andrex