Home

What’s -More?

MooTools More (often referred to just as “-more”) is the official plugin repository of the MooTools JavaScript Library. These plugins extend and build upon the MooTools Core (often just “-core”). The MooTools Core is developed by the principal developers for MooTools and is essentially a separate project. MooTools More is more open for contributions and involvement. This is where YOU can get involved.

Getting Involved

By definition, the contributors to -more are the MooTools team. The criteria to be a MooTools -more developer are only that you are a) good at writing MooTools code and b) consistently contribute to the project. In other words, anyone can get involved with -more. All you have to do is fork the code in github and start checking in bug fixes or whatever. You can fix documentation errors, fix bugs, write unit tests, etc. (Bugs that need fixing can be found in GitHub

More’s Branch Policy

MooTools More follows the nvie branching model though not entirely. The develop branch is the main tracking branch where reviewed code that is not released goes. The master branch contains the latest release. Topic branches are typically named develop-topic and are works in progress until they are pulled and then destroyed. These topic branches may be rebased at any time, so watch for forced updates to them should you pull them. Occasionally, large overhauls are required (such as a point release in MooTools Core requiring us to do a large port). These typically are named after the release with “wip” – “work in progress” attached (i.e. 1.3wip). These branches are also tracking branches of released code, so they behave much like the develop branch.

Submitting Code

You can also submit your own plugins for the repository, but it’s not a drop-off box. We aren’t interested in just taking things from people – if you are involved and are committed, then adding your own plugins will be welcome. If you just have something we think would be cool to include, we’re not as interested.

The criteria for a plugin being accepted into -more are as follows:

1. there must be a valid use case for the code – not just something that’s kinda cool that no one can figure out how to use.
2. the code must be relatively well written (it will likely be combed over by the development team before it goes out).
3. it should, when possible, build on existing plugins.
4. it should follow the general design principals that exist throughout the -core and -more libraries.

Additionally, a minority of -more developers must agree that it belongs (i.e. not just you).