Newbie questions...

Ben Sawyer bsawyer at
Tue May 1 23:53:32 UTC 2001


I have a few potentially newbie questions I'm trying to sort out for writing
a license.  I've read as many of the licenses that I could find and I'm now
overflowing with information.  So I'm at the point of trying to clarify a
few things.

I have a project where we would like to publish the source code to the
project however we would like to restrict commercial redistribution or use
of any kind by its users.  Specifically we don't want the following to

1. User downloads software - recompiles and sends out the compiled software
to clients and charges them for it or makes it available as part of a
commercial program such as training, etc. (i.e. to get around the idea of
selling the software itself they give it away but charge for a training
session, etc.)

2. User downloads software makes changes and resells that full superset
version to clients.

What we want to do is encourage the following...

non-commercial community modifications which people could add on top of the
commercial version - or we might ask permission to compile into future

academic and discussion use of any kind (it's an educational product)

non-commercial personal use of any kind

We're also fine with people using segments of our code in completely
non-related projects or products so long as their is some level of

The big issue is the project needs to protect what revenue it does earn from
compiled sales of the software as a means of further support and it doesn't
want to confuse the market with other commercial spinoffs.

Any feedback about licenses or sections of licenses that help with this
would be useful.

Also I've looked at the Apple Public Source License which I know has major
faults among the open source community can anyone answer the following:

1. What specifically (sections if possible) is bad about this license
vis-a-vis the license itself and the community in general

2. Is there a license near this that is acceptable?

One of the big reasons I like the Apple License and a few other "big
company" licenses is that they've spelled out the warranty areas a lot more
specifically than some of the more general licenses have and that is
important given the background of some of the supporters of this project who
will need to absolve themselve as explicitly as possible of any issues
concerning reuse of the source code.

I know some of this may have been kicked around already but any help here
would be appreciated.

More information about the License-discuss mailing list