7 ms·
> I will block discussions here now, since I don't think we need the input from the script kiddie peanut gallery here. How not to interact with your community
by falcolas 6y ago
> I will block discussions here now, since I don't think we need the input from the script kiddie peanut gallery here.
How not to interact with your community 101.
Defaults matter, because even if they are changeable via a build-time flag, most of the time they won't (how many people knew this was a default before now?)
- threatofrain 6y agoThis isn't something normally set by the end-user but by vendors, and I do presume that distro teams absolutely have enough opinion and energy to set DNS defaults.
- raverbashing 6y agoDoes it matter now (that the maintainers can't dialogue with the community)? In one side major linux distros took in systemd (as, ok, granted, the "less worse" of the options) so the point is moot. I mean everybody should know how LPs management of the project works. At the same time I can understand trying to cut down on drama in online discussions (though I agree that default might make more sense as a run-time configurable, not as a build-time one). (And yes defaults are important)
- falcolas 6y agoSystemd being the default init system in the distro, and google being a default resolver in systemd, are separate issues. Yes, it does matter. It's being pushed out as the init system for a lot of linux systems, and I believe it's perfectly reasonable to expect that your fallback DNS resolver is not set to a for-profit data-collection organization.
- yadco 6y agoWhoever knows how to build systemd should know about this build-time flag
- falcolas 6y agoI have to picture that systemd has hundreds, if not thousands, of build time flags. Is it reasonable to expect all non-systemd builders to grok every flag? My opinion is that it is not - that pushing it back on the individual distros is a cop out on Red Hat's side. EDIT: 172 distinct build-time options, in today's master. Not all appear to be used as part of the build, since the build script only references 142 of the options set in meson_options.txt.
- ckastner 6y agosystemd plays a crucial role on systems that use it. Whoever builds systemd for a distribution should definitely be aware of those flags; if you don’t understand them, then you are not qualified sufficiently to ship systemd for others to use. Edit: Speaking as a package maintainer myself.
- falcolas 6y agoHow many packages do you, as a package maintainer, maintain? Can you say with high confidence that you are aware of all of the flags offered by all of those packages, including changes to the defaults between package releases? I expect that package maintainers are human, and put a fair bit of trust in the upstream developers, and will only tinker with build flags for issues which are specific to the distro. I also expect that they will miss changes to defaults, or new flags, or deprecated flags, quite often. I looked at the systemd defaults to see this issue for myself, and the fact that Google's nameservers are in the DNS defaults didn't immediately pop out to me (it's a list of 8 mixed IPv4 and IPv6 addresses).
- ckastner 6y ago> How many packages do you, as a package maintainer, maintain? Can you say with high confidence that you are aware of all of the flags offered by all of those packages, including changes to the defaults between package releases? Absolutely. For a responsible package maintainer, reading changelogs and release notes of new releases is a must. For sensitive software (eg: key system libraries), I usually also look at the full diff between releases. I also run tests with dependent software before uploading my version, lest I break any packages that depend on mine. etc. And this is quite typical of your average distribution package maintainer.
- packetlost 6y agoDefaults matter, but he's right to say each distro should be the ones setting the default. Most people aren't compiling systemd themselves, they're using the one compiled by their distro maintainer(s). I don't think this is anything to worry about and he's right to shut out pointless conversation from people who misunderstand the actual situation. Accusations of being paid by Google (or any other entity) is ludicrous and can easily be interpreted as insulting too.
- vonmoltke 6y ago> Defaults matter, but he's right to say each distro should be the ones setting the default. Most people aren't compiling systemd themselves, they're using the one compiled by their distro maintainer(s). In that case, the final comment in the discussion is correct: systemd itself should not have a default, and should require the distro maintainer to explicitly set these values to whatever default they want to use.
- packetlost 6y agoI'm inclined to agree, though without being familiar with systemd's codebase and infrastructure, there may be technical reasons why that hasn't been done
- djsumdog 6y agoI agree. There shouldn't be any hardcoded DNS/NTP fallbacks. I don't use systemd on any of my personal systems or my dedicated server (Gentoo/Void), so I don't have to worry about this. But on my Ubuntu VMs, I guess there's a fallback DNS/NTP in my startup process I never knew about. I agree. The default should be set (and required; without defaults) by the distro maintainers downstream. Just leave them out here.
- Kaze404 6y agoThere were no accusations. Someone asked a fair question. The maintainer clearly overreacted.
- 6y ago
- megous 6y ago> (how many people knew this was a default before now?) Pretty much everyone who ever opened /etc/systemd/resolved.conf
- munchbunny 6y agoPretty much everyone who ever opened /etc/systemd/resolved.conf That's a vanishingly small percentage of people who use systemd.
- megous 6y agoPerhaps, but still larger than the set of people who compile their own systemd builds. Also it's the answer to the question. The defaults are visible in config files as commented out lines. No need to check build scripts, etc.
- falcolas 6y agoDid you know that there are at least four different file locations that resolvers can be set in for systemd-resolved? The defaults being in a commented-out section in one of these four locations (and in a file whose name does not match the linux standard of resolv.conf) is, frankly, not a big help in identifying what's really being used. https://jlk.fjfi.cvut.cz/arch/manpages/man/systemd-resolved.8#%2FETC%2FRESOLV.CONF https://jlk.fjfi.cvut.cz/arch/manpages/man/systemd-resolved....
- akerro 6y agoThis is why Linux and SystemD will struggle to find maintainers in the future: https://www.theregister.com/2020/06/30/hard_to_find_linux_maintainers_says_torvalds/ https://www.theregister.com/2020/06/30/hard_to_find_linux_ma...
- offbyone 6y agoI'm not sure I agree; Poettering isn't being harsh to his collaborators, here. He's protecting them against the implicit accusation of a hostile community member. I'd be _more_, not less likely to want to work on a project with someone who does that.
- akerro 6y ago>I'm not sure I agree; Poettering isn't being harsh to his collaborators Not accepting any discussion by blocking all community efforts is quite bad imo. Would like still like to start any discussion, put effort into making even smallest change, to be blocked? This is strong sign of ignorance. I often contribute to OSS on gitlab and github. When a single/first MR is not merged OR commented on within a week I don't even try there again, waste of time.
- ocdtrekkie 6y agoIn open source, today's community member is tomorrow's collaborator. If you are a tool to your community members, you will end up getting less new collaborators.
- tomxor 6y ago> How not to interact with your community 101. Maybe, but lowering a discussion to accusations of bribery is also not how to interact with project members.
- falcolas 6y agoNo, it's not. But one person is a paid maintainer for the project, the other an (admittedly paranoid) non-paid user. The standards for a paid employee are (and should be) higher.
- scrollaway 6y agoYou don't get to be an asshole to waiters just because they're "paid" and it's "their job". You don't get to be an asshole to open source maintainers just because they're "paid" and it's "their job". If in either situation, a person is an asshole to the paid employee, said employee most definitely has a right to defend themselves.
- falcolas 6y agoIf a waiter said something like this, they would likely have been fired. What was said was only a bit rude, not even remotely abusive, and hardly justifies the attitude expressed towards the community as a whole (the so-called "script kiddy peanut gallery").
- scrollaway 6y agoIf a waiter said something like this to a client being an asshole, some restaurants may fire them if the client is "important" enough, primarily because waiters are easily replaced. But nowadays, a lot of restaurants will side with the waiter on such issues and they're damn right to do so. I'll add that what you're seeing here is but the tip of the iceberg of abuse that Lennart has to deal with every day. I challenge you to put up with 1/100th of what he's putting up with without "raising your voice" or what have you.
- theevilsharpie 6y ago> How _not_ to interact with your community 101. On the contrary, I think he handled it perfectly. I've become exhausted with most discussions on social media, because conversations frequently get hijacked by loud people with strong opinions that don't express them in good faith. Without strict moderation, it can become impossible to have a rational discussion on certain topics. For example, pretty much anything on HN involving Google devolves into worthless noise. In the case discussed in the OP, Poettering clearly has no intention of changing the default configuration (at least based on the reasons given in the issue), and has provided a way of modifying the configuration for those that care enough to change it. There's no value in further debate, and closing the issue to further discussion keeps Poettering and other contributors from getting distracted/burned out by unproductive conversation. If people don't like it, they're free to fork Systemd or start up their own competing software project, and then they can handle community interaction for their own project in whatever way suits them. Frankly, I wish more discussion were handled this efficiently.
- KaiserPro 6y agoIts not really efficiently. Something like: "we've discussed this a number of times, see #12345" closing now would have closed the ticket and not made the front page. By being a top draw dick about it (when the originator was at least being earnest) the debate rolls on. He had given a full answer, he could have left it there, but chose not to. its this kind of "rock star" and cheerleaders that give IT a bad smell.
- bad_user 6y agoAre you talking about the comment that closed the ticket [1]? Are we not seeing the same thing, because that's not a "top draw dick" I'm seeing. He was perfectly reasonable. And I don't know if you've ever managed any popular open source projects, however it's best to close tickets fast instead of letting them linger on, especially when you have over 1000 opened issues and especially if, as a maintainer, you know that you won't change your mind about that issue. Then he got accused of being funded by Google. He actually showed restraint. [1] https://github.com/systemd/systemd/issues/12499#issuecomment-490057558 https://github.com/systemd/systemd/issues/12499#issuecomment...
- michaelcampbell 6y agoPoettering being insulting and smug? Who'd've guessed.
- hedora 6y agoAlso, “work with your downstream” rings hollow coming from a RedHat employee. Anyway, per his advice, here is how I worked with my Linux distribution to fix the problem: I switched away, and donated to ones that don’t use systemd.
- joana035 6y ago> How not to interact with your community 101. Give Poettering a break! You have no clue what is to be in his shoes. ;)
- nimbius 6y agobingo. Since the early days of pulseaudio Pottering has been an absolute wet towel when it comes to technical discussions or dissenting opinions. systemd is becoming a boondoggle of esoteric crap that nobody asked for. Binary logs that are a pain to ship to a central server, home directory management, and now corporate US servers as defaults for new users to fall back on because "well gosh google devs dont work on my project so everything is okay" is just inexcusable hand-waving. part of open source is collaboration. If you cant defend what was clearly your personal decision on technical merit, then it needs to be reconsidered. whiners get forks.
- tobyhinloopen 6y agoIt was called for. The commenters were pretty toxic IMO.
- Hnrobert42 6y agoYeah. That was very rude. I’d heard the systemd developers severely lack social skills. The way he went from 0 - EXASPERATED was surprising and uncalled for.
- offbyone 6y agoAlmost as if he'd been the target of a nearly-non-stop decade of constant hostility and abuse or something.
- finnthehuman 6y agoLennart is not that good at the human-facing parts of maintainership. That's fine, he doesn't have to be. I'm just surprised that people don't see how his communication style (in general and in the linked thread) makes interactions harder than it needs to be for himself and everyone involved.