# Licensing terms for playbooks/modules developed in my use of Ansible and delivered to other people

**URL:** <https://forum.ansible.com/t/licensing-terms-for-playbooks-modules-developed-in-my-use-of-ansible-and-delivered-to-other-people/12294>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [February 6, 2013, 3:03am UTC](https://forum.ansible.com/t/licensing-terms-for-playbooks-modules-developed-in-my-use-of-ansible-and-delivered-to-other-people/12294 "2013-02-06T03:03:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [February 6, 2013, 3:03am UTC](https://forum.ansible.com/t/licensing-terms-for-playbooks-modules-developed-in-my-use-of-ansible-and-delivered-to-other-people/12294/1 "2013-02-06T03:03:44Z")

</div>

Good question.

It does absolutely not require your playbooks or modules to be GPLv3.

Playbooks are data and are yours, and are modules. Same true of any  
inventory scripts you write, as they are simply executed. (Callbacks  
and server side actions of course don't have this luxury, but if you  
are not distributing them, this is not a problem, and only requires  
that you redistribute source for them if you do... so no big deal)

I have been thinking it may be reasonable to make just  
lib/ansible/module\_common.py (which is not part of the rest of ansible  
but really a utility) BSD just to prevent any doubt of this, please  
yell if any active contributors to specifically that file (and only  
that file) object and I'll make it so ASAP.

--Michael