Merge pull request #2 from Senzing/issue-1.dockter.1

Issue 1.dockter.1

.dockerignore

@@ -0,0 +1,13 @@
+.github/
+docs/
+.DS_Store
+.gitignore
+.project
+.pydevproject
+CHANGELOG.md
+CODE_OF_CONDUCT.md
+CONTRIBUTING.md
+docker-compose.test.yml
+LICENSE
+PULL_REQUEST_TEMPLATE.md
+README.md

.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# Default code owner
+
+* @Senzing/go-developers

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/documentation_request.md

@@ -0,0 +1,26 @@
+---
+name: Documentation request
+about: Identify an area for improvement in documentation
+
+---
+
+**What is the URL of the documentation?**
+
+- **Example:** https://github.com/Senzing/template-docker#external-database
+    - *Note:*  This URL includes the web page and the section of the documentation.
+
+**What can be improved?**
+
+A clear and concise description of what can be improved.
+Examples:
+
+- "I don't understand where the ${XYZ} variable is set."
+- "There seems to be a step missing between 'X' and 'Z'.   I don't know how to get to 'Z'."
+- "When I run `command sub-command ...`  I get the following error:"
+- "I don't know what is meant by 'gerble barb gazoink` in the instructions".
+
+**Additional context**
+
+Add any other context or screenshots to help describe the documentation improvement.
+If you think the documentation improvement is operating system specific,
+please indicate which operating system is being used.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/dependabot.yml

@@ -0,0 +1,13 @@
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "daily"
+  - package-ecosystem: gomod
+    directory: /
+    schedule:
+      interval: daily

.github/workflows/add-dependabot-request-to-project-t-comm.yaml

@@ -0,0 +1,24 @@
+# Based on
+# - https://github.com/srggrs/assign-one-project-github-action
+
+name: add-dependabot-request-to-project-t-comm.yaml
+on:
+  pull_request:
+    types:
+      - opened
+      - reopened
+env:
+  GITHUB_TOKEN: ${{ secrets.SENZING_GITHUB_ACCESS_TOKEN }}
+  CREATOR: ${{ github.event.pull_request.user.login }}
+jobs:
+  assign_one_project:
+    name: Add dependabot pull request to Senzing Community project
+    runs-on: ubuntu-latest
+    steps:
+    - name: Assign pull request to project
+      env:
+          BOOL: ${{ contains( env.CREATOR, 'dependabot' ) }}
+      uses: Senzing/github-action-add-issue-to-project@main
+      if: ${{ env.BOOL == 'true' }}
+      with:
+        project: 'https://github.com/orgs/Senzing/projects/2'

.github/workflows/add-issue-to-project-t-comm.yaml

@@ -0,0 +1,21 @@
+# Based on
+# - https://github.com/srggrs/assign-one-project-github-action
+
+name: add-issue-to-project-t-comm.yaml
+on:
+  issues:
+    types:
+      - reopened
+      - opened
+env:
+  GITHUB_TOKEN: ${{ secrets.SENZING_GITHUB_ACCESS_TOKEN }}
+jobs:
+  assign_one_project:
+    name: Add issue to Senzing Community project
+    runs-on: ubuntu-latest
+    steps:
+    - name: Assign issue to project
+      uses: Senzing/github-action-add-issue-to-project@main
+      with:
+        project: 'https://github.com/orgs/Senzing/projects/2'
+        column_name: 'Backlog'

.github/workflows/add-triage-label.yaml

@@ -0,0 +1,19 @@
+# Based on
+# - https://docs.github.com/en/actions/guides/adding-labels-to-issues
+# - https://github.com/andymckay/labeler
+
+name: add-triage-label.yaml
+on:
+  issues:
+    types:
+      - reopened
+      - opened
+jobs:
+  automate-issues-labels:
+    name: Add triage label to issue
+    runs-on: ubuntu-latest
+    steps:
+      - name: initial labeling
+        uses: andymckay/labeler@1.0.4
+        with:
+          add-labels: "triage"

.github/workflows/go-proxy-pull.yaml

@@ -0,0 +1,22 @@
+# Based on
+# - https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions
+# - https://github.com/marketplace/actions/go-proxy-warming
+# - https://github.com/andrewslotin/go-proxy-pull-action
+# - https://futurestud.io/tutorials/github-actions-run-a-workflow-when-creating-a-tag
+
+name: go-proxy-pull.yaml
+
+on:
+  push:
+    tags:
+      - "v[0-9]+.[0-9]+.[0-9]+"
+
+jobs:
+  build:
+    name: Renew documentation
+    runs-on: ubuntu-latest
+    steps:
+      - name: Pull new module version
+        uses: andrewslotin/go-proxy-pull-action@v1.1.0
+        with:
+          import_path: github.com/senzing

.github/workflows/go-test.yaml

@@ -0,0 +1,23 @@
+# Based on
+# -https://github.com/marketplace/actions/setup-go-environment
+
+name: go-test.yaml
+
+on: [push]
+
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        go: ["1.19"]
+    name: Go ${{ matrix.go }} sample
+    steps:
+      - uses: actions/checkout@v3
+      - name: Setup go
+        uses: actions/setup-go@v3
+        with:
+          go-version: ${{ matrix.go }}
+      - run: pwd
+      - run: go test -v -p 1 ./...

.github/workflows/identify-customer.yaml

@@ -0,0 +1,21 @@
+name: identify-customer.yaml
+on:
+  issues:
+    types:
+      - opened
+env:
+  GITHUB_TOKEN: ${{ secrets.ORG_MEMBERSHIP_TOKEN }}
+  MEMBER_LIST: ${{ secrets.SENZING_MEMBERS }}
+  CREATOR: ${{ github.actor }}
+jobs:
+  automate-issues-labels:
+    name: Add customer-submission label
+    runs-on: ubuntu-latest
+    steps:
+      - name: initial labeling
+        env:
+          BOOL: ${{ contains( env.MEMBER_LIST, env.CREATOR ) }}
+        if: ${{ env.BOOL == 'false' }}
+        uses: andymckay/labeler@1.0.4
+        with:
+          add-labels: "customer-submission"

.gitignore

@@ -13,3 +13,5 @@
 
 # Dependency directories (remove the comment below to include it)
 # vendor/
+.history
+target/

.project

@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+	<name>template-go</name>
+</projectDescription>

CHANGELOG.md

@@ -0,0 +1,17 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+[markdownlint](https://dlaa.me/markdownlint/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+-
+
+## [0.1.0] - 2023-02-d06
+
+### Added to 0.1.0
+
+- Initial artifacts

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at support@senzing.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/