* Ihor Radchenko <[email protected]> [2026-03-15 20:54]: > Jean Louis <[email protected]> writes: > > >> Sorry, but community guidelines is an actual industry standard. Absence > >> of the guidelines have been shown to hurt the project development. > >> See https://dl.acm.org/doi/10.1145/3106237.3106246 > > > > Link isn't readable to me. I am skipping it. > > This one should work without non-free JS: https://arxiv.org/pdf/1707.02327
Thanks, though too many contradictions in that "paper". Sounds to me as paper-factory product. We were just talking about LLM generated code lacking quality. Same here. So, basically, these researchers wanted to figure out why modern free software (they speak open source) projects on GitHub die. They looked at a bunch of popular projects that had gone quiet or straight-up said "we're done," then asked the developers what happened. Turns out, the top reasons are a mix of getting crushed by a bigger competitor (like Google or Apple releasing something similar), the project just becoming obsolete or based on outdated tech, or the main devs simply running out of time or losing interest. They also found that the projects that failed were way less likely to have used "best practices" like having clear rules for contributors or automated testing, compared to the ones that stayed successful. So, it's a mix of getting out-competed, the tech world moving on, the maintainers burning out, and sometimes not setting the project up for others to easily help out from the start. I don't consider project failed if there are no commits for long time. I am using lot of software which is not maintained for reason that it works. Anyway, thanks, but no practical use of it. -- Jean Louis
