-
Notifications
You must be signed in to change notification settings - Fork 135
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
Create repository nodejs/tweet
under the Social Team
#529
Comments
cc @nodejs/tsc @nodejs/community-committee |
+1 |
2 similar comments
+1 |
+1 |
+1. A clear definition of what type of content qualifies (or a best practice around that) would be great to set upfront, IMO. |
+1 |
Plenty of +1s. No -1s. Been open for > 3 days. Going to go ahead and kick this off here soon. |
This is now completed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of my initial recommendation around creating the social team was to create a repository and use Twitter Together by @gr2m (a former CommComm member ❤️ ) to enable us to provide more broad control of the Twitter account for project members outside of just Social Team members.
As a social team member, I've now gone through and requested API access from Twitter for the @nodejs account and have been approved.
I'd like to go ahead and create this repository now, with the following goals:
This also opens up the possibility for some level of automation for the social team to enhance the content we're putting out - think along the lines of a weekly calendar roundup that balances signal vs. noise.
The text was updated successfully, but these errors were encountered: