Servo style guide?
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 254
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
(Context: https://github.com/servo/servo/pull/39052/files#r2333120334)
What's the style guide for Servo? I assume we are at least following the Rust Style Guide, but it doesn't cover what we are discussing at https://github.com/servo/servo/pull/39052/files#r2333120334.
Should we compile a more detailed style guide?
Contributor guide
No contributing guide indexed for this repository
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 by reading the linked Servo pull request discussion and the Rust Style Guide to identify the style questions not covered there. Define the agreed Servo-specific conventions and document the resulting style guide, including where it should live in the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100