All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Fertser <fercerpav@gmail.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: Update on some maintainers / contributors.
Date: Thu, 31 Oct 2024 13:05:12 +0300	[thread overview]
Message-ID: <ZyNWWLJOBOPdmbVI@home.paul.comp> (raw)
In-Reply-To: <ZyMIJfBoYDPeJhxK@heinlein.vulture-banana.ts.net>

Hello Patrick,

On Thu, Oct 31, 2024 at 12:31:33AM -0400, Patrick Williams wrote:
> it seems like we should be more forward about what is going on.

Great to hear you think that, and thanks a lot for approaching this in
a more humane way.

>    - We are not accepting new CCLAs from entities on the sanctions list
>      or accepting ICLAs from individuals associated with these
>      entities.

Please consider trying to do better than the "high ranking members of
the kernel community" mentioned earlier and adding specific, explicit
rules regarding this issue to the project documentation.

In particular, it would be really important to clarify 

1. Which sanctions list it is exactly; for Linux they say they are
going to follow just the SDN and not the whole OFAC so even despite
e.g. Huawei is sanctioned they are still allowed to not only
contribute code but also maintain parts of the project.

2. How association of an individual with an entity is established. The
kernel people were mentioning some documents that a developer might
provide to prove they're not associated but it's hard to imagine what
kind of document that might even be.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

  reply	other threads:[~2024-10-31 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31  4:31 Update on some maintainers / contributors Patrick Williams
2024-10-31 10:05 ` Paul Fertser [this message]
2024-10-31 11:14   ` Patrick Williams
2025-04-03 15:04 ` Patrick Williams
2025-04-03 20:43   ` Paul Fertser

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=ZyNWWLJOBOPdmbVI@home.paul.comp \
    --to=fercerpav@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.