Features/WPA-WPA2-Enterprise-Network-Connections - Revision history

Ajay Garg: /* Use-Cases That need to pass */

2012-10-10T05:56:05Z

Use-Cases That need to pass

← Older revision		Revision as of 01:56, 10 October 2012
Line 45:		Line 45:
	* 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).		* 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).

	== Use-Cases That need to pass ==		== Use-Cases That need to pass (thanks Sridhar Dhanapalan for the exhaustive list) ==
	* Network should connect, provided the credentials are correct (base-case).		* Network should connect, provided the credentials are correct (base-case).
	* Thereafter,		* Thereafter,
	** network should auto-connect, ~~upon reboot~~.		** network should auto-connect, when XO reboots.
	** network should auto-connect, ~~upon resume~~-from-~~suspend~~.		** network should auto-connect, when XO resumes from being suspended.
			** network should auto-connect, when XO wakes up from Automatic Power Management.
			** network should auto-connect, when the wirless radio is turned off, and then turned on again.

	== Dependencies ==		== Dependencies ==

Ajay Garg at 05:51, 10 October 2012

2012-10-10T05:51:08Z

← Older revision		Revision as of 01:51, 10 October 2012
Line 44:		Line 44:
	* 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.		* 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).		* 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).

			== Use-Cases That need to pass ==
			* Network should connect, provided the credentials are correct (base-case).
			* Thereafter,
			** network should auto-connect, upon reboot.
			** network should auto-connect, upon resume-from-suspend.

	== Dependencies ==		== Dependencies ==

FGrose: sort in category list

2012-07-07T14:14:16Z

sort in category list

← Older revision		Revision as of 10:14, 7 July 2012
Line 1:		Line 1:
	<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>). -->

Ajay Garg at 14:54, 14 December 2011

2011-12-14T14:54:44Z

← Older revision		Revision as of 10:54, 14 December 2011
Line 32:		Line 32:

	== 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==

Ajay Garg at 14:52, 14 December 2011

2011-12-14T14:52:59Z

← Older revision		Revision as of 10:52, 14 December 2011
Line 24:		Line 24:

	== 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.

	~~''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''~~

	== Scope ==		== Scope ==

Ajay Garg at 14:48, 14 December 2011

2011-12-14T14:48:57Z

← Older revision		Revision as of 10:48, 14 December 2011
Line 19:		Line 19:

	== 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 ==

Ajay Garg at 13:13, 14 December 2011

2011-12-14T13:13:31Z

← Older revision		Revision as of 09:13, 14 December 2011
Line 46:		Line 46:

	== 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. -->

Ajay Garg at 13:08, 14 December 2011

2011-12-14T13:08:59Z

← Older revision		Revision as of 09:08, 14 December 2011
Line 35:		Line 35:

	==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~~.''		* The network-icon for a WPA/WPA2-Enterprise Network, will appear just like any other network-icon, in the Neighbourhood-view.
			* When a user clicks on the icon, she will be asked for parameters-cum-secrets (much more in number, but just like any other network-type).
			* 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).

	== Dependencies ==		== Dependencies ==

Ajay Garg at 11:43, 14 December 2011

2011-12-14T11:43:59Z

← Older revision		Revision as of 07:43, 14 December 2011
Line 5:		Line 5:
	[[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>). -->
	</noinclude>		</noinclude>

	~~'''Comments and Explanations:'''~~

	There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy\|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''

	<!-- All fields on this form are required to be accepted.		<!-- All fields on this form are required to be accepted.

Ajay Garg: /* Owner */

2011-12-14T10:52:07Z

Owner

← Older revision		Revision as of 06:52, 14 December 2011
Line 19:		Line 19:

	== Owner ==		== Owner ==
	~~''This should link to your home wiki page so we know who you are''~~
	* Name: [[User:ajay\| Ajay Garg]], [[User:anish\| Anish Mangal]], [[User:silbe\| Sascha Silbe]]		* Name: [[User:ajay\| Ajay Garg]], [[User:anish\| Anish Mangal]], [[User:silbe\| Sascha Silbe]]
			* Email: ajay@activitycentral.com, anish@activitycentral.com, silbe@activitycentral.com
	~~''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''~~
	* Email: ~~<your email address so we can contact you~~, ~~invite you to meetings~~, ~~etc~~.>

	== Current status ==		== Current status ==