I have followed the Mach4 threads for a while. I don't have the expertise of either simpson36 or BR549, but I can see both of your viewpoints. I can program and I plan on trying to make a contribution in that area, but I'd obviously prefer to get as many features without programming as possible. I like both of simpson36's views that the community can contribute a lot of the features to Mach4 through scripting and that there needs to be good documentation. Every programmer likes to develop features, and very few programmers like to develop docs. How will documentation for the 'core' features and community contributed features be related? The more tightly integrated they are, the better. The current forum is great if you post a problem and someone answers you. It's not so great for trying to find the answer to your question by searching through previous posts. It seems like an actively curated, organized wiki might be a good solution. There should be multiple indexes organized based on different criteria. This would allow a lot of the work for the documentation to be taken off the backs of the dev team. The docs for the core functionality would be curated by the dev team or some other expert, the structure of the add on features could be curated by someone like simpson36,
and the entries for the specific features could be curated by the feature creators. Links could be made from the wiki to the forum. I know this will take work to set up, but I think it would be worth the investment after the core functionality is set up. I would much prefer a solid but limited core with good documentation over having more core features without documentation. I also think it needs to be as easy as possible to add the desired community-generated functionality to Mach4 from within Mach4.