tree: d309f9bfd227d624701673333b6b2098fb5da67b [path history] [tgz]
  1. browser_management/
  2. client_certificates/
  3. connectors/
  4. core/
  5. data_controls/
  6. data_protection/
  7. identifiers/
  8. idle/
  9. incognito/
  10. platform_auth/
  11. profile_management/
  12. remote_commands/
  13. reporting/
  14. signals/
  15. signin/
  16. test/
  17. util/
  18. watermark/
  19. webstore/
  20. chrome_browser_main_extra_parts_enterprise.cc
  21. chrome_browser_main_extra_parts_enterprise.h
  22. DEPS
  23. DIR_METADATA
  24. OWNERS
  25. README.md
chrome/browser/enterprise/README.md

About //chrome/browser/enterprise/

This directory is used for enterprise or edu related features and util functions.

Creating new sub-directory

  • Each new feature needs to be in its own sub-directory.
  • Each new feature needs to be in its own namespace that begins with enterprise_.
  • Sub-directory should be owned by the feature owners.

What does not belong here

  • Code that does not belong to //chrome/browser/.
  • Code that is related to policy loading and applying. It should be put into //components/policy/ or //chrome/browser/(chromeos/)policy/.
  • Code that fits in a more narrow context. This includes most of the policy implementations.

Responsibilities of //chrome/browser/enterprise/OWNERS

  • Reviewing new features.
  • Reviewing large scale refactoring.
  • Maintaining util functions that don't have owners.