Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Spotlight Plan #649

Open
dcramer opened this issue Jan 8, 2025 · 0 comments
Open

Define Spotlight Plan #649

dcramer opened this issue Jan 8, 2025 · 0 comments

Comments

@dcramer
Copy link
Member

dcramer commented Jan 8, 2025

We need to concretely define how we plan to approach getting this a v1 and push adoption.

  1. Define goal
  2. Define measuring stick
  3. Define near term objective, blockers, and generally speaking, the gates\
  4. Articulate our GTM Plan

The goal is basically aligned w/ Sentry's: we want to build something so valuable that every developer uses it.

The measuring stick is debatable:

  • Grow faster than Sentry (net developers)
  • 100% of Sentry developers use Spotlight

Near term objectives I think we've decided we'll focus on Django first.

  • What needs done before Spotlight can go into Sentry's onboarding Docs?
  • What would it take from the Django push to feel comfortable focusing on a second community?

The go-to-market plan has two angles, but the objective is to gain critical mass in one community that Spotlight is validated and self-propagates. This is primarily done through feedback + awareness.

  1. Use Sentry's distribution to create awareness.
  2. Get help from relevant third parties (e.g. DSF, core Django folks, etc) both for awareness and feedback

Ref #545
Ref #468
Ref #543

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant