Skip to content
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

Update Contributing.md to reflect post-IESG world #4824

Merged
merged 7 commits into from Feb 17, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
32 changes: 6 additions & 26 deletions CONTRIBUTING.md
Expand Up @@ -5,12 +5,12 @@ specifications that were written by the QUIC Working Group.

The set of documents are:

* QUIC: A UDP-Based Multiplexed and Secure Transport
* Version-Independent Properties of QUIC
* Using TLS to Secure QUIC
* QUIC Loss Detection and Congestion Control
* Hypertext Transfer Protocol Version 3 (HTTP/3)
* QPACK: Header Compression for HTTP/3
* [QUIC: A UDP-Based Multiplexed and Secure Transport](https://tools.ietf.org/html/draft-ietf-quic-transport)
* [Version-Independent Properties of QUIC](https://tools.ietf.org/html/draft-ietf-quic-invariants)
* [Using TLS to Secure QUIC](https://tools.ietf.org/html/draft-ietf-quic-tls)
* [QUIC Loss Detection and Congestion Control](https://tools.ietf.org/html/draft-ietf-quic-recovery)
* [Hypertext Transfer Protocol Version 3 (HTTP/3)](https://tools.ietf.org/html/draft-ietf-quic-http)
* [QPACK: Header Compression for HTTP/3](https://tools.ietf.org/html/draft-ietf-quic-qpack)
Comment on lines +8 to +13
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The URLs should eventually be changed to the archival URLs at rfc-editor.org.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that we should create our own renderings of the final RFCs and point to those. The official renderings are terrible.



**All of the documents have been approved for publication as RFC. We will no
LPardue marked this conversation as resolved.
Show resolved Hide resolved
Expand Down Expand Up @@ -40,26 +40,6 @@ list](https://www.ietf.org/mailman/listinfo/quic) with a clear marking in the
Any change will be subject to careful review and discussion, which might involve
the editors, chairs, Working Group, and our Area Director.

LPardue marked this conversation as resolved.
Show resolved Hide resolved
### Resolving Issues

Issues will be labeled by the Chairs as either `editorial` or `design`:

* **Editorial** issues that are minor or unsubstantial can be dealt with by the
editor(s) without consensus or notification.

* **All other** issues require discussion and consensus among the Working Group,
Area Director. This discussion can happen both in the issue and on
the [Working Group mailing list](https://www.ietf.org/mailman/listinfo/quic),
and all other relevant mailing lists.

### Pull Requests

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; it may not be
noticed.

# Engaging with the QUIC community

The scope of work in the QUIC Working Group is described in our
Expand Down