Closed charlescook-ph closed 3 years ago
We can do #2 and #3 - wouldn't worry about overloading our audience with emails at the moment since they're not that frequent.
I was also reminded today (https://posthog.slack.com/archives/C0113360FFV/p1627389342215900?thread_ts=1627373899.206200&cid=C0113360FFV) that we don't have a good story for migrations yet, but we likely want to have that FAQ at least beforehand (fast to add)
We'll potentially want to wait until https://github.com/PostHog/product-internal/issues/114 is resolved and chart default tag/sha updated
We'll potentially want to wait until PostHog/product-internal#114 is resolved and chart default tag/sha updated
Ok yep makes sense to wait then.
We can still prep everything ready to go now.
Action plan for next week based on conversation just now in Marketing sprint planning with @shehuphd and @leggetter:
Just to mention that as with any new release we might discover some things we want to fix a bit, so maybe it's good to do the paid ads part a bit latter (thinking to target starting 2 weeks after the email).
Doing an interview with James G next week on this; will take it through the usual workflow.
Should we also pin the charts-clickhouse repo in the Posthog organization in GitHub?
@shehuphd as referred to here, we should just call this PostHog Open Source (new and improved, better, shinier etc)
Should we also pin the charts-clickhouse repo in the Posthog organization in GitHub?
We currently pin posthog, posthog.com and posthog-js. We can pin up to 6, so that seems to make sense! Anyone else we need to ask or shall I just do it?
Just noticed https://posthog.com/blog/the-posthog-array-1-27-0#clickhouse-is-now-free-to-use we already mentioned ClickHouse being free for everyone
@piemets @tiina303 can you update this so we know whether or not we need to carry this forward to the next sprint! Basically just looking for a what has been done and what is still outstanding that still needs to be done. Thanks!
In terms of this checklist, I believe nothing is ready to be checked off yet - @shehuphd is just back from holiday now and I think the next step is to have Sam edit the interview vide (@shehuphd please add any relevant updates here?)
Yes - first draft is done, finalizing video edits today for Sam. Will push a PR after our interview.
Excited to see it 🥳
First draft here - needs additional/more accurate details in the first part of the announcement.
@piemets - I think we should ensure we have the user guide docs in place. See https://github.com/PostHog/posthog.com/issues/1744
@piemets - I think we should ensure we have the user guide docs in place. See PostHog/posthog.com#1744
I think we can actually close this particular issue - we publicised the launch of Clickhouse Free back in August.
Oh actually, are you referring to this issue instead around funnels @leggetter?
@piemets ah, yes, sorry. I had it in my head that we were publicising the new amazing funnels experience. ~I don't know if we have an issue for that or plan to do it?~ That should be https://github.com/PostHog/posthog.com/issues/1915.
Anyway, for this "new PostHog Open Source" issue it's not related so I wouldn't see the docs as a blocker.
Ok cool, we can close this issue then 👍
According to @tiina303 it sounds like we are ready to start letting people know about the availability of free Clickhouse to our users more broadly (relevant issue here).
2 questions:
I think the second option makes the most sense (once we're happy we're ready) given it's a big change that's good for our users, but keen to hear other perspectives on this. For context, we have 553 newsletter subscribers currently.
cc @shehuphd