All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>
Subject: Re: Simon Glass's future with Das U-Boot project?
Date: Wed, 15 Jan 2025 19:19:06 -0600	[thread overview]
Message-ID: <20250116011906.GF3476@bill-the-cat> (raw)
In-Reply-To: <20250102161313.GP3476@bill-the-cat>

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

On Thu, Jan 02, 2025 at 10:13:13AM -0600, Tom Rini wrote:

> Hey all,
> 
> While I had hoped that the quiet of the last week or so had meant that
> things would perhaps return to how they had been before, Simon's large
> patch series and then comments on the TPM+bloblist patch have shown
> otherwise.
> 
> At this point, I do not know how best to handle Simon's behavior,
> without soliciting feedback in public first. At best he's created a
> soft-fork of the project with his "sjg/master" branch. I've asked him
> repeatedly to explain how he thinks this is all going to work out, in
> public. I've had private conversations with him, but I want him to
> explain in public. Or, he can post the messages if he likes.
> 
> And I am in the process of getting outside help that would in turn be
> able to help the project move beyond the BDFL model we've always used.
> Because at the end of the day, if most of the active developers would
> prefer the direction Simon wants to take everything in, that's something
> I can accept. But what's going on now is towards the worst end of
> possible outcomes I think for the project itself. And by that I mean,
> one prominent contributor steam-rolling over others and doing as the
> please and implicitly acting as an authoritative voice for the project.

It's been not quite two weeks. On the positive side, Simon and I are
continuing to talk in private and things are moving in what I hope (and I
believe Simon hopes) to be a good direction for both individuals and the
project as a whole. And to answer some of the "wait, what is this
about?" in order to not misconstrue things I would point anyone at the
list archives of the last few months for how things have finally reached
this point, but it's been a much longer running problem.

-- 
Tom

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

      parent reply	other threads:[~2025-01-16  1:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 16:13 Simon Glass's future with Das U-Boot project? Tom Rini
2025-01-08 13:53 ` Ilias Apalodimas
2025-01-10 15:50   ` Michael Nazzareno Trimarchi
2025-01-10 16:45     ` Alex Kiernan
2025-01-15 16:53 ` Quentin Schulz
2025-01-16  1:19 ` Tom Rini [this message]

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=20250116011906.GF3476@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.