chore: add api-logging to codeowners (#262)

* Add api-logging to codeowners * chore: add api-logging to codeowners * chore: update repo metadata with codeowners

Author: Simon Zeltser

.github/CODEOWNERS

@@ -4,7 +4,7 @@
 # For syntax help see:
 # https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners#codeowners-syntax
 
-* @googleapis/yoshi-java
+* @googleapis/api-logging @googleapis/yoshi-java
 
 # The java-samples-reviewers team is the default owner for samples changes
-samples/**/*.java @googleapis/java-samples-reviewers
+samples/**/*.java @googleapis/api-logging @googleapis/java-samples-reviewers

.repo-metadata.json

@@ -1,6 +1,6 @@
 {
  "name": "clouderrorreporting",
- "name_pretty": "Stackdriver Error Reporting",
+ "name_pretty": "Cloud Error Reporting",
  "product_documentation": "https://cloud.google.com/error-reporting",
  "client_documentation": "https://googleapis.dev/java/google-cloud-errorreporting/latest/",
  "issue_tracker": "https://issuetracker.google.com/savedsearches/559780",
@@ -11,5 +11,6 @@
  "distribution_name": "com.google.cloud:google-cloud-errorreporting",
  "api_id": "clouderrorreporting.googleapis.com",
  "transport": "grpc",
+ "codeowner_team": "@googleapis/api-logging",
  "api_description": "counts, analyzes, and aggregates the crashes in your running cloud services. A centralized error management interface displays the results with sorting and filtering capabilities. A dedicated view shows the error details: time chart, occurrences, affected user count, first- and last-seen dates and a cleaned exception stack trace. Opt in to receive email and mobile alerts on new errors."
 }

CONTRIBUTING.md

@@ -31,14 +31,14 @@ This project follows
 
 To build, package, and run all unit tests run the command
 
-```
+```bash
 mvn clean verify
 ```
 
 ### Running Integration tests
 
 To include integration tests when building the project, you need access to
-a GCP Project with a valid service account. 
+a GCP Project with a valid service account.
 
 For instructions on how to generate a service account and corresponding
 credentials JSON see: [Creating a Service Account][1].
@@ -57,14 +57,15 @@ Code Samples must be bundled in separate Maven modules, and guarded by a
 Maven profile with the name `enable-samples`.
 
 The samples must be separate from the primary project for a few reasons:
+
 1. Primary projects have a minimum Java version of Java 7 whereas samples have
  a minimum Java version of Java 8. Due to this we need the ability to
  selectively exclude samples from a build run.
 2. Many code samples depend on external GCP services and need
  credentials to access the service.
-3. Code samples are not released as Maven artifacts and must be excluded from 
+3. Code samples are not released as Maven artifacts and must be excluded from
  release builds.
-  
+ 
 ### Building
 
 ```bash
@@ -106,13 +107,14 @@ mvn -Penable-samples clean verify
 Code in this repo is formatted with
 [google-java-format](https://github.com/google/google-java-format).
 To run formatting on your project, you can run:
-```
+
+```bash
 mvn com.coveo:fmt-maven-plugin:format
 ```
 
 ### Profile Activation
 
-To include code samples when building and testing the project, enable the 
+To include code samples when building and testing the project, enable the
 `enable-samples` Maven profile.
 
 #### Command line

README.md

@@ -1,6 +1,6 @@
-# Google Stackdriver Error Reporting Client for Java
+# Google Cloud Error Reporting Client for Java
 
-Java idiomatic client for [Stackdriver Error Reporting][product-docs].
+Java idiomatic client for [Cloud Error Reporting][product-docs].
 
 [![Maven][maven-version-image]][maven-version-link]
 ![Stability][stability-image]
@@ -82,7 +82,7 @@ See the [Authentication][authentication] section in the base directory's README.
 
 ### Prerequisites
 
-You will need a [Google Cloud Platform Console][developer-console] project with the Stackdriver Error Reporting [API enabled][enable-api].
+You will need a [Google Cloud Platform Console][developer-console] project with the Cloud Error Reporting [API enabled][enable-api].
 
 [Follow these instructions][create-project] to get your project set up. You will also need to set up the local development environment by
 [installing the Google Cloud SDK][cloud-sdk] and running the following commands in command line:
@@ -93,13 +93,13 @@ You will need a [Google Cloud Platform Console][developer-console] project with
 You'll need to obtain the `google-cloud-errorreporting` library. See the [Quickstart](#quickstart) section
 to add `google-cloud-errorreporting` as a dependency in your code.
 
-## About Stackdriver Error Reporting
+## About Cloud Error Reporting
 
 
-[Stackdriver Error Reporting][product-docs] counts, analyzes, and aggregates the crashes in your running cloud services. A centralized error management interface displays the results with sorting and filtering capabilities. A dedicated view shows the error details: time chart, occurrences, affected user count, first- and last-seen dates and a cleaned exception stack trace. Opt in to receive email and mobile alerts on new errors.
+[Cloud Error Reporting][product-docs] counts, analyzes, and aggregates the crashes in your running cloud services. A centralized error management interface displays the results with sorting and filtering capabilities. A dedicated view shows the error details: time chart, occurrences, affected user count, first- and last-seen dates and a cleaned exception stack trace. Opt in to receive email and mobile alerts on new errors.
 
-See the [Stackdriver Error Reporting client library docs][javadocs] to learn how to
-use this Stackdriver Error Reporting Client Library.
+See the [Cloud Error Reporting client library docs][javadocs] to learn how to
+use this Cloud Error Reporting Client Library.
 
 
 
@@ -122,7 +122,7 @@ To get help, follow the instructions in the [shared Troubleshooting document][tr
 
 ## Transport
 
-Stackdriver Error Reporting uses gRPC for the transport layer.
+Cloud Error Reporting uses gRPC for the transport layer.
 
 ## Java Versions