[oclug] Semi-[OT]: Source code ethical dilemma

Jon Earle je_oclug at kronos.honk.org
Mon Sep 19 10:40:59 EDT 2005


Adrian Irving-Beer wrote:
...
> * Freedom to copy and modify the program, as long as the beginning of
>   the source code contains the copyright, credits, and license.
>         * Derivative works must contain the original's copyright,
>           absence of warranty, and revision history.
>         * Executables must show the user the original's copyright and
>           absence of warranty.
> * Freedom to copy and distribute the program, but only under the same
>   license and with no fees.
...

The licence contained in the code is plain and simple... you can modify the
code and release it under the same terms.  Can't get any simpler than that.
As for trying to read the original author's mind to figure out why s/he
released the program in a binary-only form with source code embedded therein,
forget it, can't be done, even by the best psychics the world has coughed up.
 The source may have been released as well and subsequently lost... hard to
say, esp. if the original author is awol.

The product has been placed into the public domain, according to the words of
the licence agreement, which are seemingly in place to keep it that way.  I'd
have no problems with releasing the source code for the benefit of all under
the same licence terms.

> * To use parts of the program in other programs (any license, same
>   language or translated to another), contact the original owner.

That part doesn't apply - you're re-releasing the same program, albeit with
modifications, which is already covered above.

-- 
Jon Earle
Software Developer / Network Manager
Specialising in Open Source Software Solutions
http://kronos.honk.org/~earlej/

"Rocket science is a lot more fun when you actually have rockets."  -- US
Navy Ad



More information about the OCLUG mailing list