MooTools has always prided itself with the quality of its developer community, and the MooTools development team has always highly valued the opinion and input of the thousands of users who continually support the framework. With this in mind, we've decided to provide everyone with a quick update on the recent work that the More team has been doing. Specifically, the meta things about More; the things we do to make working on MooTools More better and better.
With the help of our two newest developers, Arian and Tim, the MooTools More team has been working hard to get More up and running with Core 1.3. Aside from updating old Core API calls, they've been fixing a lot of the Lighthouse bugs, as well as providing new improvements like Event.Pseudos, Locale and more.
The last of the 1.2.x More releases has been a priority since the Core 1.2.5 release. It will come with a lot of bug fixes and a few new features. The hold up is converting all of More's tests to use the new process described below. As such, it looks like More 184.108.40.206 and More 220.127.116.11 will likely be released together.
To help with this increased development—and to make sure less bugs squeak by—we have set up a new testing environment using the wonderful Windmill testing framework. An example of the new sandbox environment can currently be found at http://review.mootools.net:9876.
A couple of us have also been hard at work improving the testing throughout all the MooTools projects, but you'll just have to wait and see the awesome details in a later article.
With the release of GitHub's new Pull Requests system, we've found that they fit very well into the MooTools development workflow. The new system makes it easier for the developers to review pull requests, and makes the discussions associated with them public.
Because the MooTools community is made up of awesome developers who are more than happy to share their work and to give back to the project, we realized that this new pull request feature could be very helpful in accepting contributions from the community. As such, we are encouraging all of you to send us your pull requests for review and possible inclusion in the Core and More repositiories.
We hope that you're as excited as we are with what's cooking on the MooTools development front. We'd like to hear your opinions, comments and suggestions in the comments section below, so don't hesitate to drop a line or two.
We also invite everyone to visit our official Github repository and drop by the official #mootools IRC Channel on Freenode. MooTools also has a twitter account that you can follow for more news and updates.
And stay tuned—we have something very special coming in the next few weeks that will hopefully blow your minds.
Now off for a chocolate milk!
To protect ourselves and the MooTools community, we've started two physical screening programs (or "meetups"), one in London and the other in the heart of Silicon Valley.
In a surprising turn of events, both groups have had very informative meetings in which actual people have shown up, allowing us to conclusively state that at least some of the members of the MooTools community are, in fact, human. Insightful discussions were had by all, new users and advanced developers alike.
If you're in the Bay Area or London, it is imperative that you attend at least one of our screening sessions, to verify yourself as human. To be notified about future meetups, as well as voice your opinion on when/where they should be, you can join the Meetup.com group for your area:
If you have something insightful and MooTools-related to share, and think you can spin it into a fifteen minute presentation, please let us know.
Right now, we don't have any formal communication set up, but it shouldn't be to hard to get in touch with either Darren (London) or myself (Bay Area). Contact information can be found on the developers page.
Thanks for using MooTools, and we hope to see you there!