For Information on MooTools usage see MooTools.net
The MooTools Community discussions take place on the MooTools Users Google Group and #mootools on irc.freenode.net
Tickets & Project ManagementThe MooTools bugtracker is located at GitHub.
Found a bug?OR Update the existing ticket.
EG: “MooTools 1.2 Release” or “MooTools Core Master d29e174d”
EG: “Microsoft Windows XP SP3 Internet Explorer 7” or “iPhone Simulator SDK 2.0”
Some bugs may actually be errors in the MooTools documentation.
How to Verify a Patch How to Contribute Minor FixesIf 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 ChangesAs 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 MooTools.net for more information on getting involved with the project.
How the MooTools Dev Team ContributesRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4