forked from balderdashy/sails
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated feature request guidelines
- Loading branch information
Rachael Shaw
committed
Mar 18, 2014
1 parent
f95245b
commit 211a999
Showing
1 changed file
with
5 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,7 +20,7 @@ When submitting an issue, please follow these simple instructions: | |
|
||
1. If you have a question about setting up/using Sails, please check out the [Sails docs](http://sailsjs.org/#!documentation) or try searching [StackOverflow](http://stackoverflow.com/questions/tagged/sails.js). | ||
2. Search for issues similar to yours in [GitHub search](https://github.com/balderdashy/sails/search?type=Issues) and [Google](https://www.google.nl/search?q=sails+js). | ||
3. Feature requests are very welcome, but we would prefer to keep them separate from actual issues with the framework. If you want to submit a feature request, please post it on our [Trello Board](https://trello.com/b/cGzNVE0b/sails-js-feature-requests). You can do so by emailing the issue to [email protected]. You can put the name of the request in the subject line, and the description in the body. It can sometimes take a few minutes for it to appear on the board, so please be patient if you don't see it right away. | ||
3. Feature requests are welcome; see [Requesting Features](https://github.com/balderdashy/sails/edit/master/CONTRIBUTING.md#requesting-features) below for submission guidelines. | ||
4. If there's an open issue, please contribute to that issue. | ||
5. If there's a closed issue, open a new issue and link the url of the already closed issue(s). | ||
6. If there is no issue, open a new issue and specify the following: | ||
|
@@ -32,15 +32,13 @@ When submitting an issue, please follow these simple instructions: | |
|
||
|
||
## Requesting Features | ||
We use [Trello](https://trello.com/b/cGzNVE0b/sails-js-feature-requests) for tracking feature requests. | ||
|
||
##### Submitting a New Feature Request | ||
|
||
1. Check to see if a feature request already exists for what you're interested in. You can upvote and comment on existing requests. | ||
2. [Send the board an email]([email protected]) with a short label (< 10 words or so) for the feature request as the subject line and a more detailed description in the body of the message with your github username. If you'd be able to help contribute to the development of the feature, please mention that in the description! | ||
|
||
It can sometimes take a few minutes for a new request to appear on the board, due to latency processing our little email message hack, so please be patient if you don't see it right away. | ||
> Note: The process for tracking feature requests has recently changed. We are still using Trello for the Sails roadmap, but are migrating feature requests back into GitHub issues in order to allow more people to participate in the discussion. | ||
#####Submitting a new feature request | ||
1. First, check to see if a feature request already exists for what you're interested in. If it does, you can join the discussion in that request's comment thread. | ||
2. If it doesn't already exist, create a new issue for it. Please prefix the title with **[#feature]** so we can easily spot it and keep track of feature requests. | ||
|
||
|
||
## Writing Tests | ||
|