cketti
Dear open source users,
If the author of your favorite open source app has announced they stopped developing and supporting the app (because they're frustrated and possibly burned out), please don't suggest they do more free work so that you can continue using the app.
Instead, consider thanking them for their past work and let them know that you enjoyed their app.
Regards,
another open source developer
Thomas Cloer πͺπΊ πΊπ¦
@cketti I have just done that via https://contact.faircode.eu/
Jeff MacKinnon
@cketti I would expand that the reason is immaterial. I started building a theme that is open source for pelican, but if I stop developing it because I found a new shiny thing, that is my prerogative.
The fact that anyone develops these amazing tools because they want to do something good/cool/etc is amazing and gives me faith that there are good in people.
I miss the late web 1/early web 2 era where I felt there was more good on the web.
Santa Claes πΈπͺππ°π
ArneBab
@clacke @cketti The post should rather be:
"Thank you very much for maintaining such a great app for so long. You have made my life better. I wish you good luck on the new path you chose. π"
Santa Claes πΈπͺππ°π
Santa Claes πΈπͺππ°π
Martin Owens
@cketti we are not good at getting the users of our software to become contributors to our software through our own material wellbeing.
You've heard of "if you're not paying you're the product".
In Foss it's "If you're not paying, you're the user" :knitting:
cketti
@cobra I'm glad to learn that you're focusing on the important part of the message π
The Cobra
@cketti
i would listen to you but you said 'open source' and free as in 0 cost
--hj
ashwansr
@cketti
Huge thanks to #M66B for all his work at the same time its so sad to see such a wonderful project going into peril. But, its totally understandable that the devs also need to make a living despite of how noble their cause is.
Csepp π©Έ
@cketti @z428 To clarify, the situation described in the OP is bad, I agree, having users shout insults at a burned out dev is bad and it should avoided.
But there are multiple ways to avoid it.
Csepp π©Έ
@cketti @z428
This isn't an all-or-nothing problem by the way. There are a lot more options than just "enterprise level support" and "project developed for the lulz and abandoned out of the blue".
Like, if the dev is burning out, they can communicate that before they completely give up on the project.
Csepp π©Έ
@cketti @z428 Well, it has a bit more layers than that. First, the user might not be aware of the risks. The license is not enough IMHO, after a certain adoption threshold, if the readme doesn't communicate the (lack of) support or stability, then the fault partially lies with the project lead(s).
It's like feeding birds. If they get used to it and then you take away the bird feeder on a whim, it's not the bird's fault. Obviously that's an exaggeration, but hopefully you get what I mean.
cketti
@csepp @z428 That sounds like a problem of the people depending on the software, rather than that of the original developer. You can't expect enterprise-level support for having paid 5 bucks (or nothing at all).
Kristian
@cketti Yes. And also: If the tool they built mattered to you, maybe not just move along trying to look for "another alternative" but actually trying to figure out how to keep that alive, how to revive, fork, maintain, fund, ... a process that keeps this project from fading away because the lead developer had to pull out of it? In the end, a lot of this current dispute feels much more like consumerism than real "FLOSS community". π
Csepp π©Έ
@z428 @cketti The harsh reality is that people might depend on the software, so indeed in that case just saying "thanks" and moving on is not the best option. Someone has to pick up the mantle.
Csepp π©Έ
@cketti @z428
Adding a simple sentence to a readme is not a lot of effort. π€·
Nor is writing a short "hey i'm having difficulties, don't expect a new release any time soon".
And no, that's not why I'm asking. *I* understand software development. A random person who downloads [insert software name] from a repo (or even from an official project page) might not. I hoped that was clear.
Devs and users alike are not exempt from societal norms or having to communicate and listen.
Csepp π©Έ
@cketti @z428
IMHO preventing contributor burnout is a more important problem than treating it after it already happened, simply because prevention is nearly always the better solution to any given problem.
If the dev feels like they are expected to do free work, they can lessen the expectation by telling their users they can't work on the project, instead of working on the project until they burn out.
cketti
> That only reinforces that issues should be communicated in advance, whatever their nature may be.
You're asking for people who already basically work for free to do even more work, so that you aren't inconvenienced too much.
I'd say you can certainly hope for that, but you shouldn't expect it, much less demand it.
Csepp π©Έ
@cketti @z428
Re:
> that's on you
I find that assigning blame is less useful than trying to figure out how to avoid the problem. π€·
No one claimed anyone is being tricked, the point I was trying to make (maybe badly), is that it's possible to communicate issues in advance, before they pile up.
And yup, it's not specific to FOSS, all projects should be transparent about their sustainability. That only reinforces that issues should be communicated in advance, whatever their nature may be.
cketti
@csepp @z428 Developers generally don't trick people into depending on their software. If you do depend on it, that was your choice. If you didn't foresee that the software might be abandoned at some point, that's on you. Really, that's not specific to FOSS at all.
But with open source software you at least still have the source code and can continue development (or pay someone to do it for you).
Csepp π©Έ
@cketti @z428
Also maybe I underestimate people, but I don't think developers have a clear perspective on how well regular folks understand how software projects are developed.
Realistically, just complaining about their lack of understanding won't make most of them understand. The most effective way to make this information reach them is via the channels where they read about updates and docs.
Chirp! is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Chirp! content and data are available under the Creative Commons Attribution 3.0 license.