bazelbuild / bazelbuild/proposals
template: Google Doc and Markdown Doc are currently inconsistent?
Open
- Dominant language
- No language data
- Stars
- 136
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
At time of writing, headers in Markdown doc (22a8b72):
* Abstract
* Background
* Proposal
* Backward-compatibility
Headers in Google doc:
* Overview
* Compatibility
* Document History
Dunno if it matters, but was a tad odd to see.
Contributor guide
Research direction
Compare the Markdown document headers from commit 22a8b72 with the Google Doc template. First determine whether the differing sections are intended to be aligned; done means the expected template structure is explicitly decided and the affected document or template is made consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100