- legal-discuss - lists.openstack.org

[kolla]is it OK to modify python code in OpenStack project?
by Jeffrey Zhang 02 Jan '17

02 Jan '17

Recently, Kolla project has requirement to modify[1] the python's ConfigParser.py code[0]. Python is using PSF license[3], which is GPL compatible. But OpenStack is using Apache License. Here is the diff view[2]. I want to make sure: is it OK to re-license ConfigParser.py? If not, what the solution? [0] https://github.com/python/cpython/blob/2.7/Lib/ConfigParser.py [1] https://review.openstack.org/412101 [2] https://gist.github.com/jeffrey4l/2258b276cbd038e73797cfa0952da371/revision… [3] https://docs.python.org/3/license.html -- Regards, Jeffrey Zhang Blog: http://xcodest.me

3 2

Re: [legal-discuss] [all][tc][kolla]is it OK to modify python code in OpenStack project?
by Michał Jastrzębski 02 Jan '17

02 Jan '17

Added all and tc tags, as it might affect everyone really. On 25 December 2016 at 23:04, Jeffrey Zhang <zhang.lei.fly(a)gmail.com> wrote: > Recently, Kolla project has requirement to modify[1] the python's > ConfigParser.py code[0]. > > Python is using PSF license[3], which is GPL compatible. But OpenStack > is using Apache License. > > Here is the diff view[2]. > > I want to make sure: is it OK to re-license ConfigParser.py? If not, what > the solution? > > [0] https://github.com/python/cpython/blob/2.7/Lib/ConfigParser.py > [1] https://review.openstack.org/412101 > [2] > https://gist.github.com/jeffrey4l/2258b276cbd038e73797cfa0952da371/revision… > [3] https://docs.python.org/3/license.html > > > -- > Regards, > Jeffrey Zhang > Blog: http://xcodest.me > > _______________________________________________ > legal-discuss mailing list > legal-discuss(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss >

4 3

Re: [legal-discuss] [all][tc][kolla]is it OK to modify python code in OpenStack project?
by Jeffrey Zhang 27 Dec '16

27 Dec '16

