Submit the launch to the newsletters and syndicate the org story

[lesnik512]

Migrated from planning/deferred.md, retired in the move to the PR-body-as-spec convention (#50).

What

A standing program, with no rooms to run:

• Participate in the official Python Discord and the FastAPI / Litestar / FastStream community
  channels.
• Submit to PyCoder's Weekly and Python Weekly.
• Pitch Talk Python to Me / Python Bytes once the docs are polished.
• Cross-post the org-story piece to dev.to / Hashnode with a canonical link back.
• Answer real DI/outbox questions on Stack Overflow.

This is the concrete form of the standing principle in
docs/adr/0002-discussions-is-the-only-owned-channel.md: borrow audiences before building our
own.

Why it was deferred

Highest-ROI gap for a young project, but unscheduled — it is a standing program rather than a task,
and the newsletter/podcast pitches land best alongside the launch.

Revisit trigger

Newsletters and cross-posts at launch; podcasts once the docs are polished enough to withstand the
traffic.

[lesnik512]

This was generated by AI during triage.

Human Brief

Category: enhancement
Summary: Submit the launch to PyCoder's Weekly and Python Weekly, and syndicate the org-story piece to dev.to and Hashnode with a canonical link back.

Scope change made during triage. As filed, this issue was a "standing program rather than a task", which meant it had no completion criteria and could never be closed. It has been reduced to the launch-timed work that can:

• Kept: newsletter submissions, and syndication of the org-story piece.
• Split out to Pitch Talk Python to Me and Python Bytes once the docs link gate is green #72: the Talk Python / Python Bytes pitches, which hung on the unevaluatable gate "once the docs are polished". That is now gated on the link gate in Add the offline link gate to the 18 green repos, and unpublish the ADRs in the two that have them #66.
• Dropped, because it is already recorded: the perpetual participation half (Python Discord, framework community channels, Stack Overflow). The principle it expressed, borrow audiences before building our own, already lives in docs/adr/0002-discussions-is-the-only-owned-channel.md, and duplicating it in an unclosable issue would restate a record that AGENTS.md says should have exactly one home. The venue list itself is re-derivable and deliberately not written down.
• Promoted to the ADR: the conduct rule for borrowing, which was previously unwritten, is now recorded in ADR-0002 under "Borrowing in practice". Link back only where the linked page actually answers the question, never as a bare repo drop; and when a question answered in someone else's venue exposes a docs gap, that gap becomes an issue here.

Blocked on: #57. Both remaining deliverables consume the launch, they do not produce it.

Boundary with #57: #57 owns first publication of the org-story piece and therefore owns the canonical URL. This issue owns syndication only, and cannot start until that URL exists. Newsletter submissions are here too, since they submit the launch links rather than produce them.

Why this cannot be delegated to an agent:

• Newsletter submissions and dev.to / Hashnode publishing run through the maintainer's own accounts and identity.
• The pitch to a newsletter editor is a judgment call about framing, made once per launch.

Acceptance criteria:

• Org-story piece published at its canonical URL first (Fire the coordinated launch (promotion strategy, Phase 4) #57)
• Submitted to PyCoder's Weekly
• Submitted to Python Weekly
• Cross-posted to dev.to with rel=canonical pointing at the original
• Cross-posted to Hashnode with rel=canonical pointing at the original
• No syndicated copy outranks the canonical URL, checked once after indexing

Out of scope:

• Podcast pitches (Pitch Talk Python to Me and Python Bytes once the docs link gate is green #72)
• The launch posts and the org-story piece itself (Fire the coordinated launch (promotion strategy, Phase 4) #57)
• Opening any owned channel (Open the org chat rooms (Telegram + Discord) during launch week #58). This issue touches borrowed audiences only, in the sense both terms now carry in CONTEXT.md.