Update charter with communication responsibilities

TSC-Charter.md

@@ -74,9 +74,33 @@ including:
 * Development process and any coding standards.
 * Mediating technical conflicts between Collaborators or Foundation
   projects.
+* Establishing and stewarding a consensus-seeking process to represent the technical community and its work in external communications.
 
 The TSC will define Node.js project’s release vehicles.
 
+The communication oversight responsibilities include:
+
+* Technical development processes of the project
+* Releases and release announcements
+* Technical documentation
+* Contributor onboarding and conduct
+* Project governance
+* Technical direction
+
+Specific exclusions from the communication oversight responsibilities include:
+
+* Brand marketing
+* Fundraising and financial sponsorship (including, but not limited to, the OpenJS Foundation's financial sponsorship of the project)
+* Legal matters
+* Marketing/ community events
+
+except when specifically approved by the OpenJS Foundation.
+
+
+The community may establish project-specific communication channels, such as social media accounts and discussion forums, subject to the above requirements. If the communication channels are used to represent the project, administrator access should be granted to both the TSC and the Foundation for oversight, while the day-to-day operation can be delegated to another party as long as they respect the consensus seeking process of the project.
+
+Nothing in this charter should be interpreted as preventing the Foundation from also publishing about any aspect of the project, including all technical aspects, so long as those communications are not presented as being endorsed by, or representative of, the TSC or the body of project contributors except when specifically approved by the TSC.
+
 ## Section 5. Node.js Project Operations
 
 The TSC will establish and maintain a development process for the