+1, * applause*
Rick On Saturday, May 3, 2014, Forrest Norvell <othiy...@gmail.com> wrote: > Hello, everyone. If you don't know me, I'm a longtime Node.js developer > and member of this group. I'm also a strong believer that this group hasn't > been living up to its potential for a while now, and in an effort to > improve its usefulness and the quality of the discussion here, I've agreed > to take on the responsibility of moderating it. > > For now, that implies one big change, which is that every message to the > group will be reviewed by an actual person before being posted to the > group. The moderation policy is pretty simple (it's included below), and > things shouldn't change much. My current plan is to continue this policy > until the end of July and then revisit how people feel about the state of > the list. (As an aside, if you're interested in helping me moderate the > list, get in touch off-list and we can talk. With conference season > starting to heat up again, I'm likely to be away from the internet a few > times between now and the end of July, and having someone to help me cover > moderation duties would be great.) > > If your message gets rejected, you may not get a whole lot of feedback as > to why it didn't get passed through. I apologize for this, but Google > Groups's interface for rejecting messages is kind of terrible and doesn't > allow me to easily include a personalized message. > > As part of more actively moderating the group, I'm also open to your > suggestions on what we can do to shape this into a more useful forum. If > you go to the gist where I put the draft of the moderation > policy<https://gist.github.com/othiym23/9886289>, > you can see that there are already a couple suggestions. Feedback on those > suggestions is welcome, as is feedback on the moderation policy itself. My > main goal here is to improve the tenor of discussion here to the point that > it's a comfortable place for both newcomers and experienced Node > developers. One of Node's greatest strengths is its community, and I'd love > to see this group become a more significant clearinghouse for the community > as a whole. > > Here's the moderation policy itself: > > The Node.js group is a tool to announce cool things you've built, discuss > interesting projects you're working on, and get help with things that are > confusing you. It is a great forum for swapping knowledge. It is part of > Node's large, loose network of resources. But it's not the only one – there > are other resources that might be a better place to seek help or ask > questions: > > - Stack Overflow <http://stackoverflow.com/questions/tagged/node.js> is > a great place to get help with specific technical questions about Node! If > you post a question there, please wait a few days before crossposting it to > the list, as many of the people who answer questions about Node on SO are > also here. Also, crosspost with a link rather than the whole text of the > question, to keep things tidy and to keep discussion of the issue in one > place. > - The development of Node itself is largely handled through Github. If > you think you've encountered a bug in Node itself, it's best to file > an issue <https://github.com/joyent/node/issues/new> there. > - Likewise, the development of npm is handled by the npm team, also on > Github <https://github.com/npm/npm>, and npm bugs should be filed > there<https://github.com/npm/npm/issues/new> > . > - For a more conversational approach to figuring things out, #node.js > and #libuv on freenode IRC <http://webchat.freenode.net/> are great > realtime resources for help with Node. > > That said, here are the rules governing the list: > > 1. No personal attacks or harassment. This group is governed by the > Conference Code of Conduct <http://confcodeofconduct.com/>, and > violating its rules will get you barred from the list permanently, at the > moderators' discretion. > 2. No spam. Self-promotion is fine, and major updates of projects to > which you've contributed merit a mention, but this is a technical forum, > not a marketplace. > 3. Large chunks of source will work much better if posted to a > requirebin <http://requirebin.com/>, jsbin <http://jsbin.com/>, > gist<https://gist.github.com/>, > or generic pastebin of some kind. > > In addition, there are some more informal guidelines that, if followed, > will make everyone's lives more pleasant: > > - There are certain arguments that recur with monotonous regularity. > Bikeshedding is a major part of hacker culture, but there is no one true > solution to any of the problems that are regularly brought up on the list > (promises vs callbacks vs coroutines vs generators vs CPS transforms vs ∞, > JavaScript vs CoffeeScript, etc). What works best for you may not work well > for somebody else. > - Not everybody comes to Node with the same background. One of Node's > touted advantages is that it unifies server-side and front-end developers. > Sometimes people need a little help crossing the gap. Be charitable. > - Even though Google Groups makes it easy, it's a little weird to > revive a message thread that's more than a few months old. Start a new > thread that summarizes the old one if you want to revisit a dead thread. > > These rules and guidelines will be enforced at the moderators' discretion. > We will do what we can to ensure they are applied consistently and fairly, > but having a useful forum trumps arguing over precise observance of the > rules. The final say about moderation decisions sits with Node's > maintainers, but TJ is busy, so be reasonable. > > I'll continue to post this policy every two weeks until the end of the > July. Thanks for reading this, and get in touch if you have comments or > complaints. My hope is that very little will change, and what changes there > are will be for the better! > > Forrest L Norvell, group moderator > > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > 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 post to this group, send email to > nodejs@googlegroups.com<javascript:_e(%7B%7D,'cvml','nodejs@googlegroups.com');> > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com<javascript:_e(%7B%7D,'cvml','nodejs%2bunsubscr...@googlegroups.com');> > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > 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<javascript:_e(%7B%7D,'cvml','nodejs%2bunsubscr...@googlegroups.com');> > . > For more options, visit https://groups.google.com/d/optout. > -- Job board: http://jobs.nodejs.org/ Moderation policy: https://gist.github.com/othiym23/9886289#file-moderation-policy-md You received this message because you are subscribed to the Google Groups "nodejs" group. --- 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/CAHfnhfp2%3Dwvo3_HO-aoQqtZjNdZpekDjSb6CcokG5htnYcqyAQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
