Comments on: How to “Pay it Back” to MooTools http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/ Making stuff work on the other side of the request. Tue, 05 Jan 2010 18:16:32 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Oliver Nassar http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32383 Oliver Nassar Mon, 10 Aug 2009 03:05:46 +0000 http://www.clientcide.com/?p=967#comment-32383 @walsh Most def. i agree with it starting with me/us asking "how can we help?" This is OS, so community/horizontal organization is really important. Hopefully with this fall's launch it'll start to become more involving. @walsh

Most def. i agree with it starting with me/us asking “how can we help?”
This is OS, so community/horizontal organization is really important. Hopefully with this fall’s launch it’ll start to become more involving.

]]> By: Michael http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32382 Michael Sun, 09 Aug 2009 20:45:13 +0000 http://www.clientcide.com/?p=967#comment-32382 I'm a bit tired saying it, but this magic central plugin place was already there in early 2008, so I guess you guys just didn't see it... So let's see how the new official thing will (hopefully) rock the community. I’m a bit tired saying it, but this magic central plugin place was already there in early 2008, so I guess you guys just didn’t see it…
So let’s see how the new official thing will (hopefully) rock the community.

]]> By: Barryvan http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32380 Barryvan Sat, 08 Aug 2009 00:53:54 +0000 http://www.clientcide.com/?p=967#comment-32380 The community plugin system and a wikitorial for MooTools sounds really good. I also like the idea of wiki-fying the main docs, so that we can start documenting some of the currently-undocumented "features" and private functions which are actually really useful. I understand that it's simple enough to modify the docs using git, but I do think that a Wiki will encourage more active maintenance of the docs because of the easier access. The community plugin system and a wikitorial for MooTools sounds really good.

I also like the idea of wiki-fying the main docs, so that we can start documenting some of the currently-undocumented “features” and private functions which are actually really useful. I understand that it’s simple enough to modify the docs using git, but I do think that a Wiki will encourage more active maintenance of the docs because of the easier access.

]]> By: Aaron N. http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32378 Aaron N. Fri, 07 Aug 2009 21:44:56 +0000 http://www.clientcide.com/?p=967#comment-32378 @Jeffrey, the community plugins system, which has been "coming" for so long is in testing. It's slow going, but we'll definitely have it online this fall. Hopefully this month, but we'll see. Note that it will be integrated w/ github, so you should push your code there rather than google code. As for the docs as a wiki, you can push changes to us easily enough if you want to contribute. Fork mootools-core or mootools-more on github, make a change, and send a pull request. You can even make the changes you want right in the browser without having to learn git. Finally, we will be adding a tutorial wiki to MooTools.net this fall as well. This will basically be the current www.mootorial.com to start, but we'll hope the community chips in to help us keep it accurate and helpful. @Jeffrey, the community plugins system, which has been “coming” for so long is in testing. It’s slow going, but we’ll definitely have it online this fall. Hopefully this month, but we’ll see. Note that it will be integrated w/ github, so you should push your code there rather than google code.

As for the docs as a wiki, you can push changes to us easily enough if you want to contribute. Fork mootools-core or mootools-more on github, make a change, and send a pull request. You can even make the changes you want right in the browser without having to learn git.

Finally, we will be adding a tutorial wiki to MooTools.net this fall as well. This will basically be the current http://www.mootorial.com to start, but we’ll hope the community chips in to help us keep it accurate and helpful.

]]> By: David Walsh http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32377 David Walsh Fri, 07 Aug 2009 21:41:19 +0000 http://www.clientcide.com/?p=967#comment-32377 @Jeffrey: I'd much, MUCH prefer the MooTools docs stay the way they are and not in Wiki format. No offense to the jQuery team, but I like the Moo doc format much more. @Jeffrey: I’d much, MUCH prefer the MooTools docs stay the way they are and not in Wiki format. No offense to the jQuery team, but I like the Moo doc format much more.

]]> By: David Walsh http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32376 David Walsh Fri, 07 Aug 2009 21:39:53 +0000 http://www.clientcide.com/?p=967#comment-32376 Hello Oliver, Thank you for the post. The community's plugin repository is in the works and we have Faces of Moo coming soon. Wheels are definitely in motion so stay tuned. Also, remember: it always starts with asking how to help. :) Cheers! David Hello Oliver,

