On Fri, Jan 10, 2025 at 3:51 PM Michael Nazzareno Trimarchi <mich...@amarulasolutions.com> wrote: > > Hi > > On Wed, Jan 8, 2025 at 2:54 PM Ilias Apalodimas <ilias.apalodi...@linaro.org> > wrote: > > > > 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 > > > > I have some private fork of the project and have some project that > implements > some features that are still not in the mainline. I think that forking > u-boot in general > is not a good idea.
This (with honourable exceptions) is the SoC vendor model - in my current world I'm stuck on 2015 U-Boot for goodness sake... forking it is a terrible idea. > > > 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. > > > > Me too. I don't have that time and for the moment how the project is > progressive is fine. > Sitting on the sidelines mostly these days, when I dip in, then realising that I spent time reading a thread which isn't on code which is heading towards the mainline, is at best annoying and frankly a waste of time. -- Alex Kiernan
