Twitter Account
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
It might be useful to have a twitter account and maybe use some common hashtag (#lesscss?). It could be used for
- new release announcements,
- new feature announcements,
- occasional tip&trics / articles / doc updates,
- active discussions when we want more feedback,
- etc.
As far as I know, there is no feed you could listen to and instantly know about these things. I usually learn about new release when someone mentions it on unrelated issue.
It does not have to tweet often, only when something important happen. It may also help with community building, twitter is less formal then github issues. I have such account for less4j and it is minimum overhead.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. Start by reviewing the discussion and deciding whether the project wants a Twitter account, who owns it, and which announcements it should cover; the work is done when ownership and an agreed posting process are established.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100