---
# System prepended metadata

title: Open Source Maintainer Tools Brainstorm

---

# Open Source Maintainer Tools Brainstorm

## Related Docs
[Open Source Maintainer Tools Brainstorm](/Er6ahj6iThyNosyXfrzhnQ)
[Open Source Metrics](https://hackmd.io/X4qM-KWqS2yi0X-CfBogQA)
[Internal Metrics](https://hackmd.io/Y5wrkPwgQWGW8bVVWWWiqw)
[Github Management Tooling](https://docs.google.com/document/d/1o-5GlRrVtkkHbQXJjlwz7Z6C1hroiaMwDyx--QWFUTM/edit)

**Objective:**

Combine Github data plus internal data to form a cohesive view of an open-source project from New Relic's perspective.


1. How do we support all our customer types, especially those not comfortable with GH?
2. How do we limit the amount of platform hopping by maintainers?
3. How do we consolidate or integrate all the conversations/issues/knowledge from their origination place?


Support issues should end up in discuss threads, bug/features in GH

NR1 Catalog should direct them to explorer's hub. Clicking on help inside one of these nerdlets doesn't provide a clear direction.

## Ideas (team brainstorming)

- A "doc" for each repository/project that shows up in in-product documentation. i.e. ensure first result is the explorer's thread for that project.
- [x] Get data from OS website indexed so it shows up in help system, show discuss thread and first few issues
- In-product - Create GH issues for 3rd party apps, update Salesforce that an issue exists tied to an account
- Dashboard for maintainers combining GH issues with Explorer's threads with GH Discussions

## Users
### Internal

#### OSPO

- Tracking [Open Source Release Checklist](https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/edit) steps
- People
  - Maintainer history and changelog, including employment changes (NR vs. not)
  - Contributors
- Metadata
- Slack channels
- Linking GH handles to customers
- Revisions/Audit Log of activity and changes to internal data
- Analytics
  - GH Issues opened by Relics
  - GH Issues opened by Non-relics

#### Maintainers

- Need to quickly see and respond to relevant conversations on different platforms - Github, Explorer's Hub, Slack, etc.
- Support different types of users ranging from active developer (engineer) to pure consumer (nr1-app end-user)
- Share recognized users and users tied to customers with maintainers
- Support end-users in Explorer's hub

#### GTS

- Some users for some repositories will be offered ticketed support. GTS needs to know who/how/etc.

### External

#### NR1 App Support

- Built-in functionality to open a GH Issue or Support ticket from an nr1-app without needing a Github username
- Integration with Discuss
- NR1 like customer feedback channel/collection
