signalfx/splunk-otel-ruby

GDI Spec Compliance

Closed this issue · 3 comments

tsloughter-splunk commented

Opening here before we open this same issue in the gdi spec repo to seek approval for a GA release.

  • Has an appropriate maintainers team.
  • Permissions set correctly.
  • Branch protection in place.
  • Dependencies appropriately locked down.
  • GitHub Applications set up per spec.
  • Follows the configuration requirements, if appropriate.
  • Follows the semantic convention requirements, if appropriate.
  • Required Files in place.
    • CHANGELOG.md
    • CODE_OF_CONDUCT.md
    • CONTRIBUTING.md
    • .github/CODEOWNERS
    • LICENSE
    • README.md
      • Build status badge
      • Getting started
      • Troubleshooting
      • Link to official Splunk docs
      • License information
    • SECURITY.md
  • Releases done to spec.
  • Type specific requirements (remove what doesn't apply)
    • Instrumentation Library
      • Documents all supported configuration parameters.
      • Documents how to configure manual instrumentation.
      • Documents how to configure log correlation.
      • Documents minimum supported version of each auto-instrumentation framework.
    • Real User Monitoring Library
      • Documents all supported configuration parameters.
      • Documents how to configure manual instrumentation.
      • Documents supported instrumentation.
      • Documents supported platforms.
pellared commented

Related issues that have to be closed

tsloughter-splunk commented

If that is the case can I open a PR on GDI Spec to say, "all build, test and example dependencies"? I interpreted "build" to only mean the deps needed to build the gem (those listed in gemspec), which are locked in Gemlock.

  • 👍1
pellared commented

All issues solved