From 6abdd50c9a0733f998642127ffed2f642fcf81f1 Mon Sep 17 00:00:00 2001 From: Oliver Beckstein Date: Thu, 19 Feb 2026 12:05:01 -0700 Subject: [PATCH 01/10] copied 2026 GSOC post with small changes (WIP) --- _posts/2026-02-19-gsoc2026.md | 170 ++++++++++++++++++++++++++++++++++ 1 file changed, 170 insertions(+) create mode 100644 _posts/2026-02-19-gsoc2026.md diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md new file mode 100644 index 00000000..e69ca252 --- /dev/null +++ b/_posts/2026-02-19-gsoc2026.md @@ -0,0 +1,170 @@ +--- +layout: post +title: Google Summer of Code 2026 +--- + +

+Google Summer of Code with +MDAnalysis 2026 +

+ +MDAnalysis has been accepted as an [organization][org] for [Google Summer of +Code][gsoc] (GSoC) 2026! If you are interested in working with us and you +are new to open source, please read the advice and links below to learn how you can apply to participate in GSoC 2026 with MDAnalysis. + +The application window **deadline** is **March 31, 2026 - 18:00 UTC**. +As part of the application process you must familiarize +yourself with [Google Summer of Code 2026][gsoc], including eligibility requirements, timelines, and generally how the program works. + +We are looking forward to all applications from *any new and beginner +open source contributors or students over 18 years old*; see a full list of the [eligibility requirements][eligibility criteria] in the [GSoC FAQ](https://developers.google.com/open-source/gsoc/faq). Projects +are scoped as either 90-hour (small), 175-hour (medium) or 350-hour (large) size. The +duration can be extended from the standard 8 weeks to up to 12 weeks (for small projects), or from the standard 12 weeks up to 22 weeks (for medium or large projects). + +Potential GSoC Contributors are expected to familiarize themselves with application +requirements and mentoring organizations **as soon as possible**. If you are interested in working with us, please read on to learn about [MDAnalysis project ideas](#project-ideas) and [MDAnalysis-specific requirements for putting together your application](#information-for-prospective-gsoc-contributors). + +## Project Ideas + +If you have your own idea about a potential project we'd love to work with you +to develop this idea; please write to us on the [GSoC with MDAnalysis discussion forum][discussion forum] to discuss it there. + +We also have listed several [possible projects][ideas] for you to work on. Our +initial list of ideas (see summaries in the table below) contains various +projects of different scope and with different skill requirements. However, +check the [ideas] page — we might add more ideas after the posting date of +this post. + +Our experience shows that having the listed skills increases the +chances that a project will be completed successfully, so we use them +as part of [our decision criteria in choosing GSoC contributors](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-Proposal-Review). + +This year, MDAnalysis is joining forces with two other open source projects to offer even more far-reaching collaborative projects: [WESTPA]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#westpa), and [Molecular Nodes]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#molecular-nodes). + + +| project | name | difficulty | project size | description | skills | mentors | +|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------------| +| 1 | [Dashboard for tracking MD simulation progress with the new streaming interface](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-1-dashboard-for-tracking-md-simulation-progress-with-the-new-streaming-interface) | easy/medium | 175/350 hours | Create a web-based dashboard for real-time monitoring and analysis of MD simulations | Python (frontend UI, multiprocessing), Networking (TCP/IP) | [@HeydenLab](https://github.com/HeydenLab) [@amrutesht](https://github.com/amrutesht) [@orbeckst](https://github.com/orbeckst) | +| 2 | [Better interfacing of Blender and MDAnalysis](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-2-better-interfacing-of-blender-and-mdanalysis) | medium | 350 hours | Improve how Blender and Molecular Nodes interface with MDAnalysis to import and animate MD trajectories | Python, MDAnalysis, Blender (and programming via its Python API) | [@bradyajohnston](https://github.com/bradyajohnston) [@nilay-v3rma](https://github.com/nilay-v3rma) | +| 3 | [Benchmarking and performance optimization](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-3-benchmarking-and-performance-optimization) | easy/medium | 90/175/350 hours | Write benchmarks for automated performance analysis and address performance bottlenecks | Python/ASV, Cython | [@orbeckst](https://github.com/orbeckst) [@yuxuanzhuang](https://github.com/yuxuanzhuang) [@talagayev](https://github.com/talagayev) | +| 4 | [Lazy trajectory loading and indexing](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-4-lazy-trajectory-loading-and-indexing) | medium | 175/350 hours | Improve performance of trajectory reading by implementing lazy indexing | Python, trajectory I/O, performance optimization | [@yuxuanzhuang](https://github.com/yuxuanzhuang) [@orbeckst](https://github.com/orbeckst) [@talagayev](https://github.com/talagayev) | +| 5 | [Dashboard for tracking WESTPA simulation progress](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-5-dashboard-for-tracking-westpa-simulation-progress) | easy | 90 hours | Create a graphical user interface to report MD trajectory progress | Python (frontend UI, multiprocessing), Networking (TCP/IP) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) [@nilay-v3rma](https://github.com/nilay-v3rma) | +| 6 | [Interface for post-analysis analysis ("crawling") of WESTPA simulations](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-6-interface-for-post-analysis-crawling-of-WESTPA-simulation) | easy | 90 hours | Create an interface for reading, analyzing, and writing post-simulation data from WESTPA HDF5 Framework | Python (frontend UI, multiprocessing), HDF5 Format (h5py, hdf5) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) | + +## Information for prospective GSoC Contributors + +You must meet our [own requirements] if you want to be a GSoC +Contributor with MDAnalysis this year (read all the docs behind these +links!) and read the points below for the application process. You must also meet the [GSoC eligibility criteria][eligibility criteria]. [Our GSoC FAQ][GSoC FAQ] collects common questions from applicants. + +In short: +1. [Agree to be bound by our Code of Conduct](#code-of-conduct) (and [WESTPA's Code of Conduct](https://github.com/westpa/westpa/wiki/Code-of-Conduct) if you are applying for a WESTPA collaboration project) +2. Agree to be bound by the **AI Policy of the project that you want to work with**, namely + - [MDAnalysis AI Policy](https://github.com/MDAnalysis/mdanalysis/blob/develop/AI_POLICY.md) + - [WESTPA AI Policy](https://github.com/westpa/westpa/blob/westpa2/AI_POLICY.md) + - MolecularNodes AI Policy (UPDATED POLICY WILL BE ADDED SOON, until then the [MDAnalysis AI Policy](https://github.com/MDAnalysis/mdanalysis/blob/develop/AI_POLICY.md) applies) +3. [Familiarize yourself with MDAnalysis and relevant partner projects](#familiarize-yourself-with-mdanalysis-and-relevant-partner-projects) and interact with the projects, e.g., through contributions of code and documentation, engage in discussion forums. +4. [Submit a short pre-proposal](#submit-a-pre-proposal) +5. **If you have been invited to proceed with your application (based on your pre-proposal)** [have a pull request merged](#have-a-pull-request-merged-by-invitation) in MDAnalysis or a partner organization. + +### Code of Conduct + +The MDAnalysis community values diversity and is committed to providing a +productive, harassment-free environment to every member. Our [Code of Conduct] +explains the values that we as a community uphold. *Every community member (and every +GSoC Contributor) agrees to follow the [Code of Conduct]*. + +### Familiarize yourself with MDAnalysis and relevant partner projects + +As a start to get familiar with MDAnalysis and open source development you +should follow these steps: +1. [Watch the MDAnalysis Trailer](#watch-the-mdanalysis-trailer) +2. [Complete the Quick Start Guide](#complete-the-quick-start-guide) +3. *If applicable to the [project idea](#project-ideas) you are interested in*, [learn more about WESTPA, Molecular Nodes, and/or ProLIF](#learn-more-about-westpa-molecular-nodes-and-prolif). + +#### Watch the MDAnalysis Trailer + +The [MDAnalysis Trailer](https://www.youtube.com/watch?v=uMAfvwFkD3o) on YouTube +is a one minute introduction to MDAnalysis. + +
+ +
+ +There are also additional [introductory videos]({{ site.baseurl }}/pages/learning_MDAnalysis/#introductory) available to give you an idea of what problems MDAnalysis is solving. + +#### Complete the Quick Start Guide + +Start by [installing] the MDAnalysis package. We have a [Quick Start Guide] explaining the basics of MDAnalysis. You +should go through it at least once to understand how MDAnalysis is +used. Continue reading the [User Guide] to learn more. + +#### Learn More About WESTPA, Molecular Nodes and ProLIF + +As some of the [project ideas][ideas] represent collaboration between MDAnalysis and other partner software projects, you should follow the recommended steps linked here to familiarize yourself (as relevant) with [WESTPA]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#westpa), [Molecular Nodes]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#molecular-nodes) and/or [ProLIF]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#prolif). + +### Submit a pre-proposal + +We ask you to submit a short *pre-proposal* so that we can evaluate your understanding of the proposed project. In this pre-proposal you tell us what project you’d like to work on, what you consider the major challenges, and how you plan to solve the problem. MDAnalysis developers will review your proposal and then either invite you to continue with your application and work on an issue to get involved in the code development or tell you that we will not consider your application. *Please note that this decision is final, and applicants should only submit **one** pre-proposal.* A rejection is not a judgment on you or your abilities but an assessment of how well you fit the specific requirements of MDAnalysis as a scientific software package — we much rather you spend your energies on contributing to another exciting GSoC project than being rejected later by MDAnalysis. + +**We require GSoC applicants to submit a pre-proposal** that will determine who is then invited to [contribute a pull request for evaluation](#have-a-pull-request-merged-by-invitation) (see below). If you are invited to contribute a pull request and ultimately submit a full application, the pre-proposal will help you gather some of the information you will need to include. + +Submit your pre-proposal via [this submission form][submission form] **as soon as possible, but no later than March 21, 2026**. You should prepare the following information for your pre-proposal: +* Email address +* GitHub handle +* Real name (optional) +* Basic information on your background (e.g., education, relevant experience with MDAnalysis and molecular dynamics or computational physics/chemistry/materials) +* Project title +* Project size (90h, 175h, 350h) +* **Problem:** Describe the problem to be solved. What is the background? What is the overarching question? You can also comment on why this is an interesting or difficult problem. Clearly define the overall goal of what you want to find out. +* **Approach:** Describe how you are going to reach your goal (i.e., answer the overarching question). Which algorithms are you going to use? Are there any libraries or other packages you want to use? Do you need to research different solutions? Be as concrete as possible; you want to convince your audience that it is feasible to solve this problem and you have an idea how to tackle it. +* **Objectives:** Use a numbered list to state 3–5 measurable non-trivial outcomes that you need to achieve in order to reach the overall goal. These are the milestones that you have to reach; they are possibly dependent on each other. For each objective it must be clear how to decide if you fulfilled it or not. Objectives are formulated in terms of actions and deliverables. + +### Have a pull request merged (*by invitation*) + +Based on your **pre-proposal** we may invite you to contribute a pull request. + +GSoC contributors with MDAnalysis will need to demonstrate that they have been seriously engaged with the MDAnalysis project and/or the partner software projects (WESTPA, Molecular Nodes, ProLIF) by **having a pull request (PR) merged *prior* to submitting their full GSoC application** on the [GSoC website][gsoc]. Submit the PR in one of the repositories under the [MDAnalysis org](https://github.com/MDAnalysis/) or, for projects related to Molecular Nodes (i.e., [Project 4]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#project-4-better-interfacing-of-blender-and-mdanalysis)) or ProLIF (i.e., [Project 5]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#project-5-hbond-interactions-from-implicit-hydrogens), [Project 6]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#project-6-continuous-ie-non-binary-interaction-fingerprints-ifps), [Project 7]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#project-7-improving-prolifs-2d-interaction-visualizations)), in the relevant repositories (MolecularNodes: [BradyAJohnston/MolecularNodes](https://github.com/BradyAJohnston/MolecularNodes), ProLIF: [chemosim-lab/ProLIF](https://github.com/chemosim-lab/ProLIF)). + +You must have *at least one commit* merged in one of the organizations to be eligible. Note that **the earlier you submit your pre-proposal (which are reviewed on a rolling basis), the more time you may have to work on having code merged!** + +We have a list of [easy bugs] and +suggested [GSOC Starter issues][GSOC Starter] to work on in our issue tracker +on GitHub. *We only accept one [GSOC Starter issue][GSOC Starter] per +applicant* so that all contributors invited to attempt pull requests get a chance. If you want to dive deeper, we encourage you to tackle some of the other issues in our issue tracker. We also appreciate contributions which add more tests or update/improve our documentation. Note that some of the [project ideas][ideas] include related issues that you might want to explore. + +To start developing for MDAnalysis have a look at our guide on +[contributing to MDAnalysis][dev-guide] and write to us on the [GSoC with MDAnalysis discussion forum][discussion forum] if you have more questions +about setting up a development environment or how to contribute. + +## Final remarks + +**Submit your pre-proposal before March 21, 2026**, but the earlier the better! We will then let you know via the email you provide in the [pre-proposal submission form][submission form] if you have been selected to attempt an issue on GitHub and ultimately submit a full application; we strive to inform you of a decision within a week of your submission. The GSoC contributor application period opens on March 24, 2026. + +Feel free to ask any questions on the [discussion forum]. We are also happy to chat on our [{{ site.discord.name }} Discord server][discord] in the `#gsoc` channel (join with the public [invitation link]({{ site.baseurl }}/#participating)). Please note that MDAnalysis as an organization highly values transparency and therefore we strive to *conduct all discussions in public forums* so please ask questions publicly and not via direct messages or emails. + +We look forward to working with you in GSoC 2026! + +— [MDAnalysis GSoC mentors and organization administrators]({{ site.github.wiki }}/Google-Summer-Of-Code#available-mentors) (GitHub [@MDAnalysis/gsoc-mentors], Discord `@gsoc-mentor`) + +[ideas]: {{ site.github.wiki }}/GSoC-2026-Project-Ideas +[submission form]: https://docs.google.com/forms/d/e/1FAIpQLSeOxd8b9MrHLtsQ6o8N7uq02P0CdyvyoWnQ1dhmJD_vW1Jh1w/viewform?usp=dialog +[org]: https://summerofcode.withgoogle.com/programs/2026/organizations/mdanalysis +[Code of Conduct]: {{ site.baseurl }}/conduct +[eligibility criteria]: https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation +[own requirements]: {{ site.github.wiki }}/Google-Summer-Of-Code#our-expectations-from-gsoc-contributors +[easy bugs]: https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3ADifficulty-easy +[GSOC Starter]: https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3A%22GSOC+Starter%22 +[installing]: https://userguide.mdanalysis.org/stable/installation.html +[Quick Start Guide]: https://userguide.mdanalysis.org/stable/examples/quickstart.html +[User Guide]: https://userguide.mdanalysis.org/ +[gsoc]: https://summerofcode.withgoogle.com/ +[dev-guide]: https://userguide.mdanalysis.org/stable/contributing.html +[discussion forum]: {{ site.mailinglists.gsoc.url }} +[GSoC FAQ]: {{ site.github.wiki }}/GSoC-FAQ +[@MDAnalysis/gsoc-mentors]: https://github.com/orgs/MDAnalysis/teams/gsoc-mentors +[discord]: {{ site.discord.url }} From 3a2e5f64c1c330b32f0ed3e71f8569a6f34c4617 Mon Sep 17 00:00:00 2001 From: Jenna M Swarthout Goddard <38287809+jennaswa@users.noreply.github.com> Date: Thu, 19 Feb 2026 12:08:59 -0700 Subject: [PATCH 02/10] draft GSOC 2026 post --- _posts/2026-02-19-gsoc2026.md | 102 ++++++++++++++++------------------ 1 file changed, 48 insertions(+), 54 deletions(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index e69ca252..b854ce64 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -1,7 +1,7 @@ ---- +— layout: post title: Google Summer of Code 2026 ---- +—

Date: Thu, 19 Feb 2026 12:26:48 -0700 Subject: [PATCH 03/10] add section on Full Proposal and added links to projects into wiki --- _posts/2026-02-19-gsoc2026.md | 30 +++++++++++++++++++----------- 1 file changed, 19 insertions(+), 11 deletions(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index b854ce64..a2b35638 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -46,12 +46,12 @@ This year, MDAnalysis is joining forces with two other open source projects to o | project | name | difficulty | project size | description | skills | mentors | |---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------------| -| 1 | [Dashboard for tracking MD simulation progress with the new streaming interface](#project-1-dashboard-for-tracking-md-simulation-progress-with-the-new-streaming-interface) | easy/medium | 175/350 hours | Create a web-based dashboard for real-time monitoring and analysis of MD simulations | Python (frontend UI, multiprocessing), Networking (TCP/IP) | [@HeydenLab](https://github.com/HeydenLab) [@amrutesht](https://github.com/amrutesht) [@orbeckst](https://github.com/orbeckst) | -| 2 | [Better interfacing of Blender and MDAnalysis](#project-2-better-interfacing-of-blender-and-mdanalysis) | medium | 350 hours | Improve how Blender and Molecular Nodes interface with MDAnalysis to import and animate MD trajectories | Python, MDAnalysis, Blender (and programming via its Python API) | [@bradyajohnston](https://github.com/bradyajohnston) [@nilay-v3rma](https://github.com/nilay-v3rma) | -| 3 | [Benchmarking and performance optimization](#project-3-benchmarking-and-performance-optimization) | easy/medium | 90/175/350 hours | Write benchmarks for automated performance analysis and address performance bottlenecks | Python/ASV, Cython | [@orbeckst](https://github.com/orbeckst) [@yuxuanzhuang](https://github.com/yuxuanzhuang) [@talagayev](https://github.com/talagayev) | -| 4 | [Lazy trajectory loading and indexing](#project-4-lazy-trajectory-loading-and-indexing) | medium | 175/350 hours | Improve performance of trajectory reading by implementing lazy indexing | Python, trajectory I/O, performance optimization | [@yuxuanzhuang](https://github.com/yuxuanzhuang) [@orbeckst](https://github.com/orbeckst) [@talagayev](https://github.com/talagayev) | -| 5 | [Dashboard for tracking WESTPA simulation progress](#project-5-dashboard-for-tracking-westpa-simulation-progress) | easy | 90 hours | Create a graphical user interface to report MD trajectory progress | Python (frontend UI, multiprocessing), Networking (TCP/IP) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) [@nilay-v3rma](https://github.com/nilay-v3rma) | -| 6 | [Interface for post-analysis analysis ("crawling") of WESTPA simulations](#project-6-interface-for-post-analysis-crawling-of-WESTPA-simulation) | easy | 90 hours | Create an interface for reading, analyzing, and writing post-simulation data from WESTPA HDF5 Framework | Python (frontend UI, multiprocessing), HDF5 Format (h5py, hdf5) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) | +| 1 | [Dashboard for tracking MD simulation progress with the new streaming interface](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-1-dashboard-for-tracking-md-simulation-progress-with-the-new-streaming-interface) | easy/medium | 175/350 hours | Create a web-based dashboard for real-time monitoring and analysis of MD simulations | Python (frontend UI, multiprocessing), Networking (TCP/IP) | [@HeydenLab](https://github.com/HeydenLab) [@amrutesht](https://github.com/amrutesht) [@orbeckst](https://github.com/orbeckst) | +| 2 | [Better interfacing of Blender and MDAnalysis](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-2-better-interfacing-of-blender-and-mdanalysis) | medium | 350 hours | Improve how Blender and Molecular Nodes interface with MDAnalysis to import and animate MD trajectories | Python, MDAnalysis, Blender (and programming via its Python API) | [@bradyajohnston](https://github.com/bradyajohnston) [@nilay-v3rma](https://github.com/nilay-v3rma) | +| 3 | [Benchmarking and performance optimization](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-3-benchmarking-and-performance-optimization) | easy/medium | 90/175/350 hours | Write benchmarks for automated performance analysis and address performance bottlenecks | Python/ASV, Cython | [@orbeckst](https://github.com/orbeckst) [@yuxuanzhuang](https://github.com/yuxuanzhuang) [@talagayev](https://github.com/talagayev) | +| 4 | [Lazy trajectory loading and indexing](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-4-lazy-trajectory-loading-and-indexing) | medium | 175/350 hours | Improve performance of trajectory reading by implementing lazy indexing | Python, trajectory I/O, performance optimization | [@yuxuanzhuang](https://github.com/yuxuanzhuang) [@orbeckst](https://github.com/orbeckst) [@talagayev](https://github.com/talagayev) | +| 5 | [Dashboard for tracking WESTPA simulation progress](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-5-dashboard-for-tracking-westpa-simulation-progress) | easy | 90 hours | Create a graphical user interface to report MD trajectory progress | Python (frontend UI, multiprocessing), Networking (TCP/IP) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) [@nilay-v3rma](https://github.com/nilay-v3rma) | +| 6 | [Interface for post-analysis analysis ("crawling") of WESTPA simulations](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-6-interface-for-post-analysis-crawling-of-WESTPA-simulation) | easy | 90 hours | Create an interface for reading, analyzing, and writing post-simulation data from WESTPA HDF5 Framework | Python (frontend UI, multiprocessing), HDF5 Format (h5py, hdf5) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) | ## Information for prospective GSoC Contributors @@ -80,7 +80,7 @@ As a start to get familiar with MDAnalysis and open source development you should follow these steps: 1. [Watch the MDAnalysis Trailer](#watch-the-mdanalysis-trailer) 2. [Complete the Quick Start Guide](#complete-the-quick-start-guide) -3. *If applicable to the [project idea](#project-ideas) you are interested in*, [learn more about WESTPA and/or Molecular Nodes (#learn-more-about-westpa-and-molecular-nodes). +3. *If applicable to the [project idea](#project-ideas) you are interested in*, [learn more about WESTPA and/or Molecular Nodes](#learn-more-about-westpa-and-molecular-nodes). #### Watch the MDAnalysis Trailer @@ -105,19 +105,19 @@ As some of the [project ideas][ideas] represent collaboration between MDAnalysis ### Interactions and engagement with MDAnalysis -GSoC contributors with MDAnalysis should demonstrate that they have been seriously engaged with the MDAnalysis project (and/or with a relevant [partner software project]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#collaborations). Submitting a pull request is a great way to know you as a good candidate. As is relevant to the [[GSoC project idea|GSoC 2026 Project Ideas]] you are interested in, you should submit your PR in one of the following repositories: +GSoC contributors with MDAnalysis should demonstrate that they have been seriously engaged with the MDAnalysis project (and/or with a relevant [partner software project]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#collaborations). Submitting a pull request is a great way to know you as a good candidate. As is relevant to the GSoC project idea you are interested in, you should submit your PR in one of the following repositories: * MDAnalysis organization (https://github.com/MDAnalysis/) * WESTPA organization (https://github.com/westpa/westpa/) * Molecular Nodes repository (https://github.com/BradyAJohnston/MolecularNodes) -We have a list of [easy bugs] and suggested [GSOC Starter issues] to work on in our issue tracker on GitHub. If you want to dive deeper, we encourage you to tackle some of the other issues in our issue tracker or create a new one. We also appreciate contributions which add more tests or update/improve our documentation. Note that some of the [[GSoC 2026 Project Ideas]] include related issues that you might want to explore. +We have a list of [easy bugs] and suggested [GSOC Starter issues] to work on in our issue tracker on GitHub. If you want to dive deeper, we encourage you to tackle some of the other issues in our issue tracker or create a new one. We also appreciate contributions which add more tests or update/improve our documentation. Note that some of the [GSoC 2026 Project Ideas][ideas] include related issues that you might want to explore. To start developing for MDAnalysis have a look at our guide on [contributing to MDAnalysis][dev-guide] and write to us on the [GSoC with MDAnalysis discussion forum][discussion forum] if you have more questions about setting up a development environment or how to contribute. ### Submit a pre-proposal -We ask you to submit a short *pre-proposal* so that we can evaluate your understanding of the proposed project. In this pre-proposal you tell us what project you’d like to work on, what you consider the major challenges, and how you plan to solve the problem. MDAnalysis developers will review your proposal and then either invite you to continue with your application and participate in a video interview or tell you that we will not consider your application. *Please note that this decision is final, and applicants should only submit **one** pre-proposal.* A rejection is not a judgment on you or your abilities but an assessment of how well you fit the specific requirements of MDAnalysis as a scientific software package — we much rather you spend your energies on contributing to another exciting GSoC project than being rejected later by MDAnalysis. +We ask you to submit a short **pre-proposal** so that we can evaluate your understanding of the proposed project. In this pre-proposal you tell us what project you’d like to work on, what you consider the major challenges, and how you plan to solve the problem. MDAnalysis developers will review your proposal and then either invite you to continue with your application and participate in a video interview or tell you that we will not consider your application. *Please note that this decision is final, and applicants should only submit **one** pre-proposal.* A rejection is not a judgment on you or your abilities but an assessment of how well you fit the specific requirements of MDAnalysis as a scientific software package — we much rather you spend your energies on contributing to another exciting GSoC project than being rejected later by MDAnalysis. **We require GSoC applicants to submit a pre-proposal** that will determine who is then invited to [participate in a video interview](#participate-in-a-video-interview-by-invitation) (see below). If you are invited to participate in an interview and ultimately submit a full application, the pre-proposal will help you gather some of the information you will need to include. @@ -137,7 +137,15 @@ Submit your pre-proposal via [this submission form][submission form] **as soon a Applicants who are invited for a video interview will be contacted no earlier than 72 hours after they submit their pre-proposal. During the interview (15 minutes), you will discuss your pre-proposal with 1-2 developers. The video may be recorded for evaluation by other developers/mentors. During the interview, you will be required to share your (full) screen and respond live to questions. The interview may involve live programing and discussions of code sections of MDAnalysis that are relevant for your project. The interview will be conducted using Google Chats or an equivalent video conferencing software. -### Final remarks +### Submit full proposal (*by invitation*) + +If you pass the interview stage, you will be invited to submit your full GSoC proposal through the GSoC site (starting March 16, 2026). We will only review invited proposals. + +Please read the additional information on our [expectations for a full proposal](https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#full-proposal). + + + +## Final remarks **Submit your pre-proposal before March 9, 2026**, but the earlier the better! We will then let you know via the email you provide in the [pre-proposal submission form][submission form] if you have been selected to participate in a video interview and ultimately submit a full application. The GSoC contributor application period opens on March 16, 2026. From 2f11af7d012da6fe7ecd030cc9dea72073369776 Mon Sep 17 00:00:00 2001 From: Oliver Beckstein Date: Thu, 19 Feb 2026 14:56:20 -0700 Subject: [PATCH 04/10] WESTPA related fixes Co-authored-by: Jeremy M. G. Leung <63817169+jeremyleung521@users.noreply.github.com> --- _posts/2026-02-19-gsoc2026.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index a2b35638..0c467097 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -51,7 +51,7 @@ This year, MDAnalysis is joining forces with two other open source projects to o | 3 | [Benchmarking and performance optimization](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-3-benchmarking-and-performance-optimization) | easy/medium | 90/175/350 hours | Write benchmarks for automated performance analysis and address performance bottlenecks | Python/ASV, Cython | [@orbeckst](https://github.com/orbeckst) [@yuxuanzhuang](https://github.com/yuxuanzhuang) [@talagayev](https://github.com/talagayev) | | 4 | [Lazy trajectory loading and indexing](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-4-lazy-trajectory-loading-and-indexing) | medium | 175/350 hours | Improve performance of trajectory reading by implementing lazy indexing | Python, trajectory I/O, performance optimization | [@yuxuanzhuang](https://github.com/yuxuanzhuang) [@orbeckst](https://github.com/orbeckst) [@talagayev](https://github.com/talagayev) | | 5 | [Dashboard for tracking WESTPA simulation progress](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-5-dashboard-for-tracking-westpa-simulation-progress) | easy | 90 hours | Create a graphical user interface to report MD trajectory progress | Python (frontend UI, multiprocessing), Networking (TCP/IP) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) [@nilay-v3rma](https://github.com/nilay-v3rma) | -| 6 | [Interface for post-analysis analysis ("crawling") of WESTPA simulations](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-6-interface-for-post-analysis-crawling-of-WESTPA-simulation) | easy | 90 hours | Create an interface for reading, analyzing, and writing post-simulation data from WESTPA HDF5 Framework | Python (frontend UI, multiprocessing), HDF5 Format (h5py, hdf5) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) | +| 6 | [Interface for post-simulation analysis ("crawling") of WESTPA simulations](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-6-interface-for-post-simulation-analysis-crawling-of-westpa-simulations) | easy | 90 hours | Create an interface for reading, analyzing, and writing post-simulation data from WESTPA HDF5 Framework | Python (frontend UI, multiprocessing), HDF5 Format (h5py, hdf5) | [@jeremyleung521](https://github.com/jeremyleung521) [@ltchong](https://github.com/ltchong) | ## Information for prospective GSoC Contributors @@ -60,7 +60,7 @@ Contributor with MDAnalysis this year (read all the docs behind these links!) and read the points below for the application process. You must also meet the [GSoC eligibility criteria][eligibility criteria]. [Our GSoC FAQ][GSoC FAQ] collects common questions from applicants. In short: -1. Agree to be bound by our [Code of Conduct](#code-of-conduct (and [WESTPA's Code of Conduct](https://github.com/westpa/westpa/wiki/Code-of-Conduct) if you are applying for a WESTPA collaboration project [i.e., [Project 5]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#project-5-dashboard-for-tracking-westpa-simulation-progress), [Project 6]({{ site.github.wiki}}/GSoC-2026-Project-Ideas#project-6-interface-for-post-analysis-analysis-crawling-of-westpa-simulations)]). +1. Agree to be bound by our [Code of Conduct](#code-of-conduct (and [WESTPA's Code of Conduct](https://github.com/westpa/westpa/wiki/Code-of-Conduct) if you are applying for a WESTPA collaboration project [i.e., [Project 5]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#project-5-dashboard-for-tracking-westpa-simulation-progress), [Project 6]({{ site.github.wiki}}/GSoC-2026-Project-Ideas#project-6-interface-for-post-simulation-analysis-crawling-of-westpa-simulations)]). 2. Agree to be bound by our [AI policy](https://github.com/MDAnalysis/mdanalysis/blob/develop/AI_POLICY.md) (and [WESTPA’s](https://github.com/westpa/westpa/blob/westpa2/AI_POLICY.md) or Molecular Node’s if you are applying for a collaboration project. 3. Engage with the MDAnalysis community through [code/documentation contributions](#interactions-and-engagement-with-mdanalysis) and discussions 4. [Familiarize yourself with MDAnalysis and relevant partner projects](#familiarize-yourself-with-mdanalysis-and-relevant-partner-projects); From ffbdf3a1e5e7ddc3e4235f36e8976e11dce04852 Mon Sep 17 00:00:00 2001 From: Oliver Beckstein Date: Thu, 19 Feb 2026 16:44:45 -0700 Subject: [PATCH 05/10] fix links and make timeline clearer --- _posts/2026-02-19-gsoc2026.md | 25 ++++++++++++++----------- 1 file changed, 14 insertions(+), 11 deletions(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index a2b35638..1f3777df 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -1,7 +1,7 @@ -— +--- layout: post title: Google Summer of Code 2026 -— +---

Date: Thu, 19 Feb 2026 17:55:22 -0700 Subject: [PATCH 06/10] highlight collaboration - extra Collaboration section at top - include WESTPA and MN logos --- _posts/2026-02-19-gsoc2026.md | 31 +++++++++++++++++++++++++++++-- 1 file changed, 29 insertions(+), 2 deletions(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index ac7270c5..97842dbf 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -27,6 +27,33 @@ duration can be extended from the standard 8 weeks to up to 12 weeks (for small Potential GSoC Contributors are expected to familiarize themselves with application requirements and mentoring organizations **as soon as possible**. If you are interested in working with us, please read on to learn about [MDAnalysis project ideas](#project-ideas) and [MDAnalysis-specific requirements for putting together your application](#information-for-prospective-gsoc-contributors). +## Partner Projects + +

+ + + + + + +

+ +For GSOC, MDAnalysis collaborates with other projects that have direct links with MDAnalysis and where it is especially useful to draw on the combined mentoring expertise. + +This year, MDAnalysis is joining forces with [WESTPA]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#westpa) and [Molecular Nodes]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#molecular-nodes). Applicants who want to work with one of the collaborating projects should familiarize themselves with MDAnalysis and the project that they are interested in. GSoC projects with either WESTPA or Molecular Nodes will be mentored by experts from the collaborating project and MDAnalysis. + + + ## Project Ideas If you have your own idea about a potential project we'd love to work with you @@ -42,7 +69,6 @@ Our experience shows that having the listed skills increases the chances that a project will be completed successfully, so we use them as part of [our decision criteria in choosing GSoC contributors](https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-Proposal-Review). -This year, MDAnalysis is joining forces with two other open source projects to offer even more far-reaching collaborative projects: [WESTPA]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#westpa) and [Molecular Nodes]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#molecular-nodes). | project | name | difficulty | project size | description | skills | mentors | |---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------------| @@ -123,10 +149,11 @@ We ask you to submit a short **pre-proposal** so that we can evaluate your under **We require GSoC applicants to submit a pre-proposal** that will determine who is then invited to [participate in a video interview](#participate-in-a-video-interview-by-invitation) (see below). If you are invited to participate in an interview and ultimately submit a full application, the pre-proposal will help you gather some of the information you will need to include. -Submit your pre-proposal via [this submission form][submission form] **as soon as possible, but no later than March 9, 2026**. You should prepare the following information for your pre-proposal: +Submit your pre-proposal via our [pre-proposal submission form][submission form] **as soon as possible, but no later than March 9, 2026**. You should prepare the following information for your pre-proposal: * Email address * GitHub handle * Real name (optional) +* Certify that you did not use AI tools to develop or produce the pre-proposal. * Basic information on your background (e.g., education, relevant experience with MDAnalysis and molecular dynamics or computational physics/chemistry/materials) * Project title * Project size (90h, 175h, 350h) From e9359fbdb086ce1de4928a1639ee1b67224c5776 Mon Sep 17 00:00:00 2001 From: Oliver Beckstein Date: Thu, 19 Feb 2026 18:09:08 -0700 Subject: [PATCH 07/10] add explicit NO AI for proposals --- _posts/2026-02-19-gsoc2026.md | 24 +++++++++++++++++++++--- 1 file changed, 21 insertions(+), 3 deletions(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index 97842dbf..6bc11590 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -90,7 +90,7 @@ In short: 2. Agree to be bound by our [AI policy](https://github.com/MDAnalysis/mdanalysis/blob/develop/AI_POLICY.md) (and [WESTPA's AI policy](https://github.com/westpa/westpa/blob/westpa2/AI_POLICY.md) or Molecular Node’s AI policy if you are applying for a collaboration project). 3. Engage with the MDAnalysis community through [code/documentation contributions](#interactions-and-engagement-with-mdanalysis) and discussions 4. [Familiarize yourself with MDAnalysis and relevant partner projects](#familiarize-yourself-with-mdanalysis-and-relevant-partner-projects); -5. Submit a short **[pre-proposal](#submit-a-pre-proposal)** as soon as possible, but no later than March 9, 2026. +5. Submit a short **[pre-proposal](#submit-a-pre-proposal)** by **March 9, 2026**. 6. Participate in a **[video interview](#participate-in-a-video-interview-by-invitation)** with developers of MDAnalysis and/or one of the partner organizations. You will be **invited for interview based on your pre-proposal**. 7. Submit your full **[GSoC proposal](#submit-full-proposal-by-invitation)**. You will be **invited to submit your proposal based on your video interview**. @@ -147,9 +147,19 @@ To start developing for MDAnalysis have a look at our guide on We ask you to submit a short **pre-proposal** so that we can evaluate your understanding of the proposed project. In this pre-proposal you tell us what project you’d like to work on, what you consider the major challenges, and how you plan to solve the problem. MDAnalysis developers will review your proposal and then either invite you to continue with your application and participate in a video interview or tell you that we will not consider your application. *Please note that this decision is final, and applicants should only submit **one** pre-proposal.* A rejection is not a judgment on you or your abilities but an assessment of how well you fit the specific requirements of MDAnalysis as a scientific software package — we much rather you spend your energies on contributing to another exciting GSoC project than being rejected later by MDAnalysis. -**We require GSoC applicants to submit a pre-proposal** that will determine who is then invited to [participate in a video interview](#participate-in-a-video-interview-by-invitation) (see below). If you are invited to participate in an interview and ultimately submit a full application, the pre-proposal will help you gather some of the information you will need to include. +**We require GSoC applicants to submit a pre-proposal** that will determine who is then invited to [participate in a video interview](#participate-in-a-video-interview-by-invitation). If you are invited to participate in an interview and ultimately submit a full application, the pre-proposal will help you gather some of the information you will need to include. -Submit your pre-proposal via our [pre-proposal submission form][submission form] **as soon as possible, but no later than March 9, 2026**. You should prepare the following information for your pre-proposal: +Submit your pre-proposal via our [pre-proposal submission form][submission form] **by March 9, 2026**. The submission form will go live a few days after this post. + +
+

+ Do not use generative AI to develop or write your pre-proposal. We need to hear your ideas and voice. +

+

You are allowed to use AI tools for grammar and spell checking and for translation into English although we are more than happy to read your proposal in your own English words.

+
+ + +You should prepare the following information for your pre-proposal: * Email address * GitHub handle * Real name (optional) @@ -172,6 +182,14 @@ If you pass the interview stage, you will be invited to submit your full GSoC pr Please read the additional information on our [expectations for a full proposal](https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#full-proposal). +
+

+ Do not use generative AI to develop or write your proposal. We need to hear your ideas and voice. +

+

You are allowed to use AI tools for grammar and spell checking and for translation into English although we are more than happy to read your proposal in your own English words.

+
+ + ## Final remarks From ab60f51d86370855721e045e6c10221b2fc69241 Mon Sep 17 00:00:00 2001 From: Oliver Beckstein Date: Thu, 19 Feb 2026 18:17:08 -0700 Subject: [PATCH 08/10] make clear: no AI in proposals --- _posts/2026-02-19-gsoc2026.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index 6bc11590..935a0eea 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -152,8 +152,7 @@ We ask you to submit a short **pre-proposal** so that we can evaluate your under Submit your pre-proposal via our [pre-proposal submission form][submission form] **by March 9, 2026**. The submission form will go live a few days after this post.
-

- Do not use generative AI to develop or write your pre-proposal. We need to hear your ideas and voice. +

❗Do not use generative AI to develop or write your pre-proposal. We need to hear your ideas and voice.

You are allowed to use AI tools for grammar and spell checking and for translation into English although we are more than happy to read your proposal in your own English words.

@@ -183,8 +182,7 @@ If you pass the interview stage, you will be invited to submit your full GSoC pr Please read the additional information on our [expectations for a full proposal](https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#full-proposal).
-

- Do not use generative AI to develop or write your proposal. We need to hear your ideas and voice. +

❗Do not use generative AI to develop or write your proposal. We need to hear your ideas and voice.

You are allowed to use AI tools for grammar and spell checking and for translation into English although we are more than happy to read your proposal in your own English words.

From 22f59ab566112ce0e2420ee7e97bbc71f755356f Mon Sep 17 00:00:00 2001 From: Oliver Beckstein Date: Fri, 20 Feb 2026 07:52:32 -0700 Subject: [PATCH 09/10] changed "full proposal" to "full application" - use same language as GSOC and distinguish from pre-proposal - also updated wiki page so that links work --- _posts/2026-02-19-gsoc2026.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index 935a0eea..4a8f0e29 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -92,7 +92,7 @@ In short: 4. [Familiarize yourself with MDAnalysis and relevant partner projects](#familiarize-yourself-with-mdanalysis-and-relevant-partner-projects); 5. Submit a short **[pre-proposal](#submit-a-pre-proposal)** by **March 9, 2026**. 6. Participate in a **[video interview](#participate-in-a-video-interview-by-invitation)** with developers of MDAnalysis and/or one of the partner organizations. You will be **invited for interview based on your pre-proposal**. -7. Submit your full **[GSoC proposal](#submit-full-proposal-by-invitation)**. You will be **invited to submit your proposal based on your video interview**. +7. Submit your full **[GSoC application](#submit-full-application-by-invitation)**. You will be **invited to submit your application based on your video interview**. ### Code of Conduct @@ -175,16 +175,16 @@ You should prepare the following information for your pre-proposal: Applicants who are invited for a video interview will be contacted no earlier than 72 hours after they submit their pre-proposal. During the interview (15 minutes), you will discuss your pre-proposal with 1-2 developers. The video may be recorded for evaluation by other developers/mentors. During the interview, you will be required to share your (full) screen and respond live to questions. The interview may involve live programing and discussions of code sections of MDAnalysis that are relevant for your project. The interview will be conducted using Google Chats or an equivalent video conferencing software. -### Submit full proposal (*by invitation*) +### Submit full application (*by invitation*) -If you pass the interview stage, you will be invited to submit your full GSoC proposal through the GSoC site (starting March 16, 2026). We will only review invited proposals. +If you pass the interview stage, you will be invited to submit your full GSoC application through the GSoC site (starting March 16, 2026). We will only review invited applications. -Please read the additional information on our [expectations for a full proposal](https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#full-proposal). +Please read the additional information on our [expectations for a full application](https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#full-application).
-

❗Do not use generative AI to develop or write your proposal. We need to hear your ideas and voice. +

❗Do not use generative AI to develop or write your application. We need to hear your ideas and voice.

-

You are allowed to use AI tools for grammar and spell checking and for translation into English although we are more than happy to read your proposal in your own English words.

+

You are allowed to use AI tools for grammar and spell checking and for translation into English although we are more than happy to read your application in your own English words.

From 069b381319a8de0571e272f9cc659043f15cdf14 Mon Sep 17 00:00:00 2001 From: Irfan Alibay Date: Fri, 20 Feb 2026 19:01:26 +0000 Subject: [PATCH 10/10] Update _posts/2026-02-19-gsoc2026.md --- _posts/2026-02-19-gsoc2026.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2026-02-19-gsoc2026.md b/_posts/2026-02-19-gsoc2026.md index 4a8f0e29..6152fdb6 100644 --- a/_posts/2026-02-19-gsoc2026.md +++ b/_posts/2026-02-19-gsoc2026.md @@ -48,7 +48,7 @@ alt="Molecular Nodes logo" style="float: right; height: 5em; " />

-For GSOC, MDAnalysis collaborates with other projects that have direct links with MDAnalysis and where it is especially useful to draw on the combined mentoring expertise. +For GSoC, MDAnalysis collaborates with other projects that have direct links with MDAnalysis and where it is especially useful to draw on the combined mentoring expertise. This year, MDAnalysis is joining forces with [WESTPA]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#westpa) and [Molecular Nodes]({{ site.github.wiki }}/GSoC-2026-Project-Ideas#molecular-nodes). Applicants who want to work with one of the collaborating projects should familiarize themselves with MDAnalysis and the project that they are interested in. GSoC projects with either WESTPA or Molecular Nodes will be mentored by experts from the collaborating project and MDAnalysis.