Adding issue templates for repo

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,61 @@
+---
+name: Bug Report
+about: If things aren't working as expected.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Bug Report
+
+<!--
+Thanks for filing an issue! Before hitting the button, please answer these questions.
+Fill in as much of the template below as you can. If you leave out information, we can't help you as well.
+
+Note: Make sure to first check the prerequisites that can be found in the main README.md file!
+-->
+
+#### What did you do?
+
+<!-- A clear and concise description of the steps you took (or insert a code snippet). -->
+
+#### What did you expect to see?
+
+<!-- A clear and concise description of what you expected to happen (or insert a code snippet). -->
+
+#### What did you see instead? Under which circumstances?
+
+<!-- A clear and concise description of what you expected to happen (or insert a code snippet). -->
+
+#### Environment
+
+**Operator type:**
+
+<!-- Uncomment the following line corresponding to the Java language of the operator type -->
+
+<!-- /language java -->
+
+**Kubernetes cluster type:**
+
+<!-- The type of cluster used for testing/deployment, ex. "vanilla", "OpenShift" -->
+
+`$ operator-sdk version`
+
+<!-- Insert the output of `operator-sdk version` here. -->
+
+`$ java -version` (if language is Java)
+
+<!-- Insert the output of `java -version` here -->
+
+`$ kubectl version`
+
+<!-- Insert the output of `kubectl version` here -->
+
+#### Possible Solution
+
+<!-- Only if you have suggestions on a fix for the bug -->
+
+#### Additional context
+
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,24 @@
+---
+name: Feature Request
+about: Suggest a feature
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Feature Request
+
+#### Describe the problem you need a feature to resolve.
+
+<!--
+A clear and concise description of what the problem is. Example:
+
+I have an issue when ...
+-->
+
+#### Describe the solution you'd like.
+
+<!-- A clear and concise description of what you want to happen. Add any considered drawbacks. -->
+
+<!-- /language java -->

.github/ISSUE_TEMPLATE/support-question.md

@@ -0,0 +1,67 @@
+---
+name: Support Question
+about: Any support questions you might have.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+Thanks for filing an issue! Before hitting the button, please answer these questions.
+
+Fill in as much of the template below as you can. If you leave out information, we can't help you as well.
+
+We will try our best to answer the question, but we also have a mailing list and slack channel for any other questions.
+-->
+
+## Type of question
+
+<!-- Uncomment one or more of the following lines depending on what you are asking about: -->
+
+<!-- Best practices -->
+<!-- How to implement a specific feature -->
+<!-- General operator-related help -->
+<!-- Open question -->
+
+## Question
+
+#### What did you do?
+
+<!-- A clear and concise description of the steps you took (or insert a code snippet). -->
+
+#### What did you expect to see?
+
+<!-- A clear and concise description of what you expected to happen (or insert a code snippet). -->
+
+#### What did you see instead? Under which circumstances?
+
+<!-- A clear and concise description of what you expected to happen (or insert a code snippet). -->
+
+#### Environment
+
+**Operator type:**
+
+<!-- Uncomment the following line corresponding to the Java language of the operator type -->
+
+<!-- /language java -->
+
+**Kubernetes cluster type:**
+
+<!-- The type of cluster used for testing/deployment, ex. "vanilla", "OpenShift" -->
+
+`$ operator-sdk version`
+
+<!-- Insert the output of `operator-sdk version` here. -->
+
+`$ java -version` (if language is Java)
+
+<!-- Insert the output of `go version` here -->
+
+`$ kubectl version`
+
+<!-- Insert the output of `kubectl version` here -->
+
+#### Additional context
+
+<!-- Add any other context about the question here. -->

CONTRIBUTING.md

@@ -1,14 +1,22 @@
 # How to contribute
 
-Operator SDK is Apache 2.0 licensed and accepts contributions via GitHub pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers, and other resources to help get contributions into operator-sdk.
+Java Operator is Apache 2.0 licensed and accepts contributions via GitHub pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers, and other resources to help get contributions into the Java Operator.
+
+## Email and Chat
+
+- Email: [operator-framework][operator_framework]  
 
 ## Getting started
 
 - Fork the repository on GitHub
+    https://github.com/operator-framework/java-operator.git
+
+- If you want to build/run the project, use command
+    `TBD`
 
 ## Reporting bugs and creating issues
 
-Reporting bugs is one of the best ways to contribute.
+Reporting bugs is one of the best ways to contribute. However, a good bug report has some very specific qualities, so please read over our short document on reporting issues before submitting a bug report. This document might contain links to known issues, another good reason to take a look there before reporting a bug.
 
 ## Contribution flow
 
@@ -17,6 +25,8 @@ This is a rough outline of what a contributor's workflow looks like:
 - Create a topic branch from where to base the contribution. This is usually master.
 - Make commits of logical units.
 - Make sure commit messages are in the proper format (see below).
+- Check your work after running all Unit and Regression Tests. You should run all the unit tests by hitting the following command
+    `TBD`
 - Push changes in a topic branch to a personal fork of the repository.
 - Submit a pull request to operator-framework/operator-sdk.
 - The PR must receive a LGTM from two maintainers found in the MAINTAINERS file.
@@ -25,7 +35,7 @@ Thanks for contributing!
 
 ### Code style
 
-The coding style suggested by the Golang community is used in operator-sdk. See the [style doc][golang-style-doc] for details.
+The coding style suggested by the Java community is used in Java operator. See the [style doc](https://google.github.io/styleguide/javaguide.html) for details.
 
 Please follow this style to make operator-sdk easy to review, maintain and develop.
 
@@ -55,6 +65,14 @@ The format can be described more formally as follows:
 
 The first line is the subject and should be no longer than 70 characters, the second line is always blank, and other lines should be wrapped at 80 characters. This allows the message to be easier to read on GitHub as well as in various git tools.
 
+### PR Review
+
+Your PR will get reviewed soon from the maintainers of the project. If they suggest changes, do all the changes, commit the changes, rebase the branch, squash the commits and push the changes. If all is fine, your PR will be merged.
+
+That's it! Thank you for your contribution!
+
+Feel free to suggest changes to this documentation. If you want to discuss something with maintainers, you can ask us on a GitHub [issue](https://github.com/operator-framework/java-operator/issues)
+
 ## Documentation
 
-If the contribution changes the existing APIs or user interface it must include sufficient documentation to explain the use of the new or updated feature. 
+If the contribution changes the existing APIs or user interface it must include sufficient documentation to explain the use of the new or updated feature.