Updates to handbook pages which have a large impact to team members should be posted to Slack in an automated way
Background
As a follow-up to concerns regarding transparency eroding and updates not being posted about changing policies, a first iteration can be to post an automated update to Slack for changes to handbook pages whichj have a large impact to team members.
First iteration
I think we can do the following to help with this first iteration:
-
Identify the SSOTs to use for controlled docs. @jlongo_gitlab can you help, please? -
Create a channel in Slack for these updates -
Once we know the path forward, we send a note to #whats-happening-at-gitlab
to let people know "Hey, we're updating our systems such that updates to handbook pages which have a large impact to team members are posted to Slack in${new_channel}
please join that channel if interested." Once implemented, we respond to that thread saying "this is live". @ipedowitz can work with Field Enablement on better comms by filing a Field Announcement request once we know what we'll do.
Examples of important docs:
-
controlled docs list. This appears to be static/manually updated in the public handbook, but there's also an entry in
CODEOWNERS
for these docs. There's likely to be an equivalent in the new public handbook as well as the internal handbooks which we should also automate postings for. - Total Rewards pages
- Expense policy documents
- Values
- etc.
Other relevant issues/MRs
Edited by Ian Pedowitz