Redesign restricted-manager code

Registered by Martin Pitt on 2007-10-18

The original code architecture of restricted-manager was very narrow, focusing on non-free kernel drivers in a Gnome application. A lot of new features have been bolted on this original structure, such as the KDE frontend, grouping of handlers, support for firmware installation, or non-free support packages of drivers which are free by themselves. This made the code very interdependent and hard to maintain/bugfix/understand.

We review the list of existing and proposed features and create a new code architecture which will be rewritten from scratch (with reusing most of the existing code modules, of course).

Blueprint information

Status:
Complete
Approver:
Scott James Remnant (Canonical)
Priority:
Medium
Drafter:
Martin Pitt
Direction:
Needs approval
Assignee:
Martin Pitt
Definition:
Approved
Series goal:
Accepted for hardy
Implementation:
Implemented
Milestone target:
None
Started by
Martin Pitt on 2007-11-28
Completed by
Martin Pitt on 2008-04-18

Related branches

Sprints

Whiteboard

jockey is in hardy, and being tested and fixed. Compared to gutsy's rm, the following things are still missing:
 - KDE port, Martin Bohm is working on it
 - broadcom wifi hander (easy to implement)

2008-04-18, pitti:
 - above two issues were implemented a few weeks ago, features in hardy (ubuntu branch) are on par with old restricted-manager
 - code is much more manageable now, has full test coverage (including UI), and much more modular
 - contact with other distros has been established (http://www.linux-foundation.org/en/Driver_Backport), RedHat and SuSE want to adopt jockey, RH is actively working on the port and a network driver DB
 - code for network driver DB handling is implemented in 'remotedb' branch (not for hardy final, though).
This covers everything mentioned in the spec, so marking as implemented.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.