You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ACM SIGSOFT Distinguished Volunteer Certificate recognizes individuals who have made exceptional contributions to SIGSOFT through sustained or exceptional volunteer service. This recognition celebrates those who have significantly advanced the mission and goals of SIGSOFT through their dedication and impact.
13
+
14
+
## Eligibility Criteria
15
+
16
+
Recipients of the Distinguished Volunteer Certificate must demonstrate:
17
+
18
+
-**Sustained Contribution**: A minimum of two years of significant volunteer service to SIGSOFT.
19
+
-**Exceptional Impact**: Contributions that have demonstrably advanced SIGSOFT's mission, improved its operations, or enhanced the experience of its members.
20
+
-**Service Areas**: Qualifying volunteer activities may include, but are not limited to, sustained or exceptional contribution to SIGSOFT programs or initiatives such as:
21
+
- Editorial work for SIGSOFT Software Engineering Notes (SEN)
22
+
- SEWorld moderation
23
+
- Membership and service to SIGSOFT committees such as CARES, CAPS, or awards committees
24
+
- Organization of SIGSOFT events such as student mentoring workshops or summer schools
25
+
- Support for the activities of the SIGSOFT Executive Committee or SIGSOFT liaison members
26
+
27
+
This recognition is not intended for major leadership positions such as General Chair or Program Chair of conferences, SIGSOFT Executive Committee roles, or SIGSOFT liaison roles. It is also not intended for service on program committees of SIGSOFT-sponsored conferences. These roles are recognized in other ways and are not eligible for this recognition.
28
+
29
+
## Nomination Process
30
+
31
+
### Who Can Nominate
32
+
33
+
- Self-nominations are not permitted.
34
+
- Current SIGSOFT Executive Committee members, SIGSOFT liaison members, steering committee members of SIGSOFT-sponsored conferences, and other individuals with close knowledge of SIGSOFT activities may nominate candidates.
35
+
36
+
### How to Nominate
37
+
38
+
Nominations should be submitted online using the [nomination form](https://docs.google.com/forms/d/1RXdnQBJFaJ6uPk32cK4viMjW5LFwQWDj7y9_DI5qpMk/viewform). The form requires:
39
+
40
+
- Details of the nominator
41
+
- Details of the nominee
42
+
- A short description of why this individual has done outstanding service
43
+
44
+
### Submission Timeline
45
+
46
+
Nominations are accepted annually, with a deadline of February 1.
47
+
48
+
## Selection Process
49
+
50
+
### Review Committee Composition
51
+
52
+
The Distinguished Volunteer Certificate Review Committee is appointed by the SIGSOFT Chair and consists of two to three senior SIGSOFT members and one member of the SIGSOFT Executive Committee in a non-voting role.
53
+
54
+
### Conflict of Interest
55
+
56
+
Committee members must recuse themselves from discussions of a particular candidate where:
57
+
58
+
- They submitted a nomination for that candidate in the current round.
59
+
- They have a conflict of interest with that nominee, following the ACM conflict of interest policy.
60
+
61
+
### Decision Making
62
+
63
+
There is no fixed limit on the number of certificates presented each year. The number of recipients depends on the number of eligible nominations received.
64
+
65
+
Decisions of the review committee are final and not subject to appeal.
66
+
67
+
## Recognition Details
68
+
69
+
Recipients receive:
70
+
71
+
- A formal certificate suitable for framing
72
+
- Recognition on the SIGSOFT website and in SIGSOFT communications
73
+
- A brief announcement at a SIGSOFT-sponsored conference
74
+
75
+
## 2026 Committee Members
76
+
77
+
- Raula Gaikovina Kula, University of Osaka, Japan
78
+
- Lin Tan, Purdue University, USA
79
+
- Cristian Cadar, Imperial College London, UK
80
+
81
+
## 2026 Recipients
82
+
83
+
- Ajay Jain, for dedicated service as production editor of SEN for over 10 years
84
+
- Joanne Atlee, for proposing, championing, and serving as inaugural co-chair of SIGSOFT CARES
85
+
- Alexander Serebrenik, for proposing, championing, and serving as inaugural co-chair of SIGSOFT CARES
86
+
- Kelly Blincoe, for proposing, championing, and serving as inaugural co-chair of SIGSOFT CARES
-**[Impact Paper Award](https://www2.sigsoft.org/awards/impactpaper/)** - Recognizes papers from SIGSOFT conferences that have had significant influence
36
36
37
+
### Service Recognition
38
+
-**[Distinguished Volunteer Certificate](/awards/distinguishedVolunteerCertificate)** - Recognizes sustained or exceptional volunteer service that has significantly advanced SIGSOFT
39
+
37
40
## Nomination Process
38
41
39
42
All awards follow a similar nomination process, with two key deadlines:
Copy file name to clipboardExpand all lines: content/policies/PCpolicy.md
+22-16Lines changed: 22 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,10 +4,8 @@ title = "ACM SIGSOFT Policy on Program Committees"
4
4
5
5
# ACM SIGSOFT Policy on Program Committees
6
6
7
-
8
7
## Program Committee Members
9
8
10
-
11
9
The program committee is responsible for objectively and thoroughly reviewing all submissions, for submitting timely, informative reviews that provide authors with feedback about their submissions, and for attending the program committee meetings.
12
10
13
11
The program committee members should be recognized experts in the subject area of the event. For recurring events, at least one-third of the program committee membership should change. Most program committee members should not serve for more than three consecutive terms and in no instance should an individual serve more than four consecutive terms.
@@ -20,29 +18,31 @@ Any restrictions on submissions by program committee members must be clearly con
20
18
21
19
## Submissions from Organizing Committee Members
22
20
21
+
For **conferences and symposia**, the **General Chair** and **Program Chair** of the event may not submit to any track of the event. This restriction also extends to the General Chair's and Program Chair's **directly supervised students, postdocs, and employees**. However, they (general and program chairs, as well as their directly supervised students, postdocs, and employees) can submit to **co-located events and workshops** of the conference they are chairing, provided that they are not the editors of the volume that includes workshop proceedings. General and program co-chairs cannot **propose/organize workshops** themselves, but members of their groups can.
23
22
24
-
For conferences and symposia, the General Chair and Program Chair of the event may not submit to any track of the event. This restriction also extends to the General Chair's and Program Chair's directly supervised students. This restriction does not apply to workshops and collocated events. All other members of the Organizing Committee and their directly supervised students may submit to any track other than the track they are chairing. Directly-supervised students are defined as only those students who are conducting their research under the primary guidance of the General Chair or Program Chair, and not those students who must have the General Chair or Program Chair as their diploma/thesis/dissertation chair of record due to university, state, province, or national rules, but are primarily advised by other (e.g., more junior) professors.
23
+
For **workshops**, the **organizers** and their **directly supervised students, postdocs, and employees** cannot submit to their workshop.
24
+
25
+
Directly-supervised students are defined as only those students who are conducting their research under the primary guidance of the General Chair or Program Chair, and not those students who must have the General Chair or Program Chair as their diploma/thesis/dissertation chair of record due to university, state, province, or national rules, but are primarily advised by other (e.g., more junior) professors.
25
26
26
-
## Conflicts of Interest and Confidentiality of Submissions
27
27
28
+
## Conflicts of Interest and Confidentiality of Submissions
28
29
29
-
SIGSOFT requires members of the program committees of its events to adhere to the highest of ethical standards. Program committee chairs must ensure that these standards are not only met to the letter of the policy but also to the spirit of its intent. This means that even the appearance of a conflict of interest or breach of confidentiality in the selection process should be avoided.
30
+
SIGSOFT requires members of the program committees of its events to adhere to the **highest ethical standards**. Program committee chairs must ensure that these standards are not only met to the letter of the policy but also to the spirit of its intent. This means that even the appearance of a **conflict of interest** or **breach of confidentiality** in the selection process should be avoided.
30
31
31
-
A program committee member (including the chair of the committee) is considered to have a conflict of interest on a submission that has an author in any of the following categories:
32
+
A **program committee member (including the chair of the committee)** is considered to have a **conflict of interest** on a submission that has an author in any of the following categories:
32
33
33
-
1. the person themselves;
34
-
2. a past or current student or academic advisor;
35
-
3. a supervisor or employee in the same line of authority within the past three years;
36
-
4. a member of the same organization (e.g., company, university, government agency, etc.) within the past three years;
37
-
5. a co-author of a paper appearing in publication within the past three years;
38
-
6. someone with whom there has been a financial relationship (e.g., grants, contracts, consultancies, equity investments, stock options, etc.) within the past three years;
39
-
7. someone with whom acceptance or rejection would further the personal goals of the reviewer (e.g., a competitor);
40
-
8. a member of the same family or anyone considered a close personal friend; or
41
-
9. someone about whom, for whatever reason, their work cannot be evaluated objectively.
34
+
1. the person themselves;
35
+
2. a past or current student or academic advisor;
36
+
3. a member of the same organization (e.g., company, university, government agency, etc.) within the past three years;
37
+
4. a co-author of a paper under preparation, submitted, or which was published (or posted online in a digital library or public repository such as arXiv) within the past three years[^1]. This rule does not apply to editorials or proceedings prefaces;
38
+
5. a co-chair (general/program) of a future conference, or a conference that occurred within the last 12 months. The rule does not apply to workshops (including events such as Shonan meetings or Dagstuhl workshops), even if they have an editorial or a published report by the organizers.
39
+
6. someone with whom there has been a financial relationship (e.g., grants, contracts, consultancies, equity investments, stock options, etc.) within the past three years;
40
+
7. a member of the same family or anyone considered a close personal friend; or
41
+
8. someone whose work cannot be evaluated objectively, for a personal or professional reason.
42
42
43
43
Committee members must declare their conflicts to the program chair before any discussions of the submissions begin.
44
44
45
-
Committee members in conflict with an author will not be allowed to see the reviews of the submission, nor will the names of the reviewers be divulged. During any and all discussions of the submission (e.g., at the program committee meeting, during pre-meeting email discussions, etc.), the member in conflict will be barred from participating in any way either actively or passively (e.g., by absenting themselves from the room in which the discussion is being held, not being a recipient of email, etc.).
45
+
Committee members in conflict with an author will not be allowed to see the reviews of the submission, nor will the names of the reviewers be divulged. During any and all discussions of the submission (e.g., at the program committee meeting, during pre-meeting email discussions, etc.), the member in conflict will be barred from participating in any way, either actively or passively (e.g., by absenting themselves from the room in which the discussion is being held, not being a recipient of email, etc.).
46
46
47
47
In case the program chair is in conflict, the chair will assign an alternate chair for any submissions for which they have a conflict. For those submissions, the alternate chair will select the reviewers and will chair the discussion of the submission in the program chair's absence. As a concession to practicality in the mechanics of organizing and reporting the results of the review process, the program chair is permitted to view all reviews for all submissions, including those with which they have a conflict. Nevertheless, the program chair must maintain the confidentiality of those reviews.
48
48
@@ -52,6 +52,8 @@ This conflict of interest and confidentiality policy extends to any supplemental
52
52
53
53
The program chair will make reasonable efforts to ensure that the manuscripts submitted are made available to and reviewed only by the program committee and supplemental reviewers acting on behalf of the program committee. Neither SIGSOFT nor ACM guarantee the confidentiality of the submitted manuscripts, and accept no liability in the event that the manuscripts are distributed beyond the reviewers.
54
54
55
+
[^1]: For arXiv reports, the last modification date matters. For conference papers, the conference date matters. For journal papers, the acceptance date matters. For example, if an arXiv paper is accepted at the conference, the conference date will be the date used in COI calculation.
56
+
55
57
## Awards and Special Issues of Journals
56
58
57
59
Program committees should present the ACM SIGSOFT Distinguished Paper Award to an appropriate subset of the accepted submissions; rules and details of the award are available [here](/awards/distinguishedpaper/). This benefits both the authors and the conference by raising visibility in the broader community. Distinguished papers should also be considered for expedited review and publication in an ACM journal, such as Transactions on Software Engineering and Methodology ([TOSEM](http://www.acm.org/tosem/)), or in any other suitable journal. Again, this has the benefit of raising the visibility of the conference. Program chairs should seek prior approval directly from the Editor in Chief of the selected publication. Distinguished paper awards and expedited journal publication should be noted in the call to make submission more appealing to authors.
@@ -63,3 +65,7 @@ Conferences should require full-length, original papers for review. Experience s
63
65
All calls should encourage students to participate in the event. Information should be included about the [Conference Attendance Program (CAPS)](/activities/capsmain/), which provides scholarships for students to help defray the cost of attending events, especially if they have an accepted paper at a conference.
64
66
65
67
In addition, all calls should make authors aware of the [ACM Policy and Procedures on Plagiarism.](http://www.acm.org/publications/policies/plagiarism_policy) Authors must be asked to indicate their understanding and acceptance of the policy and procedures at the time of submission. This can normally be done as part of the electronic submission process, such as through a checkbox that must be checked in order for the submission to be recorded.
68
+
69
+
## Changelog
70
+
71
+
-**2026-04**: Updated the conflict of interest section to clarify COI rules for directly supervised students, postdocs, employees, recent co-authorship, and conference co-chair relationships; added workshop-specific guidance.
Copy file name to clipboardExpand all lines: content/volunteers.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@ SIGSOFT offers a variety of opportunities for getting involved in SIGSOFT events
7
7
If you would like to participate as a volunteer for SIGSOFT,
8
8
please fill in the appropriate information on the [Google Form](https://docs.google.com/forms/d/e/1FAIpQLSe3fEsroIbpcOPrqQbEaFl5Wh1YeT3S_UNl-s2EGqDZ6dJNmQ/viewform?usp=dialog).
9
9
10
+
SIGSOFT also recognizes exceptional volunteer service through the [Distinguished Volunteer Certificate](/awards/distinguishedVolunteerCertificate).
11
+
10
12
## Volunteer Opportunities
11
13
12
14
There are many ways to get involved in SIGSOFT activities as volunteers.
@@ -21,4 +23,4 @@ Here are some examples.
21
23
- SIGSOFT special projects that need some extra help
22
24
- Run for election for SIGSOFT executive committee
23
25
- Serve on program committees of SIGSOFT sponsored conferences
24
-
- Serve as conference or program chair of SIGSOFT sponsored conference
26
+
- Serve as conference or program chair of SIGSOFT sponsored conference
0 commit comments