-
Notifications
You must be signed in to change notification settings - Fork 1
Home
First, look through these resources to see if your question has been answered already:
- Official Meteor Docs
- Questions tagged 'meteor' on StackOverflow
- Unofficial Meteor FAQ
- meteor-talk mailing list - public discussion list
- meteor-core mailing list - for discussing Meteor internals and proposed changes to Meteor itself
Make a good first effort to find an answer before asking your question. If you can't find an existing answer to your question, try one of the following, in this order:
- Ask it on StackOverflow
- Ask it in IRC #meteor channel on irc.freenode.net
- Ask it on meteor-talk
- The Meteor Roadmap shows the core team's current development priorities
- Follow the Meteor Style Guide
- What those GitHub Issue Labels in our issue queue mean
Please see our contributing guidelines for details on how to file a bug report or submit a pull request. In brief:
-
Bug reports are welcome. It's essential that they include a full reproduction recipe so that others can help fix the issue.
-
If possible, publish new features as separate packages on Atmosphere.
-
Most changes to core packages should be discussed first on
meteor-core, where you can build consensus and work out most of the design. Submit a pull request once you have a core developer on board. Themeteor-corelist is also a fine place to request new features without a specific proposal. GitHub issues aren't as good place for those that sort of thing: we'll close "feature request" issues.
Here are drafts of docs that haven't made it into http://docs.meteor.com yet. You may find these useful. We appreciate suggestions and improvements: file issues or submit pull requests.