this post was submitted on 01 Nov 2023
70 points (100.0% liked)

Free and Open Source Software

17937 readers
97 users here now

If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 52 points 1 year ago (10 children)

I did maintain an opensource project for a while and that taught me how to do it correctly:

  • Don't. Just don't.
  • If you really, really want to, just do what you need to fulfill your needs, never do something for someone else.
  • If someone is really insistent, say you'll do it if that person pays for the implementation of the feature, and use your day job's hourly rate for it.
  • Then don't implement anything you don't want to, because nobody is going to pay for it anyway.

Or to put it differently: Never see your project or contribution as anything more than a hobby. You will never see an return on investment.

[–] [email protected] 2 points 1 year ago (1 children)

As I understood it, one of the foundations of open source development is scratching your own itches, then putting what you made up for grabs in case it scratches someone else's. There shouldn't be any expectation of support on your part beyond an email or two. The code's out there if they want to scratch the itch a different way. It's kind of a homesteader ethic.

[–] [email protected] 1 points 1 year ago (1 children)

That's basically right. But it's quite a difference what you have to do to scratch your itch, and what you need to do for it to be useful for others.

If you do it for yourself, there are no tests or documentation or even a GUI. It's quick and dirty, all configuration is hardcoded. If you need a different config, you'll just change the code.

All that doesn't really fly if you expect someone else to use the project.

On the other side, especially if it's too polished, idiots will perceive the project as being a commercial one and demand that you do what they want.

If you don't know the stories, maybe read up on the maintainer of core-js or Marcel Bokhorst. These two people complained about how tough it is to make good open source software. Both talked specifically about their toxic audience. So in turn the audience ridiculed them and they even received death threats.

[–] [email protected] 1 points 1 year ago (1 children)

I suppose the thing is, I personally wouldn't care much if anyone else used it or not, my itch has been scratched. If someone else finds it of use, great! If they need changes, they've got the code and can get crackin' on it themselves. Or, they can pay me to do it if we can agree on a price. Outside of that I have no expectations.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

That's definitely a healthy way of dealing with that.

But with this way, something like Linux, Distros, Firefox, Blender or LibreOffice would have never happened. There are those who want to build retail-level open source software, mostly out of idealism, and then you are stuck between a non-monetizable rock and a toxic hard place.

But I totally agree with you, unless you are super idealistic, your way of handling it is probably the most healthy one and the one that will cause you the least amount of trouble. And it's also what I do, except when I sometimes do get idealistic.

[–] [email protected] 1 points 1 year ago (1 children)

I put it to you that ideals may constitute a scratchable itch.

[–] [email protected] 1 points 1 year ago (1 children)

That is true, but then you probably are in trouble ;)

[–] [email protected] 1 points 1 year ago

Depends on how hard you scratch! lol

load more comments (8 replies)