It'd take a team, not only of software developers, but also mechanical engineers and others that would represent the target audience. Part of the problem with so much open-source stuff is that it often doesn't address the needs of many of its potential users, in large part because either those users' feedback is not solicited, or is dismissed out of hand. A package you write might scratch your particular itch, but it also has to scratch the itch of a lot of other people if it's to be widely successful. Software devs are often notoriously susceptible to the Dunning-Kruger effect and unwilling to accept constructive criticism.
Add technical writers to that team too - a professional's time usually has a substantial dollar value attached to it, and a package isn't going to see a lot of use if the lack of documentation ends up costing more time for them than using a well-documented commercial product of at least equal functionality. This also extends to making the package easy to install/remove - it may be trivial for a lot of us, but a lot more of the professional types aren't going to do well with a "configure/make/make install" process.