CoC - Minor disagreement

[RWOverdijk]

From the CODE-OF-CONDUCT:

Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome, and will result in your exclusion. This includes abusing support channels such as GitHub issues or social media to link to off-topic discussions or promote a personal fork or rival project. Sharing links to relevant tutorials, plugins, or issue workarounds is encouraged.

There are some people that are unsure as to what this means exactly (including me). It's a very open for interpretation rule. I also think I know why this was added, but I still think it doesn't belong in the CoC. It should either be rephrased, or removed.

Actually, talking about rival projects is a good thing. It's used to learn, to educate yourself. Sure; just jumping in a channel and spamming "screw sails, use this other project" would be wrong. But mentioning a project shouldn't constitute for reason of exclusion, ever.

[sailsbot]

Hi @RWOverdijk! It looks like you didn’t follow the instructions fully when you created your issue. Please edit your comment (use the pencil icon at the top-right corner of the comment box) and fix the following issues:

• Provide your Sails version
• Provide your Node version
• Provide your NPM version
• Provide your Operating system
• Verify "I am experiencing a concrete technical issue with Sails (ideas and feature proposals should follow the guide for proposing features and enhancements (http://bit.ly/sails-feature-guide), which involves making a pull request). If you're not 100% certain whether it's a bug or not, that's okay--you may continue. The worst that can happen is that the issue will be closed and we'll point you in the right direction."
• Verify "I am not asking a question about how to use Sails or about whether or not Sails has a certain feature (please refer to the documentation(http://sailsjs.org), or post on http://stackoverflow.com, our Google Group (http://bit.ly/sails-google-group) or our live chat (https://gitter.im/balderdashy/sails)."
• Verify "I have already searched for related issues, and found none open (if you found a related closed issue, please link to it in your post)."
• Verify "My issue title is concise, on-topic and polite ("jst.js being removed from layout.ejs on lift" is good; "templates dont work" or "why is sails dumb" are not so good)."
• Verify "I have tried all the following (if relevant) and my issue remains:"
• Verify "I can provide steps to reproduce this issue that others can follow."

As soon as those items are rectified, post a new comment (e.g. “Ok, fixed!”) below and we'll re-open this issue. Thanks!

[RWOverdijk]

@sgress454 Staple your bot to a wall please.

[sailsbot]

Hi @RWOverdijk! It looks like you didn’t follow the instructions fully when you created your issue. Please edit your comment (use the pencil icon at the top-right corner of the comment box) and fix the following issues:

• Provide your Sails version
• Provide your Node version
• Provide your NPM version
• Provide your Operating system
• Verify "I am experiencing a concrete technical issue with Sails (ideas and feature proposals should follow the guide for proposing features and enhancements (http://bit.ly/sails-feature-guide), which involves making a pull request). If you're not 100% certain whether it's a bug or not, that's okay--you may continue. The worst that can happen is that the issue will be closed and we'll point you in the right direction."
• Verify "I am not asking a question about how to use Sails or about whether or not Sails has a certain feature (please refer to the documentation(http://sailsjs.org), or post on http://stackoverflow.com, our Google Group (http://bit.ly/sails-google-group) or our live chat (https://gitter.im/balderdashy/sails)."
• Verify "I have already searched for related issues, and found none open (if you found a related closed issue, please link to it in your post)."
• Verify "My issue title is concise, on-topic and polite ("jst.js being removed from layout.ejs on lift" is good; "templates dont work" or "why is sails dumb" are not so good)."
• Verify "I have tried all the following (if relevant) and my issue remains:"
• Verify "I can provide steps to reproduce this issue that others can follow."

As soon as those items are rectified, post a new comment (e.g. “Ok, fixed!”) below and we'll re-open this issue. Thanks!

[wbprice]

Negative, I am a meat popsicle.

[sailsbot]

Hi @RWOverdijk! It looks like you didn’t follow the instructions fully when you created your issue. Please edit your comment (use the pencil icon at the top-right corner of the comment box) and fix the following issues:

• Provide your Sails version
• Provide your Node version
• Provide your NPM version
• Provide your Operating system
• Verify "I am experiencing a concrete technical issue with Sails (ideas and feature proposals should follow the guide for proposing features and enhancements (http://bit.ly/sails-feature-guide), which involves making a pull request). If you're not 100% certain whether it's a bug or not, that's okay--you may continue. The worst that can happen is that the issue will be closed and we'll point you in the right direction."
• Verify "I am not asking a question about how to use Sails or about whether or not Sails has a certain feature (please refer to the documentation(http://sailsjs.org), or post on http://stackoverflow.com, our Google Group (http://bit.ly/sails-google-group) or our live chat (https://gitter.im/balderdashy/sails)."
• Verify "I have already searched for related issues, and found none open (if you found a related closed issue, please link to it in your post)."
• Verify "My issue title is concise, on-topic and polite ("jst.js being removed from layout.ejs on lift" is good; "templates dont work" or "why is sails dumb" are not so good)."
• Verify "I have tried all the following (if relevant) and my issue remains:"
• Verify "I can provide steps to reproduce this issue that others can follow."

As soon as those items are rectified, post a new comment (e.g. “Ok, fixed!”) below and we'll re-open this issue. Thanks!

[RWOverdijk]

The issue is a discussion point about a document. How can I do any of these things? Please disable this bot.

[sailsbot]

Hi @RWOverdijk! It looks like you didn’t follow the instructions fully when you created your issue. Please edit your comment (use the pencil icon at the top-right corner of the comment box) and fix the following issues:

• Provide your Sails version
• Provide your Node version
• Provide your NPM version
• Provide your Operating system
• Verify "I am experiencing a concrete technical issue with Sails (ideas and feature proposals should follow the guide for proposing features and enhancements (http://bit.ly/sails-feature-guide), which involves making a pull request). If you're not 100% certain whether it's a bug or not, that's okay--you may continue. The worst that can happen is that the issue will be closed and we'll point you in the right direction."
• Verify "I am not asking a question about how to use Sails or about whether or not Sails has a certain feature (please refer to the documentation(http://sailsjs.org), or post on http://stackoverflow.com, our Google Group (http://bit.ly/sails-google-group) or our live chat (https://gitter.im/balderdashy/sails)."
• Verify "I have already searched for related issues, and found none open (if you found a related closed issue, please link to it in your post)."
• Verify "My issue title is concise, on-topic and polite ("jst.js being removed from layout.ejs on lift" is good; "templates dont work" or "why is sails dumb" are not so good)."
• Verify "I have tried all the following (if relevant) and my issue remains:"
• Verify "I can provide steps to reproduce this issue that others can follow."

As soon as those items are rectified, post a new comment (e.g. “Ok, fixed!”) below and we'll re-open this issue. Thanks!

[sgress454]

@RWOverdijk If you have a proposal as to how the code of conduct should be changed, you can make a PR to that document!

[mikermcneil]

@RWOverdijk I'll hit you up on gitter