On Mon, Aug 15, 2016 at 11:24 AM, Andrew Cooper <andrew.coop...@citrix.com> wrote: > On 12/08/16 10:37, Lars Kurth wrote: >> COPYING file: >> The motivation of this change is to make it easier for new >> contributors to conduct a license and patent review, WITHOUT >> changing any licenses. >> - Remove references to BSD-style licenses as we have more >> common license exceptions and replace with "other license >> stanzas" >> - List the most common situations under which code is licensed >> under licenses other than GPLv2 (section "Licensing Exceptions") >> - List the most common non-GPLv2 licenses that are in use in >> this repository based on a recent FOSSology scan (section >> "Licensing Exceptions") >> - List other license related conventions within the project >> to make it easier to conduct a license review. >> - Clarify the incoming license as its omission has confused >> past contributors (section "Contributions") >> >> CONTRIBUTION file: >> The motivation of this file is to make it easier for contributors >> to find contribution related resources. Add information on existing >> license related conventions to avoid unintentional future licensing >> issues. Provide templates for copyright headers for the most commonly >> used licenses in this repository. >> >> Signed-off-by: Lars Kurth <lars.ku...@citrix.com> > > Reviewed-by: Andrew Cooper <andrew.coop...@citrix.com>, with one style > correction. > >> diff --git a/CONTRIBUTING b/CONTRIBUTING >> new file mode 100644 >> index 0000000..67ecdb7 >> --- /dev/null >> +++ b/CONTRIBUTING >> @@ -0,0 +1,210 @@ >> <snip> >> + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, >> + * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF >> + * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. >> + * IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY >> + * CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, >> + * TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE >> + * SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. >> + */ >> \ No newline at end of file > > Newline at the end.
That can presumably be fixed up on check-in -- no need to resend. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
