That's the dark side of open source. Companies think these projects grow on trees and they use them without paying anything. We need law changes to ensure that open source can be sustainable and companies pay the fair share of revenue they make by using it.
> We need law changes to ensure that open source can be sustainable and companies pay the fair share of revenue they make by using it. We don't need more laws. There is something called a License Agreement. However if you publish your stuff on GPL and other permissive licenses you can't really complain about Amazon, Google and Microsoft making millions on your code while you beg for donations on your Github page.
Sorry everybody, I failed with you
41–50 of 357 posts
Re: Sorry everybody, I failed with you
#42Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…
It is particularly apparent in schools. Students start something, then they graduate and do something else. Most of the times, no one takes over, at least not in a sustainable way.
It is not always the case, but it is the most common outcome. Simply, I think there are simply more people who want to start something than there are people who want to lead somebody else's project.
Re: Sorry everybody, I failed with you
#43> ...People want a lot of things from you and your project, big companies are using the project and need a lot of things as well from it in order to keep their projects healthy, but in most of the cases this is a talk in just one way. There are more people interest in have things from you, than help! And this crashed me If they are all users of your open source software and are begging for features for free, ignore t…
We don't know how much pay/sponsorship was the issue here. It seems to me that the maintainer was simply overworked and slept very, very little. This is bearable for a certain amount of time but after that one really has to look after themselves, regardless of financial interests or a crash is inevitable.
Either way, no developer wants to do free work on someone else's deadline and it is always done in their own time, unless they want to pay for the effort.
Re: Sorry everybody, I failed with you
#44Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…
I've seen lots of these calls for help fail.
And someone else points out: It's open source. Literally anyone can continue the work at any time. There's no need for the original creator to find someone else to continue it. Anyone can just do it.
Re: Sorry everybody, I failed with you
#45Earlier quoted context omitted.
How about the insane entitlement that many devs have when it comes to open source? Getting bombarded with requests and angry emails from people who demand free support and bug fixes can burn anyone out. I think Github can be a positive force for change here. Redesign the UI to encourage donations, to encourage people to get involved in project work, to write less hostile issues, etc. If devs and designers can weaponi…
I wonder if this is a back-firing of the push for people to be "nice" and "professional". Open source maintainers used to have the sterotype of being rather harsh, and basically telling people to f off if they had stupid questions, didn't RTFM or didn't follow cultural norms. And dont get me wrong, there's a lot wrong with that, but maybe it was also that way for a reason.
I'm sure they lose a good amount of potential contributers that way. But the few newcomers that remain are highly motivated.
Re: Sorry everybody, I failed with you
#46Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…
"I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work?" I've seen lots of these calls for help fail. And someone else points out: It's open source. Literally anyone can continue the work at any time. There's no need for the original creator to find someone else to continue it. Anyone can just do it.
Re: Sorry everybody, I failed with you
#47That's the dark side of open source. Companies think these projects grow on trees and they use them without paying anything. We need law changes to ensure that open source can be sustainable and companies pay the fair share of revenue they make by using it.
The point of open source is people can use it freely. A better project, which hits the right spots will naturally attract financial and technical support, both from the companies and the community. It is really just a free market, where the best projects survive.
OpenSSL has only recently received support despite powering all the Internet infrastructure for decades.
Xorg, xterm etc. have received very little or nothing. Same for most Unix system tools.
Projects that receive the most are "open" source corporate vanity projects that are also used for bait-and-switch hiring.
Re: Sorry everybody, I failed with you
#48Of course it's terrible to become burnt out and it feels awful not having enough time to work on an open source project that you love. But, is it just me or has it become rarer for open source project maintainers to feel free to let projects go? I don't mean to let them die, I mean, to find like-minded individuals to which you can defer some or all of the work? I realize that as the original author one feels a sense…
There are few projects that actually get used for longer than a couple years at most, the churn (especially in JS projects) is massive. You'll always find people to work on Big Old Stuff that's used everywhere - think Linux kernel, Qt/KDE, Gnome, Firefox, Thunderbird, libc, gcc, LLVM, jQuery, ReactJS - but the small stuff that gets disrupted ehhh replaced by some shinier newer toy? That will eventually diminish and die off, when the original author either has all their needs met, burns out or no longer needs the project.
Additionally, all of the above projects have massive financial firepower and/or other institutional backing behind them that contributes either with direct man hours or financial grants.
Re: Sorry everybody, I failed with you
#49Earlier quoted context omitted.
There's really something to be said for software that is so ruthlessly simple it runs forever without maintenance. Like most of what DJB has written: djbdns still works after all these years... And of course Knuth's TeX. Maybe people shouldn't start software projects if there isn't a "can leave it here unmaintained" milestone within sight.
> Maybe people shouldn't start software projects if there isn't a "can leave it here unmaintained" milestone within sight. It's because these projects have tons of dependencies and moving parts which tend to break themselves (often for very little reasons) so of course it's going to affect upstream. The software you listed are usually mostly self-contained or rely on stable projects. There is no such thing as "stabil…
Nodejs is the new Java jar dependency hell.
Maybe package the entire project into a docker container so that people can download and run the pile of dependencies in one step.
Re: Sorry everybody, I failed with you
#50Earlier quoted context omitted.
The thing is, if the new project maintainers go against the community, but the community really need to use it, the community will just fork out a new path and move on. If the project is really open source.
I don’t think that really happens, anymore. Twenty years ago, they would have done that, but these days, someone would just write a replacement from scratch (quite possibly, proprietary), or everyone would abandon it, along with their own projects that depend on it. Most open-source (and closed-source) APIs and SDKs are “Swiss Army knife” projects, with many functions that serve many purposes. Most API consumers use…
As I have made my point before, if all I want is money I would spend my time working a paying job. But money is not everything isn't it?