Skip to content

Change rules about expensing books for bookclubs

Gosia Ksionek requested to merge mk-bookclub-expenses into master

Why is this change being made?

Bookclubs in GitLab are a way to discuss in cross-teams groups in a series of regular meetings. Some of them are strictly connected to the role (https://gitlab.com/gitlab-com/books-clubs/combined-book-clubs/-/issues/45+), some are more general (https://gitlab.com/gitlab-com/books-clubs/combined-book-clubs/-/issues/46+) - they foster individual growth and support cross-cultural understanding. There were also multiple bookclubs organized under wings of TMRGs: https://gitlab.com/gitlab-com/books-clubs/combined-book-clubs/-/issues/43+, https://gitlab.com/gitlab-com/books-clubs/combined-book-clubs/-/issues/18+. In general bookclubs not only support growth, also cross-teams relationships and can be great place for creating social connections.

There I propose treating books for bookclubs differently expense-wise, and allow more transactions (not one per quarter) and lift the strict connection between the book and the role (therefor allow more flexibility for TMRG-lead bookclubs).

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, 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 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