On Wed, Dec 10, 2014 at 12:27 AM, Ryan Schmidt <google-2...@ryandesign.com> wrote:
> > On Dec 9, 2014, at 1:09 PM, Matt wrote: > > > I highly recommend you subscribe to nodeweekly - it's a weekly roundup > of node news where you'll at least get to hear about this stuff. > > > > http://nodeweekly.com/ > > Done. I'll point out that this, too, is a resource that has never been > mentioned here before. (Why hasn't it?) Because nobody's mentioned it. I don't say this to be a smartass – this group is a community resource, and, putting on my moderator hat for a second, it's run with a pretty light hand. The addition of Aria as a moderator (which I probably should have announced, and I apologize for not doing so) has made the lag time between posting and approval much lower, so the friction to get a message in front of the group's users is about the same as it's always been. If stuff isn't showing up here, it's because nobody's seen it as being worth sharing with the group. That's on all of us. As I said in my earlier post on this thread, I understand how frustrating it must be to learn about potentially transformational events around Node in such an incomplete and tardy way. It frustrates me, and I'm better informed than many due to my job and my location. A year or two ago, it would have been much easier for everyone to stay on top of things, because a lot (if not most) of the engaged members of the community were all using this group. However, that isn't the case anymore. There are a bunch of reasons for that – the many flame wars at the end of last year that led to me volunteering to moderate the mailing list were the last straw for many former group members that I've talked to; others just don't see the value of old-school mailing lists, or email period – but the reality is that there's now many Node communities doing many different things with the platform, and if you want to keep tabs on more than a few, it's going to take some work. This is both unfortunate (and a little sad) and a consequence of Node's success – to pick one example I'm familiar with, there's enough happening with NodeBots that an entire community can have its own meetups (and even conferences) without really needing to interact much with the rest of the Node world. My friends in that community aren't preoccupied with the fork because Node already does what they need, more or less. And NodeBots is just the most obvious, self-contained example. Node is *big*, and it's natural for it to sort out into more manageable communities. And yes, it does suck that the larger community only found out about the fork so late in the game. But Aria and Stephen have already pointed to what's been going on – while I think things are in an OK place right now, there's been a lot of negotiation and politicking that's led to this point, and there have been many explicit requests to keep those discussions private and restricted to the parties involved. I agree that the community should be leading these discussions instead of following them, and all I can really say is that the people to whom you should be addressing your questions and concerns are not active participants of this group. F -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CAHG3qKrJLZuMmPWPfcGLPq45ffmyvKFHiVxB73skZrcBzAMQ3Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
