You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: social-guidelines.md
+17-16
Original file line number
Diff line number
Diff line change
@@ -16,17 +16,18 @@ The objectives of project social media:
16
16
17
17
18
18
### Strategy and Guidelines
19
-
Keep messages positive and uplifting, consistent with the values and principles of CNCF
20
-
Communicate big picture ideas vs “announcements” or news. News will be positioned less like an announcement and more around what it means.
21
-
Share content across social media channels that benefit the ecosystem as a whole
22
-
Share vendor-neutral, community-sourced posts that are informational, engaging, and ecosystem-focused
23
-
Engage with the community through retweets and sharing of community content.
24
-
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, cloud native-specific Meetups, etc.
25
-
CNCF is not able to share anything on our channels that promotes a vendor product or directs to a company website.
26
-
Social posts from member company handles and/or vendor channels cannot be shared.
27
-
RTs are limited to news outlet handles, project handles + personal handles.
28
-
Community content that abides by the channel guidelines + includes insight from/work with more than one CNCF project will be prioritized for sharing.
29
-
Activities that are hosted by and open to the public can be promoted, as they benefit the ecosystem as a whole.
19
+
* Keep messages positive and uplifting, consistent with the values and principles of CNCF
20
+
* Communicate big picture ideas vs “announcements” or news. News will be positioned less like an announcement and more around what it means.
21
+
* Share content across social media channels that benefit the ecosystem as a whole
22
+
* Share vendor-neutral, community-sourced posts that are informational, engaging, and ecosystem-focused
23
+
* Engage with the community through retweets and sharing of community content.
24
+
* 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, cloud native-specific Meetups, etc.
25
+
* CNCF is not able to share anything on our channels that promotes a vendor product or directs to a company website.
26
+
* Social posts from member company handles and/or vendor channels cannot be shared.
27
+
* RTs are limited to news outlet handles, project handles + personal handles.
28
+
* Community content that abides by the channel guidelines + includes insight from/work with more than one CNCF project will be prioritized for sharing.
29
+
* Activities that are hosted by and open to the public can be promoted, as they benefit the ecosystem as a whole.
30
+
30
31
31
32
### Images & Videos
32
33
Images shared, unless specifically credited back to a community member, will meet the requirements of “free for commercial use” and “no attribution required.”
@@ -64,11 +65,11 @@ For all CNCF social activity, we remain a neutral foundation. Examples of the ty
64
65
* Owned content is CNCF news, blogs, case studies, survey data, etc.
65
66
* Project content is anything sourced from [CNCF’s currently hosted projects](https://www.cncf.io/projects/), including project news, roadmap updates, new releases, performance/security updates, blogs, conferences slides/videos, etc.
66
67
* 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, cloud native-specific Meetups, etc.
67
-
* CNCF is not able to share anything on our channels that promotes a vendor product or directs to a company website.
68
-
* Social posts from member company handles and/or vendor channels cannot be shared.
69
-
* RTs are limited to news outlet handles, @linuxfoundation, @kubecon_, project handles + personal handles.
70
-
* Community content that abides by the channel guidelines + includes insight from/work with more than one CNCF project will be prioritized for sharing.
71
-
* Activities that are hosted by and open to the public can be promoted, as they benefit the ecosystem as a whole.
68
+
* CNCF is not able to share anything on our channels that promotes a vendor product or directs to a company website.
69
+
* Social posts from member company handles and/or vendor channels cannot be shared.
70
+
* RTs are limited to news outlet handles, @linuxfoundation, @kubecon_, project handles + personal handles.
71
+
* Community content that abides by the channel guidelines + includes insight from/work with more than one CNCF project will be prioritized for sharing.
72
+
* Activities that are hosted by and open to the public can be promoted, as they benefit the ecosystem as a whole.
72
73
73
74
### Images & Videos
74
75
Images shared, unless specifically credited back to a community member, will meet the requirements of “free for commercial use” and “no attribution required.”
0 commit comments