can`t you put up a test page ^_^ 2007/2/27, Matt Oakes <[EMAIL PROTECTED]>:
Ok I'm going to reply to everyone at once :D First what is and isnt current supported by jqueryplugins.com: > - what is it, what it does Yes in the descriptions. > - demo Currently just a link to the ones that the authors provide but I realize that these link have a tenancy to disappear so I might add them into the site. > - how-to I've added a section where people can add a how to with formatted code examples. > - download Most are linked to the place were the developer host the plugin but eventually I'll add them to the site. > - documentation Currently I have got a full documentation page, just a how to section which often includes more advanced ways of using the plugin > - support Currently not supported. > - changelog Version support is planned but i haven't added it yet. I want to do this before I release it as it will be hard to do once I roll the site out. > - dedicated support forum Not supported yet. I was going to add a comments system but this idea does seem a lot more sensible and manageable. > 1. The "official" list of plugins should get its own page and be clearly > separated from other non-official plugins. They should meet some tough > standards, be updated and supported, and avoid overlapping functionality as > much as possible. It should be clear what is required for a plugin to be > considered "official". Currently not there but could be done easily. > 2. Official plugins should have a common naming convention, always have the > same license as jQuery itself, and follow some similar coding guidelines. > > 3. Documentation should be consistent. There should be a single format which > all plugins should follow - perhaps an enhanced version of jsdoc? This way the > API for every plugin could be published using the same structure and format, > and multiple libraries could be combined and documented together. Thats more of something the core team could encourage people to do, however eventually I'd like to only host plugins that comply to some agreed standards. Any jQuery amin input on this bit? > 5. There should definitely be a ratings system or some way for the best plugins > to quickly rise to the top. From a user perspective, there's nothing worse than > a long list of optional modules like exists now. If a user is looking for a > plugin, they might lack the experience or knowledge to create the functionality > on their own. So how are they supposed to pick the best and most appropriate > plugin to accomplish a task? Those "in the know" need to help them do it by > making the best ones most visible. The planning is there fore the system and will most likely be added before the site comes out. > Hey Matt(s). I'm heading up the effort within the jQuery team to standardize > the way we handle plugins. We've already begun adding meta-data to plugins > to make it easier to automate searches and indexing of plugins in the > subversion repository. I'd be interested in added support for this once its all standardized. Currently the search feature can search by the name, words in the description or the authors name. Meta data would be a great way to make the support even better. > We're also in the process of putting together an official plugin repository > that would be hosted on the jQuery website with many of the same features > that you're suggesting. I'm really excited to see activity on this front > outside of the jQuery core team, and am looking forward to both the official > repository and jqueryplugins.com each having a unique place in the evolving > world of jQuery. Ah I wasn't aware of this. How far into the process are the jQuery team? > 4/ Maintenance process: > Finally, a last thought: when i think about the wordpress plugin repository, > from a nice slick ajaxified central place, it quickly became a plugin > cemetary, with most info being outdated, plugins not being usable anymore. > So i wonder: should each publisher maintain its own plugins information on > the repository, or better have an administrator team behind taking in charge > the website content maintenance? I guess i would favor a way in between, > with plugins authors having control on their plugins, but with > administrators people behind that can curate what is being published (maybe > a link "report outdated content to the administrators" on each plugin page, > so that administrators have users as error / dead content detectors :) ). > Since we all have a life to earn, do you plan to "recruit" among good > willing jquerians potential moderators to become this administration team? I do plan on have an authors interface, all-though currently there isn't one. The plugins will be added by the admins (read: me) until i can sort something out. Moderation is planned with report dead links and the like but not currently in place. I'll be posting back with some more comments on this soon, I'm off now to add version support :P Should have added it earlier in hindsight :S Matt _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
_______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
