Disable/enable echo for enterprise device.

chrome/app/policy/policy_templates.json

 {
 # policy_templates.json - Metafile for policy templates
 #
 # The content of this file is evaluated as a Python expression.
 #
 # This file is used as input to generate the following policy templates:
 # ADM, ADMX+ADML, MCX/plist and html documentation.
 #
 # Policy templates are user interface definitions or documents about the
 # policies that can be used to configure Chrome. Each policy is a name-value
@@ skipping 94 matching lines @@
 #   templates and documentation. The policy definition list that Chrome sees
 #   will include policies marked with 'future'. If a WIP policy isn't meant to
 #   be seen by the policy providers either, the 'supported_on' key should be set
 #   to an empty list.
 #
 # IDs:
 #   Since a Protocol Buffer definition is generated from this file, unique and
 #   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:
 #     $1 -> Google Chrome / Chromium
 #     $2 -> Google Chrome OS / Chromium OS
 #     $3 -> Google Chrome Frame / Chromium Frame
 #     $6 is reserved for doc_writer
 #
 # Device Policy:
 #   An additional flag device_only (optional, defaults to False) indicates
@@ skipping 3743 matching lines @@
       'desc': '''Limit the maximum length of a user session.
 
       When this policy is set, it specifies the length of time after which a user is automatically logged out, terminating the session. The user is informed about the remaining time by a countdown timer shown in the system tray.
 
       When this policy is not set, the session length is not limited.
 
       If you set this policy, users cannot change or override it.
 
       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.
     'win_supported_winxpsp2': {
       'desc': '''A label specifying the oldest possible compatible version of Windows. This text will appear right next to a label containing the text 'Supported on:'.''',
       'text': '''Microsoft Windows XP SP2 or later'''
     },
     'mac_chrome_preferences': {
       'desc': '''A text indicating in Mac OS X Workgroup Manager, that currently the preferences of Chrome are being edited''',
       'text': '''<ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> preferences'''
@@ skipping 82 matching lines @@
       'desc': '''Text appended in parentheses to the policy name to indicate that it has been deprecated''',
       'text': 'deprecated',
     },
     'doc_recommended': {
       'desc': '''Text appended in parentheses next to the policies top-level container to indicate that those policies are of the Recommended level''',
       'text': 'Default Settings (users can override)',
     },
   },
   'placeholders': [],
 }