Re: [ovs-dev] [PATCH v2] Edit Open vSwitch license info so that GitHub recognizes it.

2018-04-17 Thread Andrea Kao 
Thanks, Ben and Aaron.

And Aaron, you're right - I agree it should've been good enough to put the
exact text of the Apache license into the COPYING file. In any case, it
looks like Licensee has finally been satisfied.

2018-04-16 13:02 GMT-07:00 Ben Pfaff :

> On Fri, Apr 13, 2018 at 03:04:11PM -0400, Aaron Conole wrote:
> > Ben Pfaff  writes:
> >
> > > From: Andrea Kao 
> > >
> > > GitHub uses a library called Licensee to identify a project's license
> > > type. It shows this information in the status bar and via the API if it
> > > can unambiguously identify the license.
> > >
> > > This commit creates a LICENSE file that stores the full text of the
> > > Apache license. It also removes the COPYING file and transfers its
> > > contents to a new "License" section in the README.
> > >
> > > Collectively, these changes allow Licensee to successfully identify the
> > > license type of Open vSwitch's codebase as Apache.
> > >
> > > Submitted-at: https://github.com/openvswitch/ovs/pull/224
> > > Signed-off-by: Andrea Kao 
> > > [b...@ovn.org removed references to COPYING and updated Makefile.am]
> > > Signed-off-by: Ben Pfaff 
> > > ---
> >
> > According to the Licensee[1] code, it should be good enough to put the
> > exact text of the Apache 2.0 license into the COPYING file.  Then again
> > COPYING is a GNU-ism, afaik.
>
> Ack on that.  I'm surprised when I see a file named COPYING that does
> not contain GPLv2 or v3.
>
> > So either way:
> >
> > Acked-by: Aaron Conole 
>
> Thanks.  I applied this to master.
>
> > As a side note, as I start editing files, I'll add SPDX identifiers if
> > others think it makes sense.
>
> Sure, thanks.
>
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v2] Edit Open vSwitch license info so that GitHub recognizes it.

2018-04-16 Thread Ben Pfaff 
On Fri, Apr 13, 2018 at 03:04:11PM -0400, Aaron Conole wrote:
> Ben Pfaff  writes:
> 
> > From: Andrea Kao 
> >
> > GitHub uses a library called Licensee to identify a project's license
> > type. It shows this information in the status bar and via the API if it
> > can unambiguously identify the license.
> >
> > This commit creates a LICENSE file that stores the full text of the
> > Apache license. It also removes the COPYING file and transfers its
> > contents to a new "License" section in the README.
> >
> > Collectively, these changes allow Licensee to successfully identify the
> > license type of Open vSwitch's codebase as Apache.
> >
> > Submitted-at: https://github.com/openvswitch/ovs/pull/224
> > Signed-off-by: Andrea Kao 
> > [b...@ovn.org removed references to COPYING and updated Makefile.am]
> > Signed-off-by: Ben Pfaff 
> > ---
> 
> According to the Licensee[1] code, it should be good enough to put the
> exact text of the Apache 2.0 license into the COPYING file.  Then again
> COPYING is a GNU-ism, afaik.  

Ack on that.  I'm surprised when I see a file named COPYING that does
not contain GPLv2 or v3.

> So either way:
> 
> Acked-by: Aaron Conole 

Thanks.  I applied this to master.

> As a side note, as I start editing files, I'll add SPDX identifiers if
> others think it makes sense.

Sure, thanks.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v2] Edit Open vSwitch license info so that GitHub recognizes it.

2018-04-13 Thread Aaron Conole 
Ben Pfaff  writes:

> From: Andrea Kao 
>
> GitHub uses a library called Licensee to identify a project's license
> type. It shows this information in the status bar and via the API if it
> can unambiguously identify the license.
>
> This commit creates a LICENSE file that stores the full text of the
> Apache license. It also removes the COPYING file and transfers its
> contents to a new "License" section in the README.
>
> Collectively, these changes allow Licensee to successfully identify the
> license type of Open vSwitch's codebase as Apache.
>
> Submitted-at: https://github.com/openvswitch/ovs/pull/224
> Signed-off-by: Andrea Kao 
> [b...@ovn.org removed references to COPYING and updated Makefile.am]
> Signed-off-by: Ben Pfaff 
> ---

