First, look through these resources to see if your question has been answered already:
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:
If you've found a bug in Meteor, file a bug report in our issue tracker. However, a Meteor app has many moving parts, and it's often difficult to reproduce a bug based on just a few lines of code. If you want somebody to be able to fix a bug (or verify a fix that you've contributed), the best way is:
meteor-reactivity-bug(or if you're adding a new reproduction recipe to an existing issue,
meteor-issue-321) and push your code to it. (Make sure to include the
git clonecommand. Copy and paste the entire command-line input and output, starting with the
git clonecommand, into the issue description of a new GitHub issue. Also describe any web browser interaction you need to do.
$ meteor --version) and what web browser you used.
By making it as easy as possible for others to reproduce your bug, you make it easier for your bug to be fixed. Issues opened without a reproduction recipe are likely to be immediately closed with a pointer to this wiki section and a request for more information.
Contributing doesn't necessarily mean working on Meteor internals. See the Get Involved page on meteor.com for a starter list of ways to contribute.
To contribute code to Meteor core, submit a pull request. Follow the Contributor Guidelines, please!
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.
Do you blog about Meteor regularly? File an issue with a link to your blog's "Posts tagged 'meteor'" page, and we'll add it here.