Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposed Infrastructure Q3 Goals #3706

Merged
merged 9 commits into from
Jul 8, 2022
Merged

Conversation

marcushyett-ph
Copy link
Contributor

To help every team have clear impactful goals to work on @jamesefhawkins @timgl @charlescook-ph @marcushyett-ph have come up with a set of ambitious and achievable proposed goals for each team to hit by the end of September 2022.

@fuziontech as team lead, by end of Thursday 7th July, we'd like:

  • You to work with the team to iterate on the proposed objective and key results and align on them
  • If you decide to radically change the objective or key results, get feedback from at least @timgl @marcushyett-ph
  • Merge this PR so we can start discussing the new goals in our weekly all hands and doing some roadmapping on what to build to achieve these, next week

@marcushyett-ph marcushyett-ph changed the title Proposed Infrsstructure Q3 Goals Proposed Infrastructure Q3 Goals Jul 4, 2022
@marcushyett-ph marcushyett-ph requested a review from timgl July 4, 2022 13:27
marcushyett-ph and others added 5 commits July 4, 2022 14:52
Co-authored-by: Guido Iaquinti <4038041+guidoiaquinti@users.noreply.github.com>
Co-authored-by: Guido Iaquinti <4038041+guidoiaquinti@users.noreply.github.com>
Co-authored-by: Guido Iaquinti <4038041+guidoiaquinti@users.noreply.github.com>
Co-authored-by: Guido Iaquinti <4038041+guidoiaquinti@users.noreply.github.com>
Co-authored-by: Guido Iaquinti <4038041+guidoiaquinti@users.noreply.github.com>
Copy link
Member

@fuziontech fuziontech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll grab this PR and tweak today

* Lots of customers are self-serving PostHog Cloud in the EU
* **Proposed Key Results**:
* >100 organizations using EU hosted PostHog Cloud
* All deployment methods are support the latest stable versions of dependencies (so we can leverage the benefits of later versions)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* All deployment methods are support the latest stable versions of dependencies (so we can leverage the benefits of later versions)
* All deployment methods support the latest stable versions of dependencies (so we can leverage the benefits of later versions)

Typo fix, but this feels arbitrary. I'd like to have concrete reasons why we should support any new version of anything. Specific security patches, performance, features? Like we don't want to support CH 22.6 because it's a mess right now, but would satisfy this goal.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, this is fairly arbitrary, is there a better way to highlight the critical dependencies for us to upgrade in Q3 as key results (e.g. like we needed to do a previous clickhouse upgrade).

@guidoiaquinti already mentioned "Kubernetes v1.25" below, and since we have some customers who rely on bleeding edge versions this could be critical.

Would be great if we could enumerate the biggest ones specifically in this key result.

* **Proposed Key Results**:
* >100 organizations using EU hosted PostHog Cloud
* All deployment methods are support the latest stable versions of dependencies (so we can leverage the benefits of later versions)
* Meet SOC 2 compliance requirements for all cloud infrastructure
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 to this line item - solid goal

@marcushyett-ph
Copy link
Contributor Author

Dear @fuziontech,

@guidoiaquinti @hazzadous and I aligned on a few tweaks to the wording during our standup this morning, let us know if you have any additional comments or changes. And feel free to merge!

Yours sincerely,
@marcushyett-ph

Copy link
Member

@fuziontech fuziontech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dear @marcushyett-ph,

I have verified and affirm that the suggested modifications to our Great Team of Infrastructure's Q3 Objectives and Key results are clear, relevant, and satisfactorily in alignment to our 3 year plans. Now, therefore, in exercise of the powers vested in me by the policies laid out in the organization of GitHub and our guiding documents of the handbook hereby approve the aforementioned changes.

Yours truly,
🚢 it

@fuziontech fuziontech merged commit 4bbd570 into master Jul 8, 2022
@fuziontech fuziontech deleted the infrastructure-q3-goals branch July 8, 2022 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants