From Fedora Project Wiki
(Add tracker bug)
 
(11 intermediate revisions by 2 users not shown)
Line 49: Line 49:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=998531 #998531]


== Detailed Description ==
== Detailed Description ==
Line 61: Line 61:


== Scope ==
== Scope ==
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
This feature affects only KDE. The only necessary action is to remove and obsolete the ''kde-plasma-networkmanagement'' package and ensure that ''kde-plasma-nm'' is installed by default.
 
* Proposal owners:
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
 
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
Network connections (including secrets stored in KWallet) are automatically migrated to the new applet.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== How To Test ==
== How To Test ==
Line 100: Line 85:


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
Users can benefit from a streamlined and highly usable[1] QML interface to handle their network connections.
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
N/A (not a System Wide Change)
[1] http://www.youtube.com/watch?v=FjuVND3VAoM


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
Plasma NM depends on ''NetworkManager'' and ''ModemManager'' packages.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Contingency Plan ==
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
No plan is necessary. KDE SC would be shipped with the current network management applet (''kde-plasma-networkmanagement'').
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== Documentation ==
== Documentation ==
Line 131: Line 108:
-->
-->


[[Category:ChangePageIncomplete]]
This release features Plasma NM, providing a modern and intuitive interface to configure network connections, adding new ones (like VPNs) and editting them in a user-friendly way.
 
[[Category:ChangeAcceptedF20]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 12:25, 20 August 2013


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

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

This feature affects only KDE. The only necessary action is to remove and obsolete the kde-plasma-networkmanagement package and ensure that kde-plasma-nm is installed by default.

Upgrade/compatibility impact

Network connections (including secrets stored in KWallet) are automatically migrated to the new applet.

How To Test

N/A (not a System Wide Change)

User Experience

Users can benefit from a streamlined and highly usable[1] QML interface to handle their network connections.

[1] http://www.youtube.com/watch?v=FjuVND3VAoM

Dependencies

Plasma NM depends on NetworkManager and ModemManager packages.

Contingency Plan

No plan is necessary. KDE SC would be shipped with the current network management applet (kde-plasma-networkmanagement).

Documentation

N/A (not a System Wide Change)

Release Notes

This release features Plasma NM, providing a modern and intuitive interface to configure network connections, adding new ones (like VPNs) and editting them in a user-friendly way.

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Plasma-nm&oldid=349938"