add osre26

0001-fix-indentations.patch

@@ -0,0 +1,51 @@
+From 0883b1a2f26ebea9e2c3278d7439a5783a332af0 Mon Sep 17 00:00:00 2001
+From: Carlos Maltzahn <carlosm@ucsc.edu>
+Date: Mon, 7 Jul 2025 13:04:14 -0700
+Subject: [PATCH] fix indentations
+
+---
+ content/authors/ankitkat042/_index.md | 18 +++++++++---------
+ 1 file changed, 9 insertions(+), 9 deletions(-)
+
+diff --git a/content/authors/ankitkat042/_index.md b/content/authors/ankitkat042/_index.md
+index 0c462ad..750f28c 100644
+--- a/content/authors/ankitkat042/_index.md
++++ b/content/authors/ankitkat042/_index.md
+@@ -15,7 +15,7 @@ role: Undergraduate Computer Science student at Indraprastha Institute of Inform
+ # Organizations/Affiliations
+ organizations:
+ - name: Indraprastha Institute of Information Technology Delhi (IIIT Delhi)
+-url: "https://iiitd.ac.in/"
++  url: "https://iiitd.ac.in/"
+
+ # Short bio (displayed in user profile at end of posts)
+ bio: BTech student at IIIT Delhi with experience in software development, network systems research and cryptography. Currently working on high-performance network benchmarking and protocol analysis.
+@@ -34,17 +34,17 @@ education:
+ # Social/Academic Networking
+ social:
+ - icon: envelope
+-icon_pack: fas
+-link: 'mailto:address.ankit@gmail.com'
++  icon_pack: fas
++  link: 'mailto:address.ankit@gmail.com'
+ - icon: github
+-icon_pack: fab
+-link: https://github.com/ankitkat042
++  icon_pack: fab
++  link: https://github.com/ankitkat042
+ - icon: linkedin
+-icon_pack: fab
+-link: https://www.linkedin.com/in/ankitk042
++  icon_pack: fab
++  link: https://www.linkedin.com/in/ankitk042
+ - icon: X
+-icon_pack: ai
+-link: https://x.com/ankitkat_042
++  icon_pack: ai
++  link: https://x.com/ankitkat_042
+
+ # Enter email to display Gravatar (if Gravatar enabled in Config)
+ email: "address.ankit@gmail.com"
+-- 
+2.45.2
+

README.md

