-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editorial: Link to whatwg/meta COMMITING.md #867
Changes from 4 commits
9e453db
e576213
cad4067
7876095
41d975a
726121c
5505cc7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,18 @@ | ||
# Contribution guidelines for the Streams Standard | ||
# Streams Standard contributor guidelines | ||
|
||
These are the guidelines for contributing to the Streams Standard. First see the [WHATWG contributor guidelines](https://github.com/whatwg/meta/blob/master/CONTRIBUTING.md). | ||
|
||
We label [good first issues](https://github.com/whatwg/html/labels/good%20first%20issue) that you could help us fix, to get a taste for how to submit pull requests, how the build process works, and so on. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This should be streams, not html |
||
|
||
## Pull Requests | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Lowercase "r" for consistency |
||
|
||
In short, change `source` and submit your patch. Try to follow the [spec editorial conventions](#spec-editorial-conventions) below. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The |
||
|
||
Follow the [guidelines for writing good commit messages](https://github.com/whatwg/meta/blob/master/COMMITTING.md). | ||
|
||
Merge commits are not allowed; history must stay linear. | ||
|
||
If you are updating the spec, also update the corresponding parts of the reference implementation where applicable, in the same commit. | ||
|
||
## Spec editorial conventions | ||
|
||
|
@@ -35,14 +49,6 @@ Use single quotes. | |
|
||
Pass ESLint. | ||
|
||
## Commit guidelines | ||
|
||
Follow the [guidelines for writing good commit messages](https://github.com/erlang/otp/wiki/Writing-good-commit-messages). | ||
|
||
Merge commits are not allowed; history must stay linear. | ||
|
||
If you are updating the spec, also update the corresponding parts of the reference implementation where applicable, in the same commit. | ||
|
||
## Building the spec | ||
|
||
Building the spec is a two-step process. First, the majority of the conversion work is done via [Bikeshed](https://github.com/tabatkins/bikeshed). Second, we run a custom portion of the [Ecmarkup](https://github.com/bterlson/ecmarkup) pipeline to convert the algorithms from [Ecmarkdown](https://github.com/domenic/ecmarkdown) syntax into HTML, and to automatically add cross-references. This second step requires a recent version of [Node.js](https://nodejs.org/en/) to be installed. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@domenic "Streams standard"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nah, in this case "Streams Standard" is a proper noun.