this post was submitted on 08 Dec 2023
243 points (99.2% liked)
Fediverse
28216 readers
168 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I thought this was one of the points of open source.
"Yeah, I'm done with this. I'm not making any more changes from what it is today. If you find value in continuing it, here's the code. Go wild!"
Yes, but if you're lucky maybe 1 in 100,000 users will be both capable and willing to take up the reins. More often than not, when single (principal) developer projects lose its single developer the project just goes into code rot. ASF maintains tons of projects that are too valuable to lose completely but which have no one doing active development on them. It's a problem.
Its a DIFFERENT problem.
OP is talking about never creating because of fear of maintaining. How many good ideas have never come to anything because of this idea?
So? You as the original developer actively wanted to get away from it, don't care what happens to it afterwards.
I've never not cared about my code. And If I didn't care about users depending on it I'd feel like a monster.
I love the way of describing Free Software. Paraphrasing and I don't recall the source: "Not free as in speech or free as in beer. Free as in puppies." You can get a puppy for free but then you have to take care of it all the time, and it incurs costs like vet visits. Free Software can be the same way.
This. Nothing is more difficult than understanding someone's else code and architecture, and even if you manage that, you're now stucked with the choices somebody else made and nobody wants that (we want to make our terrible choices!).
More than a final app, the best thing to publish as FOSS is libraries extracted from it to help other developers build there own products faster. That's something other may want to maintain when we abandon it. And on top of that, it still help to publish your app using this lib to serve as practical example about how to use your it, of course.
Not sure what ASF is (something Software Foundation?) but sounds like they are a solution and not a problem
Apache. The problem is there is foundational software in the world that is aging and not being actively maintained. Basically they jump into action when someone catches a security issue, but also that way too many of those security issues only get found when they're being actively exploited. Even if it's being used by your bank.
I recall reading about a university ?compsci? lab where the professor who leads it assigns her students to examine priority dependency chains. They trace everything back and report on who is maintaining various upstream packages, and identify situations where it is like just one person or otherwise really vulnerable. Then they have some sort of institutional resources to offer that person support and add extra hands to the workflow. So it is more proactive than what you are describing in that they are going out and looking for things that could be problems, not just awaiting a disastrous exploit and patching it up after the fact.
But it's just some small group somewhere. On the main I think we agree on the deficit of support for FLOSS components and applications that functionally run the whole world. It's so crazy but invisible. I am not a developer, just a fan of developers and their work. Most people I know IRL are not developers. Everyone thinks the software on their phone works because Apple and Google pay engineers to build everything. They don't know about all the FLOSS components to the phone, the services it uses, the network etc, and how so many bits and pieces are maintained in part or in whole by volunteers on their free time.
Remember when the boat got stuck in the panama canal and everyone was suddenly interested in supply chains? I forsee/fear the event that prompts the whole world to learn about dependency chains.
Relevant xkcd
That was the Suez Canal lol
yes axactly
omg i stand corrected
https://en.wikipedia.org/wiki/2021_Suez_Canal_obstruction
also it only lasted 1 week?? i felt like it was 9 months long
TODO: read the wikipedia beyond the introduction
I can think of only one concrete example where the lead dev walked away - rightfully IIRC - and the community was able to pick it up, fork it, and actually maintain and continue to develop new features.
Sadly, that’s not often the case.
I think youtube-dl had a situation like that, now yt-dlp. (except I don't know if the original dev's status is confirmed?)
also exa, now forked to eza. My impression is for this case, the original dev is OK.
But honestly I have encountered lots of software packages which have been dropped and picked up in this way. Man pages can contain history like this, occasionally going back to the 80s or even 70s for the basics. The main problem is that the original software package is so well known and sometimes it's hard to find out about the newer iterations so they have a difficult time picking up steam. I used to have a bookmarklet that would show forks on github sorted by activity; occasionally this allowed finding the more recently-developed project. But more likely you have to wait to stumble on it in a forum.