On Sat, 2023-07-08 at 04:54 +0100, Matthew Wilcox wrote: > On Fri, Jul 07, 2023 at 12:26:19PM -0400, James Bottomley wrote: > > On Fri, 2023-07-07 at 05:18 -0400, Kent Overstreet wrote: > > > Christain, the hostility I'm reading is in your steady passive > > > aggressive accusations, and your patronizing attitude. It's not > > > professional, and it's not called for. > > > > Can you not see that saying this is a huge red flag? With you > > every disagreement becomes, as Josef said, "a hill to die on" and > > you then feel entitled to indulge in ad hominem attacks, like this, > > or be dismissive or try to bury whoever raised the objection in > > technical minutiae in the hope you can demonstrate you have a > > better grasp of the details than they do and therefore their > > observation shouldn't count. > > > > One of a maintainer's jobs is to nurture and build a community and > > that's especially important at the inclusion of a new feature. > > What we've seen from you implies you'd build a community of little > > Kents (basically an echo chamber of people who agree with you) and > > use them as a platform to attack any area of the kernel you didn't > > agree with technically (which, apparently, would be most of block > > and vfs with a bit of mm thrown in), leading to huge divisions and > > infighting. Anyone who had the slightest disagreement with you > > would be out and would likely behave in the same way you do now > > leading to internal community schisms and more fighting on the > > lists. > > > > We've spent years trying to improve the lists and make the > > community welcoming. However technically brilliant a new feature > > is, it can't come with this sort of potential for community and > > reputational damage. > > I don't think the lists are any better, tbh. Yes, the LF has done a > great job of telling people not to use "bad words" any more. But > people are still arseholes to each other. I don't think the LF has done much actively on the lists ... we've been trying to self police. > They're just more subtle about it now. I'm not going to enumerate > the ways because that's pointless. Well, we can agree to differ since this isn't relevant to the main argument. > Consider this thread from Kent's point of view. He's worked for > years on bcachefs. Now he's asking "What needs to happen to get this > merged?" And instead of getting a clear answer as to the technical > pieces that need to get fixed, various people are taking the > opportunity to tell him he's a Bad Person. And when he reacts to > that, this is taken as more evidence that he's a Bad Person, rather > than being a person who is in a stressful situation (Limbo? > Purgatory?) who is perhaps not reacting in the most constructive way. That's a bit of a straw man: I never said or implied "bad person". I gave two examples, one from direct list interaction and one quoted from Kent of what I consider to be red flags behaviours on behalf of a maintainer. > I don't think Kent is particularly worse as a fellow developer than > you or I or Jens, Greg, Al, Darrick, Dave, Dave, Dave, Dave, Josef or > Brian. I don't believe any of us have been unable to work with a fairly prolific contributor for 15 years ... > There are some social things which are a concern to me. There's no > obvious #2 or #3 to step in if Kent does get hit by the proverbial > bus, but that's been discussed elsewhere in the thread. Actually, I don't think this is a problem: a new feature has no users and having no users, it doesn't matter if it loses its only maintainer because it can be excised without anyone really noticing. The bus problem (or more accurately xkcd 2347 problem) commonly applies to a project with a lot of users but an anaemic developer community, which is a thing that can be grown to but doesn't happen ab initio. The ordinary course for a kernel feature is single developer; hobby project (small community of users as developers); and eventually a non technical user community. Usually the hobby project phase grows enough interested developers to ensure a fairly healthy developer community by the time it actually acquires non developer users (and quite a few of our features never actually get out of the hobby project phase). James
