Changes

<noinclude>

<noinclude>

[[Category:Feature Page Incomplete]]

[[Category:Feature Page Incomplete]]

[[Category:Feature|.]]

[[Category:Feature|WPA]]

<!-- You can add categories to tie features back to real deployments/schools requesting them, for example  

<!-- You can add categories to tie features back to real deployments/schools requesting them, for example  

[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->

[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->

== Current status ==

== Current status ==

* Targeted release: (SUGAR_VERSION)

* Targeted release: Not Specified

* Last updated: (DATE)

* Last updated: December 14, 2011

* Percentage of completion: XX%

* Percentage of completion: 100% (tentative, subject to LEAP-authentication testing. Codewise, it seems to be complete. Obviously, any bugs/enhancements are not being considered here).

== Detailed Description ==

== Detailed Description ==

''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.''

WPA/WPA2-Enterprise Networks are just another kind of networks, requiring secured-authentication. This feature helps connect to such networks, which require authentication following the RADIUS protocol.

== Benefit to Sugar ==

== Benefit to Sugar ==

''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''

This is an extension to the sugar-capability, to connect to wireless-networks.

This feature has been originally requested from Australia deployment.

== Scope ==

== Scope ==

''What work do the 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?''

This is an isolated change. Non-completion of this feature will just prevent the users from connecting to WPA/WPA2-Enterprise networks.

==UI Design==

==UI Design==

''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''

There is no impact on the workflow; it's just that the user will have to enter way more parameters for conencting to a WPA/WPA2-Enterprise networks. Please see "User Experience" section for details.

== How To Test ==

== How To Test ==

{{:{{PAGENAME}}/Testing}}

{{:{{PAGENAME}}/Testing}}

== User Experience ==

== User Experience ==

''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''

* Upon clicking the 'ok' button (and provided all sufficient-and-correct parameters are provided), the connection will be made. This can be confirmed by the tray-icon.

* Once a connection is made, user need not re-enter parameters-cum-secrets next time (reboot) onwards. The parameters-cum-secrets will automatically be read from sugar-settings-file (connections.cfg) (just like any other network-type).

 

** network should auto-connect, when the wirless radio is turned off, and then turned on again.

== Dependencies ==

== Dependencies ==

''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time?  Other upstream projects like Python?''

There are no external dependencies. This feature is just an addon, with just another network-type being added to the list of "connectable" networks.

== 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 "None necessary, revert to previous release behaviour."  Or it might not.  If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

None necessary, revert to previous release behaviour.

== Documentation ==

== Documentation ==

''Is there upstream documentation on this feature, or notes you have written yourself?  Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

Discussions are on, on the "sugar-devel-" and "dextrose-" mailing lists.

== Release Notes ==

== Release Notes ==

''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release.''

There are no changes in ABIs/APIs, configuration or data file formats.

Also, there are no upgrade concerns.

== Comments and Discussion ==

== Comments and Discussion ==

* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->

* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->