This repository serves as a curation tool for the @MozillaCH Twitter account. Each issue represents a Tweet or Retweet on that account. The issue gets validated by a service, if it is tweetable. If it is deemed ready and the curators of the Twitter account accept the content it will eventually be tweeted. This allows any user with a GitHub account to suggest content for the Twitter account while still retaining control over what is actually tweeted. Further it simplifies letting multiple users tweet from a single account.
To suggest tweet content, open an issue in this repository and fill out the issue template. The issue will be added to the "Ideas" column on our project board.
Tweets should be English, though linked content does not need to be English. You can attach images by uploading them to the issue and embedding them using the GitHub image syntax in the tweet content.
A tweet does not need to be scheduled to a specific time. Please only schedule it to a specific time if the content is time-sensitive, like event notices or campaigns.
To reply to a tweet add a ## Reply to section to the issues and paste the link to the tweet to reply to as its content. Example:
## Reply to
https://twitter.com/MozillaCH/status/917786667259482124The template suggests a normal tweet by default, but you can also retweet a tweet by changing the ## Tweet Content heading to ## Retweet and pasting a link to the tweet to retweet as its contents. Example:
## Retweet
https://twitter.com/MozillaCH/status/917786667259482124The service will assign the "ready" label, once your tweet satisfies the formating restrictions of the service and its contents will be tweetable. It will report any outstanding issues else.
Curators will now take over and first move the issue into the "Proofread" column and someone will be assigned to proof read it. Once that is done and potential spelling mistakes are fixed, the issue will finally be moved to "To Tweet" where it will be tweeted.
Mentions are automatically added to the "Needs Reaction" column and a curator is assigned to handle creation of a reply. It then moves through the same stages as a tweet submitted as idea.
Events for the filter query "switzerland" (the same query used for the events widget on mozilla.ch) will automatically be added to the "Events" column. It has its due date set for the event start. Curators should then at least create an announcement tweet from it and move it through the same stages as a tweet submitted as idea. Optionally a retweet of the tweet should be queued once the original event tweet was tweeted.
If tweet content is changed last-minute after the tweet is approved for reasons that weren't discussed in the issue, we may exclude you in the future from submitting tweets.
The general Mozilla Community Participation Guidelines apply.
Curators are members of the mozilla.ch community that are active around the mozilla.ch Twitter account and moderate tweet content in this repository.
After 5 of your tweets have been successfully approved, you can nominate yourself as a curator by opening a thread in our discourse category. Please also mention if you intend to handle mentions to the Twitter account or not. At least two curators who have interacted with the nominee in the context of this repository before must vouch for them for the nomination to pass.
Members of the focus group can get curator status without formal self-nomination.
Curators who have not interacted with the repository for 3 months may have their access rights revoked, but can re-nominate themselves at any point.
Curators should not move issues with tweet content they created through the board. Curators should self-assign themselves to an issue if they are handling its movements through a board and are coaching the contributor that is authoring a tweet.
Curators can volunteer to also handle mentions, where they will be assigned in revolving order to incoming mentions on the Twitter account and will author replies. A curator may defer to other community memebers to suggest content for the reply, but only curators will be able to actually author the tweet (since the issue created by the service has to be edited).
Curators that feel confident in English orthography and grammar should proof-read tweets pending in the "Proofread" column and move them to the "To Tweet" column when tweet content is error-free and they have not authored the content themselves.
Sounds good to me! Thanks for this work.
Good question. The curators themselves? Or is that a task for the focus group?