@liw well this is a refreshing take after spending the past few weeks reading internal gnu mailing list threads. thanks for sharing!

@Lars Wirzenius A very nice writeup. This kind of behaviour may have been less of an issue as long as free software remained a small fringe of the ecosystem, but it's definitely about time these issues are being discussed and handled.

@liw Thank you for taking the time to write. This is a very thoughtful post. It gives me hope.

@liw OK I promise from now on to be intolerant of intolerance and bad behaviour !

Great post, thanks :)
I have just one minor nitpick: I consider shirky.com/writings/group_enem as gospel, so I wouldn't characterize some decisions as "technical": it's almost always impossible to draw a clear line between " technical " and "not technical", do you agree?

@nobru Not sure I agree. It's been too long since I read that to debate it, though.

But certainly I'm having a hard time to think of sorting algorithm choice as a non-technical decision, for example.

Yes, there are some purely technical decisions. But think about init systems freedom of choice...

@liw unrelated to the article, but what i do to automate the ikiwiki/comment bridge is to link my RSS feed to masto automatically using feed2exec feed2exec.readthedocs.io/en/st works well!

@anarcat I very strongly don't want to have comments on my blog directly. The fediverse link is an experiment, to see if it results in useful and intereresting discussions.

@liw It's not easy to deal with difficult people without becomng one of them. I think you've nailed it - you don't want to have to deal with these people because they ruin it for everone elese. I like this - I saw it quoted on LWN - because you are consistent and principled - you walked away when it felt wrong for you, even if that meant less contact with the good folk which was a hard decision. Thanks for clear writing about what's right for you without ramming it down other people's throats.

@liw in industry, the user/client has a word to say about bugs, and can refuse deliveries (and thus deny payment to the provider/developer) if some bugs are detected, and are not fixed.
In free software, the provider has too much power compared to users, especially when the developer is not paid by the users. Communities should leverage this by empowering the users.

Sign in to participate in the conversation

Lars and friends