Conversation
CaptainEmerson
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
Preview deployed at: https://www2.sigsoft.org/pr-108 |
There was a problem hiding this comment.
Pull request overview
This PR adds a comprehensive Communications Playbook for SIGSOFT that documents the organization's communication strategy across multiple channels. The playbook serves as a guide for determining which channel to use for different types of content and establishes clear ownership and workflows.
Changes:
- Added a new communications playbook document that defines SIGSOFT's multi-channel communication strategy
- Documented six communication channels with their purposes, audiences, and appropriate content types
- Created a content type matrix showing primary and amplification channels for different types of announcements
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### Coordination? | ||
| - Monthly brief sync among channel owners? | ||
| - Shared calendar for major announcements? | ||
| - Email thread or Slack for quick coordination? |
There was a problem hiding this comment.
The section heading "Coordination?" with a question mark appears incomplete or uncertain. This should either be finalized with a concrete plan or the section should be removed if still under discussion. The content below also consists of questions rather than established guidelines.
| ### Coordination? | |
| - Monthly brief sync among channel owners? | |
| - Shared calendar for major announcements? | |
| - Email thread or Slack for quick coordination? | |
| ### Coordination | |
| - Hold a monthly brief sync among channel owners to review upcoming communications and align messaging. | |
| - Maintain a shared calendar for major announcements to avoid conflicts and ensure timely coverage across channels. | |
| - Use a dedicated email thread or Slack channel for quick coordination and ad hoc updates between channel owners. |
There was a problem hiding this comment.
Yes, this ought not to be merged, but instead is a placeholder for discussion for us SIGSOFT comms folks.
yqtianust
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
Preview deployed at: https://www2.sigsoft.org/pr-108 |
the exact page can be found at https://www2.sigsoft.org/pr-108/resources/comms-playbook/ |
|
Other parts look good to me. Thanks a lot @CaptainEmerson |
|
@CaptainEmerson I've opened a new pull request, #110, to work on those changes. Once the pull request is ready, I'll request review from you. |
|
@CaptainEmerson I've opened a new pull request, #111, to work on those changes. Once the pull request is ready, I'll request review from you. |
|
@CaptainEmerson I've opened a new pull request, #112, to work on those changes. Once the pull request is ready, I'll request review from you. |
|
@CaptainEmerson I've opened a new pull request, #113, to work on those changes. Once the pull request is ready, I'll request review from you. |
CaptainEmerson
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
Preview deployed at: https://www2.sigsoft.org/pr-108 |
CaptainEmerson
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
Preview deployed at: https://www2.sigsoft.org/pr-108 |
|
@copilot please review the comments on this PR and fix any remaining issues |
|
@CaptainEmerson I've opened a new pull request, #114, to work on those changes. Once the pull request is ready, I'll request review from you. |
CaptainEmerson
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
Preview deployed at: https://www2.sigsoft.org/pr-108 |
This document outlines SIGSOFT's communication strategy, detailing various channels, their purposes, content types, and ownership.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: CaptainEmerson <5417003+CaptainEmerson@users.noreply.github.com>
Co-authored-by: CaptainEmerson <5417003+CaptainEmerson@users.noreply.github.com>
Co-authored-by: CaptainEmerson <5417003+CaptainEmerson@users.noreply.github.com>
yqtianust
force-pushed
the
CaptainEmerson-patch-1
branch
from
511fc8e to
58b501d
Compare
yqtianust
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
Preview deployed at: https://www2.sigsoft.org/pr-108 |
|
@copilot, please adjust the menu bar in config.toml to include this playbook. |
|
@yqtianust I've opened a new pull request, #115, to work on those changes. Once the pull request is ready, I'll request review from you. |
* Initial plan * Add Communications Playbook to menu bar Co-authored-by: yqtianust <41743566+yqtianust@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: yqtianust <41743566+yqtianust@users.noreply.github.com>
yqtianust
temporarily deployed
to
github-pages
GitHub Actions
Inactive
|
Preview deployed at: https://www2.sigsoft.org/pr-108 |
|
@copilot there is no blog editor. Please update this term with Information Director. Thanks. |
|
@yqtianust I've opened a new pull request, #116, to work on those changes. Once the pull request is ready, I'll request review from you. |
…nks (#116) * Initial plan * Replace Blog Editor with Information Director Co-authored-by: yqtianust <41743566+yqtianust@users.noreply.github.com> * Update Information Director contact link to correct URL Co-authored-by: yqtianust <41743566+yqtianust@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: yqtianust <41743566+yqtianust@users.noreply.github.com>
|
Preview deployed at: https://www2.sigsoft.org/pr-108 |
This document outlines SIGSOFT's communication strategy, detailing various channels, their purposes, content types, and ownership.