# Relicensing GPLv3 - need ok from Seth/Jeremy/Tim

**URL:** <https://forum.ansible.com/t/relicensing-gplv3-need-ok-from-seth-jeremy-tim/15072>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [April 23, 2014, 6:21am UTC](https://forum.ansible.com/t/relicensing-gplv3-need-ok-from-seth-jeremy-tim/15072 "2014-04-23T06:21:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roger\_Qiu1](https://avatars.discourse-cdn.com/v4/letter/r/3be4f8/32.png) [@Roger\_Qiu1](https://forum.ansible.com/u/Roger_Qiu1)\
**Post date:** [April 23, 2014, 6:21am UTC](https://forum.ansible.com/t/relicensing-gplv3-need-ok-from-seth-jeremy-tim/15072/1 "2014-04-23T06:21:14Z")

</div>

Hello Michael, James,

I want to bundle Ansible as part of a bigger package. This means the entire Ansible source would sit in its own folder. Another program which may or may not be GPL will call Ansible via exec/fork/sockets. It will not be embedding the Ansible code or modifying it anyway. Is this in violation of GPLv3?

I’ve researched GPL and it has said that plugins or calling those dependencies from fork/exec/sockets will not be constituted as a single program. But the part where it talks about an aggregate distribution is not clear on this.

Thanks,  
Roger

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [April 23, 2014, 1:20pm UTC](https://forum.ansible.com/t/relicensing-gplv3-need-ok-from-seth-jeremy-tim/15072/2 "2014-04-23T13:20:02Z")

</div>

Hi Roger,