PostHog Handbook Library / Engineering

368 words. Estimated reading time: 2 min.

# SDK support rotation

The SDK Support Hero rotation is managed by the . Each week, one member of the team is designated the SDK Support Hero. The schedule is managed in incident.io.

Your primary responsibility is to make sure SDK questions get some love — across all SDKs, including mobile. During the rotation, please keep an eye on:

- Escalated SDK tickets in PostHog Support — your team's view is bookmarked in `#support-client-libraries`
- New issues in the SDK repositories:
- posthog-js (Web, Web Lite, React, React Native, Next, Node, AI)
- posthog-python
- posthog-ios
- posthog-android
- posthog-flutter
- Others, see /docs/libraries

### How should I prioritize my time?

Firstly, try to stay on top of new escalated tickets in PostHog Support and GitHub issues, and make sure that issues related to a specific team are routed to them. If there is a relevant team (e.g. the issue is related to session replay in posthog-js), you can assign the ticket to that team, and use the team's label in GitHub. If there is no relevant team for a GitHub issue, please label with `SDK Support Hero`. Feel free to try to fix things yourself before tagging the team.

Next, please work on SDK tickets in PostHog Support, and GitHub issues labeled `SDK Support Hero` (and unlabeled, but please label these!). You can use your own judgement to decide which issues to work on but please consider effort / reward / urgency / your skill set. For example, `posthog-js` usually has the most issues, but if you're a Python expert, you might want to focus on `posthog-python`.

For mobile SDK issues, prioritize accordingly — rolling out fixes on mobile apps may take weeks or even months, so faster turnaround on these is important. Make sure, however, to validate changes carefully, avoid breaking changes and think through edge cases before shipping, since our ability to correct mistakes after release is significantly constrained.

At the end of the week, please write a public handover message in `#support-client-libraries`, to let the next person know what work is in progress, let the team know how the support rotation is going in general, and to share any learnings or feedback.

Canonical URL: https://posthog.com/handbook/engineering/sdks/support-rotation

GitHub source: contents/handbook/engineering/sdks/support-rotation.md

Content hash: `20574c4e8968adae`

Static reader notes

- `MDX_COMPONENT_STATIC_ADAPTER`: Adapted interactive MDX components for static reading: SmallTeam.