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

docs: add social-team.md #494

Merged
merged 18 commits into from
Apr 28, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
80 changes: 80 additions & 0 deletions social-team.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
# Social Team

Node.js as a project has a Social Team, a joint team between the TSC and CommComm to which the project has delegated the management of its official social media.

## Responsibilities

The Social Team is tasked with maintaining the project's social accounts. This includes:

- Content creation
- Amplification of our community
- Sharing, retweeting, and so on
- Engagement with our community
- Liking, replying, and so on
- Updating account metadata (like bio, avatar, header images, and so on)

With regard to posts and community interaction, there is no requirement or entitlement - rather, all posts and interactions are made and/or validated completely at the discretion of the Social Team's members.

### Platforms

This team controls and maintains the various social platforms in which Node.js has an official presence:

- [Node.js on Twitter](https://twitter.com/nodejs)
- [Node.js on Facebook](https://www.facebook.com/nodejsfoundation)
- [Node.js on LinkedIn](https://www.linkedin.com/company/node.js-foundation/)

### Access

Social Team members will have full access to all [platforms](#platforms).

### Expectations

The basic expectations are that **all** Social Team members will have both a willingness and ability to...

- Spend time engaging on various platforms weekly, or communicate the inability to do so with other social team members and work with them to ensure there is *some* coverage
- Spend time working with other social team members on building out good content
- Spend time working with project committees, working groups, initiatives, and teams to build effective outward communication as needed

### Repositories

The Social Team will be responsible for and maintain the following:
Copy link
Member

Choose a reason for hiding this comment

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

Fix: Readability.

Suggested change
The Social Team will be responsible for and maintain the following:
The Social Team will be responsible for, and maintain the following:


- [nodejs/tweet](http://github.com/nodejs/tweet): a repo leveraging [Twitter Together](https://github.com/gr2m/twitter-together) that enables project members to queue up tweets to [@nodejs](https://twitter.com/nodejs) from within GitHub.
Copy link
Member

Choose a reason for hiding this comment

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

Fix: Readability.

Suggested change
- [nodejs/tweet](http://github.com/nodejs/tweet): a repo leveraging [Twitter Together](https://github.com/gr2m/twitter-together) that enables project members to queue up tweets to [@nodejs](https://twitter.com/nodejs) from within GitHub.
- [nodejs/tweet](http://github.com/nodejs/tweet): a repo leveraging [Twitter Together](https://github.com/gr2m/twitter-together) which enables project members to queue up tweets to [@nodejs](https://twitter.com/nodejs) from within GitHub.


bnb marked this conversation as resolved.
Show resolved Hide resolved
## Membership

### Nominations

Nominations and self-nominations are open to **project members** on an ongoing basis. An issue should be created in [nodejs/admin](https://github.com/nodejs/admin) for any kind of nomination.

### Objections

Membership in the Social Team **requires** zero objections from [TSC](https://github.com/nodejs/tsc) and [CommComm](https://github.com/nodejs/community-committee) members.

Should there be an objection from a TSC member or CommComm member to a nomination, there are multiple paths to surface it:

- Directly in a nomination issue
- By requesting a peer on the TSC or CommComm to proxy your objection
- Through the TSC or CommComm chairperson who will proxy your objection

An objection *does* require substantiation beyond a simple `-1`, which can be commented or otherwise passed along through an objection proxy. Since this is a role built upon extreme trust and high impact, the substantiation is not negotiable by either the nominee or other TSC or CommComm members.

More explicitly: If an objection is stated, the nomination does not pass.

#### Re-nomination

If a nomination is objected to, the nominee can be re-nominated or re-self-nominated after 6 months.

bnb marked this conversation as resolved.
Show resolved Hide resolved
### Re-certification

An annual recertification vote is required for all Social Team members. For an individual to be recertified, a simple majority vote in favor of recertification is required by both the TSC and CommComm.

### Removal

A member of the Social Team may be removed by the request of any TSC or CommComm member. This request can be raised in the same way as is listed for raising an [objection](#objection) to a nomination, in the original nomination issue.

### Membership Expectations

The Social Team is expected to adhere to the [Membership Expectations](https://github.com/nodejs/admin/blob/master/MemberExpectations.md) document.

Furthermore, the Social Team is expected to be responsive and open to good-faith feedback from both project and community members about their approach to content and interactions on the platforms they maintain. Social Team members are expected to be proactive in reacting to any good-faith feedback received from project and community members.