Re: CopyRight, CopyLeft, almost Public Domain, etc. [ l-o-o-ong ]

I do some projects for other non-profits and they do not pay me much,
not enough to give copyrights of my work away. I did several years of
studying the licenses. And I got a Non-Disclosure Agreement from my
old Attorney so that when I disclose code that gives away my own ideas
that outline my conceptual knowledge, I pull out the NDA. I have been
presenting The Clarified Artistic License for my coding on projects that
are open ended and other people will work on. I do web programming,
so of course others would need to modity and update it. I also believe
that you can write your own license agreement if you have end-user
binaries that you want to license and do not want to be modified. I
do not work with large corporations or anyone who would want a
patent so I have not had to deal with thos issues. But I was asked to
submit my projects to for a grant and I did not do it because I did not
want to give out my project concepts unless I had an NDA prior to
presenting my outlines.

Jodell

----- Original Message -----
From: "Richard Owlett" <rowlett_at_atlascomm.net>
Newsgroups: comp.lang.forth
To: <sftalk_at_forth.com>
Sent: Friday, September 06, 2002 3:05 PM
Subject: [sftalk] CopyRight, CopyLeft, almost Public Domain, etc. [
l-o-o-ong ]

>
> I'm considering a project for which I do not consider traditional
> copyright, GPL ( of any form I've seen ), or public domain to be an
> acceptable solution. As I have problems verbalizing what I do want, I
> will describe the project aims and then list why each of the above
> approaches to copyright fails.
>
> BACKGROUND:
> I have a visually impaired adult friend able to read ~20 pt. type.
> He likes to read.
> He is a newbie computer user with limited learning skills due to
> repetitive strokes and other medical problems.
> Aids for the visually impaired (or blind) exist suffering from two
> pervasive problems:
> 1. VERY expensive and due to their disability many are on
> restricted incomes.
> 2. they attempt to be ALL things to ALL people -- a lost cause by
> definition.
> "Project Gutenberg" [ http://promo.net/pg/history.html ] exists to
> provide a computer readable repository of literature in the public
> domain.
>
> RELEVANT SIDE ISSUEs:
> I] Enduring perennial questions include:
> 1. How to promote FORTH [ I'll never use term "killer app" on
> clf again ;} ]
> 2. How can FORTH newbie learn both FORTH and good programming
> techniques?
> II] I am of the persuasion that one learns by solving "real"
> problems.
> I have been working on a program to provide a restricted subset of the
> capabilities of BRAVO.EXE &/or POWERPNT.EXE. [ For my problem they are
> simultaneously "over endowed" and lacking in needed capabilities.
> Working on this 'problem' has instructed me much on the benefits of
> factoring .] This has resulted in some routines that should be useful
> in displaying an arbitrary length text file in a fixed monitor width
> in an arbitrary font size.
>
> PREFERRED FORM OF SOLUTION:
> I] Input from a wide variety of sources as to BOTH problem
> definition and actual code.
>
> This introduces my problem with copyright etc.
> 1. Traditional "copyright" is to restrictive any way you look at it
> for a problem to which many DONATE effort.
> 2. "Public domain" allows anyone to appropriate WITHOUT ATTRIBUTION
> underlying work of others.
> 3. GPL [ http://www.gnu.org/copyleft/gpl.html ] seems to me to deny
> ANY intellectual property rights to any expansion of a GPL'd work.
> 4. I would prefer something that might be termed an _Ambidextrous
> Publication License_. The obvious abbreviation is already covered by a
> copyright ;}! It would require the disclosure of the underlying code
> and appropriate credits to the original author. The code added could
> be as proprietary as desired.
>
> II] A record of the evolution of the solution. It should illustrate
> Top-down design, bottom-up programming and FACTOR FACTOR FACTOR ....
> ,]
>
> I have some ideas on how this might be displayed on the web inspired
> by FAQ-O-MATIC as illustrated by
> http://www.forth.com/cgi-bin/swiftforth and David Williams' work. [I
> have yet to determine all the restrictions on the WEB space that comes
> with my logon account. I do know that whatever I do has to run on a
> WindowsNT box and learning Perl etc. as an additional task is not in
> the cards.]
>
> As a practical matter, anything I put on these pages must run under
> SwiftForth.
> This still leaves open any sections dealing with how to approach this
> ( or any other ) programming task.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.385 / Virus Database: 217 - Release Date: 9/4/2002
----------------------------------------------------------------------
sftalk_at_forth.com      The SwiftForth programming discussion email list
To unsubscribe,  send subject "unsubscribe sftalk" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/sftalk -- check them out!
Search the archives!    Visit http://www.forth.com/search for details.