senzing-garage/community-roadmap

Issues

• Update repository after transfer

  #78 opened a year ago
  1

• Python SDK - next version

  #77 opened a year ago
  0

• Go/Golang SDK

  #76 opened 2 years ago
  0

• Create scenario-based tutorials

  #75 opened 2 years ago
  0

• Consolidate SSHD, XTERM, and consoles

  #74 opened a year ago
  0

• Improve and add type checking to SDK modules

  #73 opened 2 years ago
  0

• Remove use of psutil

  #72 opened 2 years ago
  1

• Improve GitHub Actions for pull requests

  #71 opened 2 years ago
  0

• Support SENZING_ENGINE_CONFIGURATION_JSON

  #70 opened 2 years ago
  1

• Improve CODEOWNERS file

  #69 opened 2 years ago
  1

• Test Issue 1

  #68 opened 2 years ago
  0

• Add .github/dependabot.yml to repository

  #67 opened 2 years ago
  0

• Remove ENTITY_TYPE references

  #66 opened a year ago
  1

• Incorporate senzingapi-runtime package

  #65 opened 2 years ago
  0

• Senzing License as environment variable

  #64 opened 2 years ago
  1

• Move DATA_SOURCE parameter to stream-producer

  #63 opened 2 years ago
  0

• Migrate from Jupyter to JupyterLab

  #62 opened 2 years ago
  0

• Deprecate obsolete repositories

  #61 opened 2 years ago
  1

• Add information in README.md on how to receive support

  #60 opened a year ago
  2

• Migrate primary branch from master to main

  #58 opened 2 years ago
  1

• Add header / banner to GitHub assets, these are accelerators and examples, learn from, adjust, make your own

  #57 opened a year ago
  1

• Add requirements.txt to /python folder

  #56 opened 3 years ago
  0

• Clear header in infrastructure based repositories stating assets are accelerators / demonstrators

  #55 opened 3 years ago
  0

• Demonstrate use of Oracle database in a Senzing Stack

  #54 opened 2 years ago
  1

• Migrate from "yum" install to "apt" install

  #53 opened 2 years ago
  0

• Investigate improving ease of deployment of compose assets

  #52 opened 3 years ago
  0

• Ideas about how to reduce tickets, stress and troubleshooting: Would like to provide the ability for a user to visualize their YAML file

  #51 opened a year ago
  1

• Demonstrate Senzing multi-tenancy in Kubernetes

  #50 opened 3 years ago
  0

• Sign Docker images

  #49 opened 3 years ago
  1

• CloudFormation on AWS for deploying the REST API for a developer

  #48 opened 2 years ago
  1

• AWS meter-based pricing

  #47 opened 3 years ago
  0

• Monitor Docker image exposures

  #46 opened 3 years ago
  0

• AWS Marketplace

  #45 opened 3 years ago
  1

• Setup discourse on senzing.community

  #44 opened a year ago
  0

• docker-compose formation showing replication to elastic search

  #43 opened a year ago
  3

• Create an "update Senzing in-place" docker image

  #42 opened a year ago
  0

• Determine an appropriate communication platform

  #41 opened 3 years ago
  3

• python/docker to transfer data from one queue to another

  #40 opened 3 years ago
  1

• Stream-loader should load any record and redoer should produce json to queues

  #39 opened a year ago
  3

• Manage runtime configuration change

  #38 opened a year ago
  0

• AWS meter-based pricing

  #37 opened 2 years ago
  3

• Verification of compatible version of Senzing and Senzing utilities

  #36 opened 4 years ago
  0

• Support for Apache Pulsar

  #35 opened a year ago
  0

• Add Jenkinsfile to repositories for additional test coverage

  #34 opened a year ago
  0

• Support for Microsoft's .NET

  #33 opened 4 years ago
  0

• Support for AWS Secrets Manager

  #32 opened a year ago
  0

• Support for AWS Kinesis

  #31 opened a year ago
  0

• Support for OpenShift 4

  #30 opened a year ago
  0

• Jupyter Notebook examples

  #29 opened a year ago
  0

• Improve test automation of Senzing GitHub repositories

  #28 opened 4 years ago
  0