Servo style guide?

Open
#173 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
documentation

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.

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?

Dominant language
No language data
Stars
254
Forks
13
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from servo/project

All issues in servo/project

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.