Mastodon — first public release
Released [Project] [version] under [license]. It is a [one-line description] for [audience] who need [capability]. Install: [install command] What works today: [feature 1], [feature 2]. What does not yet: [known limitation]. Code and issues: [repo link] Contributions welcome, especially [area]. #OpenSource #[LanguageTag] #[TopicTag]
X — install-first
[Project] [version] is out. [License]. [One-line description.] [install command] Docs: [link] Repo: [link]
LinkedIn — why we open-sourced it
Today we open-sourced [Project], the [description] we have used internally for [time]. Why open source: [reason, e.g. others kept asking, we want outside review, we rely on open source ourselves]. What it does: - [Capability] - [Capability] What it does not do: [honest scope limit]. License: [license]. Repository: [link] If you try it, issues and pull requests are the best feedback.
Bluesky — contributor thanks
[Project] [version] shipped with help from [number] contributors, [number] of them new. Thanks [@handle], [@handle], [@handle]. Notes: [link]
Tips
- Put the install command in the post itself. The fewer clicks between reading and trying, the more people try.
- State the license. Many developers and companies filter projects by license before reading further.
- Name a known limitation. It sets expectations and invites the right contributions.
- Label good first issues in the repository before announcing, and link to them for new contributors.
Frequently asked questions
Where should I announce an open source release?
Mastodon and Bluesky have active developer communities, X still reaches many developers, and LinkedIn works for projects aimed at companies. Also post in the project's own forum or discussion board.
Can a GitHub release trigger the announcement?
Yes. A GitHub release can become a draft in SocialHandoff, where an agent fills this template and a maintainer approves it before it publishes to each network.