Do you use Open Source projects that have been abandoned for years ?? ๐ง
Do you guys use OSS project that its last commit was 1/2/3/4 years ago ???
I like Open Source project, but sometimes, one of the Open source projects that I love to use/contribute was abandoned for years ๐ โฆ like the last commit was on 2016/2017โฆ last 3-4 years
What's your guy's opinions on this ?? ๐
Yes we do. One of our big product called Quix(page builder) use a state manager lib that is dead very long ago. But due to its complexity and we've made workaround we never migrated to another lib. its been 4y now :)
If it ain't broken don't change ;)
awesome, now I would consider the old repo if it still works ;pโฆ Thanks for sharing experience ๐
Nah. I always check last commit date < six months.
coolโฆ same as me at firstโฆ But, sometimes I look through all the file && code on that repo, if the logic part understandable, I choose them.. hahaโฆ Thanks for sharing ๐
Some open source projects are perfect and don't need many updates. If the code looks good and it is understandable then why not. Especially if it's a small focused library.
I guess it depends on how many open issues or open PRs there might be. But if it's a seriously useful project then it might be worth forking and applying the PRs yourself, and trying to create a new open source fork that makes some progress.
yeah, same as I did. Look on issues, pr, and the logic partโฆ if it still works, I will fork itโฆ. good answer, thanks @foucist
Yes, sadly I do: I think one of my favorite pieces of software, Telepot for Python, hasn't been maintained in monthsโฆ
I do, as long as it works or as long as I can find a way to make it work, then all's good!
I tend to stay clear because even if it has reached maturity, it might have vulnerabilities that have gone unchecked and I don't want to introduce those into my code.
@nblackburn That's a good point that I don't see anyone raised. Vulnerabilities are very real issues.
Depends - if it is a library then it might be feature complete with the original goals. So that is totally fine. Of course you need to be careful if the lib can not be ported to current version of the language, as it might then miss security fixes in the ecosystem.
For full fledged software, like CMS, I would like new shinny stuff.
Mostly I avoid a project if its not maintained for long time. But if there is no alternative then I check for any forks which are maintained by someone else.
In most cases the original author gets busy and prs/issues remain pending. But if some individual/company's code base depends upon that project, then they usually maintain it in their fork.
Please sign in to leave a comment.