> and if this was a bad call they’ll revisit it.

how would they know? - this is (one of) the ways for people to let them know

const_cast a day ago | parent | next [-]

Let's stop bullshitting, nobody here is going to contribute to Gentoo and is now put off because of this policy change.

What we're looking at is mostly JavaScript monkeys who feel personally offended because they're unable to differentiate criticism of their tools from criticism of their own personal character.

The outrage is purely theoretical.

▲

dizlexic a day ago | parent [-]

As a JavaScript monkey I believe you have a point, and this was the core of my original question.

How many contributors to gentoo are upset by this? Probably none.

How many potential contributors to gentoo are upset by this? Maybe dozens?

I'll be amazed if this has any notable negative outcomes for Gentoo and their contributions.

	▲	SAI_Peregrinus a day ago \| parent \| next [-]
		I suspect most of the people upset by this are the sort to dump a pile of unreviewed slop on the maintainers & get upset when it gets rejected, i.e. they're the problem this is aimed at fixing.
	▲	const_cast 20 hours ago \| parent \| prev [-]
		No offense intended to JavaScript monkeys, I'm a JavaScript monkey too. And a PHP monkey, which I think is worse.

▲

joecool1029 2 days ago | parent | prev [-]

It isn't though. This is just noise. It's a good conversation thread for HN, but it has absolutely zero influence on Gentoo policy.

The only way it'll be revisited is if active Gentoo developers and/or contributors really start to push with a justification to get it changed and they agree to revisit discussing it again. I can tell you every maintainer has heard the line: 'I would have contributed if you did X thing'.