K.S. Bhaskar wrote:
/snip/

> In the case of the pedi project, I recommend
> the GPL.

As I understand the architecture of VistA, new functionality will tend to
include / result from modifications to existing code rather than simply
additions of new code modules that are completely seperate from the existing
code.  To the extent that this is true it seems to me that there may be some
non-trivial questions that need to be addressed.  For example...

Is is possible for a single piece of source code to have more than one
license?

    If the code is a mix of FOIA software and new
    additions, can the additions be licensed at all?
    For example, "lines 1,2,3 and 7 are FOIA but
    lines 4,5, and 6 are additions subject to the GPL."
    I've never heard of a situation like this.

Is it possible to release FOIA software under a more restrictive license?

    In general, all the OSS licenses I'm aware of
    preclude the licensee from releasing derivative
    code under a more restrictive license.  The
    licensee must give recipients at least the same
    rights he was given.  FOIA software contains
    no license restrictions.  OSS licenses do.  So
    it would seem that there may be an issue
    attendant with the re-release of FOIA software
    under an OSS license.

Is it even possible to for anyone other than the original author to set the
license terms?

    I'm not aware of a situation where someone
    other than the original author(s) has (have) set
    the license terms.  Is there any legal precedent
    for this?

Assuming that FOIA software *can* be re-released by someone other than the
original author(s) under an OSS license, what steps have to be taken?

    In general, for a license to be valid, its terms
    must be presented and accepted.  Most software
    presents you with a license agreement upon
    installation.  Are there accepted alternatives?  Or
    does this capability have to be built into WorldVistA
    software?  Also, for example, many OSS licenses
    require the terms to be included in the source code.
   Anybody sized this effort?

Even if the new code (e.g., pedi) is completely seperate from the existing
code, if the FOIA portion can't be re-released under an OSS license, is
there any precedent in the market for a mixed-license model?

I'm no lawyer, but I'd want the answers to these and other questions before
I contributed code.  If WorldVistA (or anyone else) has already investigated
these issues, is there a document somewhere that provides the answers?

Thanks,
Bill




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Hardhats-members mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to