Disable/enable echo for enterprise device.

chrome/app/policy/policy_templates.json

Index: chrome/app/policy/policy_templates.json
diff --git a/chrome/app/policy/policy_templates.json b/chrome/app/policy/policy_templates.json
index 3f3f44dc299c1b9f274a60453e08ce0fb6523aae..56bb35376565472615c015cacb64f075dc6ed3f3 100644
--- a/chrome/app/policy/policy_templates.json
+++ b/chrome/app/policy/policy_templates.json
@@ -112,7 +112,7 @@
 #   persistent IDs for all fields (but not for groups!) are needed. These are
 #   specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs,
 #   because doing so would break the deployed wire format!
-#   For your editing convenience: highest ID currently used: 171
+#   For your editing convenience: highest ID currently used: 172
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
@@ -3876,6 +3876,26 @@
 
       The policy value should be specified in milliseconds. Values are clamped to a range of 30 seconds to 24 hours.''',
     },
+    {
+      'name': 'DeviceChromeOsRegistrationEnabled',

[oscarpan, 2013/02/02 01:50:56]

The policy was named ***Disabled, but presubmit checks complained about the
naming convention to be XYZEnabled. So I updated accordingly. However, the
extension api is still left as ***Disabled b/c it fits the logic better. 

[xiyuan, 2013/02/02 07:49:27]

Please update extension api as well. I found it's a bit confusing to read
through the CL.

[oscarpan, 2013/02/02 21:52:35]

Ok, I will fix it in my new patch.

+      'type': 'main',
+      'schema': { 'type': 'boolean' },
+      'supported_on': ['chrome.*:26-'],

[Mattias Nissler (ping if slow), 2013/02/04 09:06:19]

Shouldn't this be 'chrome_os.*:26-'?

[oscarpan, 2013/02/05 00:17:47]

Done.

+      'device_only': True,
+      'features': {
+        'dynamic_refresh': True,
+      },
+      'example_value': True,
+      'id': 172,
+      'caption': '''Enable Chrome OS Registration''',
+      'desc': '''Enable Chrome OS Registration.

[Mattias Nissler (ping if slow), 2013/02/04 09:06:19]

So "Chrome OS Registration" is the official term for ECHO? I think that's kind
of unfortunate naming, as an admin I'd have no idea what this thing is. Can you
add one sentence to the description that recaps the high-level idea behind ECHO?

[oscarpan, 2013/02/05 00:17:47]

Done.

+
+      If this policy is set to true, Chrome OS Registration will be enabled.
+
+      If this policy is set to false, Chrome OS Registration will be disabled, and user will not be able to use Goodies to redeem offers.

[Mattias Nissler (ping if slow), 2013/02/04 09:06:19]

Playing dump admin again: What are Goodies and offers?

[oscarpan, 2013/02/05 00:17:47]

Done.

+
+      If this policy is left not set, Chrome OS Registration will not be disabled.''',

[xiyuan, 2013/02/02 07:49:27]

I don't understand this. "will no be disabled" means "will be enabled"?

[oscarpan, 2013/02/02 21:52:35]

Yes, I mean "will be enabled", will fix it in my new patch.

[Mattias Nissler (ping if slow), 2013/02/04 09:06:19]

If there's no difference between set to true and unset, merge the two sentences.

[oscarpan, 2013/02/05 00:17:47]

Done.

[oscarpan, 2013/02/05 00:17:47]

Done.

+    },
   ],
   'messages': {
     # Messages that are not associated to any policies.