Skip to content

Update Chief Product Officer (or CProdO) to VP of Product (or VPP)

Magdalena Frankiewicz requested to merge update-CPO-to-VPP into master

Why is this change being made?

Scott Williamson and Anoop Dawar left the company. David DeSanto is VP of Product and he leads the Product division. With this changes, GitLab handbook needs to be adjusted as well.

Note:

I didn't change any working groups descriptions, as they are historic, and mention also other people that are no longer with GitLab (files like: sites/uncategorized/source/company/team/structure/working-groups/gitlab-com-cost/index.html.md, sites/uncategorized/source/company/team/structure/working-groups/gitlab-com-revenue/index.html.md, sites/uncategorized/source/company/team/structure/working-groups/simplify-groups-and-projects/index.html.md.

I didn't change press releases either, for the same reason (files like sites/uncategorized/source/press/releases/2019-09-20-gitlab-named-cloud-native-continuous-integration-tools-leader.html.md).

I didn't change, for the same reason: sites/uncategorized/source/company/gitlab-assembly/index.html.md sites/uncategorized/source/company/okrs/fy21-q1/index.html.md sites/uncategorized/source/company/okrs/fy20-q2/index.html.md sites/uncategorized/source/company/okrs/fy20-q3/index.html.md

I don't know what to do with the mention here: sites/handbook/source/handbook/product/product-manager-role/learning-and-development/index.html.md.erb - there's embedded video with Scott Williamson.

Should this page be removed: sites/uncategorized/source/job-families/product/chief-product-officer/index.html.md ?

Should mentions in Chief Product Officer in data/variable_pay_frequency.yml and of CPO in data/communication/misused_terms.yml be removed?

@fseifoddini updated sites/handbook/source/handbook/product/product-okrs/previous-quarters/index.html.md.erb in !102387 (closed), but that file has many mentions of CProdO. Should it stay this way?

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports