Merge pull request #71 from matejak/lic

Clarified license of generated content.

Author: matejak

LICENSE

@@ -11,7 +11,7 @@ modification, are permitted provided that the following conditions are met:
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.
 
-* Neither the name of argbash nor the names of its
+* Neither the name of Argbash nor the names of its
   contributors may be used to endorse or promote products derived from
   this software without specific prior written permission.
 
@@ -26,3 +26,7 @@ CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
+Clarification concerning content generated by Argbash:
+License of content generated by Argbash has no relation towards the Argbash
+project itself - it is up to the entity who triggered the generation to
+determine the license of the generated content.

doc/index.rst

@@ -149,6 +149,7 @@ Now we launch it and the output is good!
 
    If something still isn't totally clear, take look at the :ref:`sec_example` section.
 
+
 .. _limitations:
 
 Limitations
@@ -168,6 +169,16 @@ Limitations
 #. The generated code generally contains bashisms as it relies heavily on ``bash`` arrays to process any kind of positional arguments and multi-valued optional arguments.
    That said, if you stick with optional arguments only, a POSIX shell s.a. ``dash`` should be able to process the ``Argbash``-generated parsing code.
 
+
+FAQ
+---
+
+* **Q**: What is the license of generated code?
+  Is it also the 3-clause BSD, as it contains parts of Argbash source code?
+
+  **A**: No, as it is mentioned in the `LICENSE` file, you can distribute Argbash output under your terms.
+  We recommend you to adhere to the BSD license --- keeping comments indicating that the code is generated is fair towards script's users.
+
 Index
 -----