Define Spotlight Plan

[dcramer]

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 https://github.com/getsentry/spotlight/issues/545 Ref https://github.com/getsentry/spotlight/issues/468 Ref https://github.com/getsentry/spotlight/issues/543