a1662cff1a
Converted from mdbook src/ in input/ to Grav pages/ format: - Added YAML frontmatter to all pages - Created numbered folder structure (01.home, 02.Bylaws.*, etc.) - Preserved all content from Bylaws, Handbook, OperatingAgreements, Policies, and JointVenture sections super ultra big merge completed. scope of work clearly defined. let's go build! Assisted-by: GLM-5 via Crush <crush@charm.land>
1.9 KiB
1.9 KiB
title, menu
| title | menu |
|---|---|
| People | People |
title: Team Extensibility sidebar: Handbook showTitle: true hideAnchor: true
People
- Marius Andra (Team lead, Full Stack Engineer)
- Michael Matloka (Full Stack Engineer)
- Yakko Majuri (DevRel + Full Stack Engineer)
Mission
Team Extensibility's job is to turn PostHog into a platform that everyone can integrate with. In essence, we enable users to:
- get data into PostHog
- get data out of PostHog
- extend PostHog itself according to their needs
Responsibilities
Team Extensibility is particularly responsible for:
- the plugin server
- the data ingestion pipeline
- PostHog integrations with all sorts of platforms (JS, Go, iOS, Zapier, Segment, etc.)
- the user experience of extensibility features in PostHog (e.g. plugins, webhooks)
Priorities
- Making sure there are no cracks in the walls and that we always keep in mind safety, security, and data integrity of our systems. We code defensively, prefer allowlists to denylists, and so on.
- A fabulous user experience. Connecting things to PostHog either via plugins or integrations should spark joy.
Customer
- Plugin developers, contributors to extensibility
- Plugin users (and in extension, all PostHog app users – who we'd love to make use of plugins)
- Integration users
Output metric
- Number of plugins installed and/or in active use
- Used plugin-seconds on cloud, breakdown by team (for billing)
- Number of integrations and their usage
Meetings
- Sync: Monday, 9:00 UTC
- Sync: Wednesday, 15:00 UTC
- Internal release planning: Friday every other week