List common packages that are org-specific or non-conformant (#1157)

Fixes #1142

Author: jskeet

aip/general/0213.md

@@ -41,6 +41,11 @@ requirements, or be too complex for general use.
   `google.geo.type` or `google.shopping.type`.
 - Organizations **must** consult the API design team before creating a new
   organization-wide common component package.
+- Organization-wide common component packages **must** be published in [the
+  `googleapis` repository](https://github.com/googleapis/googleapis).
+- Organizations creating and publishing a new organization-wide common component
+  package **must** update this AIP to include it in the
+  [list below](#existing-organization-specific-common-component-packages).
 - Organizations **must not** define generic components in organization-specific
   common component packages, instead preferring global common components.
 - Common components **must not** be "moved" (that is, deleted from one common
@@ -157,6 +162,37 @@ Occasionally, it may be useful to add protos to these packages or to add to the
 list of commonly-available protos. In order to do this, [open an issue][] on
 the AIP repository in GitHub, noting the guidelines above.
 
+## Existing organization-specific common component packages
+
+The following organization-specific common component packages exist and conform with the above guidance:
+
+- [`google.apps.script.type`](https://github.com/googleapis/googleapis/tree/master/google/apps/script/type)
+  Common component package for Google Apps Script.
+- [`google.geo.type`](https://github.com/googleapis/googleapis/tree/master/google/geo/type)
+  Common component package for Google Maps and the Geo organization.
+- [`google.actions.type`](https://github.com/googleapis/googleapis/tree/master/google/actions/type)
+  Common component package for Actions on Google APIs.
+
+## Non-conformant common component packages
+
+The following common component packages exist, but do not conform with the above guidance,
+and do not form a precedent for further such packages.
+
+- [`google.cloud.common`](https://github.com/googleapis/googleapis/tree/master/google/cloud/common):
+  This does not conform to the requirement for the package name to end in `.type`. (This would otherwise
+  be acceptable, and this package should be considered as the Cloud common component package.)
+- [`google.logging.type`](https://github.com/googleapis/googleapis/tree/master/google/logging/type):
+  This appears to be API-specific, although it's used from multiple APIs; some aspects should probably
+  be global or in a Cloud common component package.
+- [`google.cloud.workflows.type`](https://github.com/googleapis/googleapis/tree/master/google/cloud/workflows/type):
+  API-specific types.
+- [`google.cloud.oslogin.common`](https://github.com/googleapis/googleapis/tree/master/google/cloud/oslogin/common):
+  API-specific types, and a non-conformant name.
+- [`google.identity.accesscontextmanager.type`](https://github.com/googleapis/googleapis/tree/master/google/identity/accesscontextmanager/type):
+  API-specific types.
+- [`google.networking.trafficdirector.type`](https://github.com/googleapis/googleapis/tree/master/google/networking/trafficdirector/type):
+  API-specific types.
+
 ## Rationale
 
 Common components are effectively unversioned: APIs evolve independently of