Address CEO feedback to update links and tier references
Why is this change being made?
-
Please indicate the applicable tier for an issue by applying the label associated with the tier (e.g. GitLab Core, GitLab Starter) and the Enterprise Edition label for features targeting a paid tier. Ensure this is defined before feature development begins. => Stop using an edition for open source vs. proprietary. EE also has open source code. Add EE to top misused terms with a link to the right section. Make point 17 of https://about.gitlab.com/handbook/marketing/strategic-marketing/tiers/#messaging-dos-and-donts a separate item -- Will be addressed in !75185 (merged) -
Get rid of starter -
Mention features.yml as the central place. -
For the persona of Premium we should say directors. I've seen managers and VPs in different places and this is inconsistent. -
Link to investment types https://about.gitlab.com/handbook/product/investment/#investment-types -
Link to https://about.gitlab.com/handbook/ceo/pricing/#buyer-based-open-core (edited)
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 -
Assign this change to the correct DRI - 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 relate to any part of the project other than updates to content and/or data files please make sure to ping(this requirement has been removed pending identification of a new DRI for the handbook)@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.
Edited by Farnoosh Seifoddini