Tiina Turban

Note that there's a project https://github.com/orgs/PostHog/projects/41/views/1 though some of the tasks there don't need to be there I'll let you take a look first though.

At a minimum from the stuff in the project we need the buffer roll-out to happen to everyone (cloud and self-hosted) before async migration & Re-migrate rows with missing person_id...

This was potentially the cause of https://posthog.slack.com/archives/C0374DA782U/p1658758589681689

To expand on the problem we have some content in docs and other in handbook and this makes things hard to find 1. [architecture](https://posthog.com/docs/self-host/architecture) in docs, [ingestion overview](https://posthog.com/handbook/engineering/event-ingestion) in handbook...

I wouldn't say it's done. Specifically the problem between docs / handbook -> engineering having content that's useful for self-hosted folks / more technical users. cc @corywatilo we very briefly...

I brought two examples in my comment. The general idea was that anything that's technical is relevant to self hosted folks or contributors, but looking into handbook seems unintuitive/unexpected. If...

Hi, if you would like to do this manually on your self-hosted instance you certainly can. Something to be aware is that for person properties overriding we don't look at...

For marketing/growth I'm not sure what's the best way to find out how to reach out, but e.g. [here](https://app.posthog.com/events?eventFilter=instance%20status%20report&tableColumns=%5B%22event%22%2C%22person%22%2C%22when%22%2C%22usage%22%2C%22posthog_version%22%2C%22%24ip%22%2C%22domain%22%2C%22site_url%22%5D&autoload=false&properties=%5B%7B%22key%22%3A%22realm%22%2C%22value%22%3A%5B%22hosted-clickhouse%22%5D%2C%22operator%22%3A%22is_not%22%2C%22type%22%3A%22event%22%7D%2C%7B%22key%22%3A%22users_who_logged_in__0__email%22%2C%22value%22%3A%22is_set%22%2C%22operator%22%3A%22is_set%22%2C%22type%22%3A%22event%22%7D%5D) we can see some site_urls & `users_who_logged_in__0__email` which might be the...

@kpthatsme - from a growth perspective any thoughts? I suspect to best retain all the existing Postgres customers longer term they need to migrate as otherwise their experience will get...

yes ASAP. Regarding emails, the best I came up with so far is https://github.com/PostHog/posthog/issues/6662#issuecomment-979442656