vacp2p
/
rfc-index
mirror of https://github.com/vacp2p/rfc-index.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
216 Commits 30 Branches 0 Tags 9.2 MiB
Markdown 100%
Go to file
Jimmy Debe 49d8578b84
Update peer-exchange.md 		2024-03-21 16:06:30 -04:00
codex Vac RFC index initial structure 2024-01-22 19:06:06 +01:00
nomos Update and rename CLARO.md to claro.md 2024-02-02 00:03:44 -05:00
status Update and rename status/57/simple-scaling.md to status/raw/57/simple-scaling.md 2024-02-12 20:09:03 -05:00
vac Rename vac/1/images/template.md to vac/template.md 2024-02-12 21:39:21 -05:00
waku Update peer-exchange.md 2024-03-21 16:06:30 -04:00
README.md Update README.md 2024-02-22 19:56:39 -05:00

README.md

Vac Request For Comments(RFC)

NOTE: This repo is WIP. We are currently restructuring the RFC process.

RFC Process

This repository contains specifications from the Waku, Nomos, Codex, and Status projects that are apart of the IFT portfolio. Vac is an IFT service that will manage the RFC process within this repository. The goal of the RFC, Request for Comments, process is to standardize techincal specification. Specifications will adhere to 1/COSS by obtianing rough consensus within each project.

See rfc.vac.dev for an easy to browse index of all RFCs.

Contributing

Please see 1/COSS for general guidelines and specification lifecycle.

Feel free to join the Vac discord. There's a channel specifically for RFC discussions.

Here's the project board used by core contributors and maintainers: Projects