[Deliverable] Waku RFC Review

[chair28980]

Milestone: https://github.com/waku-org/pm/milestone/19
Research Milestone

Summary

• Goal: On completion, the set of RFCs for Waku will be simplified, reasonably up to date and accessible.
• Deliverables: (3)
• Research tracks: All
• Estimated date of completion: 2024Q1

Review our Waku RFC strategy, review the content of the most important RFCs, improve RFC indexing and ensure that
important RFCs are easily identified and accessible.

2 outputs are expected to achieve this milestone:

Review and implement RFC strategy

Ownership note: this Epic is a collaboration between Waku Research (R/A) and Vac RFCs (C/I)

Consult with stakeholders (Waku teams, Waku Community and Vac RFC team) to come up with an improved strategy for Waku RFCs to answer:

1. Should Waku RFCs be in a separate Waku-owned repo?
2. What is the role of proof of concepts vs raw RFCs?
3. How should Waku RFCs be indexed?
4. How should Waku RFCs be presented to make important specs obvious and easy to find?
5. Should we continue with the same RFC categories (Standards, Informational and Best Current Practices)?
6. Should we continue with the same RFC tags (Waku core vs application)?
7. Should we continue with the same COSS lifecycle? Should we add a "stagnant" status a la EIPs?
8. How do we clarify the responsibility of the Vac team vs Waku team when it comes to RFCs?
9. How can external contributors contribute or propose improvements to Waku specifications?
10. Clarify intended scope of topics that can be covered in Waku RFCs, delineate categories clearly and revise the spec lifecycles.

This item includes actioning the new proposed strategy, such as potentially moving Waku specs to a waku-org repo,
updating references to these in documentation, adding/removing tags and categories, writing up the proposed strategy
in contributor guidelines, etc.

Epics

• research:

[jm-clius]

Waku work on implementing this strategy is being done in https://github.com/waku-org/specs. This repo will be made public once work on both Vac and Waku repos are done.

[fryorcraken]

Waku work on implementing this strategy is being done in waku-org/specs. This repo will be made public once work on both Vac and Waku repos are done.

It is public already. What "work" are you talking about please?

[jm-clius]

It is public already. What "work" are you talking about please?

I think you're responding to an old comment. :) Have spoken to @chair28980 and recommended that we close this issue as both https://github.com/waku-org/specs and the new rfc.vac.dev is now live.