Clarify how we'll communicate changes to the handbook

[coreycaitlin]

Comment/suggestion

Per feedback (in survey): How will we communicate changes to the Handbook to staff (particularly folks who have already signed/acknowledged the Handbook)?

Context and user stories

As a Bloom employee, I want to be confident that the Handbook I acknowledged and committed to is the same Handbook that currently exists (and have a chance to flag concerns if something changes that I'm not comfortable with or wouldn't have signed on to).

Section

About this Handbook / signature part

Notes

• All major policy changes should start with/come from a decision doc or other internal announcement (ie the Handbook would come last, not first
• We could consider adding a checkbox/flag to the PR template for folks to consider and identify whether the proposed change should be accompanied by internal comms

[danielhonker]

Depending on how we implement this, it might be relevant to #125 from engineering perspective (i.e., data on date last updated).

[coreycaitlin]

Idea: Slackbot that pushes merged PRs to the #handbook channel, then People Ops or other can repost to #general

AND for major PRs, we can use tags to help trigger appropriate Slack message + include decision doc link in PR description or issue description.