From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>
Subject: Re: Simon Glass's future with Das U-Boot project?
Date: Wed, 8 Jan 2025 15:53:57 +0200 [thread overview]
Message-ID: <Z36DdfO_EH454Xdw@hera> (raw)
In-Reply-To: <20250102161313.GP3476@bill-the-cat>
Hi Tom,
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
Everyone is entitled to create a fork. But as noted in another mail, he
can't use the public mailing lists asking feedback for his forked patches,
nor can he use the public infra (incl patchwork) to test and maintain his
changes.
> 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.
+1 here. As long as patches get reviewed properly we should follow what the
majority thinks is the proper technical direction.
> 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.
I personally don't want to pay attention to out of tree patches.
Simon randomly responds to emails 'applied to sjg1/master' or something
along those lines, which further complicates things as people might think
their code got merged.
I think we should wait a few more days and give Simon a chance to respond
and perhaps explain what drove him to create his fork.
Regards
/Ilias
>
> --
> Tom
next prev parent reply other threads:[~2025-01-08 13:54 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 [this message]
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
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=Z36DdfO_EH454Xdw@hera \
--to=ilias.apalodimas@linaro.org \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox