sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-08 21:18:16 +03:00
Code

Add VFS-License-clarification.txt as discussed on the Team list.

Browse Source 
Update WHATSNEW.txt with a copy for the next release.

Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Ralph Boehme <slow@samba.org>

Autobuild-User(master): Ralph Böhme <slow@samba.org>
Autobuild-Date(master): Thu Oct 22 15:34:54 UTC 2020 on sn-devel-184
This commit is contained in:
Jeremy Allison 2020-10-21 10:53:27 -07:00 committed by Ralph Boehme
parent c03a265030
commit 1262b13f4d
2 changed files with 60 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
VFS-License-clarification.txt Normal file
View File

@ -0,0 +1,28 @@
A clarification of the GNU GPL License boundary within the Samba
Virtual File System (VFS) layer.
Samba is licensed under the GNU GPL. All code committed to the Samba
project or creating a derived work must be either licensed under the
GNU GPL or a compatible license.
Samba has several plug-in interfaces where external code may be called
from Samba GNU GPL licensed code. The most important of these is the
Samba VFS layer.
Samba VFS modules are intimately connected by header files and API
definitions to the part of the Samba code that provides file services,
and as such, code that implements a plug-in Samba VFS module must be
licensed under the GNU GPL or a compatible license.
However, Samba VFS modules may themselves call third-party external
libraries that are not part of the Samba project and are externally
developed and maintained.
As long as these third-party external libraries do not use any of the
Samba internal structure, APIs or interface definitions created by the
Samba project that are licensed under the GNU GPL then it is the view
of the Samba Team that such third-party external libraries called from
Samba VFS modules are not part of the Samba code and cannot be
considered a derived work of Samba for the purposes of GNU GPL
licensing. Thus such libraries are not required to be under the GNU
GPL or a GNU GPL compatible license.

32
WHATSNEW.txt
View File

@ -16,6 +16,38 @@ UPGRADING
NEW FEATURES/CHANGES
====================
Here is a copy of a clarification note added to the Samba code
in the file: VFS-License-clarification.txt.
--------------------------------------------------------------
A clarification of the GNU GPL License boundary within the Samba
Virtual File System (VFS) layer.
Samba is licensed under the GNU GPL. All code committed to the Samba
project or creating a derived work must be either licensed under the
GNU GPL or a compatible license.
Samba has several plug-in interfaces where external code may be called
from Samba GNU GPL licensed code. The most important of these is the
Samba VFS layer.
Samba VFS modules are intimately connected by header files and API
definitions to the part of the Samba code that provides file services,
and as such, code that implements a plug-in Samba VFS module must be
licensed under the GNU GPL or a compatible license.
However, Samba VFS modules may themselves call third-party external
libraries that are not part of the Samba project and are externally
developed and maintained.
As long as these third-party external libraries do not use any of the
Samba internal structure, APIs or interface definitions created by the
Samba project that are licensed under the GNU GPL then it is the view
of the Samba Team that such third-party external libraries called from
Samba VFS modules are not part of the Samba code and cannot be
considered a derived work of Samba for the purposes of GNU GPL
licensing. Thus such libraries are not required to be under the GNU
GPL or a GNU GPL compatible license.
Client Group Policy
-------------------