Thank you for the post. The community’s plugin repository is in the works and we have Faces of Moo coming soon. Wheels are definitely in motion so stay tuned.

Also, remember: it always starts with asking how to help. :)

Cheers!

David

]]> By: Jeffrey http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32375 Jeffrey Fri, 07 Aug 2009 21:38:37 +0000 http://www.clientcide.com/?p=967#comment-32375 Well said, Oliver. The two things Mootools needs as a community is: 1) an official home for additional "More" plugins (with a community review process to allow the best of the best to bubble to the top). The way that Drupal has module projects at their site would be killer. 2) Mootools documentation needs to be a Wiki. I can't count how many times I've seen "that's not quite right" or "there's a better way to say that" issues in the documentation. I'd love to help more <em>directly</em> in this way. Mootools as a <em>code base</em> doesn't seem to need much more - it's going in the right direction by itself. It's the periphery things that need help. Well said, Oliver. The two things Mootools needs as a community is:

1) an official home for additional “More” plugins (with a community review process to allow the best of the best to bubble to the top). The way that Drupal has module projects at their site would be killer.

2) Mootools documentation needs to be a Wiki. I can’t count how many times I’ve seen “that’s not quite right” or “there’s a better way to say that” issues in the documentation. I’d love to help more directly in this way.

Mootools as a code base doesn’t seem to need much more – it’s going in the right direction by itself. It’s the periphery things that need help.

]]> By: Merrick Christensen http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32374 Merrick Christensen Fri, 07 Aug 2009 21:35:55 +0000 http://www.clientcide.com/?p=967#comment-32374 That was really well said. None the less MooTools is still where its at. That was really well said. None the less MooTools is still where its at.

]]> By: Oliver Nassar http://www.clientcide.com/best-practices/how-to-pay-it-back-to-mootools/comment-page-1/#comment-32373 Oliver Nassar Fri, 07 Aug 2009 20:49:46 +0000 http://www.clientcide.com/?p=967#comment-32373 One of the things that's always bothered me about Mootools is the community. I've spent a lot of time researching the competing frameworks, and have been faithful to moo for a long time now (since 06), but organization is the one thing Moo def. doesn't have compared to some of the other guys (jquery, yui, dojo). There are reasons for that (exposure, private funding, etc.), and I'm not faultless in this, but for those of us who want to help and contribute it's difficult to know where to start. We want a central place for plugins/extensions/classes to go, a central place for us to post these and should demo's, add documentation, etc. I'll be releasing a bunch of stuff hopefully in the next couple months under MIT on code.google.com, but hopefully a central community will come together. That being said, clientcide is an awesome place for new comers/users to learn more, but a more community driven site would be the icing on the cake of the best client side framework around; that's not even a subjective statement :) One of the things that’s always bothered me about Mootools is the community. I’ve spent a lot of time researching the competing frameworks, and have been faithful to moo for a long time now (since 06), but organization is the one thing Moo def. doesn’t have compared to some of the other guys (jquery, yui, dojo).

There are reasons for that (exposure, private funding, etc.), and I’m not faultless in this, but for those of us who want to help and contribute it’s difficult to know where to start. We want a central place for plugins/extensions/classes to go, a central place for us to post these and should demo’s, add documentation, etc.

I’ll be releasing a bunch of stuff hopefully in the next couple months under MIT on code.google.com, but hopefully a central community will come together.

That being said, clientcide is an awesome place for new comers/users to learn more, but a more community driven site would be the icing on the cake of the best client side framework around; that’s not even a subjective statement :)

]]>