Definition of open source

Alan Rihm alan at
Sat Nov 6 13:08:08 UTC 2004


I realize this is a topic that has been discussed many times in the
community, and I have taken my time to do research before sending this
email. From what I can tell, it seems that many new entrants struggle
with the current definition and available or "approved" licenses.
Hopefully the community agrees that it is worth continuing the

Here are my thoughts.

Currently the number one requirement from the OSI to be considered "open
source" is "Free Redistribution". It seems to me that this requirement
is not by itself the key point to determining if a project is open
source or not. What it does do, however, is cause a great divide. My
perception is that this requirement means that the only new projects
that can be justified are those originated by developers who wish to
further their resume, or companies with deep pockets who feel they can
out-code the competition. Of course the exception to the rule are those
who were early entrants, and have time and wide-scale adoption on their

The other problem that I see, is that the "dual license" strategy causes
people to launch a project, and then essentially end-of-life the project
to encourage people to buy the paid/closed version. This seems like a
clear sign that the current definition needs to be updated, so why not
fix the problem instead of "working around" the problem.

Could we consider changing the definition to focus on the following (in
layman terms)?

 1) Your source code is open and available to anyone to see and
download. The term "open source" seems to imply that this would be
requirement #1

 2) End-Users and Developers can use the code/software for free

 3) Derivative works allowed/encouraged

 4) And all the other basics that most in the community seem to accept

As for distribution, let each project owner carve out what can and can't
be done. This would foster so many more projects, and it would
ultimately help end users and developers. After all, aren't we really
trying to foster options to closed source solutions, and give the
end-users and developers freedom to make software work the way they want
it to work? It doesn't seem like the goal of open source was to reduce a
companies ability to make money by going open.

The bottom line reason for my thinking is this: 

Why should someone be able to make money on someone else's code, without
any financial responsibility to the originator of that code? If the
originator charges too much, shame on them. Their project will not gain
much support. If they are reasonable, then "for profit" businesses will
consider partnering with the originator.

Thanks in advance for your constructive responses.

Ps. We are launching our project based on the Mozilla 1.1 license, but
with changes to the distribution rights.

Alan Rihm
CentraView, LLC
alan at
(610)410-7457 Office
(610)450-6771 Fax 

More information about the License-discuss mailing list