[fork-setup] Draft & publish fork announcement

[bew]

Note

Take inspiration from my message in wezterm's Next release checklist thread
(note: not linking to it directly to avoid making other people aware of this org/repo yet)

The public-facing announcement that presents the fork, invites contributions.

Will be posted on the Wezterm repo.

Tasks

• Draft announcement (as a PR? or in a HedgeDoc?)
• Make https://github.com/orgs/rezterm-org/projects/2 public
• Post it on Wezterm repo
• Link to it in RezTerm' README

Anything else?

[bew]

Note

Title ideas:

• Announcement: RezTerm fork, a WezTerm reboot 🚀
• Announcement: RezTerm fork is open to contributions 🚀

Stuff to mention in the fork announcement

Important

Use friendly & welcoming tone

👉 Start by saying how much AI was used for this announcement (probably only for initial draft)

Context & legitimacy

• WezTerm is basically unmaintained since @[DATE], almost no reaction nor response from Wez on known communication channels
• This is a community continuation, not a hostile fork → full credit to Wez for everything he's done!
• If Wez returns, open to reconciliation / re-merging upstream

Project name & vision:

• RezTerm ftw!
• Few bullet points on the mid/long term vision

What RezTerm is right now

• Direct fork at sha <abc123>, no feature divergence yet
• Same codebase, same Lua config API — existing WezTerm configs work as-is
• (note somewhere) Binaries will be renamed to rezterm before first release
• (note somewhere) Crates won't get new releases for now (need to see if there are interest first)

Governance

• me as BDFL for now
• Decisions made in the open via Discussions before issues/PRs
• AI contribution policy: (link to AI_POLICY.md), non-negotiable for all Issues/PRs

Short-term goals

• Triage / review / merge ~50-70 upstream PRs (link to GH project?)
• Prepare pipelines and release workflows for releasing RezTerm-named artefacts
• (Out of scope? Nightly builds available at [link] — test today's main without waiting for a release)
• First release target: [rough timeframe] 🤔

How to get involved right now

• 👋 Introduce yourself (FIXME: where? in discussions?) + state what you want to help with 🤔
  link to [README] I'm interested to contribute 😉 #2
• Help with PR review work, link to PR triage project
• Explain the immediate things needed (PR testing, review)
• (if you are knowledgeable about this) Help needed to re-setup release pipelines
• Link to [Tracking-Issue] Prepare first release #8
• Need Wayland testers (TODO: make dedicated issue about it?)

Longer-term vision (brief, no commitments)
Link to vision section in README

End with a note:

• it's my first big project fork, we're here to learn!
• I don't know everything, we're here to learn !
• it's a big undertaking, want to see the project thrive with hopefully a community around it 🙃 ᕕ( ᐛ )ᕗ

---

Anything else?