From 115c16bc0ff72e8c96f478bf27b45020dadae1a4 Mon Sep 17 00:00:00 2001 From: lkcl Date: Wed, 5 Oct 2022 14:22:05 +0100 Subject: [PATCH] --- nlnet_2022_opf_isa_wg/discussion.mdwn | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/nlnet_2022_opf_isa_wg/discussion.mdwn b/nlnet_2022_opf_isa_wg/discussion.mdwn index 69613f2cc..34c3a0aab 100644 --- a/nlnet_2022_opf_isa_wg/discussion.mdwn +++ b/nlnet_2022_opf_isa_wg/discussion.mdwn @@ -82,14 +82,19 @@ I don't have a problem with that, if you are fine with the extra admin work :) i appreciate it does mean not needing a special EU Auditor, and also an opportunity to review, half-way through. +** What would work on the legal compliance for the development look like? Who would be doing that? +** -IBM - or more to the point the OPF ISA WG - requesting that all -contributors sign an "Inbound Patent License Agreement". in our +The OpenPOWER Foundation - probably using IBM or LinuxFoundation +Legal Counsel - requesting that all contributors sign an +"Inbound Patent License Agreement". in our case there *aren't* any patents, but we still have to sign an agreement that there aren't any, and, also, that if we *do* create any patents that those will be assigned to the OPF immediately. +There is also a Copyright Assignment requirement (which IBM also had +to agree to, now that the Power ISA is owned by the OpenPOWER Foundation) Perhaps a budget for some legal assistance in reviewing that agreement might be a good idea? NLnet has funded this work under its "Works for the Public Good" mandate: we don't want to be caught out -- 2.30.2