[OpenAFS] OpenAFS Licensing Update Discussion
Todd DeSantis
atd@us.ibm.com
Thu, 10 Jun 2021 19:23:48 -0400
--0__=8FBB0C63DFF8B7878f9e8a93df938690918c8FBB0C63DFF8B787
Content-type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Greetings OpenAFS Community
I would like to introduce an OpenAFS community proposal to change the
licensing terms for future releases of the kernel components of OpenAFS.
Today OpenAFS is exclusively available under the IBM Public License
(IPL-1.0). Due to OpenAFS having some Linux kernel modules, the IPL is not
optimal for development and consumption of the kernel code on Linux. We're
proposing that, going forward, OpenAFS kernel components should be
available under a dual licensing model - the GNU GPL Version 2 and the
existing IPL-1.0. Based on a recent request from the community, IBM is
already in support of and working toward the dual licensing change for the
OpenAFS kernel components.
This change has many benefits for the OpenAFS community as well as users of
OpenAFS in Linux environments. Having the OpenAFS kernel code available
under the GNU GPLv2 will provide the appropriate licensing model for the
OpenAFS Linux kernel code that meets current Linux kernel licensing
standards. The time has come to institute this change and your agreement
and support is needed.
Among the many benefits of OpenAFS kernel components under the GPLv2
include:
Avoidance of tainting Linux kernels when OpenAFS kernel components are
installed
Ability to leverage modern Linux kernel features
Opportunity to distribute OpenAFS kernel modules in Linux distributions
Hosting of OpenAFS kernel support on POWER architecture
In order to realize the advantages of the dual-licensing model for the
OpenAFS kernel components, the following items need to be addressed:
Identify what OpenAFS source code needs to be licensed under the dual
licensing model - the GNU GPL Version 2 and the existing IPL-1.0.
Obtain agreement from all OpenAFS code Copyright holders to dual-license
their code contributions under the GPLv2 and IPL-1.0. This will be
accomplished with a new OpenAFS Contributors License Agreement (CLA) and
Corporate Contributors License Agreement (CCLA) to be drafted and used
for this effort.
Clean-room code module replacements in situations where Copyright
holders cannot be found or will not agree to the licensing change
Annotate each OpenAFS source file with the appropriate GPLv2 and IPL-1.0
notices.
Add MODULE_LICENSE("GPL and additional rights"); to the OpenAFS kernel
source files and other technical code updates.
We will have a discussion on the Dual Licensing effort during the AFS
Technologies Workshop -- June 14th through June 16th via a Virtual
Workshop during the "IBM Status Update" session on Tuesday, June 15th in
the 10:15 to 10:45 slot. We may also have a BOF session on this subject
later on Tuesday or Wednesday during the Workshop.
Here's a link to the AFS Technologies Workshop page:
https://workshop.openafs.org/afsbpw21/
The OpenSSL Community went through a similar license activity a few years
back and here is a pointer to that site.
https://www.openssl.org/blog/blog/categories/license/
A link to the CLA details that the OpenSSL effort used is
https://www.openssl.org/policies/cla.html
The OpenAFS Community might do something like this as well to help group
contributors with contributions and what area of the code it hits, etc.
Please use the openafs-devel@openafs.org mailing list as the list to be
used for discussions regarding re-licensing.
Thanks for your help and support on this important initiative.
Todd DeSantis
IBM AFS Support
OpenAFS Foundation Board Member
--0__=8FBB0C63DFF8B7878f9e8a93df938690918c8FBB0C63DFF8B787
Content-Transfer-Encoding: quoted-printable
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
<html><body><p><font size=3D"2">Greetings OpenAFS Community </font><br><br>=
<font size=3D"2">I would like to introduce an OpenAFS community proposal to=
change the licensing terms for future releases of the kernel components of=
OpenAFS. Today OpenAFS is exclusively available under the IBM Public Licen=
se (IPL-1.0). Due to OpenAFS having some Linux kernel modules, the IPL is n=
ot optimal for development and consumption of the kernel code on Linux. We'=
re proposing that, going forward, OpenAFS kernel components should be avail=
able under a dual licensing model - the GNU GPL Version 2 and the existing =
IPL-1.0. Based on a recent request from the community, IBM is already in =
support of and working toward the dual licensing change for the OpenAFS ker=
nel components.</font><br><br><font size=3D"2">This change has many benefit=
s for the OpenAFS community as well as users of OpenAFS in Linux environmen=
ts. Having the OpenAFS kernel code available under the GNU GPLv2 will provi=
de the appropriate licensing model for the OpenAFS Linux kernel code that m=
eets current Linux kernel licensing standards. The time has come to instit=
ute this change and your agreement and support is needed. </font><br><br><b=
><font size=3D"2">Among the many benefits of OpenAFS kernel components unde=
r the GPLv2 include: </font></b><br>
<ul type=3D"disc"><li><font size=3D"2">Avoidance of tainting Linux kernels =
when OpenAFS kernel components are installed</font><li><font size=3D"2">Abi=
lity to leverage modern Linux kernel features </font><li><font size=3D"2">O=
pportunity to distribute OpenAFS kernel modules in Linux distributions </f=
ont><li><font size=3D"2">Hosting of OpenAFS kernel support on POWER archite=
cture </font></ul><br><b><font size=3D"2">In order to realize the advantage=
s of the dual-licensing model for the OpenAFS kernel components, the follow=
ing items need to be addressed: </font></b><br>
<ul type=3D"disc"><li><font size=3D"2">Identify what OpenAFS source code ne=
eds to be licensed under the dual licensing model - the GNU GPL Version 2 a=
nd the existing IPL-1.0.</font><li><font size=3D"2">Obtain agreement from a=
ll OpenAFS code Copyright holders to dual-license their code contributions =
under the GPLv2 and IPL-1.0. This will be accomplished with a new OpenAFS C=
ontributors License Agreement (CLA) and Corporate Contributors License Agre=
ement (CCLA) to be drafted and used for this effort. </font><li><font size=
=3D"2">Clean-room code module replacements in situations where Copyright ho=
lders cannot be found or will not agree to the licensing change</font><li><=
font size=3D"2">Annotate each OpenAFS source file with the appropriate GPLv=
2 and IPL-1.0 notices. </font><li><font size=3D"2">Add MODULE=5FLICENSE(&qu=
ot;GPL and additional rights"); to the OpenAFS kernel source files and=
other technical code updates.</font></ul><br><font size=3D"2">We will have=
a discussion on the Dual Licensing effort during the AFS Technologies Work=
shop -- June 14th through June 16th via a Virtual Workshop </font><font si=
ze=3D"2" face=3D"Arial">during the "IBM Status Update" session on=
Tuesday, June 15th in the 10:15 to 10:45 slot.</font><font size=3D"2"> </f=
ont><font size=3D"2" face=3D"Arial">We may also have a BOF session on this =
subject later on Tuesday or Wednesday during the Workshop.</font><font size=
=3D"2"><br><br>Here's a link to the AFS Technologies Workshop page</font><f=
ont size=3D"2" face=3D"Arial">: </font><a href=3D"https://workshop.openafs.=
org/afsbpw21/" target=3D"=5Fblank"><u><font size=3D"2" color=3D"#0000FF" fa=
ce=3D"Arial">https://workshop.openafs.org/afsbpw21/</font></u></a><font siz=
e=3D"2" face=3D"Arial"><br></font><br><font size=3D"2">The OpenSSL Communit=
y went through a similar license activity a few years back and here is a p=
ointer to that site.</font><font size=3D"2" face=3D"Arial"><br></font><u><f=
ont size=3D"2" color=3D"#0000FF" face=3D"Arial"><br></font></u><a href=3D"h=
ttps://www.openssl.org/blog/blog/categories/license/" target=3D"=5Fblank"><=
tt><u><font color=3D"#0000FF">https://www.openssl.org/blog/blog/categories/=
license/</font></u></tt></a><br><br><font size=3D"2">A link to the CLA deta=
ils that the OpenSSL effort used is</font><br><br><a href=3D"https://www.op=
enssl.org/policies/cla.html"><font size=3D"2" face=3D"Arial">https://www.op=
enssl.org/policies/cla.html</font></a><br><tt><br></tt><font size=3D"2">The=
OpenAFS Community might do something like this as well to help group contr=
ibutors with contributions and what area of the code it hits, etc.</font><b=
r><br><font size=3D"2">Please use </font><font size=3D"2">the </font><a hre=
f=3D"mailto:openafs-devel@openafs.org"><u><font size=3D"2" color=3D"#0000FF=
">openafs-devel@openafs.org</font></u></a><font size=3D"2"> mailing list as=
the list to be used for discussions regarding re-licensing.</font><br><tt>=
<br></tt><font size=3D"2">Thanks for your help and support on this importan=
t initiative. <br><br>Todd DeSantis</font><br><font size=3D"2">IBM AFS Sup=
port<br>OpenAFS Foundation Board Member</font><BR>
</body></html>
--0__=8FBB0C63DFF8B7878f9e8a93df938690918c8FBB0C63DFF8B787--