vacp2p
/
rfc-index
mirror of https://github.com/vacp2p/rfc-index.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
252 Commits 25 Branches 0 Tags 3.8 MiB
Markdown 100%
Go to file
Filip Pajic 69f2853407
fix: Syntax fix for index documents inside Waku foldersFix syntax (#34) 
# What does this PR resolve? 🚀
- Changes title inside Waku/README.md from h2 to h1
- Changes title inside Waku/Deprecated/README.md from h2 to h1

# Details 📝
The syntax for the title of the markdown seems to not be proper one
comparing to other README documents.
It's important to define titles with h1(#) to be able to parse it
properly later on by the website
 		2024-04-23 14:17:17 -04:00
.github/workflows Fix Markdown Lint (#25) 2024-03-26 17:42:18 +01:00
codex Update README.md 2024-02-23 10:00:20 -05:00
nomos Update README.md 2024-02-23 09:58:24 -05:00
status Broken Links + Change Editors (#26) 2024-03-21 10:08:40 -04:00
vac feat(rln-stealth-commitments): add initial tech writeup (#23) 2024-04-15 17:34:56 +05:30
waku fix: Syntax fix for index documents inside Waku foldersFix syntax (#34) 2024-04-23 14:17:17 -04:00
README.md Update README.md 2024-03-01 19:14:36 +01:00

README.md

Vac Request For Comments(RFC)

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

This repository contains specifications from the Waku, Nomos, Codex, and Status projects that are part of the IFT portfolio. Vac is an IFT service that will manage the RFC, Request for Comments, process within this repository.

New RFC Process

This repository replaces the previous rfc.vac.dev resource. Each project will maintain initial specifications in separate repositories, which may be considered as a raw specification. All Vac raw specifications and discussions will live in the Vac subdirectory. When projects have reached some level of maturity for a specification living in their repository, the process of updating the status to draft may begin in this repository. Specifications will adhere to 1/COSS before obtaining draft status.

Implementations should follow specifications as described, and all contributions will be discussed before the stable status is obtained. The goal of this RFC process will to engage all interseted parities and reach a rough consensus for techcinal specifications.

Contributing

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

Feel free to join the Vac discord.

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

IFT Projects' Raw Specifications

The repository for each project raw specifications: