Muon/2.1: Difference between revisions

From KDE Community Wiki
No edit summary
No edit summary
Line 10: Line 10:
{{FeatureTodoTB|muon-updater|Work on improving muon-updater usability, less dialogs, more automatic stuff happening|aurélien}}
{{FeatureTodoTB|muon-updater|Work on improving muon-updater usability, less dialogs, more automatic stuff happening|aurélien}}
{{FeatureTodoTB|muon-updater|Remove QApt dependencies and make proper use of the AbstractResourcesBackend by enhancing AbstractUpdater|aleix}}
{{FeatureTodoTB|muon-updater|Remove QApt dependencies and make proper use of the AbstractResourcesBackend by enhancing AbstractUpdater|aleix}}
{{FeatureInProgressTB|muon-discover|Improve integration of the GUI into the KDE's look & feel|aleix}}
{{FeatureInProgress|muon-discover|Improve integration of the GUI into the KDE's look & feel|aleix}}
{{FeatureTodoTB|muon-pkbackend|Work on a PackageKit backend, look into how far we can go with a generic backend for a package manager|jonathan}}
{{FeatureTodoTB|muon-pkbackend|Work on a PackageKit backend, look into how far we can go with a generic backend for a package manager|jonathan}}
{{FeatureTodoTB|documentation|Document Backend creation|jonathan}}
{{FeatureTodoTB|documentation|Document Backend creation|jonathan}}
|}
|}
<br>
<br>

Revision as of 16:44, 11 January 2013

Status Project Description Contact


TODO muon-updater Work on improving muon-updater usability, less dialogs, more automatic stuff happening <aurélien>
TODO muon-updater Remove QApt dependencies and make proper use of the AbstractResourcesBackend by enhancing AbstractUpdater <aleix>
IN PROGRESS muon-discover Improve integration of the GUI into the KDE's look & feel
TODO muon-pkbackend Work on a PackageKit backend, look into how far we can go with a generic backend for a package manager <jonathan>
TODO documentation Document Backend creation <jonathan>