https://github.com/logseq/rfcs
https://github.com/logseq/rfcs
Last synced: 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/logseq/rfcs
- Owner: logseq
- Created: 2021-05-11T03:38:25.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2021-05-11T03:39:16.000Z (over 4 years ago)
- Last Synced: 2024-05-23T04:25:35.179Z (over 1 year ago)
- Size: 1000 Bytes
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Logseq RFCs
Logseq RFC (request for comments) provides a consistent and controlled path for new features to enter the project. During the process, the author can gather feedbacks as soon as possible, while enhancing the design and implementation.
Since Logseq is not a code library or a pure tech product, its RFCs should be less formal and more flexible.
## When to create a RFC
Start this process if you intend to add a "substantial" feature to Logseq. Issues and feature request do not require an RFC.
## The Process
- Fork the repo http://github.com/logseq/rfcs
- Copy `0000-template.md` to `text/0000-my-feature.md` (where
'my-feature' is descriptive. Don't assign an RFC number yet)
- Fill in the RFC
- Submit a pull request. As a pull request the RFC will receive design
feedback from the larger community, and the author should be prepared
to revise it in response.
- If the RFC gains broad support and the team's approval, the pull request will be merged and given a incremental number.
- Along the process, someone (need not be the RFC author) can provde implementation for the RFC.
- The team will accept the implementation when they decide it's ready to go.
**Logseq's RFC process owes its inspiration to the [React RFC process].**
[react rfc process]: https://github.com/react/rfcs