not simple override the _read() method. I also copied some code from ConfigParser.py(more than 80%, i think). is that OK? is there any difference between override method and copy codes? On Tue, Dec 27, 2016 at 3:12 AM, Monty Taylor <mordred(a)inaugust.com> wrote: > On 12/26/2016 07:27 AM, Davanum Srinivas wrote: > > PSF is ok per (https://governance.openstack.org/tc/reference/licensing. > html) > > Though the overriding the _read() seems like something that could > > break easily > > Yah - you can't relicense it - but you can include it with the PSF > license. It might be worth adding a PSF license header to that file and > a note that the code is copied from [0] > > That said - I agree with dims, overriding the _read() method like that > seems prone to sadness. > > > On Mon, Dec 26, 2016 at 12:13 PM, Michał Jastrzębski <inc007(a)gmail.com> > wrote: > >> Added all and tc tags, as it might affect everyone really. > >> > >> On 25 December 2016 at 23:04, Jeffrey Zhang <zhang.lei.fly(a)gmail.com> > wrote: > >>> Recently, Kolla project has requirement to modify[1] the python's > >>> ConfigParser.py code[0]. > >>> > >>> Python is using PSF license[3], which is GPL compatible. But OpenStack > >>> is using Apache License. > >>> > >>> Here is the diff view[2]. > >>> > >>> I want to make sure: is it OK to re-license ConfigParser.py? If not, > what > >>> the solution? > >>> > >>> [0] https://github.com/python/cpython/blob/2.7/Lib/ConfigParser.py > >>> [1] https://review.openstack.org/412101 > >>> [2] > >>> https://gist.github.com/jeffrey4l/2258b276cbd038e73797cfa0952da3 > 71/revisions?diff=split > >>> [3] https://docs.python.org/3/license.html > >>> > >>> > >>> -- > >>> Regards, > >>> Jeffrey Zhang > >>> Blog: http://xcodest.me > >>> > >>> _______________________________________________ > >>> legal-discuss mailing list > >>> legal-discuss(a)lists.openstack.org > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss > >>> > >> > >> _______________________________________________ > >> legal-discuss mailing list > >> legal-discuss(a)lists.openstack.org > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss > > > > > > > > > _______________________________________________ > legal-discuss mailing list > legal-discuss(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss > -- Regards, Jeffrey Zhang Blog: http://xcodest.me

1 0

AGPLv3+ acceptable for third party dependencies?
by Ade Lee 11 Nov '16

11 Nov '16

Hi, Just a quick question: Is AGPLv3+ an acceptable license for a third party library that is a dependency for an Openstack project? I read: (from http://governance.openstack.org/reference/licensing.html) In order to be acceptable as dependencies of OpenStack projects, external libraries (produced and published by 3rd-party developers) must be licensed under an OSI-approved license that does not restrict distribution of the consuming project. The list of acceptable licenses includes ASLv2, BSD (both forms), MIT, PSF, LGPL, ISC, and MPL. Licenses considered incompatible with this requirement include GPLv2, GPLv3, and AGPL. Is AGPL the same as AGPLv3 (and therefore not acceptable)? Thanks, Ade Lee

5 7

[tc][kolla] Ansible module with GPLv3
by Michał Jastrzębski 07 Nov '16

07 Nov '16

Cross-post from [1] Hello everyone, I'm looking for legal advice about having GPLv3 file in Kolla repository. Our use case doesn't seem to be derivative, so I think that should be possible to pull off - having an single gpl v3 module within Kolla without affecting general Kolla license, but it's highly unorthodox so I would like to have second opinion on that front. Regards, Michal inc0 Jastrzebski [1] http://lists.openstack.org/pipermail/openstack-dev/2016-November/106761.html

3 4

Adding license header to autogenerated content
by Steve Martinelli 22 Oct '16

22 Oct '16

I recently came across a patch [1] that is trying to add the Apache license to an autogenerated file. We've recently had issues with contributors finding patches that apply to all the projects; this would definitely be one of those. My quick search [2] is showing that around 350 repositories have the license in the file. Out of the 1000+ we have in openstack (not including what's in openstack-infra or openstack-dev) Yes, it's a python file, there is some "code" there, but it's auto-generated, either from sphinx or our cookiecutter (which now includes the license [3]). So before we use up resources in merging a bunch of patches, I wanted to know if the license was actually necessary. Thanks for reading, Steve [1] https://review.openstack.org/#/c/377170/1 [2] http://codesearch.openstack.org/?q=Apache&i=nope&files=doc%2Fsource%2Fconf.… [3] https://github.com/openstack-dev/cookiecutter/blob/master/%7B%7Bcookiecutte…

4 6

Question on the ICLA
by Michael Latchmansingh 19 Oct '16

19 Oct '16

Hi OpenStack legal community I have a question on the purpose of the ICLA. In attempting to setup my local Git repository with the OpenStack Gerrit system, I ran into an issue where I was asked to sign the ICLA. My submissions to OpenStack are on behalf of the company I work for, and we have already a signed CCLA. Our general counsel does not want me to sign an individual CLA because I do not own any of the IP being submitted. Can you clarify, in legal terms for my general counsel, why there is this requirement? Thanks and Regards, Michael Latchmansingh | Director, Product Development 954-377-6058 t 561-927-5754 c michael.latchmansingh.datacore (skype) DataCore Software Corporation Corporate Park 6300 NW 5th Way Ft. Lauderdale, FL 33309 http://www.datacore.com<http://www.datacore.com/>

7 6

Trademark for a specific OpenStack project
by Davanum Srinivas 18 Oct '16

18 Oct '16

Hi, Does the foundation hold trademarks for any of the big tent projects? Does the policy cover any such marks? [1] What are the options if someone active in the community decides to continue their work outside the foundation using the same project name? Thanks, Dims [1] http://www.openstack.org/brand/openstack-trademark-policy/ -- Davanum Srinivas :: https://twitter.com/dims

2 2

Legal Affairs Committee Meeting, September 30, 1:15 PDT
by Strottman, Nissa 22 Sep '16

22 Sep '16

Hi- The Legal Affairs Committee will be meeting Friday, September 30, at 1:15 PDT to discuss Facebook's additional patent license grant in addition to the BSD license for ReactJS, which is being used in at least two projects (Fuel-UI and TripleO). The text for the patent grant may be viewed here: https://github.com/facebook/react/blob/master/PATENTS Call-in number: 1-702-696-4520 Passcode: 7612918876 Best, Nissa Nissa M. Strottman Associate General Counsel Software, Cloud and Open Source Office of the General Counsel +1 650 857 6279 Office +1 650 387 4987 Mobile Palo Alto, CA hpe.com [HPE logo]<http://www.hpe.com/>

1 0

Docker Inc. trademark guidelines
by Steven Dake (stdake) 19 Sep '16

19 Sep '16

It has come to my attention that Docker Inc has published trademark guidelines. The OpenStack Kolla community wishes to comply with the trademark guidelines Docker has published. I humbly request a legal review of the following change from a foundation attorney: https://review.openstack.org/#/c/372133/ Note the term “website” in the published guidelines could be parsed in multiple ways which I find confusing. Some guidance here would be helpful as well. (CCs are self-nominated PTLs for the Ocata cycle). Regards -steve

2 1