3 ms·
> creating a bunch of immediately abandoned forks is a joke. This part is not inherently true. Only time will tell how Audacity reacts, and they could very wel
by smoldesu 5y ago
> creating a bunch of immediately abandoned forks is a joke.
This part is not inherently true. Only time will tell how Audacity reacts, and they could very well have an UnGoogled-Chromium/Codium situation on their hands.
- orf 5y agoPicking two applications with less global users than a small town or a large village doesn’t make a great point. They might as well have been abandoned - no relevant mass of people use them.
- smoldesu 5y agoAh, my bad. I'll stick to S&P Top 500 companies next time.
- orf 5y agoNo, stick to forks that manage to reach a self-sustaining level above “one or two users cherry-picking from an upstream repo as a passion project”. My point is that a fork can be abandoned by users even if the project is still active.
- monetus 5y agoYour point is worth thinking about it, audacity needs a critical mass of users. But does it have enough original users to keep from being considered abandonded already? Edit: to be clear, other software is often used instead of audacity. It isn't as well known as say photoshop, or maybe even inkscape.
- deleted 5y ago[deleted]
- sdesol 5y agoIn the last 90 days they had 11 contributors that changed c,cpp, and c header files with at least 10 lines of code churn: https://public-001.gitsense.com/insights/github/repos?p=commits&q=file-churn%3A%3E%3D10%2Blangs%3Ac_header%2Ccpp%2Cc%2Bwindow%3A90&r=github%3Acookiengineer%2Faudacity&v=repo https://public-001.gitsense.com/insights/github/repos?p=comm... The user crsib appears to be the main contributor to audacity, so I would have to imagine others would have to pick up the slack for a fork to be viable. cookiengineer also changed 71 files https://public-001.gitsense.com/insights/github/repos?p=commits&q=authors%3Acookiengineer%40protonmail.com%2Binvolves%3Acookiengineer&r=github%3Acookiengineer%2Faudacity&v=repo https://public-001.gitsense.com/insights/github/repos?p=comm... so he/she will have to constantly monitor these files moving forward, for the fork to be stable/similar to audacity/audacity, which I am not sure if he/she/others are interested in doing this for the long term, but I guess time will tell. Full disclosure: I'm the creator of the tool that I linked to