This is why I abandoned slackware. It was one of the first distros that 'worked'. However, after becoming a developer with source control and some sort of sys

This is why I abandoned slackware. It was one of the first distros that 'worked'. However, after becoming a developer with source control and some sort of system that let you track things. I did not want to go back. They have steadfastly refused to move to more 'modern' development practices (they have been arguing about it since the mid 90s). With simple things like issue tracking. That is fine, it works for them. But after a few years I got tired of spinning my own just to have something kind of current (think that has changed). But I bailed out, when they kicked out the dudes who made it into a distro that was easier to update with some simple commands (like apt). That is something OS at the time had but them. I gave up. I just moved onto whatever my employer decided we were going to use (usually redhat or debian based). I enjoyed my time using it, but it became a chore to maintain. So I moved on to things that had automated some of that. They may have even fixed some of the issues I had with them. But I no longer have the time to bother going back. I have seen this pattern with a few projects. Basically whoever runs the project just does not want to mess with it. That is fine. But it really holds their project back. It works fine when you have 1-2 people working on it. But you add a few dozen with people dipping in and out randomly you need to add some control to the chaos. One project I watched the main dev go kicking and screaming how it would not help. The project is now clicking along pretty good. He now does not feel like he is all alone fighting the world. He has people to help him and can track it easily. He even stated he should have done it sooner.