Update Trade Compliance Considerations language
-
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?
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.
This change is being made to reflect our current company policy due to the new more restrictive sanctions put into effect by OFAC regarding Russia.
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
Merge request reports
Activity
added HandbookContent label
requested review from @pegan and @cgudgenov
assigned to @lcloonan
Thanks for your contribution to GitLab @lcloonan!
Did you know about our community forks? Working from there will make your contribution process easier. Please check it out!
- If you need help, comment
@gitlab-bot help
or come say hi on Discord. - When you're ready for a review, comment on this merge request with
@gitlab-bot ready
. - Tip: Start @gitlab-bot commands at the beginning of a new comment and do not wrap the command in quotes or backticks.
- We welcome AI-generated contributions! Read more/check the box at the top of the merge request description.
- To add labels to your merge request, comment
@gitlab-bot label ~"label1" ~"label2"
.
This message was generated automatically. You're welcome to improve it.
- If you need help, comment
added Community contribution workflowin dev labels
This merge request will be counted as part of the running Hackathon!
Find yourself in the Hackathon Leaderboard or check out the Hackathon page for more information!
This message was generated automatically. You're welcome to improve it.
added Hackathon label
assigned to @rachelpack and unassigned @lcloonan
- Resolved by Erik Lentz
Hi @pegan @cgudgenov @tdilbeck - I don't know if you were aware, but there have been some recent changes issued by OFAC with sanctions relating to Russia. This has resulted in tighter restrictions and I wanted to update the travel policy to reflect that we are no longer allowing team members to take company-owned devices or otherwise work from Russia or Belarus. We previously required a legal review to approve a request. Please let me know if you have any questions. Thank you for your review!
- Resolved by Cassiana Gudgenov
@cynthia Would you be able to advise as to why there is no movement in this MR? Thank you so muc! This is what I see:
added 383 commits
-
20d844e3...d4b3e3aa - 382 commits from branch
main
- 65eec880 - Update file _index.md
-
20d844e3...d4b3e3aa - 382 commits from branch
started a merge train
mentioned in commit 492a8dff
@lcloonan, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:
- React with a
or a on this comment to describe your experience. - Create a new comment starting with
@gitlab-bot feedback
below, and leave any additional feedback you have for us in the comment.
Subscribe to the GitLab Community Newsletter for contributor-focused content and opportunities to level up.
Thanks for your help!
This message was generated automatically. You're welcome to improve it.
- React with a