Relicensing GPLv3 - need ok from Seth/Jeremy/Tim

[Michael DeHaan]

I'm reconsidering the MIT license pick for various reasons.

Is everybody ok with changing the license?

(We are not going to require copyright assignment so this will become more difficult later)

--Michael

[seth vidal]

I'm fine with either.

-sv

[Jeremy Katz]

Fine by me

- Jeremy

[Tim Bielawa]

That's fine with me.

[Roger Qiu]

Will this be going ahead? It's still GPLv3 currently.

[James Cammarata]

The core ansible code is and will remain GPL3+, however the code in the modules and the parts that interface with them (the module_utils/*.py files) are licensed using the BSD license so that all modules written by the authors is owned by them. If you have any further questions regarding this, please contact sup...@ansible.com.

Thanks!

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/ef6d40fb-c790-42cf-bb8e-24c4e62265e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael DeHaan]

Hi Roger,

Your post is in reply to a post that was 2 years old.

What James says above is correct -- every module in core is GPLv3, but modules you write are only mixed in with BSD bits, so you can pick whatever license you like for a module that you don't intend to contribute back to core.

However, Ansible itself still has assurances that the core bits remain free forever.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAMFyvFhcF96mXo5RwxRCJ%2BO2Ew2EKNLrLoO%2B4jXSHcjYH%2B1Q-w%40mail.gmail.com.

[Roger Qiu]

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

---

From: Michael DeHaan
Sent: Wed, Apr 23, 2014 02:46
To: ansible...@googlegroups.com
Subject: Re: [ansible-project] Re: Relicensing GPLv3 - need ok from Seth/Jeremy/Tim

You received this message because you are subscribed to a topic in the Google Groups "Ansible Project" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ansible-project/kGutk0IHjpE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ansible-proje...@googlegroups.com.

To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgxK9qs%2B7kX3-yOxgwXxUqzhctr5BPg4huqwTCKF4s3KyA%40mail.gmail.com.

[Michael DeHaan]

Hi Roger,

The GPL says that if you distribute Ansible, you must be able to supply the source including modifications.  This would include any plugins you wrote, so you'd want to take care those plugins were self contained.   (ansible library modules wouldn't apply).   Shelling out to ansible isn't linkage in our book, so from what I've read it seems you are fine.

However, I'd really ask that -- if possible, you install ansible from a common package manager and you not bundle it.  This ensures folks can continue to get updates and fixes, including security updates.

You may wish to consult an IP lawyer.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/lwutcjxu2utc76fw6yog1e28.1398234074672%40email.android.com.