Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it 'hilariously pointless' in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.
I care. One thing is “you know, fields with this name have been around since before you were born”, another thing is “some idiots passed the law half the globe away, now we are preparing your system to comply. Someone has to ©”. The field is not the danger, the thinking, attitude and act is
Edit: some local law, for fuck’s sake
Half a world away where do you live since this is happening everywhere. To be half a world away from any place doing this would be hard.
Being half a world away from Americas is pretty easy, don’t ya think?
That’s a fair argument.
Is it fair to say: The field is benign but there is contention about if it should be added or not and users of the software are concerned that their voices were not heard on the issue. That can be handled in the normal project framework, perhaps by suggesting a publicly stated policy about these issues around legal compliance so the community can determine if they want to support the project or not.
My argument is that I don’t think that the damage that was done justifies the hitpiece in the OP which is, almost literally, painting a target on the developer with the mugshot photograph and loaded language.
So, if you’re not one of the people then we’re having different conversations. In that conversation, I do agree with what you just said. I’d like to see the very large projects, which affect a lot of users, such as systemd, have a more formal way to accept public comment and respond on contentious changes and feature requests.
To be fair, I am bit split on this. On one hand, name and shame is an effective strategy and should be used. On the other hand, “put age verification into Linux” is a hilarious stretch. And yes, it feels strange that I have yet to see any kind of response from other systemd maintainers and managers - after all, the man authored a pull-request, not merged into into upstream. I have not been looking for that kind of response myself though, which also serves your point: putting all the blame and anger on this one man (I purposefully omit name) is too much
It is benign if it is optional, remains 100% local and under the user’s control and doesn’t prevent other software from functioning as expected.