Plugins:PluginDirectory: Difference between revisions
Jump to navigation
Jump to search
LesOrchard (talk | contribs) |
LesOrchard (talk | contribs) (→Goals) |
||
| Line 20: | Line 20: | ||
** Provide tools for editing plugin information for plugin vendors and other interested parties in personal sandboxes. | ** Provide tools for editing plugin information for plugin vendors and other interested parties in personal sandboxes. | ||
*** eg. Trusted vendors could potentially submit updates to a protected API during an automated release process. | *** eg. Trusted vendors could potentially submit updates to a protected API during an automated release process. | ||
** Provide editorial | ** Provide editorial workflow (ie. for Mozilla employees, trusted vendors) to manage anonymous submissions and plugin data changes from registered members. | ||
*** Promote changes from personal sandboxes to live public view | *** Promote changes from personal sandboxes to live public view | ||
Revision as of 23:36, 22 December 2009
Plugin Directory
The main purpose of this project is to build and maintain a public directory of browser plugins, for both human consumption as well as for machines to use as a finder and update check service.
Goals
- As a directory:
- Offer a human browsable and searchable directory of plugins and releases.
- Like PluginDoc.mozdev.org, but more dynamic and easier to keep updated.
- Offer a machine-queryable API to search plugins and releases.
- See also: PFS2
- Power things like Plugins:PluginCheck
- Usable to find plugins for unknown content types.
- Usable to check for version updates or security alerts.
- Offer a human browsable and searchable directory of plugins and releases.
- Keeping things up-to-date:
- Allow anonymous submission of data detected on plugins in a user's browser.
- Simple submission of detected browser information (eg. locale, version, build ID, name) combined with plugin information (eg. name, version, description, filename).
- Provide tools for editing plugin information for plugin vendors and other interested parties in personal sandboxes.
- eg. Trusted vendors could potentially submit updates to a protected API during an automated release process.
- Provide editorial workflow (ie. for Mozilla employees, trusted vendors) to manage anonymous submissions and plugin data changes from registered members.
- Promote changes from personal sandboxes to live public view
- Allow anonymous submission of data detected on plugins in a user's browser.
Hosting
- Temporary demo, to be replaced soon:
Source Code
Installation
Bugs / TODO
- https://svn.mozilla.org/projects/plugindir/trunk/TODO.markdown
- Open plugins.mozilla.org bugs
- New plugins.mozilla.org bug