Skip to content

Remove myself as database reviewer

Robert May requested to merge robotmay_gitlab-master-patch-37682 into master

Why is this change being made?

I've had to red circle myself for months due to review workload being too much of a distraction from my actual deliverables, so in an effort to actually be able to get through reviews again, I'd like to remove myself from the pool of database reviewers.

I think this makes sense as in my normal role I have very few actual interactions with our database anyway, so my experience in how our database is set up and configured is weaker than my Ruby experience which I work in every day. Database reviews take up a disproportionate amount of time (I probably complete 5 backend reviews to every 1 database review in terms of time) and this isn't tracked in any of our productivity measurements, so it's a bit of a pain point in trying to get my productivity levels back up.

Also slightly trims my bio section.

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
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign 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 #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.

Merge request reports