> What happens when a gang of amateur photographers, turned into amateur developers, joined by a bunch of back-end developers who develop libraries for developers, decide to work without method nor structure on an industry software for end-users, which core competency (colorimetry and psychophysics) lies somewhere between a college degree in photography and a master’s degree in applied sciences, while promising to deliver 2 releases each year without project management ? All that, of course, in a project where the founders and the first generation of developers moved on and fled ?
A number of open source design software comes to mind, but I am too scared to name them.
Yeah it's a common problem, but it is in the nature of open source to be done by enthusiasts (of course it can be done by professionals/enterprises, but I think it's fair to say that most open source software stems from a personal need).
I'm really not judging any project, because a working solution that is done by enthusiastic amateurs is better than no solution at all and let's be honest, most of my code is amateurish at best/hacked in a week/month as well.
It's only bad if you see a project heading in the wrong direction and not being able to stop this, but for this god invented forks ;)
A number of open source design software comes to mind, but I am too scared to name them.