Reorder content and clarifying sections of the stock option page
Why is this change being made?
I found the content order difficult to follow on the stock option page and am suggesting changes that could improve the content flow.
Summary of changes:
- added a high level description under opening section of what equity incentive plans are available at GitLab
- as RSUs are the primary grant type since Sept 2021, 1) moved the RSU information to the first section, 2) collected all RSU related sections together, 3) added a New hire grant section.
- as ESPP is available since Sept 2021, 1) moved ESPP section second on the page and adjusted header depths accordingly
- as Stock Options are now less frequent, 1) moved stock options section third on the page, 2) collected all stock option related sections together
- left Taxes and Dual-class stock section unchanged
- adjusted to a consistent treatment of E-Trade throughout the document
- adjusted header depth to support classifications describe above
Author Checklist
-
Provided a concise title for this Merge Request (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 MR to the correct Directly Responsible Individual/s (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 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 DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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.
Edited by David Langemak