All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: Update on some maintainers / contributors.
Date: Thu, 3 Apr 2025 11:04:40 -0400	[thread overview]
Message-ID: <Z-6jiKlhgkOStFZp@heinlein> (raw)
In-Reply-To: <ZyMIJfBoYDPeJhxK@heinlein.vulture-banana.ts.net>

[-- Attachment #1: Type: text/plain, Size: 2974 bytes --]

The Linux Foundation made a clarifying post on this situation[1].

[1]: https://www.linuxfoundation.org/blog/navigating-global-regulations-and-open-source-us-ofac-sanctions

On Thu, Oct 31, 2024 at 12:31:33AM -0400, Patrick Williams wrote:
> Hello,
> 
> This is not a great situation for Open Source as a whole; involving
> legal issues and international politics.  Since there has been some
> public activity on other Open Source projects, especially the kernel,
> it seems like we should be more forward about what is going on.
> 
> In early 2022, some of our contributors associated with a specific
> company lost access to GitHub.  As a result of this they were unable to
> access Gerrit.  Since that time, access has not been restored and they
> continue to not be able to contribute to the project or provide feedback
> as maintainers on sub-repositories (which some of them were).
> 
> I assume the reason those developers had their GitHub accounts
> suspended was due to their company's appearance on a US government
> sanctions list[1].  Recently, the Linux Kernel has removed a number of
> maintainers for seemingly similar reasons.  A good article on the
> situation can be found on Phoronix[2].
> 
> I have not seen any official/public policy from the Linux Foundation on
> this situation, but it appears that high ranking members of the kernel
> community decided to act based on some non-public guidance they were given.
> 
> The way we are handling the situation is as follows:
> 
>    - We use GitHub for authentication to Gerrit and have no plans to
>      change from this.  Anyone interacting with the code there will
>      need to have GitHub access.  Anyone who has been suspended /
>      blocked by GitHub will not be able to interact with the codebase
>      by either contributions or reviews.
> 
>    - We are not accepting new CCLAs from entities on the sanctions list
>      or accepting ICLAs from individuals associated with these
>      entities.
> 
>    - Maintainers who have lost access to Gerrit are being removed from
>      OWNERS files to provide clarity to contributors.  I believe this
>      affects one full repository and one meta layer.  I am assigning
>      myself as the OWNER of the affected repository to ensure continuity
>      of reviews but would greatly appreciate if someone else has an
>      interest to take it over.  If the situation changes and the
>      previous maintainers are able to resume participation, we can
>      restore owner status to them.
> 
>    - No change is being implemented to the mailing list or Discord.
> 
> I do not have any advice for individual contributors on the project.  If
> you have concerns, you may want to seek guidance within your company.
> 
> [1]: https://ofac.treasury.gov/faqs/topic/1631
> [2]: https://www.phoronix.com/news/Linux-Compliance-Requirements
> 
> -- 
> Patrick Williams



-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2025-04-03 15: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
2024-10-31 11:14   ` Patrick Williams
2025-04-03 15:04 ` Patrick Williams [this message]
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=Z-6jiKlhgkOStFZp@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    /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.