Add "Following Discussion"; http -> https

CONTRIBUTING.md

@@ -3,14 +3,16 @@
 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](http://www.ietf.org/tao.html).
+IETF](https://www.ietf.org/tao.html).
 
 **Be aware that all contributions fall under the "NOTE WELL" terms outlined below.**
 
 
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 
+
+- [Following Discussion](#following-discussion)
 - [Raising Issues](#raising-issues)
 - [Resolving Issues](#resolving-issues)
 - [Pull Requests](#pull-requests)
@@ -20,6 +22,17 @@ IETF](http://www.ietf.org/tao.html).
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
 
+## Following Discussion
+
+The Working Group has a few venues for discussion:
+
+* We have a session at most [IETF meetings](https://www.ietf.org/meeting/), and sometimes in between. Agendas, minutes and other materials for these meetings can be found in our [meeting materials repository](https://github.com/httpwg/wg-materials), and in the [official proceedings](https://datatracker.ietf.org/wg/httpbis/meetings/).
+* Our [mailing list](https://lists.w3.org/Archives/Public/ietf-http-wg/) is used for most communication, including notifications of meetings, new drafts, consensus calls and other business, as well as issue 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.
+
+
 ## Raising Issues
 
 We use our [issues list](https://github.com/httpwg/http-extensions/issues) to 
@@ -31,10 +44,10 @@ Before filing a new issue, please consider a few things:
   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]((http://lists.w3.org/Archives/Public/ietf-http-wg/)).
+* 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](http://lists.w3.org/Archives/Public/ietf-http-wg/) by clearly marking them as such (e.g., 
+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
@@ -49,7 +62,7 @@ commits will only be responded to with best effort, and may not be seen.
 
 Issues will be labeled by the Chair 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]((http://lists.w3.org/Archives/Public/ietf-http-wg/)). 
+* **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://lists.w3.org/Archives/Public/ietf-http-wg/)). 
 * **Editorial** issues can be closed by the editor(s) without consensus or notification. Typically, any discussion will take place on the issue itself.
 
 Once the resolution for a design issue is determined, it will be recorded in the
@@ -73,13 +86,13 @@ Please do not use a pull request to open a new design issue.
 
 ## Code of Conduct
 
-The [IETF Guidelines for Conduct](http://tools.ietf.org/html/rfc7154) applies 
+The [IETF Guidelines for Conduct](https://tools.ietf.org/html/rfc7154) applies 
 to all Working Group communications and meetings.
 
 
 ## NOTE WELL
 
-Any submission to the [IETF](http://www.ietf.org/) intended by the Contributor
+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
@@ -95,16 +108,16 @@ are addressed to:
  * 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](http://tools.ietf.org/html/rfc5378) and 
-   [RFC 3979](http://tools.ietf.org/html/rfc3979) 
-   (updated by [RFC 4879](http://tools.ietf.org/html/rfc4879)).
+   [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](http://tools.ietf.org/html/rfc5378) and [RFC 
-3979](http://tools.ietf.org/html/rfc3979) for details.
+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.