Zingg-0.3.4
  • Welcome to Zingg
  • Step-By-Step Guide
    • Installation
      • Docker
        • Sharing custom data and config files
        • Shared locations
        • File read/write permissions
        • Copying Files To and From the Container
      • Installing From Release
        • Single Machine Setup
        • Spark Cluster Checklist
        • Installing Zingg
        • Verifying The Installation
      • Compiling From Source
    • Hardware Sizing
    • Zingg Runtime Properties
    • Zingg Command Line
    • Configuration
      • Configuring Through Environment Variables
      • Data Input and Output
        • Input Data
        • Output
      • Field Definitions
      • Model Location
      • Tuning Label, Match And Link Jobs
      • Telemetry
    • Working With Training Data
      • Finding Records For Training Set Creation
      • Labeling Records
      • Find And Label
      • Using pre-existing training data
      • Updating Labeled Pairs
      • Exporting Labeled Data
    • Building and saving the model
    • Finding the matches
    • Linking across datasets
  • Data Sources and Sinks
    • Zingg Pipes
    • Snowflake
    • JDBC
      • Postgres
      • MySQL
    • Cassandra
    • MongoDB
    • Neo4j
    • Parquet
    • BigQuery
  • Working With Python
  • Running Zingg on Cloud
    • Running on AWS
    • Running on Azure
    • Running on Databricks
  • Zingg Models
    • Pre-trained models
  • Improving Accuracy
    • Ignoring Commonly Occuring Words While Matching
    • Defining Domain Specific Blocking And Similarity Functions
  • Documenting The Model
  • Interpreting Output Scores
  • Reporting bugs and contributing
    • Setting Zingg Development Environment
  • Community
  • Frequently Asked Questions
  • Reading Material
  • Security And Privacy
Powered by GitBook
On this page

Reporting bugs and contributing

Contribute, report a bug and connect with us!

PreviousInterpreting Output ScoresNextSetting Zingg Development Environment

Last updated 2 years ago

Want to report a bug or request a feature? Let us know on , or open an .

Want to commit code? Please take a look at the or choose the ones marked . Let us talk on if you need help deciding what to fix or how.

As the sponsor of Zingg, Zingg Labs would like to ensure the long-term viability of Zingg and its community. For all code contributions to Zingg, we ask that contributors complete and sign a Contributor License Agreement. The Contributor License Agreement helps ensure everyone can enjoy Zingg with confidence that Zingg is here to stay.

Specifically, our Contributor License Agreement (CLA) grants the contributor and Zingg Labs joint copyright interest in contributed code. Further, it provides assurance from the contributor that contributions are original work that does not violate any third-party license agreement. The agreement between contributors and the Zingg project is explicit. This ensures that Zingg users can be confident in the legal status of the source code and their right to use it.

The above agreement is based on the Contributor License Agreements published by the , with modifications:

Slack
issue
open issues
good first issue
Slack
Individual Contributor License Agreement v1.0
Apache Software Foundation
Individual Contributor License Agreement ("Agreement") V2.0