The first one always takes way longer than the code itself deserves. Most of the work is figuring out the unwritten rules, not writing the patch.

fooker 3 hours ago | parent | next [-]

This is a big problem in open source that seems taboo to discuss.

In my opinion, unwritten rules are for gatekeeping. And if a new person follows all the unwritten rules, magically there's no one willing to review.

I think this is how large BFDL-style open source projects slowly become less and less relevant over the next few decades.

	▲	cromka 3 hours ago \| parent \| next [-]
		Agreed. The level of aggressive gatekeepers is just crazy, take Linux ARM mailing list for example. I found the Central and Eastern Europeans particularly aggressive there and I'm saying this as on myself. They sure do like to feel special there, with very little soft skills.
	▲	tossandthrow an hour ago \| parent \| prev \| next [-]
		This will likely be alleviated when Ai first projects take over as important OSS projects. Fir these projects everything "tribal" has to be explicitly codified. On a more general note: this is likely going to have a rather big impact on software in general - the "engineer to company can not afford to loose" is likely loosing their moat entirely.
	▲	2 hours ago \| parent \| prev [-]
		[deleted]

yu3zhou4 3 hours ago | parent | prev | next [-]

Can confirm that it also happens in other complex systems! Still a lot of good time and the novelty factor helps with pushing through

seb1204 3 hours ago | parent | prev [-]

Sand that after so many years these rules are still not written down.