Project setup.

.ge_ignore

@@ -0,0 +1,34 @@
+**/*go-earlybird*
+**/*.jpg
+**/*.png
+**/*.bmp
+**/*.svg
+**/*.mp3
+**/*.wav
+**/*.ogg
+**/*.gif
+**/*.tif
+**/*.tiff
+**/*.psd
+**/*.xcf
+**/*.gz
+**/*.tar
+**/*.7z
+**/*.pyc
+**/*.git*
+**/*.svn*
+**/*vendor*
+**/bin/*
+**/binaries/*
+**/pom.xml*
+**/release.properties
+**/dependency-reduced-pom.xml
+**/*.DS_Store
+**/.classpath
+**/.checkstyle
+**/*.class
+**/*hs_err_pid*
+**/.idea
+**/*.iml
+**/*.vertx
+**/README.md

.github/ISSUE_TEMPLATE/bug_report_template.md

@@ -0,0 +1,50 @@
+name: Bug Report
+description: File a bug report
+title: "[Bug]: "
+labels: ["bug"]
+projects: ["americanexpress/connectchain"]
+assignees:
+  - none
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. [email protected]
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: version
+    attributes:
+      label: Version
+      description: What version of our software are you running?
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](../../CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request_template.md

@@ -0,0 +1,58 @@
+name: Feature Request
+description: Create a request for a new feature or functionality
+title: "[Feature]: "
+labels: ["feature"]
+projects: ["americanexpress/connectchain"]
+assignees:
+  - none
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to request a new feature!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. [email protected]
+    validations:
+      required: false
+  - type: textarea
+    id: feature-description
+    attributes:
+      label: Please describe the functionality you wish to see implemented.
+      description: Specific packages, usecases, and/or examples are helpful.
+      placeholder: Tell us what you want to see!
+      value: "New feature!"
+    validations:
+      required: true
+  - type: textarea
+    id: usage-example
+    attributes:
+      label: Please provide a code snippet of how you would use this feature.
+      description: Showing the how you intend to use this feature will help us understand your usecase.
+      render: shell
+  - type: textarea
+    id: version
+    attributes:
+      label: Version
+      description: What version of our software are you running?
+    validations:
+      required: true
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Contribution Guidelines
+      description: By submitting this request, you agree to follow our [Contribution Guidelines](../../CONTRIBUTING.md)
+      options:
+        - label: I agree to follow this project's Contribution Guidelines
+          required: true
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this request, you agree to follow our [Code of Conduct](../../CODE_OF_CONDUCT.md)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/pull_request_template.md

@@ -0,0 +1,33 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Description
+<!--- Describe your changes in detail -->
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+<!--- If it fixes an open issue, please link to the issue here. -->
+
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, tests ran to see how -->
+<!--- your change affects other areas of the code, etc. -->
+
+## Types of Changes
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation (adding or updating documentation)
+- [ ] Dependency update
+
+## Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] My change requires a change to the documentation and I have updated the documentation accordingly.
+- [ ] My changes are in sync with the code style of this project.
+- [ ] There aren't any other open Pull Requests for the same issue/update.
+- [ ] These changes should be applied to a maintenance branch.
+- [ ] I have added the Apache 2.0 license header to any new files created.
+
+## What is the Impact to Developers Using `connectchain`?
+<!--- Please describe how your changes impacts developers using `connectchain`. -->

.github/review_template.md

@@ -0,0 +1,24 @@
+## Author self-review
+
+- [ ] The changes in this PR meet the user experience and goals outlined in the content design plan.
+- [ ] I've compared my PR's source changes to the latest `staging` branch and reviewed for versioning issues and code conflicts.
+- [ ] I've worked through build failures and tests are passing.
+- [ ] The changes adhere to the style guidlines in the respository's [Contribution Guidelines](../CONTRIBUTING.md#contribution-guidelines).
+
+## Review request
+
+### Summary
+
+_Help reviewers understand this PR and its context by writing a paragraph summarizing its goals and changes to functionality and explaining how the PR meets those goals._
+[Link to issue or feature](LINK HERE)
+
+### Technical review
+
+_Ping a respository contributor or owner, asking them to review whether content is technically accurate and meets the objectives of the issue/feature._
+_Highlight areas for them to consider in their review and ask them questions you need answered to ship the PR._
+
+[PR on staging](LINK HERE)
+
+### Notes
+
+_Discuss test failures, versioning issues, or anything else reviewers should know to consider the overall user experience of the PR._