Comments on: Managing the creative process behind a jQuery plugin http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin Tips, techniques, and tutorials for the jQuery JavaScript library Thu, 11 Mar 2010 20:27:25 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Alexandre Magno http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin/comment-page-1#comment-28820 Alexandre Magno Wed, 30 Jan 2008 07:07:02 +0000 http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin#comment-28820 I love the article and the brazilian community of jQuery lacks of plugin development. If you don´t care, Im translating your post to portuguese. Im Web Developer and recently I receive the authorization to write the Learning jQuery book and I really appreciate if let me send this information for people not fluent in english, but that wish to learn jQuery. You have friends here, you can be sure! Thanks I love the article and the brazilian community of jQuery lacks of plugin development. If you don´t care, Im translating your post to portuguese.

Im Web Developer and recently I receive the authorization to write the Learning jQuery book and I really appreciate if let me send this information for people not fluent in english, but that wish to learn jQuery. You have friends here, you can be sure!

Thanks

]]> By: Brian Reindel http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin/comment-page-1#comment-23961 Brian Reindel Tue, 11 Dec 2007 12:35:31 +0000 http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin#comment-23961 Hi Stan, I think I would recommend the jQuery plugin repository only because a designer searching for a plugin is more likely to end up on the jQuery Web site. Google Code is definitely an option though -- just about any code repository that supports bug logs, feature requests, and release management is better than email. Brian Hi Stan,

I think I would recommend the jQuery plugin repository only because a designer searching for a plugin is more likely to end up on the jQuery Web site. Google Code is definitely an option though — just about any code repository that supports bug logs, feature requests, and release management is better than email.

Brian

]]> By: Stan http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin/comment-page-1#comment-23935 Stan Tue, 11 Dec 2007 04:56:20 +0000 http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin#comment-23935 Curious... you recommend using the jQuery plugin repo for bug tracking over something like Google Code? Curious… you recommend using the jQuery plugin repo for bug tracking over something like Google Code?

]]> By: Marc http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin/comment-page-1#comment-23904 Marc Mon, 10 Dec 2007 20:00:57 +0000 http://www.learningjquery.com/2007/12/managing-the-creative-process-behind-a-jquery-plugin#comment-23904 Even though I eventually found myself completely overwhelmed with emails and comments, they were great modes of communication for my users to easily engage with the project. I think people really liked that I was actively engaging with the people using my plugin, and the result was a really <a title="jQuery UI Datepicker" href="http://marcgrabanski.com/code/ui-datepicker/" rel="nofollow">great datepicker</a>. The feedback got too overwhelming though, and I had to shut comments off - and I still can't keep up with the emails. I think that if you are a plugin author you should just focus on getting the code out to the public and open all doors to public feedback. Revise based on that feedback and then later consider how you, 'shut the doors' so to speak when you get overwhelmed. Communication with your users should be top priority - and I need to get back on that train soon. Even though I eventually found myself completely overwhelmed with emails and comments, they were great modes of communication for my users to easily engage with the project.

I think people really liked that I was actively engaging with the people using my plugin, and the result was a really great datepicker. The feedback got too overwhelming though, and I had to shut comments off – and I still can’t keep up with the emails.

I think that if you are a plugin author you should just focus on getting the code out to the public and open all doors to public feedback. Revise based on that feedback and then later consider how you, ’shut the doors’ so to speak when you get overwhelmed. Communication with your users should be top priority – and I need to get back on that train soon.

]]>