Skip to content

docs: remove Sponsio Cloud launch plan from OSS_PROMISE#60

Merged
yfxiao16 merged 1 commit into
mainfrom
chore/remove-cloud-launch-plan
May 22, 2026
Merged

docs: remove Sponsio Cloud launch plan from OSS_PROMISE#60
yfxiao16 merged 1 commit into
mainfrom
chore/remove-cloud-launch-plan

Conversation

@yfxiao16
Copy link
Copy Markdown
Contributor

Summary

  • Drops the "Opens mid-May 2026." line from OSS_PROMISE.md § 2
  • Drops § 6 "Cloud waitlist" (launch date + early-access pricing + waitlist link)
  • Keeps the factual OSS / Cloud boundary description

Forward-looking launch marketing doesn't belong in OSS docs before the product ships.

Scope note: the original draft of this branch also edited the root READMEs + llms-full.txt; those were dropped so the root README stays owned by its separate curation worktree (and llms-full.txt's README-derived License blurb stays consistent with it). Net change is OSS_PROMISE.md only.

Test plan

  • Rebased onto current main, 1 ahead / 0 behind
  • git diff main shows only OSS_PROMISE.md (+1 −10)

🤖 Generated with Claude Code

The "opens mid-May 2026" launch claim, early-access pricing, and
waitlist section are forward-looking marketing that doesn't belong in
OSS docs before the product actually ships.

* OSS_PROMISE.md: drops "Opens **mid-May 2026**." from section 2
  intro; drops section 6 ("Cloud waitlist") in its entirety
  (launch date + early-access pricing + waitlist link).

Kept: the factual OSS / Cloud boundary description in OSS_PROMISE
section 2 (what Cloud will provide vs OSS).

Note: the parallel README launch-sentence edits from the original
draft of this branch are dropped — root README.md (en/zh/ja) is
curated in a separate worktree; llms-full.txt's README-derived
License blurb left untouched to stay consistent with it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@yfxiao16 yfxiao16 merged commit 730f52c into main May 22, 2026
9 checks passed
@yfxiao16 yfxiao16 deleted the chore/remove-cloud-launch-plan branch May 22, 2026 04:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant