Skip to content

Update times to be UTC-centric

Brian Rhea requested to merge utc-centric-times into master

Please provide a brief explanation for this change:

After reading the feedback from @nagyv-gitlab and @hphilipps regarding ways to improve the employee experience for non-US team members, I took a quick pass at the Handbook pages related to the Product team.

image

The changes I'm suggesting don't address every team member and are perhaps still too US-centric and I'm open to suggestions. My reasoning is that this format

3 pm UTC (10 am ET / 7 am PT)

is UTC-centric and is easy to interpret for the majority of GitLab Team Members.

Potential Issues

There are times during the year when the offset between UTC, CET, PT, etc fluctuates. Is there a more robust solution we could implement? For example, a job that identifies and standardizes times in the Handbook and injects a :before element that displays on hover with real-time ... uh, times ... and more timezones?

Please indicate the types of revisions being suggested for the Product Handbook (please check all that apply):

  • Small improvement (typos, clarifications, etc.)
  • Adding a new section
  • Modifying existing section
  • Documenting a new process
  • Adding a new page or directory
  • Other

Please indicate Milestone

  • Assigned to Milestone

Author Checklist

  • Provided a concise title for the MR
  • Provided a brief explanation for this change (Say why, not just what)
    • (Attach screenshots, Slack conversations, etc. as necessary)
  • Indicated the types of changes included in this MR
  • Verified that no confidential data is in this MR
  • Assigned 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 #product or #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 Brian Rhea

Merge request reports