You know guys, there is a lesson somewhere at the last part of this thread… (and it is slightly off-topic).
Something called Husk is judged based on quality and quantity of information available to the public. I had mentioned this on few occasions and tried to point out how important is to deal with the community and project foundation work at the very beginning, even before the takeover from Microsoft.
I see no reason and justification to be so secretive or uninterested in that part of the project/community. Yes, coding is something that the founders and the most prominent members are interested in the most, but neglecting everything else for no obvious reasons helps situations like this (in relation to Husk).
From what I saw in the posts of @sk89q and others, I don’t think that they are uninterested completely at this time, it seems that they have more important and interesting things to do (namely, programming).
I don’t think that you would feel threatened if you would allow someone, who is not (primarily) interested in programming, to step in and help you and us come up with a few pivotal pieces of information about what this endeavor is all about.
Try to define what should be the mission behind this project, objectives, milestones. What are the constraints? Which are the “red lines” that will not be crossed? Which are the areas for help, support, improvements, suggestions, etc?
Who is the “official” contact for this project and for which topics?
Maybe a little bit about history, present and plans for the future (high-level overview).
At the end, you can make a summary about all the “technical mumbo-jumbo”, as it will be perceived by many, I believe (chosen approaches to API, systems for continuous integration, source code management, ticketing, forum, etc.).
Having this established you would be providing sufficient information for all the stakeholders (future supporters, programmers, plugin developers, server admins, lurkers, competitors, but also Mojang and Microsoft), which in turn would guarantee that we have left all the necessary doors open. The stakeholders would understand where is this project coming from and where would it like to go, and could make their standpoints based on their interests. Therefore, instead of being concerned and thinking if the project could be hostile or ignorant towards their interests, they could have enough information to “make the next step” whichever that might be (words of support, concerns, proposals, etc.).
I know I am still beating a dead horse but some habits are hard to exterminate.