diff options
| author | Russell Bryant <russell@russellbryant.com> | 2009-06-30 16:40:38 +0000 |
|---|---|---|
| committer | Russell Bryant <russell@russellbryant.com> | 2009-06-30 16:40:38 +0000 |
| commit | c511a2674906fd93470f0a9b77340041771466e1 (patch) | |
| tree | d3d6aa7ea86d11ecaa6e88efbc46a5dde1c63ea5 /README-addons.txt | |
| parent | 62d3f1dfd9632f18c4f7c12e44af30f4cc08c292 (diff) | |
Move Asterisk-addons modules into the main Asterisk source tree.
Someone asked yesterday, "is there a good reason why we can't just put these
modules in Asterisk?". After a brief discussion, as long as the modules are
clearly set aside in their own directory and not enabled by default, it is
perfectly fine.
For more information about why a module goes in addons, see README-addons.txt.
chan_ooh323 does not currently compile as it is behind some trunk API updates.
However, it will not build by default, so it should be okay for now.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@204413 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'README-addons.txt')
| -rw-r--r-- | README-addons.txt | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/README-addons.txt b/README-addons.txt new file mode 100644 index 000000000..4d5e1986f --- /dev/null +++ b/README-addons.txt @@ -0,0 +1,27 @@ +=============================================================================== +=== Asterisk Add-on Modules === +=============================================================================== + + This document pertains to the modules that reside in the addons/ +subdirectory of the source tree. By default, these modules are not compiled +and installed. If you choose to enable them, you must be aware of what +potential licensing and/or patent implications that has on your usage and +distribution of Asterisk. + + Even though Asterisk is released as open source under the terms of the +GPLv2 (see LICENSE for details), no core functionality in Asterisk has any +dependencies on libraries that are licensed under the GPL. One reason a module +may be in the add-ons category is that it may have a GPL dependency. Since +these dependencies are not compatible with dual licensing of Asterisk, the +dependant modules are set aside to make it clear that they may not be used +with commercial versions of Asterisk, unless other licensing arrangements are +made with the copyright holders of those dependencies. + + Another reason that modules may be set aside is that there may be +additional restrictions on the usage of the code imposed by the license or +related patents. The MySQL and MP3 modules are examples of this. + + If you have any questions, contact your lawyer. + +=============================================================================== +=============================================================================== |