https://office.wikimedia.org/wiki/Community_Relations_Specialists/Internal may provide some good inspiration, e.g. team norms on using Phabricator.

[Moving here from 1:1:] We have some Phab project tags that we interact with, in addition to our team tag: Technical-blog-posts, Outreach-Programs-Projects, International-Developer-Events, Key docs update 2021-22 etc. We don't really have a concept of using/following them which could be covered. While nobody else in the team should care if I created some Phab project tag, some tasks and projects do feel like "more than 1 person on this team" level where I'd draw my blurry line.

(Tasks must have at least one active team project tag or codebase project tag so a task can be found in a related bucket (task search result, workboard, etc). Thus I'm re-adding Developer-Advocacy as this task is about Developer-Advocacy (and nothing else applies).)

According to today's team meeting, this should become a subpage of https://office.wikimedia.org/wiki/Developer_Advocacy

Status update: I finished the final draft of the Communication section and shared it with Birgit and Karen for a final check before sending out to the rest of the team for their feedback and approval.

@KHernandez-WMF: I guess you could realistically set the task status to declined, or do you plan to work on this? :)