Initial stab at social guidelines for the GraphQL Foundation#30
Initial stab at social guidelines for the GraphQL Foundation#30Urigo wants to merge 2 commits intographql:masterfrom
Conversation
social-guidelines.md
Outdated
| * Owned content is GraphQL Foundation news, blogs, case studies, survey data, etc. | ||
| * Project content is anything sourced from [GraphQL Foundation’s currently hosted projects](https://github.com/graphql), including project news, roadmap updates, new releases, performance/security updates, blogs, conferences slides/videos, etc. | ||
| * Ecosystem content is vendor-neutral and project-impartial sourced from contributors, maintainers, ambassadors, news outlets, etc., including blog posts, news coverage, thought leadership bylines, technology demos, sketch notes, GitHub work, GraphQL-specific Meetups, etc. | ||
| * CNCF is not able to share anything on our channels that promotes a vendor product or directs to a company website. |
There was a problem hiding this comment.
copied from the CNCF one.
Isn't that a bit strict?
Maybe times a company shares an open source library they've built.
Would that be something we cannot share at all?
There was a problem hiding this comment.
I think this is a pretty important restriction, personally.
There was a problem hiding this comment.
what about an individual that shares a blog post from a company's website or publication?
Most blog posts are on something like that no?
There was a problem hiding this comment.
I see a distinction between "a company's website" vs "a company's blog", but I hear what you mean - they control both, and it's a bit nuanced. I think adding an explicit exception for blog posts might be one way of addressing this.
There was a problem hiding this comment.
I'm with on making sure it's not becoming a marketing platform for companies, but I wonder if there are more exceptions..
On the other hand, we can always start very strict and later open more.
I'm good with that.
There was a problem hiding this comment.
the idea here would be to point to the github repo or code versus something on a company website
There was a problem hiding this comment.
@caniszczyk what about blog posts and articles?
| * Project content is anything sourced from [GraphQL Foundation’s currently hosted projects](https://github.com/graphql), including project news, roadmap updates, new releases, performance/security updates, blogs, conferences slides/videos, etc. | ||
| * Ecosystem content is vendor-neutral and project-impartial sourced from contributors, maintainers, ambassadors, news outlets, etc., including blog posts, news coverage, thought leadership bylines, technology demos, sketch notes, GitHub work, GraphQL-specific Meetups, etc. | ||
| * CNCF is not able to share anything on our channels that promotes a vendor product or directs to a company website. | ||
| * Social posts from member company handles and/or vendor channels cannot be shared. |
| * To organize or categorize shares (for example, #GraphQL). | ||
|
|
||
| ## To request content to be shared ## | ||
| Share your tweet on the [#socialmedia](https://app.slack.com/client/T08PSQ7BQ/C12MRQ97A) channel on the GraphQL Slack channel or email social@cncf.io. |
There was a problem hiding this comment.
@brianwarner @caniszczyk we should open a channel for it and also update the email address?
Do we need an email address at all or we can simply just rely on Slack?
There was a problem hiding this comment.
@Urigo SGTM, it's up to @brianwarner but I would simply just reference the slack channel vs email
Signed-off-by: Chris Aniszczyk <caniszczyk@gmail.com>
3 participants
Based on https://github.com/cncf/foundation/blob/master/social-guidelines.md