diff --git a/content/rfc/codex/2025q4-rfc-iteration.md b/content/rfc/codex/2025q4-rfc-iteration.md new file mode 100644 index 000000000..4d8c8ff59 --- /dev/null +++ b/content/rfc/codex/2025q4-rfc-iteration.md @@ -0,0 +1,74 @@ +--- +title: RFC Iteration +tags: + - rfc + - codex +draft: false +description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected RFCs." +--- + +`vac:rfc:codex:2025q4-rfc-iteration` + +Iteration commitments generally comprise: +through discussion and curation, +support the process of auditing raw, draft, mature selected RFCs. + +This commitment covers this process for the following Codex RFCs: +block exchange, Erasure coding, Proving system + +## Description + +This commitment supports the process of the choosing which raw RFCs, +from the existing documentation to be put in pipeline to be written or updated. + +This commitment supports the audit of the following mature RFCs, which are +either in draft or raw states: +- The block exchange +- Erasure coding +- Proving system + +We will also include specification validation - +editorial work through previous and future RFCs to improve them +(identify edge cases for example) + + + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). + +## Task List + +### The Block Exchange + +- Fully qualified name: + `vac:rfc:codex:2025q2-rfc-iteration:the-block-exchange' +- Owner: cofson +- Status: 0% +- Start date: 2025/07/01 +- End date: 2025/07/20 + +### Erasure Coding + +- Fully qualified name: + `vac:rfc:codex:2025q2-rfc-iteration:erasure-coding` +- Owner: cofson +- Status: 0% +- Start date: 2025/08/01 +- End date: 2025/08/20 + +### Proving System + +- Fully qualified name: + `vac:rfc:codex:2025q2-rfc-iteration:proving-system` +- Owner: cofson +- Status: 0% +- Start date: 2025/09/20 +- End date: 2025/09/30 diff --git a/content/rfc/ift/2025q3-rfc-index-maintenance.md b/content/rfc/ift/2025q3-rfc-index-maintenance.md index 7ec0e5bd2..182f746c6 100644 --- a/content/rfc/ift/2025q3-rfc-index-maintenance.md +++ b/content/rfc/ift/2025q3-rfc-index-maintenance.md @@ -7,7 +7,7 @@ draft: false description: This commitment revolves around a continuous effort to fix and update across the relevant RFC websites (including the communication). --- -`vac:rfc:ift:2025q2-rfc-index-maintenance` +`vac:rfc:ift:2025q3-rfc-index-maintenance` ## Description diff --git a/content/rfc/ift/2025q4-rfc-index-maintenance.md b/content/rfc/ift/2025q4-rfc-index-maintenance.md new file mode 100644 index 000000000..3c3813293 --- /dev/null +++ b/content/rfc/ift/2025q4-rfc-index-maintenance.md @@ -0,0 +1,61 @@ +--- +title: rfc-index-maintenance +tags: + - rfc + - vac +draft: false +description: This commitment revolves around a continuous effort to fix and update across the relevant RFC websites (including the communication). +--- + +`vac:rfc:ift:2025q4-rfc-index-maintenance` + +## Description + +This commitment revolves around a continuous effort +to fix and update across the relevant RFC websites +(including the communication). + +**Alignment with VAC Narratives:** + +- The information needs to be up to date +in order for projects and external parties +to have a clear view of information provided, +in accordance with the IFT standards. + +## Task List + +### Maintenance + +- Fully qualified name: `vac:rfc:ift:2025q3-rfc-index-maintenance:maintenance` +- Owner: Filip +- Status: not started +- Start date: 2025/10/01 +- End date: 2025/12/31 + +#### Description + +Check on the rfc-index, +fix any issues that arise and +note them properly. + +#### Deliverables + +- Fixed version of rfc-index + +### Maintenance of vac.dev + +- Fully qualified name: `vac:rfc:ift:2025q3-rfc-index-maintenance:maintenance-of-vac.dev` +- Owner: Filip +- Status: not started +- Start date: 2025/10/01 +- End date: 2025/12/31 + +#### Description + +Check on the vac.dev, +fix any issues that arise and +note them properly. + +#### Deliverables + +- Fixed version of vac.dev \ No newline at end of file diff --git a/content/rfc/nomos/2025q4-rfc-iteration.md b/content/rfc/nomos/2025q4-rfc-iteration.md new file mode 100644 index 000000000..3cb4a9777 --- /dev/null +++ b/content/rfc/nomos/2025q4-rfc-iteration.md @@ -0,0 +1,56 @@ +--- +title: RFC Iteration +tags: + - rfc + - nomos +draft: false +description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Nomos RFCs." +--- + +`vac:rfc:nomos:2025q4-rfc-iteration` + +Iteration commitments generally comprise: +through discussion and curation, +support the process of auditing raw, draft, mature selected Nomos RFCs. + +## Description + +This commitment supports the process of the writing raw RFCs, +from the existing documentation and specifications in Nomos team Notion. +We will also include specification validation - +editorial work through previous and future RFCs to improve them +(identify edge cases for example) +as well as making sure that the relevant document has enough information +in order to ease the developer experience for coming developers. + +The specifications in pipeline are all the specifications for Nomos v1. + + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). + +## Task List + +### Choosing New RFCs + + Fully qualified name: + `vac:rfc:nomos:2025q2-rfc-iteration-choosing-new-rfcs` +- Owner: cofson +- Status: not started +- Start date: 2025/07/01 +- End date: 2025/09/30 + +#### Description + +This task revolves around staying up to date with the Nomos documentation. +closely following which specifications are in "green" status +and thus ready for being included in the rfc-index. + diff --git a/content/rfc/status/2025q3-rfc-iteration.md b/content/rfc/status/2025q3-rfc-iteration.md index 4da1e0109..147db39aa 100644 --- a/content/rfc/status/2025q3-rfc-iteration.md +++ b/content/rfc/status/2025q3-rfc-iteration.md @@ -24,7 +24,6 @@ as well as making sure that the relevant document has enough information in order to ease the developer experience for coming developers. The specifications in pipeline: -- Blend - diff --git a/content/rfc/status/2025q4-rfc-iteration.md b/content/rfc/status/2025q4-rfc-iteration.md new file mode 100644 index 000000000..2417bb35b --- /dev/null +++ b/content/rfc/status/2025q4-rfc-iteration.md @@ -0,0 +1,44 @@ +--- +title: RFC Iteration +tags: + - rfc + - nomos +draft: false +description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Nomos RFCs." +--- + +`vac:rfc:status:2025q4-rfc-iteration` + +Iteration commitments generally comprise: +through discussion and curation, +support the process of auditing raw, draft, mature selected Nomos RFCs. + +## Description + +This commitment supports the process of the writing raw RFCs, +from the existing documentation and specifications in Nomos team Notion. +We will also include specification validation - +editorial work through previous and future RFCs to improve them +(identify edge cases for example) +as well as making sure that the relevant document has enough information +in order to ease the developer experience for coming developers. + +The specifications in pipeline: +- + + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). + +## Task List + + + diff --git a/content/rfc/waku/2025q4-rfc-iteration.md b/content/rfc/waku/2025q4-rfc-iteration.md new file mode 100644 index 000000000..3edf707ba --- /dev/null +++ b/content/rfc/waku/2025q4-rfc-iteration.md @@ -0,0 +1,50 @@ +--- +title: RFC Iteration +tags: + - rfc + - waku +draft: false +description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Waku RFCs." +--- + +`vac:rfc:waku:2025q4-rfc-iteration` + +Iteration commitments generally comprise: +through discussion and curation, +support the process of auditing raw, draft, mature selected Waku RFCs. + +## Description + +This commitment supports the audit of mature RFCs, which are +either in draft or raw states. The audit comprises of: +- Reading through the spec; +- Checking the relevant codebase; +- Changing the parts of the spec (descriptions and codebase) where applicable; +- Updates of relevant links; +- Changing the RFC status (optional); +- Going through rounds of feedback with the relevant project team; +- Adding clarifications where needed in the spec; +- Checking for inconsistencies with other documentation/codebase. + +The following RFCs will be worked on in this quarter: +- + +We will also include specification validation - +editorial work through previous and future RFCs to improve them +(identify edge cases for example) + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). +- We aim to provide feedback on specifications +from the point of view of a new developer. + +## Task List + diff --git a/content/rfc/zerokit/2025q4-rfc-iteration.md b/content/rfc/zerokit/2025q4-rfc-iteration.md new file mode 100644 index 000000000..8872022b0 --- /dev/null +++ b/content/rfc/zerokit/2025q4-rfc-iteration.md @@ -0,0 +1,50 @@ +--- +title: RFC Iteration +tags: + - rfc + - waku +draft: false +description: "Iteration commitments generally comprise: through discussion and curation, support the process of auditing raw, draft, mature selected Waku RFCs." +--- + +`vac:rfc:zerokit:2025q4-rfc-iteration` + +Iteration commitments generally comprise: +through discussion and curation, +support the process of auditing raw, draft, mature selected Waku RFCs. + +## Description + +This commitment supports the audit of mature RFCs, which are +either in draft or raw states. The audit comprises of: +- Reading through the spec; +- Checking the relevant codebase; +- Changing the parts of the spec (descriptions and codebase) where applicable; +- Updates of relevant links; +- Changing the RFC status (optional); +- Going through rounds of feedback with the relevant project team; +- Adding clarifications where needed in the spec; +- Checking for inconsistencies with other documentation/codebase. + +The following RFCs will be worked on in this quarter: +- + +We will also include specification validation - +editorial work through previous and future RFCs to improve them +(identify edge cases for example) + +**Alignment with VAC Narratives:** + +- The VAC RFC team plans to become a repository +for RFCs regarding all IFT + projects. +- By promoting the RFC culture, +we hope to incentivize projects to submit their RFCs +to the rfc-editors team. +- We aim to have the broader web3 community use our RFCs +in their projects, similar to [IETF](https://www.ietf.org/). +- We aim to provide feedback on specifications +from the point of view of a new developer. + +## Task List +