@@ -12,13 +12,13 @@ A project serves as the context for one or more project ideas. Each project is r
 - Option A: email OSRE [administrators](mailto:slieggi@ucsc.edu) 
 - Option B (via git):
   - Fork [git repository](https://github.com/ucsc-ospo/ucsc-ospo.github.io)
-  - Create `content/project/osre25/ORGANIZATION/PROJECTNAME` directory or copy it from previous year's `content/project/osre24/ORGANIZATION/PROJECTNAME`
+  - Create `content/project/osre26/ORGANIZATION/PROJECTNAME` directory or copy it from previous year's `content/project/osre24/ORGANIZATION/PROJECTNAME`
   - In that directory create/update `index.md` and the project's image (`featured.png` or `featured.jpg`) 
   - In `index.md` fill in the frontmatter (see [example](https://raw.githubusercontent.com/ucsc-ospo/ucsc-ospo.github.io/main/content/project/osre22/ucsc/polyphorm/index.md)):
     - Add the project's title in `title:`, 
     - Date the project entry with `date:` and `lastmod:`, using the format `2022-05-27`. **Note that projects dated in the future will not display**.
     - Include a list of `authors:`, using either names in quotes or user names (see below for instructions on how to establish user names)
-    - **IMPORTANT**: set a list of tags that include `"osre25"` and either `"uc"` or `"reproducibility"` or both, depending on whether your project has a mentor affiliated with a UC campus or associated national lab (LBL, LANL, LLNL), or is a _Summer of Reproducibility_ project. Feel free to add additional tags.
+    - **IMPORTANT**: set a list of tags that include `"osre26"` and either `"uc"` or `"reproducibility"` or both, depending on whether your project has a mentor affiliated with a UC campus or associated national lab (LBL, LANL, LLNL), or is a _Summer of Reproducibility_ project. Feel free to add additional tags.
     - Below the frontmatter start with a description of the project and include links to the project's webpage. 
     - Add each project idea with level-3 header, i.e., `### ...` and add a list of **essential information** that includes *topics*, *skills*, *difficulty*, *size* (175 vs 350 hours), and *mentors*.
   - Make a pull request.
@@ -47,36 +47,36 @@ The website has five "lists":
 
 ## How to add a new annual edition of the Open Source Research Experience
 
-To archive the current year (e.g. 2024) and start a new OSRE edition: 
+To archive the current year (e.g. 2025) and start a new OSRE edition: 
 - Update `/content/osre/index.md`
-- Copy `/content/osre24` to `/content/osre25` 
-- Make the following updates within `/content/osre25`:
-  - Update `/content/osre25/intro.md`
-  - Rename and update `content/osre25/osre25.md`
+- Copy `/content/osre25` to `/content/osre26` 
+- Make the following updates within `/content/osre26`:
+  - Update `/content/osre26/intro.md`
+  - Rename and update `content/osre26/osre26.md`
   - For Student Pages:
-    - In `/content/osre25/studentpages.md` 
-      - Update `subtitle: "Go to [2024 student pages](/osre24/#studentpages)"`
-      - Update `tag: [osre25]`
-      - Update "OSRE 2025" in body
-    - In `/content/osre24/studentpages.md` update `subtitle: "Go to [2023 student pages](/osre23/#studentpages)  \nReturn to [2025 student pages](/osre25/#studentpages)"`
+    - In `/content/osre26/studentpages.md` 
+      - Update `subtitle: "Go to [2025 student pages](/osre25/#studentpages)"`
+      - Update `tag: [osre26]`
+      - Update "OSRE 2026" in body
+    - In `/content/osre25/studentpages.md` update `subtitle: "Go to [2024 student pages](/osre24/#studentpages)  \nReturn to [2026 student pages](/osre26/#studentpages)"`
   - For Projects:
-    - In `/content/osre25/projects.md` 
-      - Update `title: 2025 Projects`
-      - Update `subtitle: "Go to [2024 projects](/osre24/#projects)"`
-      - Update `tag: [osre25]`
-    - In `/content/osre24/projects.md"` update `subtitle: "Go to [2023 projects](/osre23/#projects)  \nReturn to [2025 projects](/content/osre25/#projects)"`
+    - In `/content/osre26/projects.md` 
+      - Update `title: 2026 Projects`
+      - Update `subtitle: "Go to [2025 projects](/osre25/#projects)"`
+      - Update `tag: [osre26]`
+    - In `/content/osre25/projects.md"` update `subtitle: "Go to [2024 projects](/osre24/#projects)  \nReturn to [2026 projects](/content/osre26/#projects)"`
   - For Timelines:
-    - In `/content/osre25/timeline.md` 
-      - Update `subtitle: "Go to [2024 timeline](/osre24/#timeline)"`
-      - In body update `caption="Table: OSRE 2025 Timeline"`
-      - Update `/content/osre25/timeline.csv`
-    - In `/content/osre24/timeline.md` update `subtitle: "Go to [2023 timeline](/osre23/#timeline)  \nReturn to [2025 timeline](/osre25/#timeline)"`
-- Copy `/content/report/osre24/ucsc/admin/20231006-admin` to `/content/report/osre25/ucsc/admin/20231021-admin` (or any other `YYYYMMDD-admin` name) and update tags (and any new instructions) in `index.md` of that directory:
-  - Update title to OSRE 2025
-  - Replace all `osre24` with `osre25`
-- Update `/content/osre25/intro.md` cta link `url: '/osre25/#projects'`
-- Update `/content/osredocs` files for mentors, students, and mentor FAQs for OSRE 2025 (The OSRE documentation is updated in place -- use version control to find out about documentation of earlier years)
-- Copy `/content/sor24` to `/content/sor25`, make 2025 updates to `/content/sor25`, and update SoR links in `/content/oser25/osre25.md` to `/sor25` and vice versa.
+    - In `/content/osre26/timeline.md` 
+      - Update `subtitle: "Go to [2025 timeline](/osre24/#timeline)"`
+      - In body update `caption="Table: OSRE 2026 Timeline"`
+      - Update `/content/osre26/timeline.csv`
+    - In `/content/osre25/timeline.md` update `subtitle: "Go to [2024 timeline](/osre23/#timeline)  \nReturn to [2026 timeline](/osre26/#timeline)"`
+- Copy `/content/report/osre25/ucsc/admin/20241021-admin` to `/content/report/osre26/ucsc/admin/20241021-admin` (or any other `YYYYMMDD-admin` name) and update tags (and any new instructions) in `index.md` of that directory:
+  - Update title to OSRE 2026
+  - Replace all `osre25` with `osre26`
+- Update `/content/osre26/intro.md` cta link `url: '/osre26/#projects'`
+- Update `/content/osredocs` files for mentors, students, and mentor FAQs for OSRE 2026 (The OSRE documentation is updated in place -- use version control to find out about documentation of earlier years)
+- Outdated: Copy `/content/sor24` to `/content/sor25`, make 2025 updates to `/content/sor25`, and update SoR links in `/content/oser25/osre26.md` to `/sor25` and vice versa.
 
 ## How to fix the deployment workflow
 

content/osre/index.md

@@ -5,9 +5,10 @@ subtitle: "Matching researchers with summer students and sponsors."
 ---
 The Open Source Research Experience (OSRE) program by the Open Source Program Office (OSPO) UC Santa Cruz provides support for undergraduate and graduate students contributing to open source research efforts. The goal of the program is to seed contributor communities of open source research efforts and to help make computational research efforts reproducible. With this program the OSPO participates as mentor organization in [Google Summer of Code](https://summerofcode.withgoogle.com) and other outreach and sponsorship programs. 
 
-{{% cta cta_link="/osre25" cta_text="OSRE 2025" %}}
+{{% cta cta_link="/osre26" cta_text="OSRE 2026" %}}
 
 <center>
+<a href="/osre25">OSRE 2025</a><br>
 <a href="/osre24">OSRE 2024</a><br>
 <a href="/osre23">OSRE 2023</a><br>
 <a href="https://cross.ucsc.edu/2022-osre/index.html">OSRE 2022</a><br>

content/osre25/projects.md

@@ -4,7 +4,7 @@ headless: true  # This file represents a page section.
 
 # Put Your Section Options Here (title, background, etc.) ...
 title: 2025 Projects
-subtitle: "For SoR eligible projects, filter for Reproducibiltiy/SoR. " 
+subtitle: "Go to [2024 projects](/osre24/#projects)  \nReturn to [2026 projects](/osre26/#projects)" 
 
 # Position of this section on the page
 weight: 70

content/osre25/studentpages.md

@@ -4,7 +4,7 @@ headless: true  # This file represents a page section.
 
 # Put Your Section Options Here (title, background, etc.) ...
 title: Student pages
-subtitle: "Go to [2024 student pages](/osre24/#studentpages)"
+subtitle: "Go to [2024 student pages](/osre24/#studentpages)  \nReturn to [2026 student pages](/osre26/#studentpages)"
 
 # Position of this section on the page
 weight: 35

content/osre25/timeline.md

@@ -4,7 +4,7 @@ headless: true
 active: true
 weight: 60
 title: Timeline
-subtitle: "Go to [2024 timeline](/osre24/#timeline)"
+subtitle: "Go to [2024 timeline](/osre24/#timeline)  \nReturn to [2026 timeline](/osre26/#timeline)"
 design:
   columns: "2"
   css_style: null

content/osre26/formentors.md

@@ -0,0 +1,45 @@
+---
+widget: blank
+headless: true
+active: true
+weight: 50
+title: For projects and mentors
+design:
+  columns: "2"
+  css_style: null
+  css_class: null
+---
+
+The UCSC OSPO is looking for mentors to be part of our 2026 Open Source Research Experience Program (OSRE). Please read the [FAQ for Mentors](/osredocs/mentorfaq) and, if interested in participating, [the instructions](/osredocs/formentors) for posting projects. 
+
+{{% cta cta_link="/osredocs/mentorfaq" cta_text="FAQ for Mentors -->" %}}
+{{% cta cta_link="/osredocs/formentors" cta_text="The Instructions -->" %}}
+
+While typical OSRE supported projects require mentors who are connected to University of California-based open source projects, the Summer of Reproducibility allows us to also support  mentors interested in research projects related to the creation and usage of reproducibilty artifacts. 
+
+The OSRE aims to increase student capabilities in working in open source projects and creating reproducible artifacts, as well as add productive open source contributors and promote open source and reproducibility throughout the UC system and beyond.
+
+The program team at the UCSC OSPO values diversity and inclusion in all our projects. We invite mentors from groups traditionally excluded in computer science/open source communities to participate in this program.
+
+### Why should you be an OSRE mentor?
+
+If you could use undergraduate* research assistance over the summer with your on-going research, this is a great opportunity to get matched to top students. Like Google Summer of Code, the OSRE allows the mentors to choose the students they want to work with based on an interactive and iterative proposal process. The proposal process provides mentors the opportunity to select someone they want to work with who will benefit their project and research.
+
+### Who can be a mentor?
+
+{{% callout note %}}
+Your project needs to have at least one mentor affiliated with the University of California or associated DOE national labs.
+{{% /callout %}}
+
+**For University of California (UC) projects:** Any UC-affiliated faculty, researchers or graduate students working on projects that are or will ultimately be part of an open source community/ecosystem. 
+
+**For Summer of Reproducibility (SoR) projects:** Researchers and faculty looking to support the open source production or use of reproducibility artifacts.
+
+{{% callout note %}}
+All software created as part of an OSRE project must be released as free and open source under a license that is both approved by the Open Source Initiative (OSI) and recognized as free by the Free Software Foundation (FSF).
+{{% /callout %}}
+
+For more details, please see the [FAQ for Mentors](/osredocs/mentorfaq) and [the instructions](/osredocs/formentors) for posting projects.
+
+{{% cta cta_link="/osredocs/mentorfaq" cta_text="FAQ for Mentors -->" %}}
+{{% cta cta_link="/osredocs/formentors" cta_text="The Instructions -->" %}}

content/osre26/forsponsors.md

@@ -0,0 +1,42 @@
+---
+widget: blank
+headless: true
+active: true
+weight: 55
+title: For sponsors
+design:
+  columns: "2"
+  css_style: null
+  css_class: null
+---
+
+**Is your organization looking to use open source more effectively and want to support projects that directly benefit your business or industry?**  
+
+**Does your company want to strengthen the talent pipeline able to work on technologies essential to your organization’s success?**  
+
+**Do you want to collaborate with innovative open source projects being developed by University of California researchers?**  
+
+{{% cta cta_link="https://forms.gle/9ZTg7pMwa1dQ94NS6" cta_text="Sponsor Projects -->" %}}
+
+The UC Open Source Research Experience (OSRE) offers your organization the chance to participate in projects that can help your development cycles run faster, benefit from wide collaborations, and help support workforce development in domains your organization needs.  
+
+To become a sponsor, fill out the [Sponsorship Interest Form](https://forms.gle/9ZTg7pMwa1dQ94NS6). You will be asked to indicate the level of sponsorship you would like to fund and [the open source projects](/osre26/#projects) you are most interested in engaging with. 
+
+### Benefits of sponsorship
+
+- Collaborating on innovative project that are of strategic interest to your industry;
+- Supporting the teaching of open source techniques to a wide range of student contributors;
+- Interacting with the next generation of open source leaders and up and coming talent; and
+- Recognition as an OSRE Sponsor at the Open Source Research Symposium (Fall 2026)
+
+### OSRE Sponsor Levels
+
+{{< table path="sponsorlevels.csv" header="true" caption="Table: OSRE Sponsorship Levels" >}}
+
+### Becoming a Sponsor
+
+Becoming a sponsor is easy! Fill out the [Sponsorship Interest Form](https://forms.gle/9ZTg7pMwa1dQ94NS6) or reach out to the [OSRE Admins](mailto:ospo-info-group@ucsc.edu) by April 20.  Information requested by the form include: name of contact person, level of sponsorship, and projects you are most interested in (if applicable.) The [OSRE Admins](mailto:ospo-info-group@ucsc.edu) will follow up with next steps for finalizing the sponsorship process.
+
+{{% cta cta_link="https://forms.gle/9ZTg7pMwa1dQ94NS6" cta_text="Sponsor Projects -->" %}}
+
+

content/osre26/forstudents.md

@@ -0,0 +1,31 @@
+---
+widget: blank # As of v5.8-dev, 'pages' is renamed 'collection'
+headless: true  # This file represents a page section.
+
+# Put Your Section Options Here (title, background, etc.) ...
+title: For students
+subtitle: ''
+
+# Position of this section on the page
+weight: 30
+
+design:
+  # Choose a listing view
+  # Choose how many columns the section has. Valid values: '1' or '2'.
+  columns: '2'
+---
+
+
+If you are interested, have a look at our [guidelines for students](/osredocs/forstudents), which includes timelines on when to contact mentors and proposal guidelines and expectations. 
+
+Mentor project ideas will be published beginning in January and updated through February. Students should begin reaching out to mentors after February 28, 2025.
+
+**Students interested in applying to any of our projects must join our Slack channel before March 23, 2025 to be considered elgibile.** THIS DEADLINE HAS PASSED. 
+
+**The FINAL proposal deadline is April 8th at 18:00 UTC.** Proposals should be submitted through the [GSoC portal](https://summerofcode.withgoogle.com/)! Do not send proposal to the organization admins or mentors unless specifically requested by them. If your proposal is not submitted to the GSoC portal by this deadline you will not be eligible for selection.
+
+{{% callout note %}}
+Due to the open source nature of all OSRE projects, contributions are welcome from students or other newcomers from anywhere in the world. Please note that you must have work authorization in your country of residence to take part in this program. For students within the University of California system, you are welcome to participate but be aware we may not be able to place you with mentors from your own campus. Please contact ospo-info-group@ucsc.edu if you have any questions about your eligibility. 
+{{% /callout %}}
+
+We typically support the work of undergraduate students; however graduate students may also apply to work on more advanced project ideas. Please check out the project ideas page and contact the mentor if you have questions.

content/osre26/index.md

@@ -0,0 +1,8 @@
+---
+# Files in this folder represent a Widget Page (homepage)
+title: "OSRE"
+summary: "The Open Source Research Experience"
+date: "2022-11-06T00:00:00Z"
+type: "widget_page"
+header.on_scroll: true
+---