Updates to replacement and repair processes for Laptop Management
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA
Why is this change being made?
Updated countries that IT can not currently ship to.
- Keeping the countries up to date on the places IT can and cannot ship to helps new hires navigate what process they will need to follow to receive a GitLab issued laptop.
Defined replacement/repair processes as well as clarified that those processes are not eligible for the Laptop buyback program.
- Replaced and repaired laptops can be used for repurposing as needed within the company. (TSPs, loaners, burners, etc.)
Added Sycomp and Presidio as regional vendors.
- Making information available regarding our shipping vendors in each region helps with transparency.
Added information that Sycomp can do repairs on broken laptops.
- As we now have vendors for recycling and repairing old/broken laptops, laptops purchased by GitLab can be fixed and repurposed or recycled responsibly.
💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.Please add the details saying why, not just what in this section. Example:
We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.
CHANGEME
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
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, and the content is SAFE
-
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
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Update file _index.md