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

Address the Google Manifesto #22

Open
thejessleigh opened this issue Aug 8, 2017 · 6 comments
Open

Address the Google Manifesto #22

thejessleigh opened this issue Aug 8, 2017 · 6 comments

Comments

@thejessleigh
Copy link
Collaborator

We definitely want to come up with some good resources to link to here. However, we feel like we need more space and we want to link to some constructive conversations coming out in the aftermath, and give the Google Manifesto itself as little airtime as possible. It's had plenty.

@sublimemarch
Copy link
Owner

I definitely agree that we should give ourselves a week or two of space before we find a way to add this in, especially because the story is still developing.

@cmho
Copy link
Collaborator

cmho commented Sep 27, 2017

just reminded by someone making the news again that we should still do this; I don't know if there's been a good roundup somewhere to link to since the initiating event

@sublimemarch
Copy link
Owner

Alright, I'm taking a look at articles and thinking how best to address this. Do we want to just add a summary of what happened? Or an article that shows how this is part of a broader problem? Or an article doing a line-by-line critique of the manifesto? I'm personally not sure of the best way to deal with it.

A listicle with example quotes: https://www.cnbc.com/2017/08/07/shocking-quotes-from-the-viral-google-manifesto.html

Some Googlers supported the ideas in the manifesto: https://www.wired.com/story/internal-messages-james-damore-google-memo/

Google's response: https://motherboard.vice.com/en_us/article/vbv54d/google-on-anti-diversity-manifesto-employees-must-feel-safe-sharing-their-opinions

@cmho
Copy link
Collaborator

cmho commented Oct 26, 2017

I think probably something that shows how this is part of a broader problem and illustrates why it was this big of a deal is probably good for the tone of this repo? Although possibly this thing may be big enough to warrant more than one article (since I could see a summary of what happened also being useful to people learning about stuff after-the-fact)

@sublimemarch
Copy link
Owner

Now that we've given this one some time, I think it's safe to say that this merits inclusion. Whatcha think @thejessleigh @cmho ?

@thejessleigh
Copy link
Collaborator Author

Definitely. There's also been a lot of think pieces and chatter since then. Do we want to try to find a more up to date version, or stick with the original docs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants