3,035
edits
| Line 42: | Line 42: | ||
== Admin Requirements List == | == Admin Requirements List == | ||
Once focus shifts to admin/developer tools, this is a short list of additional features we will need to implement. | Once focus shifts to admin/developer tools, this is a short list of additional features we will need to implement. | ||
{|border=1 | |||
! Task !! Hours | |||
|- | |||
| Solve version comparison and sorting problem using internal versions that are sortable via SQL (best solution at this point) || 8-10 | |||
|- | |||
| Modify all admin CRUD tools to have sort and search capabilities || 20 | |||
|- | |||
| Add compatibility flag and ability to mark something as "verified" by QA || 4 | |||
|- | |||
| Re-implement "trusted" status for Add-on developers who are trusted || 2 | |||
|- | |||
! Add better support for search engine plug-ins | |||
|- | |||
| Create database tables for storing search plug-in meta data || 1 | |||
|- | |||
| Create tools to generate .src files and store them on FTP || 12 | |||
|- | |||
| Create tools to modify and re-save .src files || 6 | |||
|- | |||
! Add better support for XPI management | |||
|- | |||
| Support advanced editing of install.rdf || 20 | |||
|- | |||
| Add ability to open, edit and repackage an .xpi based on updated database information || 25 | |||
|- | |||
| Add improved install.rdf validation and help techniques || 10 | |||
|- | |||
| Find ways to support localization || ? | |||
|- | |||
| Find ways to weight other trust metrics in order to speed up the approval process || ? | |||
|} | |||
== Roadmap == | == Roadmap == | ||
edits