Key Data for Hub Singer Taps and Targets

[MeltyBot]

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/3

Originally created by @tayloramurphy on 2021-04-14 15:26:19

---

On Singer.io when you look at a tap or target you see this information:

• Name
• Logo
• Brief description of the tap source
• Link to API sometimes
• Language (Python)
• Data Catalog (not really sure what this does, most say "Supports the extraction of individual data streams and fields")
• "Example Data" which is just a list of words
• Link to Singer Spec
• pip install tap-x code block
• Link to repo
• LInk to PRs, Issues, and link to Singer Slack
• List of available targets
• Pitch for Stitch

---

What is our future state for the Hub?

• Much of the above
• Prominent Singer Spec page
• Cross-links to https://hub.getdbt.com
• License of Tap clearly displayed
• Metrics on taps/targets:
  • number of open PRs
  • number of open issues
  • Last activity on repo (latest commit)
  • Number of downloads / uses
  • anonymous Meltano runs
  • how is this tap used in combination with targets
  • CI Badges
• Tap/target Capabilities:
  • replication types
  • configuration listings
  • latest catalog output in a human readable format (downloadable)
  • mark columns with available metadata (PII, etc.)
  • Built with SDK yes/no
• Ownership / Governance:
  • Who's the current sponsor/maintainer
  • Is this actively maintained or potentially abandoned / up for adoption (can be manual at first but then can programmatically update)
• Variants:
  • What variants are available under the same namespace (tap-gitlab) ?

Additional points brought up in office hours:

• What's going to be the Meltano "semver". How will people know if something is production ready or not?
• API coverage of the tap - is this missing 2/3rds of the endpoint? <- can get people to contribute this
  • Mark items in the catalog as unsupported
• SDK can have a demo mode with some stored JSON data - that can be added as well
• What's the decision process for upgrading a variant to the "blessed" version <- should be documented on the website
• "Most wanted" section for taps that don't exist yet - maybe we can make placeholders? should these be ranked?

[MeltyBot]

View 3 previous comments from the original issue on GitLab