Repository navigation
🗓️ Add 2022 meetings - #2785
🗓️ Add 2022 meetings#2785JFWooten4 wants to merge 16 commits into
Conversation
Co-authored-by: Codex Web <noreply@openai.com>
There was a problem hiding this comment.
Pull request overview
Adds 22 archived 2022 Stellar meeting recordings and summaries to the meetings collection.
Changes:
- Adds protocol, Soroban, and community meeting pages.
- Adds an author profile and generated routes.
- Requires corrections to several CAP identifiers and links.
Recommendation: NEEDS-CHANGES — correct the inaccurate CAP-35, CAP-52, and CAP-46 resource references.
Reviewed changes
Copilot reviewed 24 out of 24 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
routes.txt |
Adds meeting, pagination, and tag routes. |
meetings/authors.yml |
Adds the meeting author profile. |
meetings/2022-02-03.mdx |
Archives the CAP-42 discussion. |
meetings/2022-02-17.mdx |
Archives CAP and SPEEDEX discussions. |
meetings/2022-03-03.mdx |
Archives CAP-42 and CAP-44 discussions. |
meetings/2022-03-11.mdx |
Archives the Stellar NFT workshop. |
meetings/2022-03-15.mdx |
Archives the blockchain bootcamp panel. |
meetings/2022-04-28.mdx |
Archives the early Soroban runtime discussion. |
meetings/2022-05-05.mdx |
Archives asset-interoperability discussions. |
meetings/2022-05-12.mdx |
Archives asset-compliance discussions. |
meetings/2022-05-17.mdx |
Archives the Colombia payment-corridor panel. |
meetings/2022-05-19.mdx |
Archives contract-invocation discussions. |
meetings/2022-05-26.mdx |
Archives storage and interaction discussions. |
meetings/2022-06-02.mdx |
Archives footprint and interoperability discussions. |
meetings/2022-06-23.mdx |
Archives event and fee-model discussions. |
meetings/2022-07-01.mdx |
Archives asset balance-model discussions. |
meetings/2022-07-12.mdx |
Archives the Jump Cannon Q&A. |
meetings/2022-08-31.mdx |
Archives the SCF winners panel. |
meetings/2022-09-16.mdx |
Archives the SCF bootcamp session. |
meetings/2022-11-17.mdx |
Archives the standardized-asset discussion. |
meetings/2022-12-07.mdx |
Archives the Gitpod development demo. |
meetings/2022-12-12.mdx |
Archives the leadership interview. |
meetings/2022-12-15.mdx |
Archives the humanitarian-aid announcement. |
meetings/2022-12-22.mdx |
Archives the Soroban Auth Next discussion. |
Suppressed comments (2)
meetings/2022-05-12.mdx:35
- This URL resolves to CAP-40, whose canonical title and subject are the signed-payload signer—not asset clawback. Link CAP-35 so this resource supports the session summary instead of sending readers to an unrelated protocol proposal.
- [CAP-40: Protocol-Level Asset Clawback](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0040.md)
meetings/2022-06-23.mdx:53
- The label names CAP-46-03 Host Functions, but this URL opens CAP-46-05 Smart Contract Data. Correct the filename so the resource resolves to the specification described by the link text.
- [CAP-0046-03: Smart Contract Host Functions](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-05.md)
💡 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>
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>
CAP-0046-04 was deleted from stellar-protocol master in stellar#1401, so pin the link to its last revision. Drop lightmint.io and stellar.org/impact/financial-inclusion, which no longer resolve and have no archived copy.
The recording was uploaded on Thursday 2022-12-01, the protocol meeting slot. It debates moving the built-in token contract to single balances, which landed in rs-soroban-env#615 on 2022-12-16. On 2022-07-01 the project was still called Jump Cannon and had no built-in token contract. The CAP-46-4 link moves with the page and is pinned like the others.
|
🤖 Automated message from the Stellar Triage Bot. Reviewing because this PR is stale (no update in 4+ weeks). Should the docs archive 2022 meetings? This is the same call as #2782, #2783 and #2784. @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, #2783, and #2784: the archive includes protocol meetings and standards discussions only. Please keep these 14 pages:
We spot-checked Please remove these eight pages:
These are talks, tutorials, SCF sessions, and announcements, not meetings. The recordings stay available on YouTube. On the 14 remaining pages:
One meeting is missing: the Open Protocol Discussion of 2022-06-09. It covers the Protocol 19 upgrade and CAP-54. Can you add it to this PR? Thanks again for your work on this archive. |
|
🤖 Automated message from the Stellar Triage Bot. Standing down because @kaankacar added bot:hands-off. I will leave this PR alone until someone calls me back in. How to reach me:
|
…s to Mintlify, add missing 2022-06-09 meeting, and address review feedback
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
|
For Jump Cannon, that transition was intentional to align all Soroban discussions in the same category for the filter card in #2373. I disagree with removing the SCF pitch sessions and talks. The Community Fund represents about 10% of the Foundation's annual lumen burn in outlays alone without considering staffing and setup costs, it appears. With tokenomics on the table for discussion, it's disingenuous to ignore documentation of how the Community Fund performs and evolves over time. An active discussion at stellar/stellar-protocol#2052 P7 directly raised the question of spending transparency, and these sessions are a significant answer to that question. The Fund represents the Foundation's most public-facing direct commitment of lumens for the Mandate for innovation. It should have proper documentation to compare against other potential uses of the network's funds. I have tried bringing these points up in other forums for years, most recently leading to trivial PRs like stellar/scf-handbook#40 sitting unresolved for months on end. I do not think the Community Fund's internal SDF team will adopt these on other site mediums, and I do not think it's appropriate to hide them from a community documentation forum. We cannot contribute quality governance proposals to better allocate XLM if we don't have shared, comprehensive, accessible historical documentation. |
Add filename-derived dates to the opening attribution lines of all fifteen 2022 meeting pages, including the June 9 Open Protocol Discussion. Preserve John Wooten's existing credit and GitHub profile without changing frontmatter, meeting content, recordings, tags, or navigation. Co-authored-by: ChatGPT 6 <noreply@openai.com>
for #1087