public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Theodore Ts'o <tytso@mit.edu>, Daniel Gomez <da.gomez@kernel.org>,
	users@kernel.org, Luis Chamberlain <mcgrof@kernel.org>,
	Chuck Lever <cel@kernel.org>,
	kdevops@lists.linux.dev
Subject: Re: Forbidden requests for kernel.org/releases.json
Date: Fri, 11 Apr 2025 19:59:09 +0300	[thread overview]
Message-ID: <20250411165909.GA11377@pendragon.ideasonboard.com> (raw)
In-Reply-To: <ee9486691d2f3a8a1d5bcdb47e757baaf9eaff2e.camel@HansenPartnership.com>

On Fri, Apr 11, 2025 at 12:48:45PM -0400, James Bottomley wrote:
> On Fri, 2025-04-11 at 11:25 -0400, Konstantin Ryabitsev wrote:
> > On Fri, Apr 11, 2025 at 10:18:00AM -0400, Theodore Ts'o wrote:
> [...]
> > > The other alternative that I've tried is to replace git.kernel.org
> > > with kernel.googlesource.com as the git mirror, is supposed to be
> > > only a few minutes behind git.kernel.org and presumably is closer
> > > to a GCE VM from a network perspective.
> > 
> > I'm fine with that as well -- just as long as you keep in mind that
> > it can go away at any time the way many Google things sometimes do.
> > I'm also considering running stable/next/mainline forks on several
> > major forges as mirror-only repos that are updated immediately after
> > each push, so people can use them as an alternative to googlesource.
> 
> Just on this point, the load from AI bots is presumably mostly
> emanating from various public clouds that provide AI services.  It does
> seem to me that those clouds having mirror repositories (even if they
> aren't public) that their AI training would use would help to lower the
> AI bot load on kernel.org and provide faster training to the cloud that
> did this (win/win).  Should kernel.org have an official program to
> facilitate this?

Do we want, as a community, to facilitate GPL violations ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2025-04-11 16:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10  8:05 Forbidden requests for kernel.org/releases.json Daniel Gomez
2025-04-10 10:30 ` Borislav Petkov
2025-04-10 12:09   ` Daniel Gomez
2025-04-11 20:54   ` Konstantin Ryabitsev
2025-04-15  9:01     ` Borislav Petkov
2025-10-13 13:15       ` Borislav Petkov
2025-10-13 15:19         ` Theodore Ts'o
2025-10-14 16:10           ` Kees Cook
2025-04-10 12:45 ` Konstantin Ryabitsev
2025-04-11 14:18   ` Theodore Ts'o
2025-04-11 15:25     ` Konstantin Ryabitsev
2025-04-11 16:48       ` James Bottomley
2025-04-11 16:59         ` Laurent Pinchart [this message]
2025-04-11 17:00         ` Konstantin Ryabitsev
2025-04-11 17:13           ` James Bottomley
2025-04-11 20:38             ` Konstantin Ryabitsev
2025-04-12  2:19               ` Theodore Ts'o
2025-04-11 20:56           ` Luis Chamberlain
2025-04-11 21:04             ` Konstantin Ryabitsev
2025-04-11 23:37               ` Luis Chamberlain
2025-04-11 20:08         ` Jonathan Corbet
2025-04-11 17:09       ` Theodore Ts'o
2025-04-11 18:23   ` Luck, Tony

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=20250411165909.GA11377@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=cel@kernel.org \
    --cc=da.gomez@kernel.org \
    --cc=kdevops@lists.linux.dev \
    --cc=konstantin@linuxfoundation.org \
    --cc=mcgrof@kernel.org \
    --cc=tytso@mit.edu \
    --cc=users@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox