Merge branch 'master' of github.com:SIGPLAN/SIGPLAN.github.io

Author: sampsyo

Cares/index.md

@@ -79,6 +79,15 @@ CARES committee members may also attend other workshops and conferences sponsore
     <th><b>Conference/Meeting</b></th>
     <th><b>CARES member attendees</b></th>
  </tr>
+    <tr>
+    <td><a href="https://popl26.sigplan.org">POPL 2026</a></td>
+    <td>Jeff Foster, Stephanie Weirich</td>
+  </tr>
+    <tr>
+    <td><a href="https://icfp25.sigplan.org">ICFP 2025</a>/
+<a href="https://2025.splashcon.org">SPLASH 2025</a></td>
+    <td>Steve Blackburn, Bor-Yuh Evan Chang, Sophia Drossopoulou, Jeff Foster, Sukyoung Ryu, KC Sivaramakrishnan</td>
+  </tr>
     <tr>
     <td><a href="https://pldi25.sigplan.org">PLDI 2025</a></td>
     <td>Steve Blackburn, Işıl Dillig, Nate Foster, Sukyoung Ryu, Manu Sridharan</td>
@@ -180,25 +189,26 @@ CARES committee members may also attend other workshops and conferences sponsore
 
 ### SIGPLAN CARES Reports
 
-### 2024:
+### 2025:
 
-This is the fifth annual report from the SIGPLAN CARES committee---a committee established to listen to and support folks in the programming languages community who experience or witness discrimination, harassment, or other violations of the ACM's code of conduct or ethics.
+This is the sixth annual report from the SIGPLAN CARES committee---a committee established to listen to and support folks in the programming languages community who experience or witness discrimination, harassment, or other violations of the ACM's code of conduct or ethics.
 
 **What CARES does.**   CARES is dedicated to providing completely confidential support to members of the programming language community.  We listen to members who come to us for advice or who just want to talk. If they would like advice on what kinds of actions they can take, we do our best to provide such advice.  
 
 **Confidentiality.**  When a person approaches a CARES member in confidence, that CARES member will not share any information about the situation with anyone else without that person's explicit permission, unless there is an imminent threat or danger of some kind.  Indeed, CARES members do not share the details of contacts made with other CARES members unless permitted.  
 
 As a result, our annual reports are brief.  They do not contain details about the types of contacts that CARES members have made and they do not even contain specific numbers of contacts.  The reports are structured this way to protect the privacy of those that approach us.  
 
-#### What happened in 2024
+#### What happened in 2025
 
-In 2024, individual SIGPLAN CARES committee members were contacted confidentially by between 1 and 5 community members throughout the year.  Such contacts sometimes led to extended conversations.  
+In 2025, individual SIGPLAN CARES committee members were contacted confidentially by between 1 and 5 community members throughout the year.  Such contacts sometimes led to extended conversations.  
 
-Members of the CARES committee represented CARES at three conferences in 2024, namely POPL 2024, PLDI 2024, and ICFP 2024.  Attendance specifics are listed on the CARES website. The presence of CARES was advertised at the opening of the conference through the general chair’s presentation. 
+Members of the CARES committee represented CARES at four conferences in 2025, namely POPL 2025, PLDI 2025, ICFP 2025, and SPLASH 2025.  Attendance specifics are listed on the CARES website. The presence of CARES was advertised at the opening of the conference through the general chair’s presentation. 
 
 We have received open, public feedback from a number of members of the community expressing the fact that they appreciate the creation of the committee---they view it as a sign that the programming languages community takes community climate and our code of conduct seriously.  The fact the committee has received confidential contacts is also evidence that the community would like mechanisms to discuss matters of harassment, discrimination, or ethics in private. 
 ### Older Reports
 
+* [2024 Report](report2024)
 * [2023 Report](report2023)
 * [2022 Report](report2022)
 * [2021 Report](report2021)
@@ -209,15 +219,11 @@ We have received open, public feedback from a number of members of the community
 <table style="width:100%" border="0">
 <tr>
    <td><img src="http://sigplan.org/images/cares-photos/ryu.png" alt="Sukyoung Ryu" width="156"><br><a href="https://plrg.kaist.ac.kr/ryu">Sukyoung Ryu</a> (she/her)</td>
-   <td>Co-Chair, <a href="mailto:sryu.cs@kaist.ac.kr">sryu.cs@kaist.ac.kr</a>, KAIST, Jan 2021-</td>
+   <td>Co-Chair, <a href="mailto:sryu.cs@kaist.ac.kr">sryu.cs@kaist.ac.kr</a>, KAIST, Jan 2021- (co-chair 2024-2027)</td>
   </tr> 
-<tr>
-   <td><img src="http://sigplan.org/images/cares-photos/silva.png" alt="Alexandra Silva"  width="156"><br><a href="https://www.alexandrasilva.org/#/main.html">Alexandra Silva</a> (she/her)</td>
-   <td>Co-Chair, <a href="mailto:alexandra.silva@cornell.edu">alexandra.silva@cornell.edu</a>, Cornell University, Jan 2020-</td>
-</tr>
     <tr>
    <td><img src="http://sigplan.org/images/cares-photos/steve.jpg" alt="Steve Blackburn"  width="156"><br><a href="https://www.steveblackburn.org">Steve Blackburn</a> (he/him)</td>
-   <td>Member, <a href="mailto:steve.blackburn@anu.edu.au">steve.blackburn@anu.edu.au</a>, Google Deepmind and ANU, Jan 2024-</td>
+   <td>Co-Chair, <a href="mailto:steve.blackburn@anu.edu.au">steve.blackburn@anu.edu.au</a>, Google Deepmind and ANU, Jan 2024- (co-chair 2026-2029)</td>
   </tr> 
  <tr>
    <td><img src="../images/cares-photos/chang.jpg" alt="Bor-Yuh Evan Chang" width="156"><br><a href="https://plv.colorado.edu/bec/">Bor-Yuh Evan Chang</a> (he/him)</td>
@@ -243,6 +249,10 @@ We have received open, public feedback from a number of members of the community
    <td><img src="../images/cares-photos/igarashi.jpg" alt="Atsushi Igarashi" width="156"><br><a href="https://www.fos.kuis.kyoto-u.ac.jp/~igarashi/index.html.en">Atsushi Igarashi</a> (he/him)</td>
    <td>Member, <a href="mailto:igarashi@kuis.kyoto-u.ac.jp">igarashi@kuis.kyoto-u.ac.jp</a>, Kyoto University, Oct 2022-</td>
   </tr> 
+<tr>
+   <td><img src="http://sigplan.org/images/cares-photos/silva.jpeg" alt="Alexandra Silva"  width="156"><br><a href="https://www.alexandrasilva.org/#/main.html">Alexandra Silva</a> (she/her)</td>
+   <td>Member, <a href="mailto:alexandra.silva@cornell.edu">alexandra.silva@cornell.edu</a>, Cornell University, Jan 2020- (co-chair 2022-2025) </td>
+</tr>
  <tr>
    <td><img src="../images/cares-photos/sivaramakrishnan.jpg" alt="KC Sivaramakrishnan" width="156"><br><a href="https://kcsrk.info">KC Sivaramakrishnan</a> (he/him)</td>
    <td>Member, <a href="mailto:kc@kcsrk.info">kc@kcsrk.info</a>, Indian Institute of Technology, Madras, Jul 2025-</td>
@@ -251,9 +261,9 @@ We have received open, public feedback from a number of members of the community
    <td><img src="http://sigplan.org/images/cares-photos/sridharan.jpg" alt="Manu Sridharan"  width="156"><br><a href="https://manu.sridharan.net">Manu Sridharan</a> (he/his)</td>
    <td>Member, <a href="mailto:manu@cs.ucr.edu">manu@cs.ucr.edu</a>, University of California, Riverside, Dec 2024-</td>
   </tr> 
-<tr>
-   <td><img src="http://sigplan.org/images/cares-photos/weirich.png" alt="Stephanie Weirich"  width="156"><br><a href="https://www.cis.upenn.edu/~sweirich/">Stephanie Weirich</a> (she/her)</td>
-   <td>Member, <a href="mailto:sweirich@cis.upenn.edu">sweirich@cis.upenn.edu</a>, University of Pennsylvania, Jan 2020-</td>
+ <tr>
+   <td><img src="http://sigplan.org/images/cares-photos/steve2017.jpg" alt="Steve Zdancewic"  width="156"><br><a href="https://www.cis.upenn.edu/~stevez">Steve Zdancewic</a> (he/his)</td>
+   <td>Member, <a href="mailto:stevez@seas.upenn.edu">stevez@seas.upenn.edu</a>, University of Pennsylvania, Feb 2026-</td>
   </tr> 
  </table>  
 

Cares/previous.md

@@ -17,7 +17,7 @@ title: "Former SIGPLAN CARES Committee Members"
    <td><a href="mailto:simon.peytonjones@gmail.com">simon.peytonjones@gmail.com</a>, Epic Games, Jan 2020-Dec 2024</td>
   </tr>
  <tr>
-   <td><img src="../images/cares-photos/keller.jpeg" alt="Gabriele Keller" width="156"><br><a href="https://www.uu.nl/staff/GKKeller">Gabriele Keller</a></td>
+   <td><img src="http://sigplan.org/images/cares-photos/keller.jpeg" alt="Gabriele Keller" width="156"><br><a href="https://www.uu.nl/staff/GKKeller">Gabriele Keller</a></td>
    <td><a href="mailto:g.k.keller@uu.nl">g.k.keller@uu.nl</a>, Utrecht University, Oct 2021-Jun 2025</td>
   </tr> 
  <tr>
@@ -30,12 +30,16 @@ title: "Former SIGPLAN CARES Committee Members"
   </tr> 
  <tr>
    <td><img src="http://sigplan.org/images/cares-photos/strout.png" alt="Michelle Strout"  width="156"><br><a href="http://cgi.cs.arizona.edu/~mstrout/">Michelle Strout</a> (she/her)</td>
-   <td><a href="mailto:michelle.strout@hpe.com">michelle.strout@hpe.com</a>, HPE and University of Arizona, Jan 2020-Jun 2025</td>
+   <td><a href="mailto:michelle.strout@hpe.com">michelle.strout@hpe.com</a>, HPE and University of Arizona, Jan 2020-Jun 2025 (co-chair 2021-2024)</td>
   </tr> 
     <tr>
    <td><img src="http://sigplan.org/images/cares-photos/walker.png" alt="David Walker" width="156"><br><a href="https://www.cs.princeton.edu/~dpw/">David Walker</a> (he/him)</td>
-   <td><a href="mailto:dpw@cs.princeton.edu">dpw@cs.princeton.edu</a>, Princeton University, Nov 2019-Dec 2024 (founder co-chair 2019-2021) </td>
+   <td><a href="mailto:dpw@cs.princeton.edu">dpw@cs.princeton.edu</a>, Princeton University, Nov 2019-Dec 2024 (founder co-chair 2019-2022) </td>
   </tr>
+<tr>
+   <td><img src="http://sigplan.org/images/cares-photos/weirich.png" alt="Stephanie Weirich"  width="156"><br><a href="https://www.cis.upenn.edu/~sweirich/">Stephanie Weirich</a> (she/her)</td>
+   <td><a href="mailto:sweirich@cis.upenn.edu">sweirich@cis.upenn.edu</a>, University of Pennsylvania, Jan 2020-Dec 2025</td>
+  </tr> 
   <tr>
    <td><img src="http://sigplan.org/images/cares-photos/wu.png" alt="Peng Wu" width="156"><br><a href="https://pengwu.wordpress.com/">Peng Wu</a> (she/her)</td>
    <td><a href="mailto:pengwu@fb.com">pengwu@fb.com</a>, Facebook, Jan 2020-Dec 2023 </td>

