|
|
Log in / Subscribe / Register

The Grumpy Editor's guide to surviving the systemd debate

The Grumpy Editor's guide to surviving the systemd debate

Posted Nov 13, 2014 17:57 UTC (Thu) by marcH (subscriber, #57642)
Parent article: The Grumpy Editor's guide to surviving the systemd debate

> Avoiding "not our problem" responses when things break would be helpful.

Very much indeed: there are so many nicer ways to answer the same thing. Starting with: "Sorry, that was not expected - however it's not on our priority list". Actually having a "lowest" priority value in the bug tracker for bugs that are never looked at and closed after a few months once the reporter has moved on. Costs little, does a lot of good. Having a personal or enforced rate-limiter on emails and bug trackers to avoid impulse responses. Etc.

By generating less inflammatory responses and hate mail this also saves a lot of noise, stress and time.

I think it's difficult but possible to be an engineer and a human being at the same time :-)


to post comments

The Grumpy Editor's guide to surviving the systemd debate

Posted Nov 13, 2014 18:35 UTC (Thu) by pflugstad (subscriber, #224) [Link]

> I think it's difficult but possible to be an engineer and a human being at the same time :-)

QotW nomination here :-)


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds