Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add guidance on sharing pronouns #665

Merged
merged 1 commit into from
Aug 19, 2022
Merged

Add guidance on sharing pronouns #665

merged 1 commit into from
Aug 19, 2022

Conversation

sallyhall
Copy link
Contributor

Adds the guidance from the hub message on sharing pronouns to guides. Step 2 is to link to this from the playbook once this is merged.

Copy link
Contributor

@mike-burns mike-burns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, this LGTM, but I have logistical questions.

How is the Playbook generated? Is it from the Handbook? Can we put this directly into the Playbook?

Sorry, I should know these things.

@SViccari
Copy link

@sallyhall Thank you for adding this. 💛

Following up on your comment in Hub: https://hub.thoughtbot.com/messages/sharing-pronouns-is-always-optional#comment_25458

I looked at the playbook and I agree, I'm having trouble discerning the right place for this information.

Here are two ideas:

  1. In the Playbook, under Planning, repurpose the page titled "A functioning remote team doesn't happen by accident" to a more general "working together" theme. For example, we could re-purpose this page to "A functioning team doesn't happen by accident" or "Team Collaboration". Then, we could include a section titled "Pronoun guidelines". This would also create space for us to link to Pair Programming Guidelines and In-Person Meetings.
  2. Add "Pronoun guidelines" to the Playbook under the Our Company -> Diversity, Equity, and Inclusion

@SViccari
Copy link

SViccari commented May 13, 2022

@mike-burns

How is the Playbook generated? Is it from the Handbook?

Yes, the Playbook is generated from the Handbook. Example:

  1. This page in the Playbook includes a link to our "Remote Meeting Guidelines".
  2. The "Remote Meeting Guidelines" live in the Guides repo.
  3. In the Handbook/playbook, we link to the Guides repo "Remote Meeting Guidelines".
  4. The Handbook/playbook content is then published to the Playbook website.

Can we put this directly into the Playbook?

What lives in Guides vs the Handbook is a bit fuzzy to me. The nicety of adding to Guides is everything is public by default. I don't feel strongly about whether this content lives in Guides vs in the Handbook/playbook.

@sallyhall
Copy link
Contributor Author

I'm going to merge this as-is, since I've been avoiding finding a better location for it for over 90 days now and I'd rather have it in than have it perfect. I'm hoping to find bandwidth to figure out how to get it into the playbook soon, but Im not 100% sure when that will happen.

@sallyhall sallyhall merged commit f96d746 into main Aug 19, 2022
@sallyhall sallyhall deleted the sh-pronoun-guidance branch August 19, 2022 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants