Plugins:PluginDirectory: Difference between revisions
Jump to navigation
Jump to search
(→Hosting: Adding production) |
(→Bugs / TODO: Adding bugzilla link) |
||
| Line 48: | Line 48: | ||
=== Bugs / TODO === | === Bugs / TODO === | ||
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=plugins.mozilla.org File A New Bug] under Websites/plugins.mozilla.org | |||
* https://svn.mozilla.org/projects/plugindir/trunk/TODO.markdown | * https://svn.mozilla.org/projects/plugindir/trunk/TODO.markdown | ||
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;component=plugins.mozilla.org;product=Websites Open plugins.mozilla.org bugs] | * [https://bugzilla.mozilla.org/buglist.cgi?resolution=---;query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;component=plugins.mozilla.org;product=Websites Open plugins.mozilla.org bugs] | ||
Revision as of 20:12, 10 March 2010
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. A knowledgeable site member could add a plugin release describing a new security issue and request a live push.
- 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.
Other Documentation
- Plugins:PluginDirectory/HowPluginDetectionWorks
- Plugins:PluginDirectory/DescribingPluginsAndReleases
- Plugins:PluginDirectory/EditingWorkflow
Hosting
- Production server
- http://plugins.mozilla.org/
- Released via IT ticket specifying the tag
- Staging server
- http://plugins.stage.mozilla.com/
- Updates every 15 minutes from SVN trunk, live plugins re-imported from JSON files checked into SVN.
Source Code
Installation
Bugs / TODO
- File A New Bug under Websites/plugins.mozilla.org
- https://svn.mozilla.org/projects/plugindir/trunk/TODO.markdown
- Open plugins.mozilla.org bugs
- New plugins.mozilla.org bug