So, there’s a bit of a history of Stallman botching GNU leadership. The organization has grown to the scale where it requires a different skill set to lead than

So, there’s a bit of a history of Stallman botching GNU leadership. The organization has grown to the scale where it requires a different skill set to lead than the skill set he has. It’s clear he has a vision for the GNU software, but the development process itself is chaotic and needs more central guidance on a policy/process level—but he tries to lead it on a more technical/maintainer level. One example is the glibc/emacs unexec discussion. He stepped in to meddle without enough knowledge of the relevant teams, in order to solve an issue that would have been avoided with a more explicit policies in place about the relationship between different GNU projects. Having a vision is not enough, there are a lot of other things you need to do right in order to lead a project like that.