Repository navigation
🗓️ Add 2023 meetings - #2786
🗓️ Add 2023 meetings#2786JFWooten4 wants to merge 9 commits into
Conversation
Co-authored-by: Codex Web <noreply@openai.com>
There was a problem hiding this comment.
Pull request overview
Adds 11 archived 2023 developer meetings with recordings, summaries, metadata, and generated routes.
Changes:
- Adds January–May 2023 meeting records.
- Registers a new author and meeting tags.
- Updates generated routes and pagination.
Recommendation: NEEDS-CHANGES — correct skipped heading levels and inaccurate CAP/resource labels.
Reviewed changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated 16 comments.
Show a summary per file
| File | Description |
|---|---|
routes.txt |
Adds meeting, tag, and pagination routes. |
meetings/authors.yml |
Registers the meeting-note author. |
meetings/2023-01-12.mdx |
Archives the Auth Next discussion. |
meetings/2023-02-23.mdx |
Archives configuration and state-rent discussions. |
meetings/2023-03-02.mdx |
Archives authorization, fees, and storage discussions. |
meetings/2023-03-09.mdx |
Archives fee-model and authorization discussions. |
meetings/2023-03-16.mdx |
Archives state-expiration planning. |
meetings/2023-03-30.mdx |
Archives metadata and token-interface discussions. |
meetings/2023-04-06.mdx |
Archives storage and upgradeability discussions. |
meetings/2023-04-13.mdx |
Archives rent discussions and a storage workshop. |
meetings/2023-04-20.mdx |
Archives state-expiration economics discussions. |
meetings/2023-04-27.mdx |
Archives storage-lifecycle discussions. |
meetings/2023-05-04.mdx |
Archives expiration-ledger design discussions. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Use unpadded proposal identifiers in meeting prose while preserving canonical padded filenames in URLs. Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
|
🤖 Automated message from the Stellar Triage Bot. Reviewing because this PR is stale (no update in 4+ weeks). Should the docs archive 2023 meetings? This is the same call as #2782, #2783, #2784 and #2785. @kaankacar called retroactive archives out of scope on #1087. @kaankacar @ElliotFriend
|
|
Hi @JFWooten4, thank you for this PR. We use the same rule as in #2782 to #2785: the archive includes protocol meetings and standards discussions only. All 11 pages are Soroban Design Discussions, so they all stay. We spot-checked Please make these changes:
Thanks again for your work on this archive. |
|
🤖 Automated message from the Stellar Triage Bot. Standing down because @kaankacar added How to reach me:
|
for #1087