PostHog
Clarify responsibility for reviewing new apps
Changes
Was going to do an issue about this, but then I thought: PRs are way cooler than issues.
PROBLEM: We're getting more regular app submissions from users, but it's unclear who is responsible for reviewing apps. Sometimes Support Hero picks it up, but they may be busy. Sometimes Appmaster Yakko picks it up, but sometimes he's away on holiday. Sometimes it lapses for a few weeks until eventually Neil takes a look, but that's not great for impatient users.
SOLUTION: I'm proposing we batch app reviews up and make it a release-owner responsibility.
This ensures:
- That the workload gets shared across the team
- That the workload is predictable for the individual
- That the work is batched efficiently
- That Marketing + Engineering work together on it and can support each other
- That we can give contributors a clear timeline to release
Downside:
- It's another thing for release owners to do
Checklist
- [ ] Titles are in sentence case
- [ ] Feature names are in title case
- [ ] Words are spelled using American English
- [ ] I have checked out our style guide
I like this idea - support hero I feel like it's not feasible for them to review them due to general workload already being quite high & it's tied to releases anyway in a sense.
On the one hand this makes for a more distributed workload (and I agree it's quite tough to fit review of apps into a support hero's schedule), but on the other hand, whoever is the release owner is less likely to know good app development practices than someone from the team owning Apps. Also, up to a month of turnaround time is a lot.
I think the best user experience would ensue from the Ingestion team being responsible for reviews (not necessarily ASAP, but sprints are just two weeks long, instead of a whole month). I can see how this could be annoying with the current headcount if there are multiple apps per sprint, but that doesn't seem like an issue currently – ownership is the unknown.
