mirror of
https://github.com/vacp2p/roadmap.git
synced 2026-01-07 23:04:01 -05:00
Fixes according to comments
- Adding preview to the roadmap - Fixing index - A couple of typos
This commit is contained in:
Cofson
@@ -49,7 +49,7 @@ in their projects, similar to [IETF](https://www.ietf.org/).
|
||||
### The Block Exchange
|
||||
|
||||
- Fully qualified name:
|
||||
`vac:rfc:codex:2025q2-rfc-iteration:the-block-exchange'
|
||||
`vac:rfc:codex:2025q3-rfc-iteration:the-block-exchange'
|
||||
- Owner: cofson
|
||||
- Status: 0%
|
||||
- Start date: 2025/07/01
|
||||
@@ -58,7 +58,7 @@ in their projects, similar to [IETF](https://www.ietf.org/).
|
||||
### Erasure Coding
|
||||
|
||||
- Fully qualified name:
|
||||
`vac:rfc:codex:2025q2-rfc-iteration:erasure-coding`
|
||||
`vac:rfc:codex:2025q3-rfc-iteration:erasure-coding`
|
||||
- Owner: cofson
|
||||
- Status: 0%
|
||||
- Start date: 2025/08/01
|
||||
@@ -67,7 +67,7 @@ in their projects, similar to [IETF](https://www.ietf.org/).
|
||||
### Proving System
|
||||
|
||||
- Fully qualified name:
|
||||
`vac:rfc:codex:2025q2-rfc-iteration:proving-system`
|
||||
`vac:rfc:codex:2025q3-rfc-iteration:proving-system`
|
||||
- Owner: cofson
|
||||
- Status: 0%
|
||||
- Start date: 2025/09/20
|
||||
|
||||
@@ -1,74 +0,0 @@
|
||||
---
|
||||
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
|
||||
@@ -1,61 +0,0 @@
|
||||
---
|
||||
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
|
||||
@@ -4,6 +4,33 @@ tags:
|
||||
- rfc
|
||||
- vac
|
||||
---
|
||||
|
||||
## 2025q3 `vac:rfc:`
|
||||
|
||||
|
||||
### `ift:`
|
||||
- [[rfc/ift/2025q3-rfc-culture-establishment|2025q3-rfc-culture-establishment]]
|
||||
+ [[rfc/ift/2025q3-rfc-index-maintenance|2025q3-rfc-index-maintenance]]
|
||||
+ [[rfc/ift/2025q3-spec-impl-test-coverage-support|2025q3-spec-impl-test-coverage-support]]
|
||||
|
||||
### `waku:`
|
||||
- [[rfc/waku/2025q3-rfc-iteration|2025q3-rfc-iteration]]
|
||||
|
||||
### `nomos:`
|
||||
- [[rfc/nomos/2025q3-rfc-iteration|2025q3-rfc-iteration]]
|
||||
|
||||
### `codex:`
|
||||
- [[rfc/codex/2025q3-rfc-iteration|2025q3-rfc-iteration]]
|
||||
|
||||
### `nescience:`
|
||||
- [[rfc/nescience/2025q3-rfc-iteration|2025q3-rfc-iteration]]
|
||||
|
||||
### `status:`
|
||||
- [[rfc/status/2025q3-rfc-iteration|2025q3-rfc-iteration]]
|
||||
|
||||
### `zerokit:`
|
||||
- [[rfc/zerokit/2025q3-rfc-iteration|2025q3-rfc-iteration]]
|
||||
|
||||
## 2025q2 `vac:rfc:`
|
||||
|
||||
|
||||
|
||||
@@ -1,56 +0,0 @@
|
||||
---
|
||||
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.
|
||||
|
||||
52
content/rfc/preview.md
Normal file
52
content/rfc/preview.md
Normal file
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: RFC Roadmap Preview
|
||||
tags:
|
||||
- rfc
|
||||
- vac
|
||||
---
|
||||
|
||||
## Roadmap Preview
|
||||
|
||||
### 2025Q3
|
||||
- Nomos
|
||||
- Continuing with the green v1 specs
|
||||
- Blend
|
||||
- P2P Network Specification
|
||||
- Common Cryptographic Components
|
||||
- Codex specs - continuing from the initial start from q2:
|
||||
- Block Exchange
|
||||
- Erasure Coding
|
||||
- Proving System
|
||||
- Waku
|
||||
- Reiterating on the updated specs from this year
|
||||
- Might include specs from layers built on top of Waku
|
||||
- Details coming
|
||||
- Nescience
|
||||
- Review and adding potential new specifications
|
||||
- IFT
|
||||
- Culture establishment - continuing team communication
|
||||
- Maintenance of rfc-index and vac.dev - continued task
|
||||
- Collaboration with the QA team on feedback to projects
|
||||
- Status
|
||||
- Inclusion of new RFCs for L2 (contracts for example)
|
||||
- Zerokit
|
||||
- Starting the first RFCs
|
||||
### 2025Q4
|
||||
- Nomos
|
||||
- Continuing with the rest of ready v1 specs so that we have all of the v1 specs before year-end - depending also on the team
|
||||
- Codex
|
||||
- After the initial 3, depending on the communication with the team, adding new specifications to the pipeline
|
||||
- Waku
|
||||
- Maintenance mode - working on the next specs in the pipeline
|
||||
- Potentially specs from layers build on waku
|
||||
- Nescience
|
||||
- Maintenance mode + adding new RFCs as the documentation comes from the team
|
||||
- Status
|
||||
- Maintenance mode + adding new RFCs as the documentation comes from the team
|
||||
- Zerokit
|
||||
- Maintenance mode + adding new RFCs as the documentation comes from the team
|
||||
|
||||
#### Uncategorized
|
||||
The following items are not part of our current roadmap. They haven't been requested by any consumer of RFC, so they do not have any prioritization status. Still, they are recorded here potential future consideration.
|
||||
|
||||
- None so far
|
||||
@@ -1,44 +0,0 @@
|
||||
---
|
||||
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
|
||||
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ from the point of view of a new developer.
|
||||
### 30/ADAPTIVE-NODES
|
||||
|
||||
- Fully qualified name:
|
||||
`vac:rfc:waku:2025q1-rfc-iteration:30/adaptive-nodes`
|
||||
`vac:rfc:waku:2025q2-rfc-iteration:30/adaptive-nodes`
|
||||
- Owner: jimstir
|
||||
- Status: 100% (https://github.com/vacp2p/rfc-index/pull/147)
|
||||
- Start date: 2025/04/04
|
||||
|
||||
@@ -1,50 +0,0 @@
|
||||
---
|
||||
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
|
||||
|
||||
@@ -1,50 +0,0 @@
|
||||
---
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user