How to Contribute

DimitarChristoff edited this page Jan 30, 2012 · 4 revisions

General help

For Information on MooTools usage see

The MooTools Community discussions take place on the MooTools Users Google Group and #mootools on

Tickets & Project Management

The MooTools bugtracker is located at GitHub.

Found a bug?

  1. Search for a similar existing ticket.
  2. Create a new ticket If you’re sure it doesn’t already exist

    OR Update the existing ticket.
  3. Add detailed instructions on how to reproduce the bug.
    • Include the MooTools version you’re using

      EG: “MooTools 1.2 Release” or “MooTools Core Master d29e174d”
    • Include your Operating System and Browser Version.

      EG: “Microsoft Windows XP SP3 Internet Explorer 7” or “iPhone Simulator SDK 2.0”
  4. Create a bug demo page that we can use to verify the bug and track down its source.
    • Either host it yourself, or upload the html file on the bug thread

Some bugs may actually be errors in the MooTools documentation.

How to Verify a Patch

How to Contribute Minor Fixes

If you want to contribute a bug fix, coordinate your fix in the comment thread of a bug ticket (see above on adding/updating tickets). You can add a code patch to the ticket there. Run git help format-patch to see how to create a git patch.

Step-by-step description: How to Submit Patches

To see if your patch is good, a member of the MooTools dev team will pull the patch into their personal fork. Once they decide that it’s good, they’ll push that change up to the official MooTools fork.

How to Contribute Major Changes

As with all Git projects, feel free to fork the project and do whatever you want with your own fork of MooTools. How to fork a repo and keep it updated with the mootools-core upstream

But, if you want your changes to be incorporated into the official releases of MooTools, please work with us to decide what direction to take the project. See for more information on getting involved with the project.

How the MooTools Dev Team Contributes