Variable | Value |
Edit count of the user (user_editcount) | 11743 |
Name of the user account (user_name) | 'Maffblaster' |
Age of the user account (user_age) | 139178157 |
Page ID (page_id) | 20121 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'Public Relations' |
Full page title (page_prefixedtitle) | 'Project:Public Relations' |
Action (action) | 'edit' |
Edit summary/reason (summary) | 'Add Cynede to the project (helping with Discord).' |
Whether or not the edit is marked as minor (no longer in use) (minor_edit) | false |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=Public Relations
|Description=The Public Relations team improves Gentoo's visibility towards the rest of the world. We maintain presence on various web silos such as Facebook, Google+, and Twitter. Below you will find those responsible on a per-site basis.
|Email=pr@gentoo.org
|Mailing list=gentoo-pr
|IRC=#gentoo-pr
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|LeadElectionDate=2017/07/27
|Members={{Project Member
|Developer=User:Dabbott
|Role=Cafepress store, Facebook (editor)
|IsLead=No
}}{{Project Member
|Developer=User:Sping
|IsLead=No
}}{{Project Member
|Developer=User:K f
|IsLead=No
}}{{Project Member
|Developer=User:Dilfridge
|Role=Facebook (admin), G+ (owner), Twitter
|IsLead=No
}}{{Project Member
|Developer=User:Maffblaster
|Role=Cafepress store, Facebook (admin), G+ (primary owner), Twitter, Telegram (admin), Slack (admin)
|IsLead=Yes
}}{{Project Member
|Developer=User:Nightmorph
|IsLead=No
}}{{Project Member
|Developer=User:Aliceinwire
|Role=Facebook (admin), G+ (owner), Twitter, Events, Telegram (admin), Slack (admin)
|IsLead=No
}}
}}
The Public Relations team improves Gentoo's visibility towards the rest of the world. We maintain presence on various [http://indieweb.org/silo web silos] such as Facebook, Google+, and Twitter. Below you will find those responsible on a per-site basis.
Extending and improving a meta-distribution such as Gentoo is not possible without the continued involvement of the users. Apart from the bug reporting, enhancement requests, mailing list/IRC activity, and other important aspects of development, the motivation of the users is one of, perhaps even the most, influential facet of distribution development. Such motivation can be brought to the users by well-coordinated public relation efforts.
PR goes well beyond just "informing the world". It embraces research, planning, communication, and evaluation manufactured to the organization's core values. It does not stop with explaining the virtues of the organization and the decisions made, but also extends to uncovering the principles that are used to go where the organization wants to go.
== Roadmap ==
Want to know what do be doing? Here is a list of things the whole team can work on.
=== 2017 ===
==== Administrator access to active members across web silos ====
The (draft) policy states that official Gentoo accounts on social media and chat should, if possible, share administrator access with 2 or more official, active Gentoo developers. The team needs to work toward granting access to:
; Facebook: <s>alicef and maffblaster would like admin level access.</s> Done!
; G+: <s>dilfridge and maffblaster would like top-level access (track down {{U|a3li}} for this).</s> Done!
; Twitter: <s>alicef and dilfridge would like top-level access.</s> Done!
==== Review PR teams commitment to Gentoo's social contract ====
Most, if not all, of the values of the social sites the PR team handles do not line up with [https://gentoo.org/get-started/philosophy/social-contract.html Gentoo's Social Contract]. We want to be careful to remain in consistency with the Social Contract. Review the social contract to be sure no violations are in effect.
==== Ask the moderators of the Reddit to join PR ====
As far as the PR teams understands, the moderators of the official Gentoo subreddit group are not involved with Gentoo's PR. It would be great to either than one of them join, or have two or more active members of PR be granted top-level access to the subreddit.
== Social silos and chat ==
The following is a list of official social media accounts for Gentoo. Those involved with PR can feel free to ask for permission to help push news updates to these locations. Please give other members of the team a brief consultation in {{IRC|gentoo-pr}} and/or on the mailing list before posting.
'''Social silos:'''
* [https://www.facebook.com/gentoo.org Facebook]
* [https://plus.google.com/+Gentoo Google+]
* [https://twitter.com/gentoo Twitter]
* [https://www.reddit.com/r/Gentoo/ Reddit]
'''Chat:'''
* [https://t.me/gentoolinux Telegram]
* [https://join.slack.com/gentoo/signup Slack] (all @gentoo.org email addresses are administrators.)
** [http://slackin.aliceinwire.net/ Slack non Gentoo email registation]
* [https://discordapp.com/invite/gentoo Discord] (Admin: {{U|Cynede}}, {{U|Aliceinwire}})
* [https://gentoo.zulipchat.com Zulip (open source)] (Admin: {{U|Aliceinwire}})
== Policy ==
{{Important|The following 'policy' content is not (yet) official. It is a current work-in-progress and is expected to change.}}
The goal of having a policy for PR is to provide uniformity across social sites so that community members can immediately recognize Gentoo's (official) presence.
# The public relations team should follow the [https://www.gentoo.org/inside-gentoo/foundation/name-logo-guidelines.html Gentoo name and logo usage guidelines] and also take into consideration the [https://gentoo.org/get-started/philosophy/social-contract.html social contract].
# For any social site to be officially run by the PR project, a minimum of two active Gentoo developers should have top-most administrative access. This is a necessary redundancy in the event that a single Gentoo developer goes missing in action.
## Active is defined as [https://www.gentoo.org/inside-gentoo/developers/retired-developers.html not retired] and [https://www.gentoo.org/inside-gentoo/developers/unavailable-developers.html not unavailable]. In the eyes of the PR team, unavailable developers are those with {{Path|~/.devaway}} files on Woodpecker for longer than 2 weeks time.
## Top-level is defined differently by each site. The priory here is to provide full permissions to manage all areas of the site to a minimum of two active developers. Note that two is the minimum, ideaily all active members of the PR team can have equal access.
# When applicable, please use Gentoo's official [https://www.gentoo.org/assets/img/logo/gentoo-signet.png 'Signet' logo] as the 'profile' picture.
== Resources ==
=== Presentations ===
The presentation project (once a solo-project) has now been merged with Public Relations. Presentations help keep our community informed about Gentoo development progress. The goal is to improve Gentoo's visibility by providing all appropriate information in up-to-date, well targeted presentations, and hand outs. These can then be downloaded and used by developers, users, and other interested parties. Developers are encouraged to not only view these themselves, but also to share with others in the public square through presentations, demonstrations, and direct contact with the community.
Presentation resources can be found in the following sub-articles:
* [[/Presentation Guide|Presentation guide]]
* [[/Available Presentations|Available presentations]]
=== Additional materials ===
Some of the following links may be deprecated or non-applicable:
* [[Project:Public_Relations/Road Maps|Road Maps]]
* [[Project:Public_Relations/Media|Media]]
* [[Project:Public_Relations/Press_Coverage|Press coverage]]
* [[Project:Public_Relations/Event Material|Event material]]' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=Public Relations
|Description=The Public Relations team improves Gentoo's visibility towards the rest of the world. We maintain presence on various web silos such as Facebook, Google+, and Twitter. Below you will find those responsible on a per-site basis.
|Email=pr@gentoo.org
|Mailing list=gentoo-pr
|IRC=#gentoo-pr
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|LeadElectionDate=2017/07/27
|Members={{Project Member
|Developer=User:Dabbott
|Role=Cafepress store, Facebook (editor)
|IsLead=No
}}{{Project Member
|Developer=User:Sping
|IsLead=No
}}{{Project Member
|Developer=User:K f
|IsLead=No
}}{{Project Member
|Developer=User:Dilfridge
|Role=Facebook (admin), G+ (owner), Twitter
|IsLead=No
}}{{Project Member
|Developer=User:Maffblaster
|Role=Cafepress store, Facebook (admin), G+ (primary owner), Twitter, Telegram (admin), Slack (admin)
|IsLead=Yes
}}{{Project Member
|Developer=User:Nightmorph
|IsLead=No
}}{{Project Member
|Developer=User:Aliceinwire
|Role=Facebook (admin), G+ (owner), Twitter, Events, Telegram (admin), Slack (admin), Discord
|IsLead=No
}}{{Project Member
|Developer=User:Cynede
|Role=Discord
|IsLead=No
}}
}}
The Public Relations team improves Gentoo's visibility towards the rest of the world. We maintain presence on various [http://indieweb.org/silo web silos] such as Facebook, Google+, and Twitter. Below you will find those responsible on a per-site basis.
Extending and improving a meta-distribution such as Gentoo is not possible without the continued involvement of the users. Apart from the bug reporting, enhancement requests, mailing list/IRC activity, and other important aspects of development, the motivation of the users is one of, perhaps even the most, influential facet of distribution development. Such motivation can be brought to the users by well-coordinated public relation efforts.
PR goes well beyond just "informing the world". It embraces research, planning, communication, and evaluation manufactured to the organization's core values. It does not stop with explaining the virtues of the organization and the decisions made, but also extends to uncovering the principles that are used to go where the organization wants to go.
== Roadmap ==
Want to know what do be doing? Here is a list of things the whole team can work on.
=== 2017 ===
==== Administrator access to active members across web silos ====
The (draft) policy states that official Gentoo accounts on social media and chat should, if possible, share administrator access with 2 or more official, active Gentoo developers. The team needs to work toward granting access to:
; Facebook: <s>alicef and maffblaster would like admin level access.</s> Done!
; G+: <s>dilfridge and maffblaster would like top-level access (track down {{U|a3li}} for this).</s> Done!
; Twitter: <s>alicef and dilfridge would like top-level access.</s> Done!
==== Review PR teams commitment to Gentoo's social contract ====
Most, if not all, of the values of the social sites the PR team handles do not line up with [https://gentoo.org/get-started/philosophy/social-contract.html Gentoo's Social Contract]. We want to be careful to remain in consistency with the Social Contract. Review the social contract to be sure no violations are in effect.
==== Ask the moderators of the Reddit to join PR ====
As far as the PR teams understands, the moderators of the official Gentoo subreddit group are not involved with Gentoo's PR. It would be great to either than one of them join, or have two or more active members of PR be granted top-level access to the subreddit.
== Social silos and chat ==
The following is a list of official social media accounts for Gentoo. Those involved with PR can feel free to ask for permission to help push news updates to these locations. Please give other members of the team a brief consultation in {{IRC|gentoo-pr}} and/or on the mailing list before posting.
'''Social silos:'''
* [https://www.facebook.com/gentoo.org Facebook]
* [https://plus.google.com/+Gentoo Google+]
* [https://twitter.com/gentoo Twitter]
* [https://www.reddit.com/r/Gentoo/ Reddit]
'''Chat:'''
* [https://t.me/gentoolinux Telegram]
* [https://join.slack.com/gentoo/signup Slack] (all @gentoo.org email addresses are administrators.)
** [http://slackin.aliceinwire.net/ Slack non Gentoo email registation]
* [https://discordapp.com/invite/gentoo Discord] (Admin: {{U|Cynede}}, {{U|Aliceinwire}})
* [https://gentoo.zulipchat.com Zulip (open source)] (Admin: {{U|Aliceinwire}})
== Policy ==
{{Important|The following 'policy' content is not (yet) official. It is a current work-in-progress and is expected to change.}}
The goal of having a policy for PR is to provide uniformity across social sites so that community members can immediately recognize Gentoo's (official) presence.
# The public relations team should follow the [https://www.gentoo.org/inside-gentoo/foundation/name-logo-guidelines.html Gentoo name and logo usage guidelines] and also take into consideration the [https://gentoo.org/get-started/philosophy/social-contract.html social contract].
# For any social site to be officially run by the PR project, a minimum of two active Gentoo developers should have top-most administrative access. This is a necessary redundancy in the event that a single Gentoo developer goes missing in action.
## Active is defined as [https://www.gentoo.org/inside-gentoo/developers/retired-developers.html not retired] and [https://www.gentoo.org/inside-gentoo/developers/unavailable-developers.html not unavailable]. In the eyes of the PR team, unavailable developers are those with {{Path|~/.devaway}} files on Woodpecker for longer than 2 weeks time.
## Top-level is defined differently by each site. The priory here is to provide full permissions to manage all areas of the site to a minimum of two active developers. Note that two is the minimum, ideaily all active members of the PR team can have equal access.
# When applicable, please use Gentoo's official [https://www.gentoo.org/assets/img/logo/gentoo-signet.png 'Signet' logo] as the 'profile' picture.
== Resources ==
=== Presentations ===
The presentation project (once a solo-project) has now been merged with Public Relations. Presentations help keep our community informed about Gentoo development progress. The goal is to improve Gentoo's visibility by providing all appropriate information in up-to-date, well targeted presentations, and hand outs. These can then be downloaded and used by developers, users, and other interested parties. Developers are encouraged to not only view these themselves, but also to share with others in the public square through presentations, demonstrations, and direct contact with the community.
Presentation resources can be found in the following sub-articles:
* [[/Presentation Guide|Presentation guide]]
* [[/Available Presentations|Available presentations]]
=== Additional materials ===
Some of the following links may be deprecated or non-applicable:
* [[Project:Public_Relations/Road Maps|Road Maps]]
* [[Project:Public_Relations/Media|Media]]
* [[Project:Public_Relations/Press_Coverage|Press coverage]]
* [[Project:Public_Relations/Event Material|Event material]]' |
Unified diff of changes made by edit (edit_diff) | '@@ -30,7 +30,11 @@
|IsLead=No
}}{{Project Member
|Developer=User:Aliceinwire
-|Role=Facebook (admin), G+ (owner), Twitter, Events, Telegram (admin), Slack (admin)
+|Role=Facebook (admin), G+ (owner), Twitter, Events, Telegram (admin), Slack (admin), Discord
+|IsLead=No
+}}{{Project Member
+|Developer=User:Cynede
+|Role=Discord
|IsLead=No
}}
}}
' |
Old page size (old_size) | 7140 |
Lines added in edit (added_lines) | [
0 => '|Role=Facebook (admin), G+ (owner), Twitter, Events, Telegram (admin), Slack (admin), Discord',
1 => '|IsLead=No',
2 => '}}{{Project Member',
3 => '|Developer=User:Cynede',
4 => '|Role=Discord'
] |
Lines removed in edit (removed_lines) | [
0 => '|Role=Facebook (admin), G+ (owner), Twitter, Events, Telegram (admin), Slack (admin)'
] |
New page text, stripped of any markup (new_text) | '
Public Relations
Description
The Public Relations team improves Gentoo's visibility towards the rest of the world. We maintain presence on various web silos such as Facebook, Google+, and Twitter. Below you will find those responsible on a per-site basis.
Project email
pr@gentoo.org
Mailing list
gentoo-pr@lists.gentoo.org | Archive
IRC channel
#gentoo-pr
Lead(s)
Matthew Marchese
(maffblaster)Cafepress store, Facebook (admin), G+ (primary owner), Twitter, Telegram (admin), Slack (admin) Last elected: 2017/07/27
Member(s)
Alice Ferrazzi
(alicef)Facebook (admin), G+ (owner), Twitter, Events, Telegram (admin), Slack (admin)David Abbott
(dabbott)Cafepress store, Facebook (editor)Andreas K. Hüttel
(dilfridge)Facebook (admin), G+ (owner), TwitterKristian Fiskerstrand
(k_f)Joshua Saddler
(nightmorph)Sebastian Pipping
(sping)
Subproject(s)(and inherited member(s))
Events
News
Matthew Marchese
(maffblaster)HostPlanet Gentoo
Website maintainers
Parent Project
Gentoo
Project listing
The Public Relations team improves Gentoo's visibility towards the rest of the world. We maintain presence on various web silos such as Facebook, Google+, and Twitter. Below you will find those responsible on a per-site basis.
Extending and improving a meta-distribution such as Gentoo is not possible without the continued involvement of the users. Apart from the bug reporting, enhancement requests, mailing list/IRC activity, and other important aspects of development, the motivation of the users is one of, perhaps even the most, influential facet of distribution development. Such motivation can be brought to the users by well-coordinated public relation efforts.
PR goes well beyond just "informing the world". It embraces research, planning, communication, and evaluation manufactured to the organization's core values. It does not stop with explaining the virtues of the organization and the decisions made, but also extends to uncovering the principles that are used to go where the organization wants to go.
Contents
1 Roadmap
1.1 2017
1.1.1 Administrator access to active members across web silos
1.1.2 Review PR teams commitment to Gentoo's social contract
1.1.3 Ask the moderators of the Reddit to join PR
2 Social silos and chat
3 Policy
4 Resources
4.1 Presentations
4.2 Additional materials
Roadmap[edit]
Want to know what do be doing? Here is a list of things the whole team can work on.
2017[edit]
Administrator access to active members across web silos[edit]
The (draft) policy states that official Gentoo accounts on social media and chat should, if possible, share administrator access with 2 or more official, active Gentoo developers. The team needs to work toward granting access to:
Facebook
alicef and maffblaster would like admin level access. Done!
G+
dilfridge and maffblaster would like top-level access (track down a3li for this). Done!
Twitter
alicef and dilfridge would like top-level access. Done!
Review PR teams commitment to Gentoo's social contract[edit]
Most, if not all, of the values of the social sites the PR team handles do not line up with Gentoo's Social Contract. We want to be careful to remain in consistency with the Social Contract. Review the social contract to be sure no violations are in effect.
Ask the moderators of the Reddit to join PR[edit]
As far as the PR teams understands, the moderators of the official Gentoo subreddit group are not involved with Gentoo's PR. It would be great to either than one of them join, or have two or more active members of PR be granted top-level access to the subreddit.
Social silos and chat[edit]
The following is a list of official social media accounts for Gentoo. Those involved with PR can feel free to ask for permission to help push news updates to these locations. Please give other members of the team a brief consultation in #gentoo-pr and/or on the mailing list before posting.
Social silos:
Facebook
Google+
Twitter
Reddit
Chat:
Telegram
Slack (all @gentoo.org email addresses are administrators.)
Slack non Gentoo email registation
Discord (Admin: Cynede , Aliceinwire )
Zulip (open source) (Admin: Aliceinwire )
Policy[edit]
ImportantThe following 'policy' content is not (yet) official. It is a current work-in-progress and is expected to change.
The goal of having a policy for PR is to provide uniformity across social sites so that community members can immediately recognize Gentoo's (official) presence.
The public relations team should follow the Gentoo name and logo usage guidelines and also take into consideration the social contract.
For any social site to be officially run by the PR project, a minimum of two active Gentoo developers should have top-most administrative access. This is a necessary redundancy in the event that a single Gentoo developer goes missing in action.
Active is defined as not retired and not unavailable. In the eyes of the PR team, unavailable developers are those with ~/.devaway files on Woodpecker for longer than 2 weeks time.
Top-level is defined differently by each site. The priory here is to provide full permissions to manage all areas of the site to a minimum of two active developers. Note that two is the minimum, ideaily all active members of the PR team can have equal access.
When applicable, please use Gentoo's official 'Signet' logo as the 'profile' picture.
Resources[edit]
Presentations[edit]
The presentation project (once a solo-project) has now been merged with Public Relations. Presentations help keep our community informed about Gentoo development progress. The goal is to improve Gentoo's visibility by providing all appropriate information in up-to-date, well targeted presentations, and hand outs. These can then be downloaded and used by developers, users, and other interested parties. Developers are encouraged to not only view these themselves, but also to share with others in the public square through presentations, demonstrations, and direct contact with the community.
Presentation resources can be found in the following sub-articles:
Presentation guide
Available presentations
Additional materials[edit]
Some of the following links may be deprecated or non-applicable:
Road Maps
Media
Press coverage
Event material
' |
Parsed HTML source of the new revision (new_html) | '<table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>Public Relations</big>
</th></tr>
<tr valign="top">
<th> Description
</th>
<td style="text-align: justify;"> The Public Relations team improves Gentoo's visibility towards the rest of the world. We maintain presence on various web silos such as Facebook, Google+, and Twitter. Below you will find those responsible on a per-site basis.
</td></tr>
<tr>
<th> <span title="Mails to member(s) listed below.">Project email</span>
</th>
<td> <a rel="nofollow" class="external text" href="mailto:pr@gentoo.org">pr@gentoo.org</a>
</td></tr>
<tr>
<th> <span title="Public discussion list.">Mailing list</span>
</th>
<td> <a rel="nofollow" class="external text" href="mailto:gentoo-pr@lists.gentoo.org">gentoo-pr@lists.gentoo.org</a> | <a rel="nofollow" class="external text" href="https://archives.gentoo.org/gentoo-pr">Archive</a>
</td></tr>
<tr>
<th> <span title="The link opens a webchat to this project's Freenode IRC channel.">IRC channel</span>
</th>
<td> <a rel="nofollow" class="external text" href="https://webchat.freenode.net/?channels=gentoo-pr">#gentoo-pr</a>
</td></tr>
<tr valign="top">
<th> Lead(s)
</th>
<td> <ul><li><a href="/wiki/User:Maffblaster" title="User:Maffblaster">Matthew Marchese</a>
(maffblaster)<br /><i>Cafepress store, Facebook (admin), G+ (primary owner), Twitter, Telegram (admin), Slack (admin)</i></li></ul> <br />Last elected: 2017/07/27
</td></tr>
<tr valign="top">
<th> Member(s)
</th>
<td> <ul><li><a href="/wiki/User:Aliceinwire" title="User:Aliceinwire">Alice Ferrazzi</a>
(alicef)<br /><i>Facebook (admin), G+ (owner), Twitter, Events, Telegram (admin), Slack (admin)</i></li><li><a href="/wiki/User:Dabbott" title="User:Dabbott">David Abbott</a>
(dabbott)<br /><i>Cafepress store, Facebook (editor)</i></li><li><a href="/wiki/User:Dilfridge" title="User:Dilfridge">Andreas K. Hüttel</a>
(dilfridge)<br /><i>Facebook (admin), G+ (owner), Twitter</i></li><li><a href="/wiki/User:K_f" title="User:K f">Kristian Fiskerstrand</a>
(k_f)</li><li><a href="/wiki/User:Nightmorph" title="User:Nightmorph">Joshua Saddler</a>
(nightmorph)</li><li><a href="/wiki/User:Sping" title="User:Sping">Sebastian Pipping</a>
(sping)</li></ul>
</td></tr>
<tr valign="top">
<th> Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td> <ul><li><a href="/wiki/Project:Events" title="Project:Events">Events</a>
</li><li><a href="/wiki/Project:News" title="Project:News">News</a>
<ul><li><a href="/wiki/User:Maffblaster" title="User:Maffblaster">Matthew Marchese</a>
(maffblaster)<br /><i>Host</i></li></ul></li><li><a href="/wiki/Project:Planet" title="Project:Planet">Planet Gentoo</a>
</li><li><a href="/wiki/Project:Website" title="Project:Website">Website maintainers</a>
</li></ul>
</td></tr>
<tr>
<th> Parent Project
</th>
<td> <a href="/wiki/Project:Gentoo" title="Project:Gentoo">Gentoo</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></table>
<p>The Public Relations team improves Gentoo's visibility towards the rest of the world. We maintain presence on various <a rel="nofollow" class="external text" href="http://indieweb.org/silo">web silos</a> such as Facebook, Google+, and Twitter. Below you will find those responsible on a per-site basis.
</p><p>Extending and improving a meta-distribution such as Gentoo is not possible without the continued involvement of the users. Apart from the bug reporting, enhancement requests, mailing list/IRC activity, and other important aspects of development, the motivation of the users is one of, perhaps even the most, influential facet of distribution development. Such motivation can be brought to the users by well-coordinated public relation efforts.
</p><p>PR goes well beyond just "informing the world". It embraces research, planning, communication, and evaluation manufactured to the organization's core values. It does not stop with explaining the virtues of the organization and the decisions made, but also extends to uncovering the principles that are used to go where the organization wants to go.
</p>
<div id="toc" class="toc"><div id="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Roadmap"><span class="tocnumber">1</span> <span class="toctext">Roadmap</span></a>
<ul>
<li class="toclevel-2 tocsection-2"><a href="#2017"><span class="tocnumber">1.1</span> <span class="toctext">2017</span></a>
<ul>
<li class="toclevel-3 tocsection-3"><a href="#Administrator_access_to_active_members_across_web_silos"><span class="tocnumber">1.1.1</span> <span class="toctext">Administrator access to active members across web silos</span></a></li>
<li class="toclevel-3 tocsection-4"><a href="#Review_PR_teams_commitment_to_Gentoo.27s_social_contract"><span class="tocnumber">1.1.2</span> <span class="toctext">Review PR teams commitment to Gentoo's social contract</span></a></li>
<li class="toclevel-3 tocsection-5"><a href="#Ask_the_moderators_of_the_Reddit_to_join_PR"><span class="tocnumber">1.1.3</span> <span class="toctext">Ask the moderators of the Reddit to join PR</span></a></li>
</ul>
</li>
</ul>
</li>
<li class="toclevel-1 tocsection-6"><a href="#Social_silos_and_chat"><span class="tocnumber">2</span> <span class="toctext">Social silos and chat</span></a></li>
<li class="toclevel-1 tocsection-7"><a href="#Policy"><span class="tocnumber">3</span> <span class="toctext">Policy</span></a></li>
<li class="toclevel-1 tocsection-8"><a href="#Resources"><span class="tocnumber">4</span> <span class="toctext">Resources</span></a>
<ul>
<li class="toclevel-2 tocsection-9"><a href="#Presentations"><span class="tocnumber">4.1</span> <span class="toctext">Presentations</span></a></li>
<li class="toclevel-2 tocsection-10"><a href="#Additional_materials"><span class="tocnumber">4.2</span> <span class="toctext">Additional materials</span></a></li>
</ul>
</li>
</ul>
</div>
<h2><span class="mw-headline" id="Roadmap">Roadmap</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=1" title="Edit section: Roadmap">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Want to know what do be doing? Here is a list of things the whole team can work on.
</p>
<h3><span class="mw-headline" id="2017">2017</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=2" title="Edit section: 2017">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<h4><span class="mw-headline" id="Administrator_access_to_active_members_across_web_silos">Administrator access to active members across web silos</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=3" title="Edit section: Administrator access to active members across web silos">edit</a><span class="mw-editsection-bracket">]</span></span></h4>
<p>The (draft) policy states that official Gentoo accounts on social media and chat should, if possible, share administrator access with 2 or more official, active Gentoo developers. The team needs to work toward granting access to:
</p>
<dl><dt> Facebook</dt>
<dd> <s>alicef and maffblaster would like admin level access.</s> Done!</dd>
<dt> G+</dt>
<dd> <s>dilfridge and maffblaster would like top-level access (track down <a href="/wiki/User:A3li" title="User:A3li">a3li <i class="fa fa-user"></i></a> for this).</s> Done!</dd>
<dt> Twitter</dt>
<dd> <s>alicef and dilfridge would like top-level access.</s> Done!</dd></dl>
<h4><span class="mw-headline" id="Review_PR_teams_commitment_to_Gentoo.27s_social_contract">Review PR teams commitment to Gentoo's social contract</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=4" title="Edit section: Review PR teams commitment to Gentoo's social contract">edit</a><span class="mw-editsection-bracket">]</span></span></h4>
<p>Most, if not all, of the values of the social sites the PR team handles do not line up with <a rel="nofollow" class="external text" href="https://gentoo.org/get-started/philosophy/social-contract.html">Gentoo's Social Contract</a>. We want to be careful to remain in consistency with the Social Contract. Review the social contract to be sure no violations are in effect.
</p>
<h4><span class="mw-headline" id="Ask_the_moderators_of_the_Reddit_to_join_PR">Ask the moderators of the Reddit to join PR</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=5" title="Edit section: Ask the moderators of the Reddit to join PR">edit</a><span class="mw-editsection-bracket">]</span></span></h4>
<p>As far as the PR teams understands, the moderators of the official Gentoo subreddit group are not involved with Gentoo's PR. It would be great to either than one of them join, or have two or more active members of PR be granted top-level access to the subreddit.
</p>
<h2><span class="mw-headline" id="Social_silos_and_chat">Social silos and chat</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=6" title="Edit section: Social silos and chat">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>The following is a list of official social media accounts for Gentoo. Those involved with PR can feel free to ask for permission to help push news updates to these locations. Please give other members of the team a brief consultation in <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="irc://irc.gentoo.org/gentoo-pr">#gentoo-pr</a></span> and/or on the mailing list before posting.
</p><p><b>Social silos:</b>
</p>
<ul><li> <a rel="nofollow" class="external text" href="https://www.facebook.com/gentoo.org">Facebook</a></li>
<li> <a rel="nofollow" class="external text" href="https://plus.google.com/+Gentoo">Google+</a></li>
<li> <a rel="nofollow" class="external text" href="https://twitter.com/gentoo">Twitter</a></li>
<li> <a rel="nofollow" class="external text" href="https://www.reddit.com/r/Gentoo/">Reddit</a></li></ul>
<p><b>Chat:</b>
</p>
<ul><li> <a rel="nofollow" class="external text" href="https://t.me/gentoolinux">Telegram</a></li>
<li> <a rel="nofollow" class="external text" href="https://join.slack.com/gentoo/signup">Slack</a> (all @gentoo.org email addresses are administrators.)
<ul><li> <a rel="nofollow" class="external text" href="http://slackin.aliceinwire.net/">Slack non Gentoo email registation</a></li></ul></li>
<li> <a rel="nofollow" class="external text" href="https://discordapp.com/invite/gentoo">Discord</a> (Admin: <a href="/wiki/User:Cynede" title="User:Cynede">Cynede <i class="fa fa-user"></i></a>, <a href="/wiki/User:Aliceinwire" title="User:Aliceinwire">Aliceinwire <i class="fa fa-user"></i></a>)</li>
<li> <a rel="nofollow" class="external text" href="https://gentoo.zulipchat.com">Zulip (open source)</a> (Admin: <a href="/wiki/User:Aliceinwire" title="User:Aliceinwire">Aliceinwire <i class="fa fa-user"></i></a>)</li></ul>
<h2><span class="mw-headline" id="Policy">Policy</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=7" title="Edit section: Policy">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<div class="alert alert-warning gw-box" style="padding-top: 8px; padding-bottom: 8px;"><strong><i class="fa fa-exclamation-circle"></i> Important</strong><br />The following 'policy' content is not (yet) official. It is a current work-in-progress and is expected to change.</div>
<p>The goal of having a policy for PR is to provide uniformity across social sites so that community members can immediately recognize Gentoo's (official) presence.
</p>
<ol><li> The public relations team should follow the <a rel="nofollow" class="external text" href="https://www.gentoo.org/inside-gentoo/foundation/name-logo-guidelines.html">Gentoo name and logo usage guidelines</a> and also take into consideration the <a rel="nofollow" class="external text" href="https://gentoo.org/get-started/philosophy/social-contract.html">social contract</a>.</li>
<li> For any social site to be officially run by the PR project, a minimum of two active Gentoo developers should have top-most administrative access. This is a necessary redundancy in the event that a single Gentoo developer goes missing in action.
<ol><li> Active is defined as <a rel="nofollow" class="external text" href="https://www.gentoo.org/inside-gentoo/developers/retired-developers.html">not retired</a> and <a rel="nofollow" class="external text" href="https://www.gentoo.org/inside-gentoo/developers/unavailable-developers.html">not unavailable</a>. In the eyes of the PR team, unavailable developers are those with <span style="font-family: monospace; font-size: 95%">~/.devaway</span> files on Woodpecker for longer than 2 weeks time.</li>
<li> Top-level is defined differently by each site. The priory here is to provide full permissions to manage all areas of the site to a minimum of two active developers. Note that two is the minimum, ideaily all active members of the PR team can have equal access.</li></ol></li>
<li> When applicable, please use Gentoo's official <a rel="nofollow" class="external text" href="https://www.gentoo.org/assets/img/logo/gentoo-signet.png">'Signet' logo</a> as the 'profile' picture.</li></ol>
<h2><span class="mw-headline" id="Resources">Resources</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=8" title="Edit section: Resources">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<h3><span class="mw-headline" id="Presentations">Presentations</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=9" title="Edit section: Presentations">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>The presentation project (once a solo-project) has now been merged with Public Relations. Presentations help keep our community informed about Gentoo development progress. The goal is to improve Gentoo's visibility by providing all appropriate information in up-to-date, well targeted presentations, and hand outs. These can then be downloaded and used by developers, users, and other interested parties. Developers are encouraged to not only view these themselves, but also to share with others in the public square through presentations, demonstrations, and direct contact with the community.
</p><p>Presentation resources can be found in the following sub-articles:
</p>
<ul><li> <a href="/wiki/Project:Public_Relations/Presentation_Guide" title="Project:Public Relations/Presentation Guide">Presentation guide</a></li>
<li> <a href="/wiki/Project:Public_Relations/Available_Presentations" title="Project:Public Relations/Available Presentations">Available presentations</a></li></ul>
<h3><span class="mw-headline" id="Additional_materials">Additional materials</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Public_Relations&action=edit&section=10" title="Edit section: Additional materials">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Some of the following links may be deprecated or non-applicable:
</p>
<ul><li> <a href="/wiki/Project:Public_Relations/Road_Maps" title="Project:Public Relations/Road Maps">Road Maps</a></li>
<li> <a href="/wiki/Project:Public_Relations/Media" title="Project:Public Relations/Media">Media</a></li>
<li> <a href="/wiki/Project:Public_Relations/Press_Coverage" title="Project:Public Relations/Press Coverage">Press coverage</a></li>
<li> <a href="/wiki/Project:Public_Relations/Event_Material" title="Project:Public Relations/Event Material">Event material</a></li></ul>
<!--
NewPP limit report
Cached time: 20180814200522
Cache expiry: 86400
Dynamic content: false
CPU time usage: 0.356 seconds
Real time usage: 0.408 seconds
Preprocessor visited node count: 648/1000000
Preprocessor generated node count: 2067/1000000
Post‐expand include size: 6923/2097152 bytes
Template argument size: 2201/2097152 bytes
Highest expansion depth: 9/40
Expensive parser function count: 0/100
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
100.00% 248.439 1 - -total
92.44% 229.649 1 - Template:Project
43.09% 107.063 8 - Template:ProjectMemberLine
20.16% 50.074 4 - Template:SubprojectLine
18.17% 45.139 8 - Template:ProjectMemberLineNickname
6.65% 16.529 8 - Template:Project_Member
2.64% 6.557 1 - Template:Important
1.60% 3.985 4 - Template:U
1.53% 3.808 1 - Template:Important/core
1.29% 3.207 1 - Template:IRC
-->
' |
Unix timestamp of change (timestamp) | 1534277122 |