Changes/Plasma-nm

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
(Detailed Description)
(Benefit to Fedora)
Line 57: Line 57:
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 +
 +
Plasma NM provides a modern and intuitive interface to configure network connections, add new ones (like VPNs) and edit them in a user-friendly way. Unlike the existing applet, its codebase is much cleaner and smaller (~50%) and therefore easier to maintain and develop in the long term. The UI itself is written entirely in QML, making it reusable in other interfaces like Plasma Active and bringing in line with the rest of the Plasma Workspace.
  
 
== Scope ==
 
== Scope ==

Revision as of 09:46, 16 July 2013


Contents

Plasma-nm

Summary

Replace current network applet in KDE with a new one and bring the latest news in NetworkManager to KDE.

Owner

Current status

  • Targeted release: Fedora 20
  • Last updated: 2013-07-16
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Plasma-nm is a new plasma applet for network management in KDE which uses the latest KDE technologies. It supports all connection types from NetworkManager like bonding, bridging etc. and it's simplier to maintain it than the old one. It absoletes the old network applet which is hardly maintainable.

Benefit to Fedora

Plasma NM provides a modern and intuitive interface to configure network connections, add new ones (like VPNs) and edit them in a user-friendly way. Unlike the existing applet, its codebase is much cleaner and smaller (~50%) and therefore easier to maintain and develop in the long term. The UI itself is written entirely in QML, making it reusable in other interfaces like Plasma Active and bringing in line with the rest of the Plasma Workspace.

Scope

  • Proposal owners:
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)

Release Notes