How temporalio/proposals works
This is an archived documentation repository for selected Temporal feature proposals, not an implementation of Temporal itself. Its documented contributor workflow starts with a proposal issue that follows the repository’s template; the repository tracks selected proposals. The remaining files organize proposals and design material by SDK, API, core, server, and cross-cutting topic. The tree supports these topic groupings, but no source excerpts were provided, so the graph does not infer relationships among proposal documents or claim their designs were implemented.
Main entry points: proposal-template.md Issue template · README.md Selected proposals
Components 20
Proposal intake
- Proposal issue
- Issue template
.github/ISSUE_TEMPLATE/proposal-template.md - Selected proposals
README.md
SDK proposals
- Kotlin SDK
kotlin - TypeScript SDK
typescript - Go SDK
go - Python SDK
python - .NET SDK
dotnet - Ruby SDK
ruby - Rust SDK
rust - PHP SDK
php
Cross-cutting proposals
- SDK-wide topics
all-sdk - Worker versioning
versioning - Developer tools
dev-tools
Other components
- Contributor
Connections 3
- Contributor → Proposal issue: creates
README.md - Proposal issue → Issue template: follows
README.md - Proposal issue → Selected proposals: tracked selectively
README.md