prepare contributing for release, update sample

Author: markxnelson

CONTRIBUTING.md

@@ -1,30 +1,45 @@
----
-
----
-
-# Source Code Submissions 
-We welcome your contributions and look forward to collaborating with you. We can only accept source code repository 
-submissions from users who have signed and returned the Oracle 
-Contributor Agreement. You will find details and the agreement to sign at this OTN web page: 
-[Oracle Contributor Agreement](http://www.oracle.com/technetwork/community/oca-486395.html). 
-
-# Other Contributions
-For all project Submissions other than source code repository contributions, the following also applies: Oracle does 
-not claim ownership of Your Submissions. However, in order to fulfill 
-the purposes of this project, You must give Oracle and all Users 
-the right to post, access, discuss, use, publish, disseminate, and refine 
-Your Submissions. 
-
-In legalese: *You hereby grant to Oracle and all 
-Users a royalty-free, perpetual, irrevocable, worldwide, non-exclusive, 
-and fully sub-licensable right and license, under Your intellectual 
-property rights, to reproduce, modify, adapt, publish, translate, create 
-derivative works from, distribute, perform, display, and use Your 
-Submissions (in whole or part) and to incorporate or implement them in 
-other works in any form, media, or technology now known or later 
-developed, all subject to the obligation to retain any copyright notices 
-included in Your Submissions. All Users, Oracle, and their 
-sublicensees are responsible for any modifications they make to the 
-Submissions of others.*
-
-Copyright © 2017 Oracle and/or its affiliates. All rights reserved.
+# Contributing
+
+Oracle welcomes contributions to this repository from anyone.
+
+If you want to submit a pull request to fix a bug or enhance an existing
+feature, please first open an issue and link to that issue when you
+submit your pull request.
+
+If you have any questions about a possible submission, feel free to open
+an issue too.
+
+## Contributing to the Oracle WebLogic Server Kubernetes Operator repository
+
+Pull requests can be made under
+[The Oracle Contributor Agreement](https://www.oracle.com/technetwork/community/oca-486395.html) (OCA).
+
+For pull requests to be accepted, the bottom of your commit message must have
+the following line using your name and e-mail address as it appears in the
+OCA Signatories list.
+
+```
+Signed-off-by: Your Name <you@example.org>
+```
+
+This can be automatically added to pull requests by committing with:
+
+```
+  git commit --signoff
+```
+
+Only pull requests from committers that can be verified as having
+signed the OCA can be accepted.
+
+### Pull request process
+
+1. Fork this repository
+1. Create a branch in your fork to implement the changes. We recommend using
+the issue number as part of your branch name, e.g. `1234-fixes`
+1. Ensure that any documentation is updated with the changes that are required
+by your fix.
+1. Ensure that any samples are updated if the base image has been changed.
+1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
+what your changes are meant to do and provide simple steps on how to validate
+your changes. Ensure that you reference the issue you created as well.
+We will assign the pull request to 2-3 people for review before it is merged.

samples/weblogicLoggingExporter.yaml

@@ -1,5 +1,5 @@
 /*
- * Copyright (c) 2018 Oracle and/or its affiliates
+ * Copyright (c) 2018, Oracle and/or its affiliates. All rights reserved.
  *
  * Licensed under the Universal Permissive License v 1.0 as shown at http://oss.oracle.com/licenses/upl.
  */
@@ -22,6 +22,11 @@ ElasticSearchHost: localhost
 # The port that Elastic Search is listening to.   Default to 9200
 ElasticSearchPort: 9200
 
+# The "domainUID" used to uniquely identify this domain.  This is used to filter logs in Kibana by the domain they came
+# from.  You should use a unique value for each domain.  If you are using the WebLogic Kubernetes Operator, it is
+# strongly recommended you use the same value as in the domain custom resource.
+domainUid: domain1
+
 # Decide if this exporter should be enabled.  Default is true.   If set to false, nothing will be logged to Elastic Search.
 weblogicLoggingExporterEnabled:  true