Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: update RFC links and README (#3675) #3839

Merged
merged 2 commits into from
Feb 16, 2022
Merged

fix: update RFC links and README (#3675) #3839

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8da80af
fix: update RFC links and README (#3675)
zhangcheng Feb 15, 2022
838263b
Merge branch 'development' into rfc-link-update
aviator-app[bot] Feb 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion RFC/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,12 @@

RFC documents for the Tari protocol

The rendered version of these docs can be found at https://rfc.tari.com
These documents are in the form of an mdbook. The rendered version of these docs can be found at https://rfc.tari.com

## View local rendered version

- run `cargo install mdbook`

- in the `/RFC` folder run `mdbook serve`

- in a browser navigate to [`localhost:3000`](http://localhost:3000)
1 change: 1 addition & 0 deletions RFC/src/SUMMARY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,4 +48,5 @@

- [RFC-0130: Mining](RFC-0130_Mining.md)

- [RFC template](RFC_template.md)
- [Glossary](Glossary.md)
4 changes: 2 additions & 2 deletions RFC/src/about.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,10 +9,10 @@ iterations before reaching this point:
not cast in stone. RFCs can, and should, undergo further evaluation and discussion by the community. RFC comments are
best made using Github [issue]s.

New RFC's should follow the format given in the [RFC template](./RFC_template.md).
New RFC's should follow the format given in the [RFC template](RFC_template.md).
## Lifecycle

RFCs go through the following lifecycle, which roughly corresponds to the [COSS](https://rfc.unprotocols.org/spec:2/COSS/):
RFCs go through the following lifecycle, which roughly corresponds to the [COSS](https://github.com/unprotocols/rfc/blob/master/2/README.md):

| Status | | Description |
|:------------|:--------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
Expand Down