Bug#276302: New upstream release and license debate

[Paul Cager]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've had a look at the new upstream release (4.0), and it's still not
clear if it is DFSG compliant.

The website[1] explicitly states that the license is "Berkeley Software
Distribution (BSD) License".

In an answer to a query the author (Sreenivas Viswanadha) states that
the "entire javacc distribution, including the example grammars comes
under BSD license"[2].

The LICENSE file in the distribution is the standard BSD license, but
with the following paragraph added at the end:

   "You acknowledge that  this software is not designed, licensed or
intended for use in the design, construction, operation or maintenance
of any nuclear facility."

Most of the source files contain a copyright declaration ending with:

    "Nuclear, missile, chemical biological weapons or nuclear maritime
end uses or end users, whether direct or indirect, are strictly
prohibited.  Export or reexport to countries subject to U.S. embargo or
to entities identified on U.S. export exclusion lists, including, but
not limited to, the denied persons and specially designated nationals
lists is strictly prohibited."

I guess that the author intends it to be truly free software, but hasn't
removed all of the licensing cruft left over from its time as a
proprietary Sun product - assuming he is legally entitled to do so. I'll
send him an email about it.

[1] https://javacc.dev.java.net/
[2] https://javacc.dev.java.net/servlets/ReadMsg?listName=users&msgNo=919

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFbrVfLSXFtdTZVSURAqJfAJ4pndKy8aPbvLgHDwF0d4QB+QqY7ACfcSZD
oOYJBxDpAPrLYvgcE6B29e0=
=A9+8
-----END PGP SIGNATURE-----