According to the Licensee[1] code, it should be good enough to put the
exact text of the Apache 2.0 license into the COPYING file.  Then again
COPYING is a GNU-ism, afaik.  So either way:

Acked-by: Aaron Conole 

As a side note, as I start editing files, I'll add SPDX identifiers if
others think it makes sense.

[1]: 
https://github.com/benbalter/licensee/blob/master/lib/licensee/project_files/license_file.rb
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] [PATCH v2] Edit Open vSwitch license info so that GitHub recognizes it.

2018-04-13 Thread Ben Pfaff 
From: Andrea Kao 

GitHub uses a library called Licensee to identify a project's license
type. It shows this information in the status bar and via the API if it
can unambiguously identify the license.

This commit creates a LICENSE file that stores the full text of the
Apache license. It also removes the COPYING file and transfers its
contents to a new "License" section in the README.

Collectively, these changes allow Licensee to successfully identify the
license type of Open vSwitch's codebase as Apache.

Submitted-at: https://github.com/openvswitch/ovs/pull/224
Signed-off-by: Andrea Kao 
[b...@ovn.org removed references to COPYING and updated Makefile.am]
Signed-off-by: Ben Pfaff 
---
v1->v2: I removed references to COPYING from the tree and updated
Makefile.am to distribute the new LICENSE file.

 COPYING |  42 -
 LICENSE | 191 
 Makefile.am |   1 +
 README.rst  |  33 +++
 debian/rules|   3 +-
 rhel/openvswitch-fedora.spec.in |   4 +-
 rhel/openvswitch.spec.in|   2 +-
 7 files changed, 228 insertions(+), 48 deletions(-)
 delete mode 100644 COPYING
 create mode 100644 LICENSE

diff --git a/COPYING b/COPYING
deleted file mode 100644
index afb98b9d7dd8..
--- a/COPYING
+++ /dev/null
@@ -1,42 +0,0 @@
-This file is a summary of the licensing of files in this distribution.
-Some files may be marked specifically with a different license, in
-which case that license applies to the file in question.
-
-Most files are licensed under the Apache License, Version 2.0:
-
-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
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-
-Files under the datapath directory are licensed under the GNU General
-Public License, version 2.
-
-File build-aux/cccl is licensed under the GNU General Public
-License, version 2.
-
-The following files are licensed under the 2-clause BSD license.
-include/windows/getopt.h
-lib/getopt_long.c
-lib/conntrack-tcp.c
-
-The following files are licensed under the 3-clause BSD-license
-include/windows/netinet/icmp6.h
-include/windows/netinet/ip6.h
-lib/strsep.c
-
-Files under the xenserver directory are licensed on a file-by-file
-basis.  Refer to each file for details.
-
-Files lib/sflow*.[ch] are licensed under the terms of either the
-Sun Industry Standards Source License 1.1, that is available at:
-http://host-sflow.sourceforge.net/sissl.html
-or the InMon sFlow License, that is available at:
-http://www.inmon.com/technology/sflowlicense.txt
diff --git a/LICENSE b/LICENSE
new file mode 100644
index ..4ba8cc0c88b0
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,191 @@
+
+ Apache License
+   Version 2.0, January 2004
+https://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+  "License" shall mean the terms and conditions for use, reproduction,
+  and distribution as defined by Sections 1 through 9 of this document.
+
+  "Licensor" shall mean the copyright owner or entity authorized by
+  the copyright owner that is granting the License.
+
+  "Legal Entity" shall mean the union of the acting entity and all
+  other entities that control, are controlled by, or are under common
+  control with that entity. For the purposes of this definition,
+  "control" means (i) the power, direct or indirect, to cause the
+  direction or management of such entity, whether by contract or
+  otherwise, or (ii) ownership of fifty percent (50%) or more of the
+  outstanding shares, or (iii) beneficial ownership of such entity.
+
+  "You" (or "Your") shall mean an individual or Legal Entity
+  exercising permissions granted by this License.
+
+  "Source" form shall mean the preferred form for making modifications,
+  including but not limited to software source code, documentation
+  source, and configuration files.
+
+  "Object" form shall mean any form resulting from mechanical
+  transformation or translation of a Source form, including but
+  not limited to compiled object code, generated documentation,
+  and conversions to other media types.
+
+  "Work" shall mean the work of authorship, whether in