Not at all. All I mean is its still up to the developer to write the plugin and develop unit tests. All I mean is that one of the dev team, or some other process that can work, runs over the plugin looking for good code, and any bugs. This means there won't be lots of different "improvments" littering the plugins page - but clear, well coded versions.
As for a roll call, it would just be a matter of interest to find out who is still activly developing and maintainingplugins. If a developer is not working on it anymore, but its useful then its down to the community, devs and normal members to take over. On 7/16/07, Christopher Jordan <[EMAIL PROTECTED]> wrote:
Well, Tane if my understand of "official" is right, that means the plug-in will be maintained by the jQuery dev team even if the original author croaks or otherwise abandons development on the plug-in, and that would mean time they have to spend *not* developing more jQuery Core or UI stuff. I dunno. Just my two-cents on that one. As for a roll call or some documentation on **exactly** how to best use the plug-in repository that would be fine by me. In fact I'd really welcome documentation on the adding and maintaining a plug-in in the repository. :o) I for one know that my most current code isn't there but instead in the RIAForge.org repository. I think I've got a link on the plug-ins page pointing there though... hmmm... maybe I'd better check. ;o) Chris On 7/16/07, Tane Piper <[EMAIL PROTECTED]> wrote: > > > Damn my last email never sent.... > > Maybe its time to do a roll call on plugins. See who is still > developing, and who is not. There are some great plugins out there, > but they haven't been updated for a while. > > The plugin repository is great and currently and underused resource. > Not all plugins are there, not many voted on or commented on, and I > noticed many plugins are using different conventions. > > Maybe it's also time to start running a "seal of approval" program, > where plugins are checked over to see if they are plugins, or scripts > or tests/examples. With good code and good documention, it would nice > to see a few more official plugins added to the lineup. > > > On 7/16/07, Rey Bango <[EMAIL PROTECTED]> wrote: > > > > It was a great question. I know I've been in that pinch and thats why I > > started archiving these emails on my box as well as downloading copies. > > That way, if I like the plugin and the author abandons it, I still have > > the code to update it with. > > > > Rey > > > > Michael E. Carluen wrote: > > > Cool deal, thanks for your offer, Rey... that's awesome. Nothing to > ask > > for > > > now, though. The thought just occurred to me when I saw Alexander's > > > Horizontal Accordion. > > > > > > > > > > > >> -----Original Message----- > > >> From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] > On > > >> Behalf Of Rey Bango > > >> Sent: Monday, July 16, 2007 2:08 PM > > >> To: jquery-en@googlegroups.com > > >> Subject: [jQuery] Re: Plugin Annoucements and Additions to Plugin > Library > > >> > > >> > > >> Hi Michael, > > >> > > >> Its each plugin author's responsibility to submit it to the plugin > repo. > > >> That way, they can add the proper info about the plugin and update it > as > > >> needed. > > >> > > >> With that said, I do my best to keep track of all new plugins and > have > > >> many downloaded. If you ever find yourself in a bind, please don't > > >> hesitate to email me. > > >> > > >> Rey... > > >> > > >> Michael E. Carluen wrote: > > >>> Hello everyone. > > >>> > > >>> > > >>> > > >>> I have always (wrongfully?) assumed that all the plugins announced > on > > >>> the list, gets added to the plugin library by Rey or someone from > the > > >>> evangelism team. That is why I never bookmark the author's plugin > sites > > >>> thinking that I can just find it on the library page of the site > when I > > >>> need it. But like the saying goes, most assumptions are wrong. ? I > am > > >>> curious whether it'll PITA to find some of the awesome plugins I > have > > >>> seen announced here recently. > > >>> > > >>> > > >>> > > >>> My question is who is really responsible for **ensuring** that a new > > >>> plugin is added or "registered" to the plugin library? Can someone > > >>> clarify or verify? > > >>> > > >>> > > >>> > > >>> Thanks, > > >>> > > >>> > > >>> > > >>> Michael > > >>> > > >> -- > > >> BrightLight Development, LLC. > > >> 954-775-1111 (o) > > >> 954-600-2726 (c) > > >> [EMAIL PROTECTED] > > >> http://www.iambright.com > > > > > > > > > > -- > > BrightLight Development, LLC. > > 954-775-1111 (o) > > 954-600-2726 (c) > > [EMAIL PROTECTED] > > http://www.iambright.com > > > > > -- > Tane Piper > http://digitalspaghetti.tooum.net > > This email is: [ ] blogable [ x ] ask first [ ] private > -- -- http://cjordan.us
-- Tane Piper http://digitalspaghetti.tooum.net This email is: [ ] blogable [ x ] ask first [ ] private
