Auto merge of #27771 - asajeffrey:new-governance, r=paulrouget

Updated CONTRIBUTING file

<!-- Please describe your changes on the following line: -->

---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: -->
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
- [x] These changes do not require tests because it's documentation

<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->

<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->

CONTRIBUTING.md

@@ -34,9 +34,14 @@ on how to start working on Servo.
 - Commits should be as small as possible, while ensuring that each commit is
   correct independently (i.e., each commit should compile and pass tests). 
 
+- Commits should be accompanied by a Developer Certificate of Origin
+  (http://developercertificate.org) sign-off, which indicates that you (and
+  your employer if applicable) agree to be bound by the terms of the
+  [project license](LICENSE.md). In git, this is the `-s` option to `git commit`
+
 - If your patch is not getting reviewed or you need a specific person to review
   it, you can @-reply a reviewer asking for a review in the pull request or a
-  comment, or you can ask for a review in [the Servo room](https://chat.mozilla.org/#/room/#servo:mozilla.org) on Mozilla's [Matrix](https://wiki.mozilla.org/Matrix) network.
+  comment, or you can ask for a review in [the Servo chat](https://servo.zulipchat.com/).
 
 - Add tests relevant to the fixed bug or new feature.  For a DOM change this
   will usually be a web platform test; for layout, a reftest.  See our [testing
@@ -46,11 +51,34 @@ For specific git instructions, see [GitHub workflow 101](https://github.com/serv
 
 ## Conduct
 
-In all Servo-related forums, we follow the [Rust Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct). For escalation or moderation issues, please contact Josh (jmatthews@mozilla.com) and Lars (larsberg@mozilla.com) instead of the Rust moderation team.
+In all Servo-related forums, we follow the [Rust Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct). For escalation or moderation issues, please contact a member of the Servo Technical Steering Committee instead of the Rust moderation team.
 
 
 ## Communication
 
-Servo contributors frequent the [Servo room](https://chat.mozilla.org/#/room/#servo:mozilla.org) on [Mozilla Matrix](https://wiki.mozilla.org/Matrix).
+Servo contributors frequent the [Servo Zulip chat](https://servo.zulipchat.com/).
 
-You can also join the [`dev-servo` mailing list](https://lists.mozilla.org/listinfo/dev-servo).
+## Technical Steering Committee
+
+Technical oversight of the Servo Project is provided by the Technical Steering Committee,
+comprised of:
+
+- [Alan Jeffrey](https://github.com/asajeffrey)
+- [Anthony Ramine](https://github.com/nox)
+- [Connor Brewster](https://github.com/cbrewster)
+- [Cheng-You Bai](https://github.com/cybai)
+- [Diane Hosfelt](https://github.com/avadacatavra)
+- [Dzmitry Malyshau](https://github.com/kvark)
+- [Emilio Cobos Álvarez](https://github.com/emilio)
+- [Fernando Jiménez Moreno](https://github.com/ferjm)
+- [Gregory Terzian](https://github.com/gterzian)
+- [Jack Moffitt](https://github.com/metajack)
+- [James Graham](https://github.com/jgraham)
+- [Josh Matthews](https://github.com/jdm)
+- [Keith Yeung](https://github.com/KiChjang)
+- [Lars Bergstrom](https://github.com/larsbergstrom)
+- [Manish Goregaokar](https://github.com/Manishearth)
+- [Martin Robinson](https://github.com/mrobinson)
+- [Patrick Walton](https://github.com/pcwalton)
+- [Paul Rouget](https://github.com/paulrouget)
+- [Simon Sapin](https://github.com/SimonSapin)