From 3d5157ea9e41768474b4ac199130c2a25bc36472 Mon Sep 17 00:00:00 2001 From: yqtian-se Date: Tue, 1 Sep 2026 14:42:11 +1000 Subject: [PATCH 1/2] Clarify SEN publication scope --- content/SEN/SEN.md | 7 ++++--- content/SEN/guideline.md | 26 ++++++++++++-------------- content/resources/comms-playbook.md | 17 +++++++++-------- 3 files changed, 25 insertions(+), 25 deletions(-) diff --git a/content/SEN/SEN.md b/content/SEN/SEN.md index 16fe57e..6e71788 100644 --- a/content/SEN/SEN.md +++ b/content/SEN/SEN.md @@ -4,10 +4,12 @@ title = "Software Engineering Notes (SEN)" # About -Software Engineering Notes (SEN) is an informal publication of the ACM Special Interest Group on Software Engineering (SIGSOFT). SEN is hence appropriate for contributions in all areas of software engineering, therein included (but not limited to) requirements, specification, design and implementation methods, software maintenance, reuse and re-engineering, quality assurance, measurement and evaluation, software processes, automated tools, practical experience, and related issues. SIGSOFT seeks to address research and development issues in these areas and to provide a common ground for both, through sponsorship of conferences, symposia and workshops, and the publication of SEN. +Software Engineering Notes (SEN) is an informal publication of the ACM Special Interest Group on Software Engineering (SIGSOFT). Its scope includes requirements, specification, design and implementation methods, software maintenance, reuse and re-engineering, quality assurance, measurement and evaluation, software processes, automated tools, practical experience, and related issues. + +SEN does not accept unsolicited manuscripts. Columns and other contributions are commissioned or arranged in advance by the editorial team. Scientific or research articles are published only as part of a workshop for which SEN has agreed in advance to serve as the publisher. SEN (ISSN: 0163-5948) appears quarterly, viz., four issues a year. It is edited, but not refereed. -Contributions should be structured and submitted as indicated by the online available publication [guidelines]({{< ref "guideline.md" >}} "guideline"). +Authors of invited or pre-arranged contributions should follow the publication [guidelines]({{< ref "guideline.md" >}} "guideline"). ## SEN online in the ACM Digital Library @@ -57,4 +59,3 @@ See [here]({{< ref "seed.md" >}} "seed"). Mark Doernhoefer wrote the _Surfing the Net for Software Engineering Notes_ column for _SEN_. Beginning with the January 2001 issue of _SEN_, Mark switched over from coverage of software engineering discussions on the Usenet newsgroups to software engineering-related sites on the World Wide Web. See [here]({{< ref "surfing.md" >}} "surfing"). - diff --git a/content/SEN/guideline.md b/content/SEN/guideline.md index 600f548..3a71775 100644 --- a/content/SEN/guideline.md +++ b/content/SEN/guideline.md @@ -5,18 +5,17 @@ title = "Software Engineering Notes (SEN) Publication Guidelines" # Publication Guidelines -## Submitting to SEN +## Publication Scope -Material for publication in **Software Engineering Notes (SEN)** should be submitted via email to **editors\_sigsoft \[at\] acm.org**. +**Software Engineering Notes (SEN) does not accept unsolicited manuscripts.** Do not send a completed manuscript unless the editorial team has invited the contribution or approved it in advance. -Contributions can be _articles_, _reports_, _reviews_, _columns_, _announcements_, or _book reviews_. -The submission of _articles_ is however restricted to scientific/research articles that are part of a workshop for which SEN has agreed to be the publisher. -Other scientific/research articles, i.e., articles that are sent unsolicited and could have been submitted to a regular journal or workshop for review, will no longer be published in SEN. As _columns_, -we instead welcome contributions that discuss topics of interest among SIGSOFT members and the software engineering community at large. -Columns should normally not be longer than 4 pages (exceptions may be allowed on a case-by-case basis) and trigger further discussion among community members. -Finally, as _reports_, we welcome summary reports from workshops conducted under the umbrella of ICSE, ASE, ESEC/FSE and other major SIGSOFT sponsored conferences. +SEN publishes editor-managed columns and may invite guest contributions that discuss topics of interest to SIGSOFT members and the software engineering community. A column is not a venue for reporting original research in the form of a conventional research paper. Columns should normally be no longer than four pages and should encourage further discussion among community members. -Manuscripts should be prepared by using **SEN style** and submitted by sending their sources and/or .pdfs with all fonts embedded. The following templates are available: +Scientific or research articles are published only as part of a workshop for which SEN has agreed in advance to serve as the publisher. Unsolicited research articles that could be submitted to a conference, workshop, or journal will not be considered. Workshop summary reports may also be published by prior arrangement with the editorial team. + +Questions about an invited or pre-arranged contribution may be sent to **editors\_sigsoft \[at\] acm.org**. + +Authors preparing an invited or pre-arranged contribution should use **SEN style** and provide the source files and a PDF with all fonts embedded. The following templates are available: * [.doc](/sen/ACM_SIGSOFT_pubform.doc): MS Word 97-2003 * [.docx](/sen/ACM_SIGSOFT_pubform.docx): MS Word 2007 @@ -24,9 +23,9 @@ Manuscripts should be prepared by using **SEN style** and submitted by sending t Authors are warmly encouraged to carefully structure the abstract of their manuscript, so as to ensure that it reflects the key points addressed in the document, which will appear in full in the ACM Digital Library. Authors are also encouraged to use the keywords found on the ACM Computer Classification System (CCS) that is available [online](https://dl.acm.org/ccs). -## Submission Deadlines +## Production Deadlines -SEN appears quarterly (four issues a year). Submission deadlines are 4 weeks before publication date or roughly: +SEN appears quarterly (four issues a year). For contributions arranged in advance, final materials are normally due four weeks before the publication date: * November 30 for the January issue * February 28 for the April issue @@ -35,7 +34,7 @@ SEN appears quarterly (four issues a year). Submission deadlines are 4 weeks bef ## Publication Terms and Conditions -By submitting your article for distribution in SEN, you hereby grant to ACM the following non-exclusive, perpetual, worldwide rights: +By submitting an invited or pre-arranged contribution for distribution in SEN, you grant ACM the following non-exclusive, perpetual, worldwide rights: * to publish in print on condition of acceptance by the editor, * to digitize and post your article in the electronic version of this publication, @@ -44,7 +43,7 @@ By submitting your article for distribution in SEN, you hereby grant to ACM the However, as a contributing author, you retain copyright to your article and ACM will make every effort to refer requests for commercial use directly to you. -By submitting your article for distribution in SEN, you also agree that: +By submitting an invited or pre-arranged contribution for distribution in SEN, you also agree that: * at this time, you, or one of your co-authors, have not submitted this article for review/acceptance in any other conference, workshop, symposium, or publication, and * should your article be accepted for publication in SEN, you, or one of your co-authors, will not submit this article to any conference, workshop, symposium, or publication. @@ -58,4 +57,3 @@ Please see the ACM webpage about [plagiarism and self-plagiarism](http://www.acm Plagiarism is copying words from another published paper (your own or someone else's) without proper quotes and citations. In writing, everything not quoted and cited is presumed to be new work by the author. Plagiarism disrespects both the original author (whose contributions are not acknowledged) and the reader (who is mislead about the contributions of the current paper, and will not know where to go when they want to learn more). It looks like theft of words or ideas. Any copied text longer than a few words should be put in quotes and given a reference. If you copy more than a full sentence, use indented paragraphs to denote a block quote. Note that copying text and then changing words here and there is not good enough. Use quotes or rewrite completely. - diff --git a/content/resources/comms-playbook.md b/content/resources/comms-playbook.md index 5bebb82..ced730b 100644 --- a/content/resources/comms-playbook.md +++ b/content/resources/comms-playbook.md @@ -38,19 +38,20 @@ See the full [SEWorld Guidelines](https://www2.sigsoft.org/seworld_guidelines/) ### 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 +**Best for:** Commissioned or pre-arranged content with lasting archival value, a formal academic tone, and material that should be preserved in the ACM Digital Library **Content types:** -- Columns on SE topics +- Editor-managed columns and approved guest 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 +- Book reviews arranged with the SEN Editor +- Reports and position papers arranged with the SEN Editor +- Invited award announcements (detailed write-ups) +- Invited SIGSOFT news and updates **Not appropriate:** - Time-sensitive announcements (use SEWorld) -- Unsolicited research papers (use conferences/journals) +- Complete manuscripts sent without prior agreement +- Unsolicited research papers, including papers relabeled as columns or reports (use conferences/journals) See the [SEN Publication Guidelines](https://www2.sigsoft.org/sen/guideline/) for formatting, deadlines, and submission details. @@ -201,4 +202,4 @@ See the [Blog Contribution Guidelines](https://sigsoft.medium.com/contribution-p | 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) | -| Wikipedia | Information Director | See [Information Director](https://www2.sigsoft.org/contact/) | \ No newline at end of file +| Wikipedia | Information Director | See [Information Director](https://www2.sigsoft.org/contact/) | From 497b056b344a053dade3e5526ee40c1e0272f150 Mon Sep 17 00:00:00 2001 From: yqtian-se Date: Tue, 1 Sep 2026 15:20:09 +1000 Subject: [PATCH 2/2] Add incoming SEN editor-in-chief --- content/SEN/SEN.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/SEN/SEN.md b/content/SEN/SEN.md index 6e71788..5e11796 100644 --- a/content/SEN/SEN.md +++ b/content/SEN/SEN.md @@ -25,6 +25,10 @@ SEN contributions are archived in the ACM Digital Library and accessible through Jacopo Soldani, University of Pisa, Italy +### Incoming Editor-in-Chief (from 2027) + +Yongqiang Tian, Monash University + ### Production Editor Ajay Jain, Adobe Systems Inc.