Re: [opnfv-tech-discuss] Licenses for OPNFV docker images
Sorry for the delay on this as I was checking internally on this. What Bryan has for VES works, but I also went ahead and created a template that people can use at https://wiki.opnfv.org/display/DEV/License+information+for+Docker+images Let me know if you have any feedback/questions. Thanks, Ray On Tue, Jan 9, 2018 at 9:00 AM, SULLIVAN, BRYAN L (BRYAN L) < bryan.sulli...@research.att.com> wrote: > I have a proposed text, included in the containers I have published at > https://hub.docker.com/u/blsaws/. Here is an example for > https://hub.docker.com/r/blsaws/ves-agent/ > > This container provides the "VES Agent" function of the OPNFV VNF Event > Stream (VES) project. The container is built via the "ves-agent.sh" script > in the VES repo folder https://github.com/opnfv/ves/tree/master/build. > For more information, see https://wiki.opnfv.org/display/ves/VES+Home. > > The container includes code developed under the OPNFV project and > distributed under the license below (# LICENSE #), and other code installed > as part of the container build process, separately licensed per the source > of that code. > > LICENSE > > Copyright 2017-2018 AT Intellectual Property, Inc > > Licensed under the Apache License, Version 2.0 (the "License"); > you may not use this file except in compliance with the License. > You may obtain a copy of the License at > > http://www.apache.org/licenses/LICENSE-2.0 > > > > > > Thanks, > > Bryan Sullivan | AT > > > > *From:* Raymond Paik [mailto:rp...@linuxfoundation.org] > *Sent:* Tuesday, January 09, 2018 8:55 AM > *To:* SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com> > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* Re: [opnfv-tech-discuss] Licenses for OPNFV docker images > > > > Hi Bryan, > > > > So you're looking for a license text for OPNFV users to use the contents > in OPNFV docker hub? Let me know if I'm mistaken. I can check with the > legal team on this... > > > > Thanks, > > > > Ray > > > > On Mon, Jan 8, 2018 at 10:04 AM, SULLIVAN, BRYAN L (BRYAN L) < > bryan.sulli...@research.att.com> wrote: > > Hi all, > > > > Should we be adding license descriptions to the > https://hub.docker.com/u/opnfv > <https://urldefense.proofpoint.com/v2/url?u=https-3A__hub.docker.com_u_opnfv=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=Vhsg_dHEzZCJSAlC9Rqj7XNCdUiysW9SBM-_Bwp4S4M=> > images? I have seen a recommendation that the license be included in the > repo description field. Just wondering, since otherwise per the docker hub > TOS (https://www.docker.com/docker-terms-service > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.docker.com_docker-2Dterms-2Dservice=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=YRdES2lVRMwnqTDaC93eWXqDR-Z-VTorQmNkEirqyVM=> > ): > > > > *6.4 *The Service allows you to specify or upload the terms under which > other users of the Service will be licensed to use your User Content. If > you do not specify or upload such license terms with respect to any User > Content, you hereby grant to any other users of the Service, a > non-exclusive license to access, download, use, modify or otherwise exploit > such part of your User Content for any personal or business purposes. > > > > Thanks, > > Bryan Sullivan | AT > > > > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=w8PKfRUudxG9-IcIX1J-Z0822Ry3Te8yDvoqQAYZyX0=> > > > ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] Licenses for OPNFV docker images
I have a proposed text, included in the containers I have published at https://hub.docker.com/u/blsaws/. Here is an example for https://hub.docker.com/r/blsaws/ves-agent/ This container provides the "VES Agent" function of the OPNFV VNF Event Stream (VES) project. The container is built via the "ves-agent.sh" script in the VES repo folder https://github.com/opnfv/ves/tree/master/build. For more information, see https://wiki.opnfv.org/display/ves/VES+Home. The container includes code developed under the OPNFV project and distributed under the license below (# LICENSE #), and other code installed as part of the container build process, separately licensed per the source of that code. LICENSE Copyright 2017-2018 AT Intellectual Property, Inc Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Thanks, Bryan Sullivan | AT From: Raymond Paik [mailto:rp...@linuxfoundation.org] Sent: Tuesday, January 09, 2018 8:55 AM To: SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com> Cc: opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] Licenses for OPNFV docker images Hi Bryan, So you're looking for a license text for OPNFV users to use the contents in OPNFV docker hub? Let me know if I'm mistaken. I can check with the legal team on this... Thanks, Ray On Mon, Jan 8, 2018 at 10:04 AM, SULLIVAN, BRYAN L (BRYAN L) <bryan.sulli...@research.att.com<mailto:bryan.sulli...@research.att.com>> wrote: Hi all, Should we be adding license descriptions to the https://hub.docker.com/u/opnfv<https://urldefense.proofpoint.com/v2/url?u=https-3A__hub.docker.com_u_opnfv=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=Vhsg_dHEzZCJSAlC9Rqj7XNCdUiysW9SBM-_Bwp4S4M=> images? I have seen a recommendation that the license be included in the repo description field. Just wondering, since otherwise per the docker hub TOS (https://www.docker.com/docker-terms-service<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.docker.com_docker-2Dterms-2Dservice=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=YRdES2lVRMwnqTDaC93eWXqDR-Z-VTorQmNkEirqyVM=>): 6.4 The Service allows you to specify or upload the terms under which other users of the Service will be licensed to use your User Content. If you do not specify or upload such license terms with respect to any User Content, you hereby grant to any other users of the Service, a non-exclusive license to access, download, use, modify or otherwise exploit such part of your User Content for any personal or business purposes. Thanks, Bryan Sullivan | AT ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_mailman_listinfo_opnfv-2Dtech-2Ddiscuss=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0=ZPXRCYu_xZVUz0EC6v-KtgPkYQlVtp8-HtA2qJtbrDM=w8PKfRUudxG9-IcIX1J-Z0822Ry3Te8yDvoqQAYZyX0=> ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] Licenses for OPNFV docker images
Hi Bryan, So you're looking for a license text for OPNFV users to use the contents in OPNFV docker hub? Let me know if I'm mistaken. I can check with the legal team on this... Thanks, Ray On Mon, Jan 8, 2018 at 10:04 AM, SULLIVAN, BRYAN L (BRYAN L) < bryan.sulli...@research.att.com> wrote: > Hi all, > > > > Should we be adding license descriptions to the > https://hub.docker.com/u/opnfv images? I have seen a recommendation that > the license be included in the repo description field. Just wondering, > since otherwise per the docker hub TOS (https://www.docker.com/ > docker-terms-service): > > > > *6.4 *The Service allows you to specify or upload the terms under which > other users of the Service will be licensed to use your User Content. If > you do not specify or upload such license terms with respect to any User > Content, you hereby grant to any other users of the Service, a > non-exclusive license to access, download, use, modify or otherwise exploit > such part of your User Content for any personal or business purposes. > > > > Thanks, > > Bryan Sullivan | AT > > > > ___ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
