-
Notifications
You must be signed in to change notification settings - Fork 13
Add SIGSOFT Communications Playbook #108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
29e50d0
Add SIGSOFT Communications Playbook
CaptainEmerson 45c9f6c
Update content/resources/comms-playbook.md
yqtian-se 7001953
Update content/resources/comms-playbook.md
yqtian-se 93808bc
Fix Executive Committee contact URL to use www2 subdomain
Copilot ecd9e19
Fix SEWorld Guidelines URL to correct link
Copilot 58b501d
Fix all remaining URL and contact information issues
Copilot ee5cbf3
Add Communications Playbook to navigation menu (#115)
Copilot caf988e
Replace Blog Editor with Information Director role and fix contact li…
Copilot 9ca4144
Initial plan
Copilot 27779c4
Add Wikipedia channel to comms playbook with when/how to update guidance
Copilot a0c6993
Delete Coordination? section and add Wikipedia guidance
Copilot 8fbb338
Merge branch 'CaptainEmerson-patch-1' into copilot/sub-pr-108-87119cd…
CaptainEmerson 6a5da72
Merge pull request #123 from acmsigsoft/copilot/sub-pr-108-87119cd3-6…
CaptainEmerson 5a7c140
Merge branch 'main' into CaptainEmerson-patch-1
yqtian-se d859191
Apply suggestions from code review
CaptainEmerson File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,204 @@ | ||
| # SIGSOFT Communications Playbook | ||
|
|
||
| This playbook defines SIGSOFT's communication strategy across all channels. | ||
|
|
||
| ## Channel Overview | ||
|
CaptainEmerson marked this conversation as resolved.
|
||
|
|
||
| | Channel | Audience | Purpose | Owner | | ||
| |---------|----------|---------|-------| | ||
| | [SEWorld](https://www2.sigsoft.org/seworld/) | SE community (broad) | Time-sensitive announcements | SEWorld Moderators | | ||
| | [SEN](https://www2.sigsoft.org/sen/sen/) | SIGSOFT members | Formal publication, columns | SEN Editor | | ||
| | [Blog](https://sigsoft.medium.com/) | SE community + public | Informal thought leadership | Information Director | | ||
| | [Website](https://www2.sigsoft.org/) | Public | Official record, resources | Information Director | | ||
| | Social Media ([X](https://twitter.com/acmsigsoft), [LinkedIn](https://www.linkedin.com/company/acm-sigsoft/)) | Public | Amplification, engagement | Social Media Chair | | ||
| | [Mastodon](https://social.sigsoft.org/) | SE community | Community building, discussion | SIGSOFT Executive Committee | | ||
| | [Wikipedia](https://en.wikipedia.org/wiki/SIGSOFT) | General public | Encyclopedic reference | Information Director | | ||
|
|
||
| ## Channel Definitions | ||
|
|
||
| ### SEWorld (Mailing List) | ||
|
|
||
| **Best for:** Time-sensitive announcements that need broad SE community reach | ||
|
|
||
| **Content types:** | ||
| - Call for papers (one per event) | ||
| - Call for participation (one per event) | ||
| - Workshop calls (one aggregate post per conference) | ||
| - Job postings (PhD+ level, academic/research institutions) | ||
| - Award nominations | ||
| - Summer schools | ||
| - PC/reviewer recruitment | ||
|
|
||
| **Not appropriate:** | ||
| - Commercial promotions, tool ads, surveys, research project announcements | ||
|
|
||
| See the full [SEWorld Guidelines](https://www2.sigsoft.org/seworld_guidelines/) for formatting and submission details. | ||
|
|
||
| --- | ||
|
|
||
| ### Software Engineering Notes (SEN) | ||
|
|
||
| **Best for:** Substantive content with lasting archival value, formal academic tone, longer-form content, and material that should be preserved in the ACM Digital Library | ||
|
|
||
| **Content types:** | ||
| - Columns on SE topics | ||
| - Workshop proceedings (where SEN is publisher) | ||
| - Book reviews | ||
| - Reports and position papers | ||
| - Award announcements (detailed write-ups) | ||
| - Major SIGSOFT news and updates | ||
|
|
||
| **Not appropriate:** | ||
| - Time-sensitive announcements (use SEWorld) | ||
| - Unsolicited research papers (use conferences/journals) | ||
|
|
||
| See the [SEN Publication Guidelines](https://www2.sigsoft.org/sen/guideline/) for formatting, deadlines, and submission details. | ||
|
|
||
| --- | ||
|
|
||
| ### Blog (Medium) | ||
|
|
||
| **Best for:** Thought leadership, community building, and reaching audiences beyond academia. Good for timely (but not urgent) content, informal tone, and material that benefits from comments/engagement and search engine visibility. | ||
|
|
||
| **Content types:** | ||
| - Interviews with researchers | ||
| - Award winner spotlights | ||
| - Conference recaps and highlights | ||
| - Opinion pieces on SE topics | ||
| - Career advice and early-career content | ||
| - "Behind the paper" stories | ||
| - Community discussions | ||
|
|
||
| **Not appropriate:** | ||
| - Formal announcements (use Website) | ||
| - Time-sensitive CFPs (use SEWorld) | ||
|
|
||
| See the [Blog Contribution Guidelines](https://sigsoft.medium.com/contribution-policies-and-guidelines-bc64caea5bbb) for submission process and editorial policies. | ||
|
|
||
| --- | ||
|
|
||
| ### Website (sigsoft.org) | ||
|
|
||
| **Best for:** Permanent record, official information | ||
|
|
||
| **Content types:** | ||
| - Award information (calls for nomination, awardee lists) | ||
| - Committee and leadership information | ||
| - Conference calendar | ||
| - Policies and guidelines | ||
| - Webinar announcements and archives | ||
| - Resources for members | ||
| - Official SIGSOFT news | ||
|
|
||
| --- | ||
|
|
||
| ### Social Media (X/Twitter, LinkedIn) | ||
|
|
||
| **Best for:** Amplification, real-time engagement, broader visibility | ||
|
|
||
| **Content types:** | ||
| - Links to blog posts | ||
| - Links to website updates | ||
| - Award announcements | ||
| - Conference highlights (live coverage) | ||
| - Community celebrations | ||
| - Retweets/shares of member achievements | ||
|
|
||
| **Note:** Social media is primarily an amplification channel—always link back to the primary source. | ||
|
|
||
| --- | ||
|
|
||
| ### Mastodon (social.sigsoft.org) | ||
|
|
||
| **Best for:** Community building and discussion within the SE research community. Unlike the other channels focused on knowledge dissemination, Mastodon is a space for ongoing conversation and connection. | ||
|
|
||
| **Content types:** | ||
| - Discussion threads and conversations | ||
| - Conference live-tooting | ||
| - Informal community engagement | ||
| - Sharing and commenting on SE topics | ||
| - Connecting researchers with each other | ||
|
|
||
| **Note:** SIGSOFT runs its own Mastodon instance, giving the community a dedicated space outside of commercial platforms. | ||
|
|
||
| --- | ||
|
|
||
| ### Wikipedia (en.wikipedia.org/wiki/SIGSOFT) | ||
|
|
||
| **Best for:** Providing accurate, encyclopedic, and verifiable information about SIGSOFT to the general public. Wikipedia is a high-visibility reference that many people encounter first when searching for SIGSOFT. | ||
|
|
||
| **When to update:** | ||
| - Leadership changes (e.g., new chair, EC composition) | ||
| - Major organizational milestones (e.g., significant anniversaries, structural changes) | ||
| - Updates to the list of flagship conferences or sponsored events | ||
| - Corrections to factual inaccuracies | ||
| - Addition of notable awards or their recipients when widely recognized | ||
|
|
||
| **How to update:** | ||
| 1. Create or log in to a Wikipedia account (editing without an account is possible but discouraged for organizational pages) | ||
| 2. Navigate to the [SIGSOFT Wikipedia page](https://en.wikipedia.org/wiki/SIGSOFT) and click **Edit** | ||
| 3. Follow [Wikipedia's guidelines](https://en.wikipedia.org/wiki/Wikipedia:Editing_policy) — all content must be neutral, verifiable, and cited with independent reliable sources where possible (for example, peer-reviewed publications, reputable news articles, and other independent coverage); use ACM/SIGSOFT official sources only where appropriate for straightforward factual details | ||
| 4. Do not use Wikipedia to promote SIGSOFT events or solicit participation — such content will be removed by Wikipedia editors | ||
| 5. After saving, monitor the Talk page for any concerns raised by other Wikipedia editors | ||
| 6. Major rewrites should be discussed on the Talk page before being made | ||
|
|
||
| **Not appropriate:** | ||
| - Calls for papers or participation | ||
| - Job postings or award nominations | ||
| - Opinions or promotional content | ||
| - Content that cannot be verified with a third-party citation | ||
|
|
||
| **Note:** Wikipedia is independently edited by the community and SIGSOFT does not control its content. Edits may be revised or reverted by other Wikipedia editors. The Information Director should periodically review the page for accuracy. | ||
|
|
||
| --- | ||
|
|
||
| ## Content Type Matrix | ||
|
|
||
| | Content Type | Website | SEN | Blog | SEWorld | Social | Wikipedia | | ||
| |--------------|:-------:|:---:|:----:|:-------:|:------:|:---------:| | ||
| | Call for papers | | | | **P** | A | | | ||
| | Call for participation | | | | **P** | A | | | ||
| | Job posting | | | | **P** | | | | ||
| | Award call for nominations | A | | | **P** | A | | | ||
| | Award winner announcement | **P** | A | A | A | A | | | ||
| | Conference recap | | | **P** | | A | | | ||
| | Interview/profile | | | **P** | | A | | | ||
| | Opinion/thought piece | | **P** | A | | A | | | ||
| | Committee updates | **P** | | | | A | A | | ||
| | Webinar announcement | **P** | | | A | A | | | ||
| | Policy/guideline update | **P** | | | | | | | ||
| | Research highlight | | **P** | A | | A | | | ||
| | Book review | | **P** | | | | | | ||
| | Organizational milestones | **P** | | | | A | A | | ||
|
|
||
| **Legend:** | ||
| - **P** = Primary channel (original content lives here) | ||
| - **A** = Amplify (cross-post or link) | ||
|
|
||
| --- | ||
|
|
||
| ## Workflow and Responsibilities | ||
|
|
||
| ### Channel Owner Responsibilities | ||
| - Monitor submissions and maintain quality | ||
| - Ensure content meets channel guidelines | ||
| - Coordinate cross-posting with Social Media chair | ||
| - Track metrics and report to EC periodically | ||
|
|
||
| ### Cross-posting Workflow | ||
| 1. Content owner publishes to primary channel | ||
| 2. Content owner notifies Social Media chair | ||
| 3. Social Media chair creates appropriate post with link | ||
| 4. For major announcements: coordinate timing across channels | ||
|
|
||
| ## Contacts | ||
|
|
||
| | Channel | Owner(s) | Contact | | ||
| |---------|----------|---------| | ||
| | SEWorld | SEWorld Moderators | See [SEWorld page](https://www2.sigsoft.org/seworld/) | | ||
| | SEN | SEN Editor | editors_sigsoft@acm.org | | ||
| | Blog | Information Director | See [Information Director](https://www2.sigsoft.org/contact/) | | ||
| | Website | Information Director | See [Information Director](https://www2.sigsoft.org/contact/) | | ||
| | Social Media | Social Media Chair | See [Executive Committee](https://www2.sigsoft.org/execcontact/) | | ||
| | Mastodon | SIGSOFT Executive Committee | See [SIGSOFT Mastodon](https://social.sigsoft.org/about) | | ||
|
CaptainEmerson marked this conversation as resolved.
CaptainEmerson marked this conversation as resolved.
|
||
| | Wikipedia | Information Director | See [Information Director](https://www2.sigsoft.org/contact/) | | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.