Skip to content

Commit

Permalink
wrapping
Browse files Browse the repository at this point in the history
  • Loading branch information
@mnot
mnot committed Jun 27, 2017
1 parent d556a1d commit 1dad383
Showing 1 changed file with 43 additions and 40 deletions.
83 changes: 43 additions & 40 deletions CONTRIBUTING.md
View file
Original file line number Diff line number Diff line change
@@ -1,9 +1,8 @@
# Contributing to HTTP

Before submitting feedback, please familiarize yourself with our current issues
list and review the [working group home page](https://httpwg.github.io/). If
you're new to this, you may also want to read the [Tao of the
IETF](https://www.ietf.org/tao.html).
Before submitting feedback, please familiarize yourself with our current issues list and review the
[working group home page](https://httpwg.github.io/). If you're new to this, you may also want to
read the [Tao of the IETF](https://www.ietf.org/tao.html).

**Be aware that all contributions fall under the "NOTE WELL" terms outlined below.**

Expand Down Expand Up @@ -32,29 +31,30 @@ The Working Group has a few venues for discussion:

* We also discuss specific issues on the [issues list](https://github.com/httpwg/http-extensions/issues) itself. If you don't want to use Github to follow these discussions, you can subscribe to the [issue announce list](https://www.ietf.org/mailman/listinfo/http-issues).

To be active in the Working Group, you can participate in any of these places. Most activity takes place on the mailing list, but if you just want to comment on and raise issues, that's fine too.
To be active in the Working Group, you can participate in any of these places. Most activity takes
place on the mailing list, but if you just want to comment on and raise issues, that's fine too.


## Raising Issues

We use our [issues list](https://github.com/httpwg/http-extensions/issues) to
track items for discussion and their resolution.
We use our [issues list](https://github.com/httpwg/http-extensions/issues) to track items for
discussion and their resolution.

Before filing a new issue, please consider a few things:

* Issues should be just that; issues with our deliverables, **not questions or
support requests**.
* Please review the issues list to make sure that you aren't filing a
duplicate.
* Issues should be just that; issues with our deliverables, **not questions or support requests**.

* Please review the issues list to make sure that you aren't filing a duplicate.

* If you're not sure how to phrase your issue, please ask on the [mailing list](https://lists.w3.org/Archives/Public/ietf-http-wg/).

Issues can also be raised on the [Working Group mailing
list](https://lists.w3.org/Archives/Public/ietf-http-wg/) by clearly marking them as such (e.g.,
in the `Subject:` line).
list](https://lists.w3.org/Archives/Public/ietf-http-wg/) by clearly marking them as such (e.g., in
the `Subject:` line).

Be aware that issues might be rephrased, changed in scope, or combined with others, so that the group
can focus its efforts. If you feel that such a change loses an important part of your original
issue, please bring it up, either in comments or on the list.
Be aware that issues might be rephrased, changed in scope, or combined with others, so that the
group can focus its efforts. If you feel that such a change loses an important part of your
original issue, please bring it up, either in comments or on the list.

Off-topic and duplicate issues will be closed without discussion. Note that comments on individual
commits will only be responded to with best effort, and may not be seen.
Expand All @@ -74,17 +74,21 @@ Consensus for the resolution of a design issue can be established in a few diffe

* Through discussion on the issues list. Once a resolution is found, it will be confirmed on the mailing list before consensus is declared.

The editors can also propose resolutions for the group's consideration by incorporating them into the draft(s); when doing so, the issue should not be closed until consensus is declared.
The editors can also propose resolutions for the group's consideration by incorporating them into
the draft(s); when doing so, the issue should not be closed until consensus is declared.

Issues that have consensus will be labelled as `editor-ready`. After the editor has incorporated a resolution into the specification, the issue can be closed.
Issues that have consensus will be labelled as `editor-ready`. After the editor has incorporated a
resolution into the specification, the issue can be closed.

When a new draft is published, the design issues that have been closed since the last draft will be highlighted on the mailing list, to aid reviewers. If substantive new information is brought to our attention, issues can be reopened by the Chairs.
When a new draft is published, the design issues that have been closed since the last draft will be
highlighted on the mailing list, to aid reviewers. If substantive new information is brought to our
attention, issues can be reopened by the Chairs.


## Pull Requests

We welcome pull requests, both for editorial suggestions and to resolve open
issues. In the latter case, please identify the relevant issue.
We welcome pull requests, both for editorial suggestions and to resolve open issues. In the latter
case, please identify the relevant issue.

Please do not use a pull request to open a new design issue.

Expand All @@ -97,35 +101,34 @@ to all Working Group communications and meetings.

## NOTE WELL

Any submission to the [IETF](https://www.ietf.org/) intended by the Contributor
for publication as all or part of an IETF Internet-Draft or RFC and any
statement made within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF sessions, as
well as written and electronic communications made at any time or place, which
are addressed to:
Any submission to the [IETF](https://www.ietf.org/) intended by the Contributor for publication as
all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF
activity is considered an "IETF Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any time or place, which are
addressed to:

* The IETF plenary session
* The IESG, or any member thereof on behalf of the IESG
* Any IETF mailing list, including the IETF list itself, any working group
or design team list, or any other list functioning under IETF auspices
* Any IETF mailing list, including the IETF list itself, any working group or design team list, or
any other list functioning under IETF auspices
* Any IETF working group or portion thereof
* Any Birds of a Feather (BOF) session
* The IAB or any member thereof on behalf of the IAB
* The RFC Editor or the Internet-Drafts function
* All IETF Contributions are subject to the rules of
[RFC 5378](https://tools.ietf.org/html/rfc5378) and
[RFC 3979](https://tools.ietf.org/html/rfc3979)
* All IETF Contributions are subject to the rules of [RFC
5378](https://tools.ietf.org/html/rfc5378) and [RFC 3979](https://tools.ietf.org/html/rfc3979)
(updated by [RFC 4879](https://tools.ietf.org/html/rfc4879)).

Statements made outside of an IETF session, mailing list or other function,
that are clearly not intended to be input to an IETF activity, group or
function, are not IETF Contributions in the context of this notice.

Please consult [RFC 5378](https://tools.ietf.org/html/rfc5378) and [RFC
Statements made outside of an IETF session, mailing list or other function, that are clearly not
intended to be input to an IETF activity, group or function, are not IETF Contributions in the
context of this notice.

Please consult [RFC 5378](https://tools.ietf.org/html/rfc5378) and [RFC
3979](https://tools.ietf.org/html/rfc3979) for details.

A participant in any IETF activity is deemed to accept all IETF rules of
process, as documented in Best Current Practices RFCs and IESG Statements.
A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in
Best Current Practices RFCs and IESG Statements.

A participant in any IETF activity acknowledges that written, audio and video
records of meetings may be made and may be available to the public.
A participant in any IETF activity acknowledges that written, audio and video records of meetings
may be made and may be available to the public.

0 comments on commit 1dad383

Please sign in to comment.