Shipping NAMED-READTABLES with ABCL in abcl-contrib.jar?

[easye]

Armed Bear Common Lisp, a conforming ANSI Common Lisp, is licensed under terms of the GPLv2 with a classpath exception that essentially allows the User to construct any licensing situation on code that is subsequently loaded by the implementation from the JVM classpath. This essentially shunts the responsibility and freedom to construct potentially infringing licensing scenarios "on abcl" to the User.

ABCL also ships with a separate abcl-contrib.jar artifact which currently packaged code for which I largely control/influence the potential copyright of. The "contrib" (ABCL-CONTRIB) mechanism provides the standard ABCL way for contributing code that is potentially useful for system construction and distribution, that for various reasons, is not currently part of Quicklisp.

It would be very useful for the abcl-contrib mechanism to have the encapsulation provided for NAMED-READTABLES available for other contrib's to manipulate the CL readtable via conforming code. And I need this to be possible in the absence of network availability. Therefore, there is a need for NAMED-READTABLES by other code in ABCL-CONTRIB. Currently JSS needs NAMED-RADTABLES the most, in order to be able to work with the ASDF-3.3 'plan' code.

Would the current maintainers be amendable to packaging a version of NAMED-READTABLES in abcl-contrib.jar?

To clarify licensing terms, I would propose

• assert 2-clause BSD on all current ASDF systems loadable from abcl.contrib.jar
• make a statement that abcl-contrib.jar itself has no defined copyright, (i.e. that ABCL-CONTRIB is merely a packaging mechanism)

then I would maintain a curated view of NAMED-READTABLES in perpetuity, as I have done with ASDF in abcl.jar since 2010.

[easye]

abcl-contrib-1.5.0.jar ships with NAMED-READTABLES.