Babylon.js/contributing.md

Contributing to Babylon.js

The foundation of Babylon.js is simplicity.

A developer should be able to quickly and easily learn to use the API.

Simplicity and a low barrier to entry are must-have features of every API. If you have any second thoughts about the complexity of a design, it is almost always much better to cut the feature from the current release and spend more time to get the design right for the next release.

You can always add to an API, you cannot ever remove anything from one. If the design does not feel right, and you ship it anyway, you are likely to regret having done so.

That's why many of the guidelines of this document are obvious and serve only one purpose: Simplicity.

Forum and Github issues

Since the very beginning, Babylon.js relies on a great forum and a tremendous community: http://www.html5gamedevs.com/forum/16-babylonjs/. Please use the forum for ANY questions you may have.

Please use the Github issues (after discussing them on the forum) only for:

• Bugs
• Feature requests

We will try to enforce these rules as we consider the forum is a better place for discussions and learnings.

Pull requests

We are not complicated people, but we still have some coding guidelines Before submitting your PR, just check that everything goes well by creating the minified version

You should read the how to contribute documentation before working on your PR. We also have a forum thread for assistance from our very helpful family.

To validate your PR, please follow these steps:

• Run "gulp" locally and make sure that no error is generated
• Make sure that all public functions and classes are commented using JSDoc syntax
• Make sure to add a line about your PR in the what's new
  

## What should go where?

In order to not bloat the core engine with unwanted or unnecessary features (that we will need to maintain forever), here is a list of questions you could ask yourself before submitting a new feature (or feature request) for Babylon.js core engine:

• Does my feature belong to a framework library?
• Can my feature be used by multiple different applications?
• Is there a general use case for this feature?
• Does this feature already exist in a similar framework?

If your PR is does not fall into the core category you can consider using our Extensions repo for more high level features.