Better architecture docs
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- CSS
- Stars
- 118
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
People still have a lot of good architecture questions. Here are some asked by Leif that really should be answerable by pasting a link to appropriate docs: https://groups.google.com/forum/#!topic/rethinkdb/kCozjR3b_es
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Google Groups discussion and identify the architecture questions that the documentation should answer. Done means those questions have clear, linkable answers in the appropriate documentation, though this issue does not name a file or test to update.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100