mozilla-services / mozilla-services/kent
investigate deprecating Kent in favor of Sentry Spotlight
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 124
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Sentry has a new Spotlight project which (in addition to many other things) covers most/all of the use cases Kent covers. Details on API endpoints in this discussion:
https://github.com/getsentry/spotlight/issues/1268
We should look at deprecating Kent in favor of Sentry Spotlight. That work involves:
- writing up a migration path for Kent -> Sentry Spotlight
- deprecating Kent
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Sentry Spotlight API details in the linked discussion and compare them with Kent's current use cases. Document a migration path from Kent to Sentry Spotlight, then define the deprecation steps for Kent; done means both the migration guidance and deprecation plan are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100