Features/Optional adhoc autoconnect - Revision history

Godiard at 19:40, 20 April 2015

2015-04-20T19:40:36Z

← Older revision		Revision as of 15:40, 20 April 2015
Line 1:		Line 1:
	<noinclude>		<noinclude>
	[[Category:~~Feature~~\|Optional Adhoc Autoconnect]]		[[Category:FeatureLanded\|Optional Adhoc Autoconnect]]
	~~[[Category:Feature Page Incomplete~~]]
	</noinclude>		</noinclude>

Tch: /* User Experience */

2014-09-04T20:01:08Z

User Experience

← Older revision		Revision as of 16:01, 4 September 2014
Line 38:		Line 38:

	== User Experience ==		== User Experience ==
	~~User~~ experienced is untouched.		The new configuration will preserve the current behaviour by default, therefore the user experienced is untouched.

Tch: /* Detailed Description */

2014-09-02T22:20:14Z

Detailed Description

← Older revision		Revision as of 18:20, 2 September 2014
Line 20:		Line 20:
	''This proposal is based around the needs of the OLPC project in Australia, but reflects a common need (current or future) of other OLPC implementations as well.''		''This proposal is based around the needs of the OLPC project in Australia, but reflects a common need (current or future) of other OLPC implementations as well.''

	'''The problem:''' Having hundreds or thousands of sugar clients creating or connecting to these adhoc networks by default is not necessary a desirable behavior, specially considering that only a few of these ~~could~~ actually be using collaboration.		'''The problem:''' Having hundreds or thousands of sugar clients creating or connecting to these adhoc networks by default is not necessary a desirable behavior, specially considering that only a few of these are actually using collaboration.

	The proposed solution is to provide a system configuration so this behavior can become optional and not mandatory as it is now.		The proposed solution is to provide a system configuration so this behavior can become optional and not mandatory as it is now.

Tch at 22:19, 2 September 2014

2014-09-02T22:19:35Z

← Older revision		Revision as of 18:19, 2 September 2014
Line 22:		Line 22:
	'''The problem:''' Having hundreds or thousands of sugar clients creating or connecting to these adhoc networks by default is not necessary a desirable behavior, specially considering that only a few of these could actually be using collaboration.		'''The problem:''' Having hundreds or thousands of sugar clients creating or connecting to these adhoc networks by default is not necessary a desirable behavior, specially considering that only a few of these could actually be using collaboration.

	The proposed solution is to provide a ~~way a~~ configuration so this behavior can become optional and not mandatory as it is now.		The proposed solution is to provide a system configuration so this behavior can become optional and not mandatory as it is now.

	== Benefit to Sugar ==		== Benefit to Sugar ==

	Make ~~sure~~ friendlier with the spectrum and save device battery.		Make Sugar friendlier with the spectrum and save device battery.

	== Scope and implementation ==		== Scope and implementation ==

Tch: Created page with " Optional Adhoc Autoconnect Category:Feature Page Incomplete == Summary == Add a new configuration to disable adhoc autoconn..."

2014-09-02T15:31:44Z

Created page with "<noinclude> Optional Adhoc Autoconnect Category:Feature Page Incomplete </noinclude> == Summary == Add a new configuration to disable adhoc autoconn..."

New page

<noinclude>
[[Category:Feature|Optional Adhoc Autoconnect]]
[[Category:Feature Page Incomplete]]
</noinclude>

== Summary ==

Add a new configuration to disable adhoc autoconnect policy.

== Owner ==
* Martin Abente Lahaye

== Current status ==
* Targeted release: 0.104
* Last updated: 02/09/2014
* Percentage of completion: 100%

== Detailed Description ==

''This proposal is based around the needs of the OLPC project in Australia, but reflects a common need (current or future) of other OLPC implementations as well.''

'''The problem:''' Having hundreds or thousands of sugar clients creating or connecting to these adhoc networks by default is not necessary a desirable behavior, specially considering that only a few of these could actually be using collaboration.

The proposed solution is to provide a way a configuration so this behavior can become optional and not mandatory as it is now.

== Benefit to Sugar ==

Make sure friendlier with the spectrum and save device battery.

== Scope and implementation ==

The implementation can be found in [https://github.com/tchx84/sugar/commit/46c78e4b4e1a92a157f33d635567577f5270dc35 here]. The changes are:

* include a new configuration to sugar settings.
* check this configuration value before auto-connecting.

This implementation will preserve the current behaviour by default. Deployment will be require to use the configuration in order to disable the auto connect policy.

== User Experience ==
User experienced is untouched.