Re: [quicwg/base-drafts] Update Contributing.md to reflect post-IESG world (#4824)

@larseggert requested changes on this pull request.

>  
-Anyone can contribute to QUIC; you don't have to join the Working Group, because there is no "membership" -- anyone who participates in the work, as outlined below, is part of the QUIC Working Group.
+The base-drafts repository is the historical home of the QUIC version 1
+specifications that were written by the QUIC Working Group.

```suggestion
specifications that were written by the IETF QUIC Working Group.
```

> +* [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)

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

>  

-<!-- START doctoc generated TOC please keep comment here to allow auto update -->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
+**All of the documents have been approved for publication as RFC. We will no

```suggestion
**All of the documents have been approved for publication as RFCs. We will no
```

> -commits will only be responded to with best effort, and may not be seen.
-
-
-## Resolving Issues
-
-Issues will be labeled by the Chairs as either `editorial` or `design`:
-
-* **Design** issues require discussion and consensus in the Working Group. This discussion can happen both in the issue and on the [Working Group mailing list](https://www.ietf.org/mailman/listinfo/quic), as outlined below.
-
-* **Editorial** issues can be dealt with by the editor(s) without consensus or notification. Typically, any discussion will take place on the issue itself.
-
-The open design issues in the issues list are those that we are currently discussing, or plan to discuss. They can be discussed on the mailing list or the issue itself.
-
-We're currently using two different processes for issue resolution, depending on draft maturity.
+Any change will be subject to careful review and discussion, which might involve
+the editors, chairs, Working Group, and our Area Director.

Maybe add:
```suggestion
After this review and discussion, errata may need to be filed for the published RFCs,
or the Working Group may otherwise address such valid issues.
```

> +  materials repository](https://github.com/quicwg/wg-materials) and the
+  [official proceedings](https://datatracker.ietf.org/wg/quic/meetings/).
+
+* Our [mailing list](https://www.ietf.org/mailman/listinfo/quic) is used for
+  most communication, including notifications of meetings, new drafts, consensus
+  calls and other business, as well as issue discussion.
+
+* We maintain several repositories in our GitHub organization
+  [Github](https://github.com/quicwg/). Specific issues are discussed on the
+  relevant issues list. 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/quic-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.

I'll note that we're not mentioning the Slack channel here - should we?

>  
+**All of the documents have been approved for publication as RFC. We will no
+longer consider design changes or substantial editorial changes unless they
+relate to severe security, interoperability or deployment problems.**

You might want to point to `CONTRIBUTING.md` for more information.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/4824#pullrequestreview-592295764