Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We are the "thin blue line" that is trying to keep the code high quality

lore.kernel.org

Post reply on HN
Print view View original

41–50 of 186 posts

Re: We are the "thin blue line" that is trying to keep the code high quality

#41

Post by layer8 »

Diggsey wrote: post #30
jf wrote: post #27

> One of the things which gets very frustrating from the maintainer's perspective is development teams that are only interested in their pet feature, and we know , through very bitter experience, that 95+% of the time, once the code is accepted, the engineers which contribute the code will disappear, never to be seen again. This was painful for me to read as someone who has seen how corporations think about “Open Sou…

He's not wrong, but he hasn't addressed the problem: Some maintainers are rejecting changes as a way to block a project they disagree with - ie. there is no path forward for the contributor. I wouldn't assume this normally, but they're not hiding this fact, it's self proclaimed. On the other hand, Linus has been largely in favour of the R4L project, and gave the green light for it to go ahead. The Linux kernel mainta…

IIRC Linus has been in favor conditioned on the agreement of the respective subsystem maintainers. Meaning, he’s not deciding over their heads. And introduction of Rust can be handled differently from subsystem to subsystem.

Re: We are the "thin blue line" that is trying to keep the code high quality

#42

Post by paulddraper »

foxes wrote: post #4

Calling yourself the “thin blue line” like a reference to police really doesn’t seem like a way to have an enduring community. Police don’t serve the community; I guess they think in the same way then.

> Police don’t serve the community

Whom do they serve?

Re: We are the "thin blue line" that is trying to keep the code high quality

#43

Post by tdb7893 »

milesrout wrote: post #35
adastra22 wrote: post #18

Earlier quoted context omitted.

Look into the history and meaning of “thin blue line.” It’s an endorsement of the us vs. them mindset prevalent in American policing that is the source of many (most? all?) police scandals.

It doesn't even originate in the US, mate.

As far as I can tell it probably is American, all the earliest mentions of it on Wikipedia are American.

https://en.m.wikipedia.org/wiki/Thin_blue_line

Re: We are the "thin blue line" that is trying to keep the code high quality

#44

Post by WhyNotHugo »

ysofunny wrote: post #3

why cannot more people learn about git and branching you want your merges in? patch it in your own branch the real crux of the issue is the quality of " the offical version", the real issue, then, is about official branding. I remember back in the day there were multiple kernel versions by different mantainers.... then again I'm probably missing the forest for the trees or something

The kernel is continuously changing (which IMHO is also an issue), so keeping a fork requires a lot of work to continuously adapt to those changes.

This is why forks made for specific devices are seldom updated for more than a few months (or a couple of years if you're very lucky).

Re: We are the "thin blue line" that is trying to keep the code high quality

#45

Post by o11c »

OJFord wrote: post #28
lexandstuff wrote: post #22

Earlier quoted context omitted.

Also, if you're not from the USA, you're more likely to associate it with the beloved Rowan Atkinson sitcom.

Or the non-politically-loaded phrase that the sitcom is named for.

There's a difference between "not politically-loaded decades ago" and "not politically-loaded now".

We still let people use the Swastika if they had a harmless tradition of using it beforetime. But if anybody new uses it, we assume it's because of the murder.

Re: We are the "thin blue line" that is trying to keep the code high quality

#48

Post by forgetfreeman »

Mr_Bees69 wrote: post #24

[flagged]

The burden of proof isn't on maintainers. Recognizing new, untried code invariably means bugs and instability to work through, often for questionable gains, is a mark of an experienced developer. Work your way through enough industry hype cycles and you'll see, new shit just causes new and usually weirder problems than whatever it was intended to replace.

Re: We are the "thin blue line" that is trying to keep the code high quality

#49

Post by sdwr »

foxes wrote: post #4

Calling yourself the “thin blue line” like a reference to police really doesn’t seem like a way to have an enduring community. Police don’t serve the community; I guess they think in the same way then.

Police can serve the community - but people who use the reference "thin blue line" are casting police as combatants rather than public servants.
Post reply on HN