Cares/report2024.md

@@ -0,0 +1,11 @@
+---
+layout: default
+title: "SIGPLAN CARES Annual Report: 2024"
+---
+In 2024, individual SIGPLAN CARES committee members were contacted confidentially by between 1 and 5 community members throughout the year. Such contacts sometimes led to extended conversations.
+
+Members of the CARES committee represented CARES at three conferences in 2024, namely POPL 2024, PLDI 2024, and ICFP 2024.  Attendance specifics are listed on the CARES website. The presence of CARES was advertised at the opening of the conference through the general chair’s presentation. 
+
+We have received open, public feedback from a number of members of the community expressing the fact that they appreciate the creation of the committee—they view it as a sign that the programming languages community takes community climate and our code of conduct seriously. The fact the committee has received confidential contacts is also evidence that the community would like mechanisms to discuss matters of harassment, discrimination, or ethics in private.
+
+[cares]: /Cares/

Conferences/OOPSLA.md

@@ -16,13 +16,17 @@ The scope of OOPSLA includes all aspects of programming languages and software e
 
 OOPSLA papers are published in the PACMPL, which [states in its procedures under governance](https://sigplan.org/PACMPL/) that "authors of all accepted papers are encouraged (but not required) to present their work at the corresponding conference". To maximise the in-person experience, we ask all the authors who choose to present their work at the conference to do so **fully in person** by attending the conference and registering for the full 3-day OOPSLA event. We are currently unable to support remote participation, and we suggest that the authors explore the optional "SIGPLAN Track" that is provided by some of the SIGPLAN conferences to allow the recent PACMPL published work to be presented in person for the first time.
 
+**OOPSLA Policy on General Chair Submissions**
+
+The SPLASH General Chair is permitted to submit papers to OOPSLA. However, a General Chair who submits must not be involved in the reviewing process in any way, including selecting RC chairs directly, overseeing the review of papers, or serving in any review-chair-like role (e.g., assisting with reviewer assignments or acting as an admin on the submission system). The RC chairs should ensure that a non-conflicted Associate Editor (AE, called "Associate Chair" in some OOPSLA documentation) handles any paper involving the General Chair. This policy is supported in part by the fact that OOPSLA now has two RC co-chairs, which makes it easier to manage such conflicts fairly. Note that the [SIGPLAN Guidelines for the General Chair](/Resources/Guidelines/GenChair/) recommend that the General Chair not submit, but the OOPSLA Steering Committee has determined that submission is allowed provided the conditions above are met.
+
 **Most Influential OOPSLA Paper Award**
 
 Each year a "Most Influential" OOPSLA paper is chosen and an presentation is made at OOPSLA. More details about this award and past winning papers can be found [here](/Awards/OOPSLA/). SIGPLAN also makes several other awards including an "Outstanding Dissertation Award." Please consider making a nomination for one of these awards.  More details about the SIGPLAN awards can be found [here](/Awards/).
 
 **Documents on How to Run SPLASH/OOPSLA Conferences**
 
-   * [OOPSLA](/Conferences/SPLASH/HowToOOPSLA)
+   * [OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA)
    * [SPLASH](/Conferences/SPLASH/HowToSPLASH)
 
 Web Pages of Previous Conferences

Conferences/SPLASH.md

@@ -31,7 +31,7 @@ The current SPLASH steering committee is:
 
 **Documents on How to Run SPLASH/OOPSLA Conferences**
 
-   * [OOPSLA](/Conferences/SPLASH/HowToOOPSLA)
+   * [OOPSLA](/Conferences/SPLASH/ObjectivesOfOOPSLA)
    * [SPLASH](/Conferences/SPLASH/HowToSPLASH)
 
 **SPLASH Steering Committee Representatives for SIGPLAN Awards**