From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: geert@linux-m68k.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements.
Date: Thu, 24 Oct 2024 11:39:11 -0400 [thread overview]
Message-ID: <7ee74c1b5b589619a13c6318c9fbd0d6ac7c334a.camel@HansenPartnership.com> (raw)
In-Reply-To: <a520d1f5-8273-d67e-97fe-67f73edce9f1@linux-m68k.org>
> On Fri, 18 Oct 2024, Greg Kroah-Hartman wrote:
> > Remove some entries due to various compliance requirements. They
> > can come back in the future if sufficient documentation is
> > provided.
>
> This is very vague...
We finally got clearance to publish the actual advice:
If your company is on the U.S. OFAC SDN lists, subject to an OFAC
sanctions program, or owned/controlled by a company on the list, our
ability to collaborate with you will be subject to restrictions, and
you cannot be in the MAINTAINERS file.
> What are "various compliance requirements"?
> What does "sufficient documentation" mean?
The documentation Greg is looking for (which a group of Lawyers at the
LF will verify) is that someone in the removed list doesn't actually
work for an OFAC SDN sanctioned entity.
> I can guess, but I think it's better to spell out the rules, as Linux
> kernel development is done "in the open". I am also afraid this is
> opening the door for further (ab)use...
I agree we should have been more transparent about this but I think it
would be hard for someone other than Greg to get a Maintainer removed
on the "compliance issue" grounds so it's probably not that open to
abuse.
Regards,
James
next prev parent reply other threads:[~2024-10-24 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024101835-tiptop-blip-09ed@gregkh>
2024-10-21 7:49 ` Geert Uytterhoeven
2024-10-21 16:29 ` Wolfram Sang
2024-10-24 6:56 ` Lukas Wunner
2024-10-24 15:39 ` James Bottomley [this message]
2024-10-24 18:41 ` NotYourFox
2024-10-25 11:43 ` 14071 | " Michael Shigorin
2024-10-25 23:44 ` Vladimir Smirnov
2024-10-26 12:00 ` Angry Dev
2024-10-26 16:27 ` John Mcenroy
2024-10-30 13:34 ` metux
2024-10-21 12:02 ` Geert Uytterhoeven
2024-10-24 15:56 ` [PATCH] MAINTAINERS: Remove some entries due to various moral requirements Enrico Weigelt, metux IT consult
2024-10-27 20:20 ` [PATCH] MAINTAINERS: Remove some entries due to various compliance requirements Alexander Pevzner
2024-10-25 21:12 Joe Putin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ee74c1b5b589619a13c6318c9fbd0d6ac7c334a.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®