mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-01-03 05:59:10 +00:00
Code Issues 1 Projects Releases Wiki Activity

add licensing advisory information to plugin writers guide

Browse source 
Original commit message from CVS:
add licensing advisory information to plugin writers guide
This commit is contained in:
Christian Schaller 2005-01-31 11:43:05 +00:00
parent 858c53eacf
commit 4439f8157b
2 changed files with 36 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
docs/pwg/appendix-licensing.xml Normal file
View file

@ -0,0 +1,34 @@
<chapter id="chapter-licensing-advisory">
<title>GStreamer licensing</title>
<sect1 id="section-application-licensing">
<title>How to license the code you write for <application>GStreamer</application></title>
<para>
GStreamer is a plugin-based framework licensed under the LGPL. The reason
for this choice in licensing is to ensure that everyone can use GStreamer
to build applications using licenses of their choice.
</para>
<para>
To keep this policy viable, the GStreamer community has made a few
licensing rules for code to be included in GStreamer's core or GStreamer's
official modules, like our plugin packages. We require that all code going
into our core package is LGPL. For the plugin code, we require the use of
the LGPL for all plugins written from scratch or linking to external
libraries. The only exception to this is when plugins contain older code
under more liberal licenses (like the MPL or BSD). They can use those
licenses instead and will still be considered for inclusion. We do not
accept GPL code to be added to our plugins module, but we do accept
LGPL-licensed plugins using an external GPL library. The reason for
demanding plugins be licensed under the LGPL, even when using a GPL
library, is that other developers might want to use the plugin code as a
template for plugins linking to non-GPL libraries.
</para>
<para>
We also plan on splitting out the plugins using GPL libraries into a
separate package eventually and implement a system which makes sure an
application will not be able to access these plugins unless it uses some
special code to do so. The point of this is not to block GPL-licensed
plugins from being used and developed, but to make sure people are not
unintentionally violating the GPL license of said plugins.
</para>
</sect1>
</chapter>

2
docs/pwg/pwg.xml
View file

@ -40,6 +40,7 @@
<!ENTITY OTHER_MANAGER SYSTEM "other-manager.xml">
<!ENTITY APPENDIX_CHECKLIST SYSTEM "appendix-checklist.xml">
<!ENTITY APPENDIX_LICENSING SYSTEM "appendix-licensing.xml">
<!ENTITY APPENDIX_PYTHON SYSTEM "appendix-python.xml">
<!ENTITY GStreamer "<application>GStreamer</application>">
@ -186,6 +187,7 @@
</partintro>
&APPENDIX_CHECKLIST;
&APPENDIX_LICENSING;
&APPENDIX_PYTHON;
</part>