FWIW my perspective on this - so far, that is, having been an active participant here for only about a week or two:
Even though I use SO regularly as a reader it’s not very inviting (to me) to put my questions on there. Not sure exactly why but I am very sure that there are so many people, especially newbies, who feel the same. This forum here feels just much more friendly and inviting… more like a community, and so it’s easier to feel like part of it and participate.
And there should be a very inviting and friendly community for Meteor developers, especially for new ones, somewhere on the web. I do appreciate that it is here, though of course it’s not my decision what kind of place MDG is intending to create here.
And all that is important because Meteor is currently speaking to lots and lots and lots of developers who are new to this – either new to programming itself, or to web development, or to modern web development, but in any case new to Meteor itself. And then providing a friendly place for these new developers to get started and feel welcome and encouraged and helped a little must, from my perspective, be part of a complete, well-aligned, fully-functioning process of inviting and onboarding and sustaining a healthy and growing developer community.
Take a look at what Digital Ocean is doing with their community. I’m not referring to, or have insight into, what kinds of discussions or threads are happening over on their site(s) and in their community. But I speak of their deliberate building and catering to a community of newbie server admins who “are new to this kind of thing”, inviting and welcoming them with very detailed and patient instructions, answering many of their (“silly” little) questions in the comments, and encouraging them on their way to becoming more capable and knowledgeable admins of their own servers, and, of course, happy and loyal customers of their service.
I’m suggesting, I suppose, that MDG may take a leaf out of DO’s book, and start paying (or similarly incentivizing) capable members of the community for 1) creating packages and 2) writing tutorials and guides that help the massive influx of new developers smoothly navigate around the rough edges that still exist, and that will always exist, to ever-lesser degrees and yet still in always new forms, throughout the life of Meteor.
From developing in Meteor full-time for just a few weeks it’s clear to me, as a more practiced developer, that probably around at least 50%, maybe even towards 70, 80, 90% of the somewhat “unwanted” (i.e. either trivial or strictly how-to-do-this) help requests that appear here (and to a lesser degree probably on SO as well) could be solved / prevented / automatically helped by a small team of dedicated, somewhat experienced developers who just start churning out: 1) packages, 2) boilerplate systems (with package sets, file/folder organization, different options in frontend stacks etc) and 3) guides and other documentation-type writing, while taking their inspiration to write and create by taking in all the data that comes in primarily through this forum and SO, but also blogs, sifting and sorting, prioritizing and working their butts off for a while until they have caught up with what is essentially improving UX.
The data that comes in is essentially requests for UX improvements, to a large degree, and from my perspective the best way to deal with that is take it as feedback and guidelines about what to create and improve next and get right to it 'til it’s done.
And once everything that actually represents UX feedback is being taken care of, then there will absolutely be an option to easily and naturally move the kind of (non-)discussion that belongs on a site like SO to that site, while not appearing unfriendly or unwelcoming or closed off to requests for help and input and encouragement. Absolutely there will be and there will be no confusion about it, or discourse necessary in achieving agreement with the community that is present, for the most part.
Thanks for reading,