Live data from Hacker News

An open-source maintainer's guide to saying “no”

jlowin.dev

91–95 of 95 posts

Re: An open-source maintainer's guide to saying “no”

#91

I’ve had some experience developing an infrastructure-level system for use around the world. I had to maintain it, almost completely alone, for ten years, before it was taken over by a competent team, and I could finally walk away. One of the most important things I did, in that decade, was say “no” a lot. Some folks were not happy about it, and Godwin’s Law was invoked on my ass, multiple times. A lot of requests we…

> Godwin’s Law was invoked on my ass

Can you elaborate?

Re: An open-source maintainer's guide to saying “no”

#92
post #41

Earlier quoted context omitted.

> I had to maintain it, almost completely alone, for ten years, before it was taken over by a competent team, and I could finally walk away. No you didn't. Younger folks reading this, you don't owe anyone free labor. If you want to donate your time to open source that's ok but just know there are thousands of people in this industry that don't care about your mental health and will continue to take advantage of you b…

Sometimes, we do stuff for reasons that folks, these days, can't relate to. I'm truly sorry that you've never had a Cause to which you could dedicate that kind of effort. No one ever "took advantage" of me. I'm actually kind of hard to hoodwink. Yes, I did "have to." If I have to explain, you wouldn't understand.

> If I have to explain, you wouldn't understand.

It's not that I don't agree with you, but this sentence is very strange. It can be used to "support" anything and everything at all.

Re: An open-source maintainer's guide to saying “no”

#93

I’ve had some experience developing an infrastructure-level system for use around the world. I had to maintain it, almost completely alone, for ten years, before it was taken over by a competent team, and I could finally walk away. One of the most important things I did, in that decade, was say “no” a lot. Some folks were not happy about it, and Godwin’s Law was invoked on my ass, multiple times. A lot of requests we…

> Godwin’s Law was invoked on my ass Can you elaborate?

I was called a Nazi.

People can get pretty upset, when you say "no."

Re: An open-source maintainer's guide to saying “no”

#94

Earlier quoted context omitted.

Sometimes, we do stuff for reasons that folks, these days, can't relate to. I'm truly sorry that you've never had a Cause to which you could dedicate that kind of effort. No one ever "took advantage" of me. I'm actually kind of hard to hoodwink. Yes, I did "have to." If I have to explain, you wouldn't understand.

> If I have to explain, you wouldn't understand. It's not that I don't agree with you, but this sentence is very strange. It can be used to "support" anything and everything at all.

But it’s true, nonetheless. I’ve had it said to me, and it applies.

If you are unable to comprehend that people will do something for altruistic or deeply personal reasons, then we live in entirely different worlds, and it’s a waste of time, trying to explain ourselves.

Re: An open-source maintainer's guide to saying “no”

#95
post #87
post #83

Earlier quoted context omitted.

The entire XLibre debacle seems like the most obvious example.

So because the maintainers of Xorg does not want patches that causes regressions Gnome makes people fork projects somehow?

I said

> the freedom to fork is one of the essential freedoms of FOSS. Many people in certain organizations (cough GNOME cough RedHat cough) don't seem to get this."

and you asked for examples. XLibre is a fork (of XOrg); people from GNOME and RedHat have spoken publicly to object to the fact that the fork exists (along with more generally expressing opinions that I find incompatible with my understanding of FOSS). The GitHub for the project has a wiki page (https://github.com/X11Libre/xserver/wiki/Are-We-XLibre-Yet%3...) tracking what Linux distributions do or will include the package; several prominent developers were found (https://github.com/X11Libre/xserver/issues/346) to have defaced this page by referring to the developers in very unkind ways. Among these was Jordan Petridis who is part of GNOME as well as XOrg and wrote extensively about the effort to remove the X11 GNOME session (both on a gnome.org blog and on social media), making many contentious claims about the XLibre developer in the process.

For more, I'd have to put in considerable time collating information, or else you'd have to follow sources that I have found are better not to mention in places like HN because doing so would attract too much drama. But I only make comments like these on the basis of what I can independently verify.

Post reply on HN