<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://www.mdanalysis.org/atom.xml" rel="self" type="application/atom+xml" /><link href="https://www.mdanalysis.org/" rel="alternate" type="text/html" /><updated>2026-05-22T23:04:34+00:00</updated><id>https://www.mdanalysis.org/atom.xml</id><title type="html">MDAnalysis</title><subtitle>working with data in the molecular sciences</subtitle><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><entry><title type="html">Google Summer of Code Students 2026</title><link href="https://www.mdanalysis.org/2026/05/21/gsoc-students/" rel="alternate" type="text/html" title="Google Summer of Code Students 2026" /><published>2026-05-21T00:00:00+00:00</published><updated>2026-05-21T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2026/05/21/gsoc-students</id><content type="html" xml:base="https://www.mdanalysis.org/2026/05/21/gsoc-students/"><![CDATA[<p>We’re excited to welcome <em>three</em> contributors to MDAnalysis through <a href="https://summerofcode.withgoogle.com">Google Summer of Code</a> this year:
@jauy123, @kunjsinha, and @PardhavMaradani.</p>

<p>This marks our seventh consecutive year participating as an independent <a href="https://summerofcode.withgoogle.com/programs/2026/organizations/mdanalysis">GSoC organization</a>.
A big thank you goes out to Google for supporting these <em>three</em> exciting projects.
We’re looking forward to getting started!</p>

<h2 id="kunj-sinha-interface-for-post-simulation-analysis-crawling-of-westpa-simulations-">Kunj Sinha: <a href="https://summerofcode.withgoogle.com/programs/2026/projects/VJMrp2UW">Interface for post-simulation analysis (“crawling”) of WESTPA simulations </a></h2>

<p><img src="https://avatars.githubusercontent.com/kunjsinha" title="Kunj Sinha" alt="Kunj Sinha" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>This project will implement WESTPAParser and WESTPAReader inside <a href="https://github.com/westpa/westpa">westpa/westpa</a>, exposing <a href="https://westpa.readthedocs.io/en/latest/users_guide/hdf5.html">WESTPA’s HDF5 Framework</a> simulation data as a standard <a href="https://userguide.mdanalysis.org/stable/universe.html">MDAnalysis Universe</a>. Post-simulation analysis currently requires custom boilerplate code via <a href="https://westpa.readthedocs.io/en/latest/users_guide/command_line_tools/w_crawl.html">w_crawl</a> which this project will replace with a single command, making the entire MDAnalysis toolkit accessible on WESTPA data.</p>

<p>Kunj is an undergraduate student at PES University, pursuing a Bachelor of Technology in Computer Science and Engineering. He has always had an interest in various fields of science and technology since his early school days. In his free time, he listens to music, plays different musical instruments and enjoys cooking as well.</p>

<p>You can find Kunj on <a href="https://github.com/kunjsinha">Github</a> and <a href="https://www.linkedin.com/in/kunjsinha">LinkedIn</a>.</p>

<p>To keep up with his work, you can check out his <a href="https://kunjsinha.github.io/blog">blog</a>.</p>

<h2 id="pardhav-maradani-dashboard-for-tracking-md-simulation-progress-with-the-new-streaming-interface">Pardhav Maradani: <a href="https://summerofcode.withgoogle.com/programs/2026/projects/DzTMshtu">Dashboard for tracking MD simulation progress with the new streaming interface</a></h2>

<p><img src="https://avatars.githubusercontent.com/pardhavmaradani" title="Pardhav Maradani" alt="Pardhav Maradani" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>This project will develop a browser-based, real-time dashboard for molecular dynamics simulations using the new IMDv3 streaming protocol, enabling live monitoring, analysis, and visualization of running simulations. The dashboard will leverage <a href="https://imdclient.readthedocs.io/">imdclient</a> and MDAnalysis to receive and analyze data streams from running simulations.</p>

<p>Pardhav is an undergraduate student from India pursuing a Bachelors in Computer Science and Engineering from Vellore Institute of Technology (Vellore) and a BS in Data Science and Applications from Indian Institute of Technology (IIT) Madras.</p>

<p>You can find Pardhav on GitHub <a href="https://github.com/PardhavMaradani">@PardhavMaradani</a>.</p>

<p>To see updates on this project, you can check out his <a href="https://pardhavmaradani.github.io/categories/gsoc-2026/">blog</a>.</p>

<h2 id="josh-uy-adding-additional-functionality-and-enhancements-to-the-fetcher-module">Josh Uy: <a href="https://summerofcode.withgoogle.com/programs/2026/projects/Jz9S7jxP">Adding Additional Functionality and Enhancements to the Fetcher Module</a></h2>

<p><img src="/public/images/joshuy.jpg" title="Josh Uy" alt="Josh Uy" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>This project intends to add web retrieval functionality to MDAnalysis by augmenting the existing fetcher module. By introducing new fetchers,
it is intended to allow MDAnalysis to download structures and trajectories from external databases such as <a href="https://alphafold.ebi.ac.uk/">AlphaFold</a> and the <a href="https://mddbr.eu/">Molecular Dynamics Data Bank</a> by passing downloaded data to the in-built <a href="https://userguide.mdanalysis.org/stable/universe.html">Universe</a> class. Additionally, this project intends to introduce a new suite of functions that is capable of retrieving any molecular data from any database supporting REST API.</p>

<p>Joshua Raphael Uy is a Physics Ph.D student at Arizona State University. He earned a Bachelor of Science in Physics, a Bachelor of Arts in
Mathematics at Miami University in Oxford, Ohio, and a Master in Science in Physics at Arizona State University. He has a <a href="https://becksteinlab.physics.asu.edu/people/155/joshua-raphael-uy">bio page</a> and a <a href="https://www.linkedin.com/in/joshua-raphael-uy-9540a0202">Linkedin</a>.</p>

<p>To follow this project, you can check out Josh’s <a href="https://jauy123.github.io/">blog</a>.</p>

<p>— @amruthesht @BradyAJohnston @HeydenLabASU @jeremyleung521 @ltchong @nilay-v3rma @orbeckst @talagayev @yuxuanzhuang @IAlibay @jennaswa (@MDAnalysis/gsoc-mentors and org admins)</p>]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[We’re excited to welcome three contributors to MDAnalysis through Google Summer of Code this year: @jauy123, @kunjsinha, and @PardhavMaradani.]]></summary></entry><entry><title type="html">Google Summer of Code 2026</title><link href="https://www.mdanalysis.org/2026/02/19/gsoc2026/" rel="alternate" type="text/html" title="Google Summer of Code 2026" /><published>2026-02-19T00:00:00+00:00</published><updated>2026-02-19T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2026/02/19/gsoc2026</id><content type="html" xml:base="https://www.mdanalysis.org/2026/02/19/gsoc2026/"><![CDATA[<p>
<img src="https://developers.google.com/open-source/gsoc/resources/downloads/GSoC-Vertical.svg" title="Google Summer of Code 2026" alt="Google Summer of Code with
MDAnalysis 2026" style="float: right; height: 10em; " />
</p>

<p>MDAnalysis has been accepted as an <a href="https://summerofcode.withgoogle.com/programs/2026/organizations/mdanalysis">organization</a> for <a href="https://summerofcode.withgoogle.com/">Google Summer of
Code</a> (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.</p>

<p>The application window <strong>deadline</strong> is <strong>March 31, 2026 - 18:00 UTC</strong>.
As part of the application process you must familiarize
yourself with <a href="https://summerofcode.withgoogle.com/">Google Summer of Code 2026</a>, including eligibility requirements, timelines, and generally how the program works.</p>

<p>We are looking forward to all applications from <em>any new and beginner
open source contributors or students over 18 years old</em>; see a full list of the <a href="https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation">eligibility requirements</a> in the <a href="https://developers.google.com/open-source/gsoc/faq">GSoC FAQ</a>. 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).</p>

<p>Potential GSoC Contributors are expected to familiarize themselves with application
requirements and mentoring organizations <strong>as soon as possible</strong>. If you are interested in working with us, please read on to learn about <a href="#project-ideas">MDAnalysis project ideas</a> and <a href="#information-for-prospective-gsoc-contributors">MDAnalysis-specific requirements for putting together your application</a>.</p>

<h2 id="partner-projects">Partner Projects</h2>

<p>
<a href="/">
<img src="/public/mdanalysis-logo_square.png" style="float: right; height: 5em;" title="MDAnalysis" alt="MDAnalysis logo" /></a>

<a href="https://westpa.github.io/westpa/"><img src="https://westpa.readthedocs.io/en/latest/_static/WESTPA2b.svg" title="WESTPA" alt="WESTPA logo" style="float: right; height: 5em; " /></a>

<a href="https://bradyajohnston.github.io/MolecularNodes/"><img src="https://bradyajohnston.github.io/MolecularNodes/images/logo.png" title="Molecular Nodes" alt="Molecular Nodes logo" style="float: right; height: 5em; " /></a>
</p>

<p>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.</p>

<p>This year, MDAnalysis is joining forces with <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#westpa">WESTPA</a> and <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#molecular-nodes">Molecular Nodes</a>. 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.</p>

<h2 id="project-ideas">Project Ideas</h2>

<p>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 <a href="https://github.com/MDAnalysis/mdanalysis/discussions/categories/gsoc-discussions">GSoC with MDAnalysis discussion forum</a> to discuss it there.</p>

<p>We also have listed several <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas">possible projects</a> 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 <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas">ideas</a> page — we might add more ideas after the posting date of
this post.</p>

<p>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 <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-Proposal-Review">our decision criteria in choosing GSoC contributors</a>.</p>

<table>
  <thead>
    <tr>
      <th>project</th>
      <th>name</th>
      <th>difficulty</th>
      <th>project size</th>
      <th>description</th>
      <th>skills</th>
      <th>mentors</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>1</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-1-dashboard-for-tracking-md-simulation-progress-with-the-new-streaming-interface">Dashboard for tracking MD simulation progress with the new streaming interface</a></td>
      <td>easy/medium</td>
      <td>175/350 hours</td>
      <td>Create a web-based dashboard for real-time monitoring and analysis of MD simulations</td>
      <td>Python (frontend UI, multiprocessing), Networking (TCP/IP)</td>
      <td><a href="https://github.com/HeydenLab">@HeydenLab</a> <a href="https://github.com/amrutesht">@amrutesht</a> <a href="https://github.com/orbeckst">@orbeckst</a></td>
    </tr>
    <tr>
      <td>2</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-2-better-interfacing-of-blender-and-mdanalysis">Better interfacing of Blender and MDAnalysis</a></td>
      <td>medium</td>
      <td>350 hours</td>
      <td>Improve how Blender and Molecular Nodes interface with MDAnalysis to import and animate MD trajectories</td>
      <td>Python, MDAnalysis, Blender (and programming via its Python API)</td>
      <td><a href="https://github.com/bradyajohnston">@bradyajohnston</a> <a href="https://github.com/nilay-v3rma">@nilay-v3rma</a></td>
    </tr>
    <tr>
      <td>3</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-3-benchmarking-and-performance-optimization">Benchmarking and performance optimization</a></td>
      <td>easy/medium</td>
      <td>90/175/350 hours</td>
      <td>Write benchmarks for automated performance analysis and address performance bottlenecks</td>
      <td>Python/ASV, Cython</td>
      <td><a href="https://github.com/orbeckst">@orbeckst</a> <a href="https://github.com/yuxuanzhuang">@yuxuanzhuang</a> <a href="https://github.com/talagayev">@talagayev</a></td>
    </tr>
    <tr>
      <td>4</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-4-lazy-trajectory-loading-and-indexing">Lazy trajectory loading and indexing</a></td>
      <td>medium</td>
      <td>175/350 hours</td>
      <td>Improve performance of trajectory reading by implementing lazy indexing</td>
      <td>Python, trajectory I/O, performance optimization</td>
      <td><a href="https://github.com/yuxuanzhuang">@yuxuanzhuang</a> <a href="https://github.com/orbeckst">@orbeckst</a> <a href="https://github.com/talagayev">@talagayev</a></td>
    </tr>
    <tr>
      <td>5</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-5-dashboard-for-tracking-westpa-simulation-progress">Dashboard for tracking WESTPA simulation progress</a></td>
      <td>easy</td>
      <td>90 hours</td>
      <td>Create a graphical user interface to report MD trajectory progress</td>
      <td>Python (frontend UI, multiprocessing), Networking (TCP/IP)</td>
      <td><a href="https://github.com/jeremyleung521">@jeremyleung521</a> <a href="https://github.com/ltchong">@ltchong</a> <a href="https://github.com/nilay-v3rma">@nilay-v3rma</a></td>
    </tr>
    <tr>
      <td>6</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-6-interface-for-post-simulation-analysis-crawling-of-westpa-simulations">Interface for post-simulation analysis (“crawling”) of WESTPA simulations</a></td>
      <td>easy</td>
      <td>90 hours</td>
      <td>Create an interface for reading, analyzing, and writing post-simulation data from WESTPA HDF5 Framework</td>
      <td>Python (frontend UI, multiprocessing), HDF5 Format (h5py, hdf5)</td>
      <td><a href="https://github.com/jeremyleung521">@jeremyleung521</a> <a href="https://github.com/ltchong">@ltchong</a></td>
    </tr>
  </tbody>
</table>

<h2 id="information-for-prospective-gsoc-contributors">Information for prospective GSoC Contributors</h2>

<p>You must meet our <a href="https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#our-expectations-from-gsoc-contributors">own requirements</a> 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 <a href="https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation">GSoC eligibility criteria</a>. <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-FAQ">Our GSoC FAQ</a> collects common questions from applicants.</p>

<p>In short:</p>
<ol>
  <li>Agree to be bound by our <a href="#code-of-conduct">Code of Conduct</a> (and the <a href="https://github.com/westpa/westpa/wiki/Code-of-Conduct">WESTPA Code of Conduct</a> if you are applying for a WESTPA collaboration project [i.e., <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-5-dashboard-for-tracking-westpa-simulation-progress">Project 5</a>, <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#project-6-interface-for-post-simulation-analysis-crawling-of-westpa-simulations">Project 6</a>])</li>
  <li>Agree to be bound by our <a href="https://github.com/MDAnalysis/mdanalysis/blob/develop/AI_POLICY.md">AI policy</a> (and <a href="https://github.com/westpa/westpa/blob/westpa2/AI_POLICY.md">WESTPA’s AI policy</a> or Molecular Node’s AI policy if you are applying for a collaboration project).</li>
  <li><a href="#familiarize-yourself-with-mdanalysis-and-relevant-partner-projects">Familiarize yourself with MDAnalysis and relevant partner projects</a>;</li>
  <li>Engage with the MDAnalysis community through <a href="#interactions-and-engagement-with-mdanalysis">code/documentation contributions</a> and discussions</li>
  <li>Submit a short <strong><a href="#submit-a-pre-proposal">pre-proposal</a></strong> by <strong>March 9, 2026</strong>.</li>
  <li>Participate in a <strong><a href="#participate-in-a-video-interview-by-invitation">video interview</a></strong> with developers of MDAnalysis and/or one of the partner organizations. You will be <strong>invited for interview based on your pre-proposal</strong>.</li>
  <li>Submit your full <strong><a href="#submit-full-application-by-invitation">GSoC application</a></strong>. You will be <strong>invited to submit your application based on your video interview</strong>.</li>
</ol>

<h3 id="code-of-conduct">Code of Conduct</h3>

<p>The MDAnalysis community values diversity and is committed to providing a
productive, harassment-free environment to every member. Our <a href="/conduct">Code of Conduct</a>
explains the values that we as a community uphold. <em>Every community member (and every
GSoC Contributor) agrees to follow the <a href="/conduct">Code of Conduct</a></em>.</p>

<h3 id="familiarize-yourself-with-mdanalysis-and-relevant-partner-projects">Familiarize yourself with MDAnalysis and relevant partner projects</h3>

<p>As a start to get familiar with MDAnalysis and open source development you
should follow these steps:</p>
<ol>
  <li><a href="#watch-the-mdanalysis-trailer">Watch the MDAnalysis Trailer</a></li>
  <li><a href="#complete-the-quick-start-guide">Complete the Quick Start Guide</a></li>
  <li><em>If applicable to the <a href="#project-ideas">project idea</a> you are interested in</em>, <a href="#learn-more-about-westpa-and-molecular-nodes">learn more about WESTPA and/or Molecular Nodes</a>.</li>
</ol>

<h4 id="watch-the-mdanalysis-trailer">Watch the MDAnalysis Trailer</h4>

<p>The <a href="https://www.youtube.com/watch?v=uMAfvwFkD3o">MDAnalysis Trailer</a> on YouTube
is a one minute introduction to MDAnalysis.</p>

<div class="js-video">
	<iframe src="https://www.youtube.com/embed/uMAfvwFkD3o" frameborder="0" allowfullscreen="" class="video"></iframe>
</div>

<p>There are also additional <a href="/pages/learning_MDAnalysis/#introductory">introductory videos</a> available to give you an idea of what problems MDAnalysis is solving.</p>

<h4 id="complete-the-quick-start-guide">Complete the Quick Start Guide</h4>

<p>Start by <a href="https://userguide.mdanalysis.org/stable/installation.html">installing</a> the MDAnalysis package. We have a <a href="https://userguide.mdanalysis.org/stable/examples/quickstart.html">Quick Start Guide</a> explaining the basics of MDAnalysis. You should go through it at least once to understand how MDAnalysis is
used. Continue reading the <a href="https://userguide.mdanalysis.org/">User Guide</a> to learn more.</p>

<h4 id="learn-more-about-westpa-and-molecular-nodes">Learn More About WESTPA and Molecular Nodes</h4>

<p>As some of the <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas">project ideas</a> represent collaboration between MDAnalysis and other partner software projects, you should follow the recommended steps linked here to familiarize yourself (as relevant) with <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#westpa">WESTPA</a> and/or <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#molecular-nodes">Molecular Nodes</a>.</p>

<h3 id="interactions-and-engagement-with-mdanalysis">Interactions and engagement with MDAnalysis</h3>

<p>GSoC contributors with MDAnalysis should demonstrate that they have been seriously engaged with the MDAnalysis project (and/or with a relevant <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas#collaborations">partner software project</a>). 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:</p>
<ul>
  <li>MDAnalysis organization:  <a href="https://github.com/MDAnalysis/">github.com/MDAnalysis/</a></li>
  <li>WESTPA organization: <a href="https://github.com/westpa/westpa/">github.com/westpa/westpa</a></li>
  <li>Molecular Nodes repository: <a href="https://github.com/BradyAJohnston/MolecularNodes">github.com/BradyAJohnston/MolecularNodes</a></li>
</ul>

<p>We have a list of <a href="https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3ADifficulty-easy">easy bugs</a> and suggested <a href="https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3A%22GSOC+Starter%22">GSOC Starter issues</a> 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 <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2026-Project-Ideas">GSoC 2026 Project Ideas</a> include related issues that you might want to explore.</p>

<p>To start developing for MDAnalysis have a look at our guide on
<a href="https://userguide.mdanalysis.org/stable/contributing.html">contributing to MDAnalysis</a> and write to us on the <a href="https://github.com/MDAnalysis/mdanalysis/discussions/categories/gsoc-discussions">GSoC with MDAnalysis discussion forum</a> if you have more questions about setting up a development environment or how to contribute.</p>

<h3 id="submit-a-pre-proposal">Submit a pre-proposal</h3>

<p>We ask you to submit a short <strong>pre-proposal</strong> 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. <em>Please note that this decision is final, and applicants should only submit <strong>one</strong> pre-proposal.</em> 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.</p>

<p><strong>We require GSoC applicants to submit a pre-proposal</strong> that will determine who is then invited to <a href="#participate-in-a-video-interview-by-invitation">participate in a video interview</a>. 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.</p>

<p>Submit your pre-proposal via our <a href="https://docs.google.com/forms/d/e/1FAIpQLSecYgZDLxSKHkHt0vSVwcfInDPG46xyHxb2XBIKl_KjZUHF4A/viewform?usp=publish-editor">pre-proposal submission form</a> <strong>by March 9, 2026</strong>. The submission form <del>will go live a few days after this post</del> is available from Feb 28, 2026.</p>

<div style="border: 1px solid #F00; padding: 10px; margin: 10px 0;">
    <p>❗<strong>Do not use generative AI</strong> to <strong>develop or write</strong> your pre-proposal. We need to hear <em>your</em> ideas and voice.
	</p>
	<p><small>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.</small></p>
</div>

<p>You should prepare the following information for your pre-proposal:</p>
<ul>
  <li>Email address</li>
  <li>GitHub handle</li>
  <li>Real name (optional)</li>
  <li>Certify that you did not use AI tools to develop or produce the pre-proposal.</li>
  <li>Basic information on your background (e.g., education, relevant experience with MDAnalysis and molecular dynamics or computational physics/chemistry/materials)</li>
  <li>Project title</li>
  <li>Project size (90h, 175h, 350h)</li>
  <li><strong>Problem:</strong> 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.</li>
  <li><strong>Approach:</strong> 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.</li>
  <li><strong>Objectives:</strong> 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.</li>
  <li><strong>Interactions:</strong> Describe the interactions you had with maintainers from MDAnalysis (or WESTPA/Molecular Nodes if you plan on working on a collaborative project). Be specific and link to specific instances of interactions (e.g. Pull Requests) if possible. (500 words)</li>
</ul>

<h3 id="participate-in-a-video-interview-by-invitation">Participate in a video interview (<em>by invitation</em>)</h3>

<p>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.</p>

<h3 id="submit-full-application-by-invitation">Submit full application (<em>by invitation</em>)</h3>

<p>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.</p>

<p>Please read the additional information on our <a href="https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#full-application">expectations for a full application</a>.</p>

<div style="border: 1px solid #F00; padding: 10px; margin: 10px 0;">
    <p>❗<strong>Do not use generative AI</strong> to <strong>develop or write</strong> your application. We need to hear <em>your</em> ideas and voice.
	</p>
	<p><small>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.</small></p>
</div>

<h2 id="final-remarks">Final remarks</h2>

<p><strong>Submit your pre-proposal before March 9, 2026</strong>, but the earlier the better! We will then let you know via the email you provide in the <a href="https://docs.google.com/forms/d/e/1FAIpQLSecYgZDLxSKHkHt0vSVwcfInDPG46xyHxb2XBIKl_KjZUHF4A/viewform?usp=publish-editor">pre-proposal submission form</a> 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.</p>

<p>Feel free to ask any questions on the <a href="https://github.com/MDAnalysis/mdanalysis/discussions/categories/gsoc-discussions">discussion forum</a>. We are also happy to chat on our <a href="https://discord.com/channels/807348386012987462/">MDAnalysis Discord server</a> in the <code class="language-plaintext highlighter-rouge">#gsoc</code> channel (join with the public <a href="https://discord.com/invite/fXTSfDJyxE">invitation link</a>). Please note that MDAnalysis as an organization highly values transparency and therefore we strive to <em>conduct all discussions in public forums</em> so please ask questions publicly and not via direct messages or emails.</p>

<p>We look forward to working with you in GSoC 2026!</p>

<p>— <a href="https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#available-mentors">MDAnalysis GSoC mentors and organization administrators</a> (GitHub <code class="language-plaintext highlighter-rouge">@MDAnalysis/gsoc-mentors</code>, Discord <code class="language-plaintext highlighter-rouge">@gsoc-mentor</code>)</p>]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">MDAnalysis Adopts the NumFOCUS Code of Conduct</title><link href="https://www.mdanalysis.org/2025/11/07/NF-CoC/" rel="alternate" type="text/html" title="MDAnalysis Adopts the NumFOCUS Code of Conduct" /><published>2025-11-07T00:00:00+00:00</published><updated>2025-11-07T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2025/11/07/NF-CoC</id><content type="html" xml:base="https://www.mdanalysis.org/2025/11/07/NF-CoC/"><![CDATA[<p>As part of our ongoing commitment to fostering an open, welcoming, and respectful community, the MDAnalysis project has updated its <a href="/conduct">Code of Conduct</a> and formally adopted the <a href="https://numfocus.org/code-of-conduct">NumFOCUS Code of Conduct</a>. This replaces our previous Code of Conduct, which had been in place since 2017, and brings our community standards into alignment with those of our fiscal sponsor, <a href="https://numfocus.org/">NumFOCUS</a>.</p>

<p>Our decision to adopt the NumFOCUS Code of Conduct was motivated by a desire to better serve our growing and diverse community through a process that is impartial, transparent, and sustainable. By aligning with NumFOCUS’s framework, all Code of Conduct reports are reviewed by the <a href="https://numfocus.medium.com/meet-the-new-numfocus-code-of-conduct-working-group-a38b40f40fc3">NumFOCUS Code of Conduct Working Group</a>, a team of trained responders who operate independently of the MDAnalysis team to ensure reports are reviewed, investigated, and advised upon with neutrality.</p>

<h2 id="whats-covered-in-the-code-of-conduct">What’s Covered in the Code of Conduct?</h2>

<p>The full text of <a href="/conduct">our Code of Conduct</a> is available on our website.</p>

<p>The document outlines:</p>
<ul>
  <li><strong>expected behavior</strong>, such as respectful communications and inclusion of diverse perspectives;</li>
  <li><strong>unacceptable behavior</strong>, including harassment and discrimination;</li>
  <li><strong>reporting procedures</strong> and contact points for individuals who experience or witness potential conduct violations;</li>
  <li><strong>enforcement procedures</strong>, namely, that the MDAnalysis Code of Conduct Committee is responsible for enforcement based on recommendations from the <a href="https://numfocus.medium.com/meet-the-new-numfocus-code-of-conduct-working-group-a38b40f40fc3">NumFOCUS Code of Conduct Working Group</a>.</li>
</ul>

<p>The Code of Conduct applies to <em>all MDAnalysis project spaces</em> — including <a href="https://github.com/MDAnalysis/mdanalysis">GitHub</a> and <a href="https://github.com/MDAnalysis/mdanalysis/discussions">GitHub Discussions</a>; <a href="https://discord.com/channels/807348386012987462/">Discord</a>; <a href="https://linkedin.com/company/mdanalysis">LinkedIn</a>; <a href="https://bsky.app/profile/mdanalysis.bsky.social">Bluesky</a>; workshops and events; and all other forums associated with MDAnalysis.</p>

<h2 id="our-commitment">Our Commitment</h2>

<p>All <a href="/pages/governance/#mdanalysis-core-developers">MDAnalysis core developers</a> have unanimously agreed to adopt the new Code of Conduct and are fully committed to upholding its principles. Our goal is to ensure that the MDAnalysis community continues to be a place where all contributors, users, maintainers, and other community members feel welcomed, valued, and safe. As it takes <em>all of us</em>, and not just core developers, to foster an inclusive environment, all MDAnalysis community members agree to share a common set of core values and act according to these principles in all interactions within our community.</p>

<p>If you have any questions or concerns regarding the Code of Conduct, we encourage you to <a href="mailto:conduct@mdanalysis.org">reach out to the MDAnalysis Code of Conduct Committee</a>. We thank you for joining us on our mission to foster a welcoming and inclusive community!</p>

<p>— <a href="https://github.com/orgs/MDAnalysis/teams/coredevs">@MDAnalysis/coredevs</a></p>]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[As part of our ongoing commitment to fostering an open, welcoming, and respectful community, the MDAnalysis project has updated its Code of Conduct and formally adopted the NumFOCUS Code of Conduct. This replaces our previous Code of Conduct, which had been in place since 2017, and brings our community standards into alignment with those of our fiscal sponsor, NumFOCUS.]]></summary></entry><entry><title type="html">Release 2.10.0 of MDAnalysis</title><link href="https://www.mdanalysis.org/2025/10/26/release-2.10.0/" rel="alternate" type="text/html" title="Release 2.10.0 of MDAnalysis" /><published>2025-10-26T00:00:00+00:00</published><updated>2025-10-26T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2025/10/26/release-2.10.0</id><content type="html" xml:base="https://www.mdanalysis.org/2025/10/26/release-2.10.0/"><![CDATA[<p>We are happy to release version 2.10.0 of MDAnalysis!</p>

<p>This is a minor release of the MDAnalysis library, which means that it
contains enhancements, bug fixes, deprecations, and other
backwards-compatible changes.</p>

<h2 id="supported-environments">Supported environments</h2>

<p>This release supports NumPy 2.0+ and offers backwards compatibility
through to NumPy 1.26.0.</p>

<p>Supported Python versions: <strong>3.11, 3.12, 3.13, 3.14</strong>.
Note: not all optional dependencies currently work with Python 3.14.</p>

<p>Supported Operating Systems:</p>
<ul>
  <li><strong>Linux</strong> (on <a href="https://en.wikipedia.org/wiki/X86-64">x86-64</a>)</li>
  <li><strong>Windows</strong> (on <a href="https://en.wikipedia.org/wiki/X86-64">x86-64</a>)</li>
  <li><strong>MacOS</strong> (on <a href="https://en.wikipedia.org/wiki/X86-64">x86-64</a> and <a href="https://en.wikipedia.org/wiki/Apple_M1">ARM64</a>)</li>
</ul>

<h2 id="upgrading-to-mdanalysis-version-2100">Upgrading to MDAnalysis version 2.10.0</h2>

<p>To update with <code class="language-plaintext highlighter-rouge">mamba</code> (or <code class="language-plaintext highlighter-rouge">conda</code>)  from the <a href="https://anaconda.org/conda-forge/mdanalysis">conda-forge channel</a> run</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mamba update <span class="nt">-c</span> conda-forge mdanalysis
</code></pre></div></div>

<p>To update from <a href="https://pypi.org/project/MDAnalysis/">PyPi</a> with <code class="language-plaintext highlighter-rouge">pip</code> run</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>python <span class="nt">-m</span> pip <span class="nb">install</span> <span class="nt">--upgrade</span> MDAnalysis
</code></pre></div></div>

<p>For more help with installation see the <a href="https://userguide.mdanalysis.org/stable/installation.html">installation instructions in the User Guide</a>. 
Make sure you are using a Python version compatible with MDAnalysis 
before upgrading (Python &gt;= 3.11).</p>

<h2 id="notable-changes">Notable changes</h2>

<p>For a full list of changes, bug fixes and deprecations see the <a href="https://github.com/MDAnalysis/mdanalysis/blob/release-2.10.0/package/CHANGELOG">CHANGELOG</a>.</p>

<h4 id="enhancements">Enhancements:</h4>

<ul>
  <li>Support for setting custom <code class="language-plaintext highlighter-rouge">dt</code> when reading/writing XTC and TRR trajectories (<a href="https://github.com/MDAnalysis/mdanalysis/pull/4908">PR #4908</a>)</li>
  <li>New parallelization support for the following analyses:
    <ul>
      <li><code class="language-plaintext highlighter-rouge">LinearDensity</code> (<a href="https://github.com/MDAnalysis/mdanalysis/pull/5007">PR #5007</a>)</li>
      <li><code class="language-plaintext highlighter-rouge">PersistenceLength</code> ([PR #5074][])</li>
      <li><code class="language-plaintext highlighter-rouge">InterRDF</code> and <code class="language-plaintext highlighter-rouge">InterRDF_s</code> (<a href="https://github.com/MDAnalysis/mdanalysis/pull/4884">PR #4884</a>)</li>
    </ul>
  </li>
  <li>Enable the selection of distance library backend in RDF analyses (<a href="https://github.com/MDAnalysis/mdanalysis/pull/5038">PR #5038</a>)</li>
  <li>Improve the speed of the GROMOS11 reader (<a href="https://github.com/MDAnalysis/mdanalysis/pull/5080">PR #5080</a>)</li>
  <li>Improvements to the RDKit inferring code (<a href="https://github.com/MDAnalysis/mdanalysis/pull/4305">PR #4305</a>)</li>
  <li>Support for position and velocity reading from TPR files (<a href="https://github.com/MDAnalysis/mdanalysis/pull/4873">PR #4873</a>)</li>
  <li>Support for non-linear time averaged MSD (<a href="https://github.com/MDAnalysis/mdanalysis/pull/5066">PR #5066</a>)</li>
  <li>Support for interactive MD (IMDv3) stream reading using the IMDReader and the <a href="https://imdclient.readthedocs.io/">imdclient</a> package (<a href="https://github.com/MDAnalysis/mdanalysis/pull/4923">PR #4923</a>)</li>
  <li>Performance improvements to <code class="language-plaintext highlighter-rouge">InterRDF_s</code> (<a href="https://github.com/MDAnalysis/mdanalysis/pull/5073">PR #5073</a>)</li>
</ul>

<h4 id="changes">Changes:</h4>

<ul>
  <li>The output precision for LAMMPS DATA files is now set to 10 decimals (<a href="https://github.com/MDAnalysis/mdanalysis/pull/5053">PR #5053</a>)</li>
  <li>Support for Python 3.10 was removed in line with <a href="https://scientific-python.org/specs/spec-0000/">SPEC 0</a> (<a href="https://github.com/MDAnalysis/mdanalysis/pull/5121">PR #5121</a>)</li>
  <li>Bond order and charges inferring code from the RDKit converter has been moved to
a new <code class="language-plaintext highlighter-rouge">RDKitInferring</code> module (<a href="https://github.com/MDAnalysis/mdanalysis/pull/4305">PR #4305</a>)</li>
</ul>

<h2 id="author-statistics">Author statistics</h2>

<p>This release was the work of 25 contributors, <strong>16</strong> of which are <strong>new contributors</strong>.</p>

<p>Our <strong>new contributors</strong> are:</p>

<ul>
  <li>@namiroues</li>
  <li>@lexi-x</li>
  <li>@BHM-Bob</li>
  <li>@yuyuan871111</li>
  <li>@jpkrowe</li>
  <li>@TRY-ER</li>
  <li>@Abdulrahman-PROG</li>
  <li>@pbuslaev</li>
  <li>@tulga-rdn</li>
  <li>@Gareth-elliott</li>
  <li>@schuhmc</li>
  <li>@gitsirsha</li>
  <li>@Pradyumn-cloud</li>
  <li>@amruthesht</li>
  <li>@gitzhangch</li>
  <li>@raulloiscuns</li>
</ul>

<h2 id="acknowledgements">Acknowledgements</h2>

<p>MDAnalysis thanks <a href="https://www.numfocus.org">NumFOCUS</a> for its continued support as our fiscal sponsor and 
the <a href="https://chanzuckerberg.com/">Chan Zuckerberg Initiative</a> for supporting MDAnalysis under EOSS4 and EOSS5 awards.</p>

<p>— @IAlibay on behalf of the <a href="/pages/team">MDAnalysis Team</a></p>

<hr />]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[We are happy to release version 2.10.0 of MDAnalysis!]]></summary></entry><entry><title type="html">UGM 2025 Announcements – Keynote Speakers, Workshop Hosts, and Registration Deadline Extension</title><link href="https://www.mdanalysis.org/2025/07/15/ugm2025-updates/" rel="alternate" type="text/html" title="UGM 2025 Announcements – Keynote Speakers, Workshop Hosts, and Registration Deadline Extension" /><published>2025-07-15T00:00:00+00:00</published><updated>2025-07-15T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2025/07/15/ugm2025-updates</id><content type="html" xml:base="https://www.mdanalysis.org/2025/07/15/ugm2025-updates/"><![CDATA[<p>We’re excited to share updates for the upcoming <a href="https://www.mdanalysis.org/pages/ugm2025/">2025 MDAnalysis User Group Meeting (UGM)</a>, taking place <strong>November 9–11, 2025</strong> at Arizona State University in Tempe, Arizona (USA). This in-person event unites a global community of users, developers, and researchers to discuss advancements in molecular dynamics analysis and to foster collaborations across disciplines. This year’s UGM will feature not only contributed talks from the community, but also insightful talks from our two keynote speakers, Drs. <a href="#dr-lillian-chong">Lillian Chong</a> and <a href="#dr-matthias-heyden">Matthias Heyden</a> and hands-on workshops/tutorials. To accommodate continued demand from the community, we are now accepting registrations on a rolling basis.</p>

<h2 id="meet-the-keynote-speakers">Meet the Keynote Speakers</h2>

<h3 id="dr-lillian-chong">Dr. Lillian Chong</h3>

<p><img src="/public/images/UGM 2025 Speaker Announcement Cards - Chong.png" alt="Dr. Lillian Chong, Professor, University of Pittsburgh. Prof. Chong's research focuses on developing and applying advanced simulation methods to investigate rare but biologically important events, with an emphasis on capturing rigorous kinetics. Her group leads the development of the open-source WESTPA software, which implements weighted ensemble path sampling strategies for efficient simulation of rare events. She also works on the development of implicitly polarized force fields and rational design of protein conformational switches." style="float:left; " /></p>

<p>Dr. Lillian Chong, Professor of Chemistry at the University of Pittsburgh, leads the <a href="https://chonglab-pitt.github.io">Chong Lab</a>, where her team develops cutting-edge tools at the interface of chemistry, physics, and biology to investicate biomolecular dynamics and function. Her research group pioneered using weighted ensemble (WE) simulation techniques to study rare events, such as large-scale conformational changes and protein-protein binding, and for creating implicitly polarized AMBER force fields. Her work garned the <a href="https://chonglab-pitt.github.io/gordon_bell_prize/">2020 Gordon Bell Special Prize</a> for high-performance computing in COVID-19 research leveraging analyses that would otherwise take years but were achieved in weeks using WE and <a href="https://westpa.github.io/westpa/">WESTPA</a>, an open-source software for weighted ensemble path sampling.</p>

<h3 id="dr-matthias-heyden">Dr. Matthias Heyden</h3>

<p><img src="/public/images/UGM 2025 Speaker Announcement Cards - Heyden.png" alt="Dr. Matthias Heyden, Associate Professor, Arizona State University. Prof. Heyden's research group studies the dynamics and function of biomolecules with molecular simulations and Monte Carlo simulations. A special interest of his is anharmonic low-frequency vibrations, which are easily excitable by molecular collisions and can exhibit large deviations from harmonic approximations." style="float:left; " /></p>

<p>The second keynote, <a href="https://www.compmolsci.com/">Dr. Matthias Heyden</a> from Arizona State University’s School of Molecular Sciences, brings expertise in modeling solvation dynamics and vibrational energy transport in crowded biomolecular environments. His research integrates realistic atomistic simulations to illuminate solute-solvent interactions and energy transfer. His group has contributed to the development of interactive molecular dynamics (IMD) workflows through tools like <a href="https://imdclient.readthedocs.io/en/latest/">IMDClient</a>, enabling real-time streaming and manipulation of molecular trajectories. These capabilities, also showcased in the <a href="https://github.com/MDAnalysis/imd-workshop-2024">MDAnalysis IMD workshop materials</a>, open new avenues for exploring simulations dynamically and interactively. This work enhances our understanding of biochemical processes in realistic settings, informing both simulation methodology and experimental interpretation.</p>

<h2 id="contributed-workshops">Contributed Workshops</h2>

<p>Alongside invited presentations, the 2025 UGM will feature <strong>community-led workshops</strong> that cover a range of tools and methods relevant to the MDAnalysis user base. Confirmed contributed workshops will include sessions from:</p>

<ul>
  <li><a href="/pages/governance/#mdanalysis-core-developers">MDAnalysis core development team</a></li>
  <li><a href="https://openadmet.org/">OpenADMET</a></li>
  <li><a href="https://openforcefield.org/">Open Force Field Initiative</a></li>
  <li><a href="https://openfree.energy/">Open Free Energy</a></li>
</ul>

<p>These workshops are a great opportunity to learn new skills and connect with fellow developers and researchers in the field.</p>

<h2 id="registration-and-bursary-applications-now-rolling">Registration and Bursary Applications Now Rolling</h2>

<p>We encourage all users, from first-time analysts to veteran contributors, to join us this November in-person in Arizona or to follow along with the online recordings. There are limited travel bursaries available. <strong>Registration is now accepted on a rolling basis</strong>, until participation limits are met. If you’re interested in attending or applying for support, we encourage you to submit as early as possible to maximize your chances of receiving a bursary and securing a spot. Visit the <a href="https://www.mdanalysis.org/pages/ugm2025/">UGM 2025 page</a> for full details and links to the application forms.</p>

<hr />

<p>We look forward to seeing you there!</p>

<p>— The 2025 MDAnalysis UGM Organizing Committee</p>]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[We’re excited to share updates for the upcoming 2025 MDAnalysis User Group Meeting (UGM), taking place November 9–11, 2025 at Arizona State University in Tempe, Arizona (USA). This in-person event unites a global community of users, developers, and researchers to discuss advancements in molecular dynamics analysis and to foster collaborations across disciplines. This year’s UGM will feature not only contributed talks from the community, but also insightful talks from our two keynote speakers, Drs. Lillian Chong and Matthias Heyden and hands-on workshops/tutorials. To accommodate continued demand from the community, we are now accepting registrations on a rolling basis.]]></summary></entry><entry><title type="html">Google Summer of Code Students 2025</title><link href="https://www.mdanalysis.org/2025/05/23/gsoc-students/" rel="alternate" type="text/html" title="Google Summer of Code Students 2025" /><published>2025-05-23T00:00:00+00:00</published><updated>2025-05-23T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2025/05/23/gsoc-students</id><content type="html" xml:base="https://www.mdanalysis.org/2025/05/23/gsoc-students/"><![CDATA[<p>We are proud to announce that MDAnalysis — in <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#collaborations">collaboration with Molecular Nodes, ProLIF, and WESTPA</a> — 
is hosting <em>four</em> <a href="https://summerofcode.withgoogle.com">Google Summer of Code</a> (GSoC) contributors: @jpkrowe, @nilay-v3rma, @PardhavMaradani, and @yuyuan871111. MDAnalysis has been accepted as its own <a href="https://summerofcode.withgoogle.com/programs/2025/organizations/mdanalysis">organization with GSoC</a> 
for the sixth year in a row. We are grateful to Google for granting us the opportunity to get started on these four very exciting projects!</p>

<h2 id="james-jamie-rowe-integrating-mdanalysis-streaming-analysis-within-westpa-propagators">James (Jamie) Rowe: <a href="https://summerofcode.withgoogle.com/programs/2025/projects/SvFaSgr5">Integrating MDAnalysis Streaming Analysis within WESTPA Propagators</a></h2>

<p><img src="https://avatars.githubusercontent.com/u/28990394?v=4" title="James (Jamie) Rowe" alt="James (Jamie) Rowe" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>James’ project is a collaboration between MDAnalysis and <a href="https://westpa.github.io/westpa/">WESTPA</a>, a toolkit for running Weighted Ensemble simulations. In Weighted Ensemble simulations, many short trajectories are run in parallel and evaluated after each iteration to identify those that have progressed along a predefined coordinate. This analysis step can become a bottleneck, as all trajectories must be loaded and processed before the next iteration can begin. The goal of this project is to use MDAnalysis’ trajectory streaming capabilities to analyze trajectories on-the-fly, reducing analysis overhead and decreasing the time between iterations.</p>

<p>James is a 3rd year PhD student at Imperial College London. His PhD project aims to use molecular dynamics to understand how mutations and modifications to the fundamental building blocks of bone, such as collagen, lead to increased fracture risk and compromised mobility. He has recently released an article on <a href="https://pubs.rsc.org/en/content/articlehtml/2023/cp/d2cp05051j">selective rupture in collagen</a> and a <a href="https://www.sciencedirect.com/science/article/pii/S0079642525000490">review article that integrates experimental and computational advances in bone research</a>.</p>

<p>You can find James on <a href="https://github.com/jpkrowe">GitHub</a>, <a href="https://www.linkedin.com/in/james-rowe-74018425b/">LinkedIn</a> and <a href="https://bsky.app/profile/jrowe2000.bsky.social">Bluesky</a>.</p>

<p>To find updates on this project, check out his blog <a href="https://jpkrowe.github.io">here!</a></p>

<h2 id="nilay-verma-enhancing-prolif-visualizations-a-hybrid-approach-for-automated-customizable-2d-interaction-layout">Nilay Verma: <a href="https://summerofcode.withgoogle.com/programs/2025/projects/XWsglxQM">Enhancing ProLIF Visualizations: A Hybrid Approach for Automated, Customizable 2D Interaction Layout</a></h2>

<p><img src="https://github.com/nilay-v3rma.png" title="Nilay Verma" alt="Nilay Verma" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>Nilay’s project focuses on improving the 2D interaction visualizations in <a href="https://github.com/chemosim-lab/ProLIF">ProLIF</a>, a tool for analyzing molecular interactions such as protein–ligand and protein–protein binding. He is enhancing LigNetwork plots by implementing graph-based algorithms to automate residue placement, reduce edge overlaps, and improve overall readability. Additionally, he is exploring the integration of visualization approaches from tools like InteractionDrawer and Flareplot to improve the visual representation of interactions. The goal is to create a more user-friendly and informative visualization tool for researchers.</p>

<p>Nilay is a sophomore at Indian Institute of Technology Gandhinagar (IITGN), pursuing a dual major in B.Tech Computer Science and Materials Science. He is passionate about computational materials science, machine learning, and generative AI and its applications.</p>

<p>You can find Nilay on <a href="https://github.com/nilay-v3rma">GitHub</a>, <a href="https://www.linkedin.com/in/nilay-verma-1110a928a/">LinkedIn</a> and his <a href="https://nilay-v3rma.github.io/">Portfolio</a>.</p>

<p>To keep up with his work, you can check out his <a href="https://nilay-v3rma.github.io/gsoc-blog/">gsoc-blog</a>.</p>

<h2 id="pardhav-maradani-better-interfacing-of-blender-and-mdanalysis">Pardhav Maradani: <a href="https://summerofcode.withgoogle.com/programs/2025/projects/9BR8jbvV">Better Interfacing of Blender and MDAnalysis</a></h2>

<p><img src="https://avatars.githubusercontent.com/pardhavmaradani" title="Pardhav Maradani" alt="Pardhav Maradani" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>MDAnalysis has a basic interface with <a href="https://www.blender.org/">Blender</a> through a popular extension called <a href="https://github.com/BradyAJohnston/MolecularNodes">Molecular Nodes</a>, which allows importing MDAnalysis universes and provides advanced rendering capabilities through a GUI. The ability to script and support advanced visualizations of MDAnalysis results is currently limited. This project attempts to define, prototype and implement various APIs along with an integrated GUI within Blender as part of <a href="https://github.com/yuxuanzhuang/ggmolvis">GGMolVis</a> and <a href="https://github.com/BradyAJohnston/MolecularNodes">Molecular Nodes</a> that will together provide advanced visualization capabilities for MDAnalysis.</p>

<p>Pardhav is an undergraduate student from India pursuing a Bachelors in Computer Science and Engineering from Vellore Institute of Technology (Vellore) and a BS in Data Science and Applications from Indian Institute of Technology (IIT) Madras.</p>

<p>You can find Pardhav on GitHub <a href="https://github.com/PardhavMaradani">@PardhavMaradani</a>.</p>

<p>To see updates on this project, you can check out his <a href="https://pardhavmaradani.github.io/categories/gsoc-2025/">blog</a>.</p>

<h2 id="yu-yuan-stuart-yang-mdanalysis-x-prolif-project-5-h-bond-interactions-from-implicit-hydrogens">Yu-Yuan (Stuart) Yang: <a href="https://summerofcode.withgoogle.com/programs/2025/projects/5Otkx8vp">MDAnalysis x ProLIF Project 5: H-Bond Interactions from Implicit Hydrogens</a></h2>

<p><img src="https://avatars.githubusercontent.com/yuyuan871111" title="Yu-Yuan (Stuart) Yang" alt="Yu-Yuan (Stuart) Yang" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p><a href="https://github.com/chemosim-lab/ProLIF">ProLIF</a>, a MDAnalysis/RDKit-based tool for identifying protein-molecule interactions in molecular dynamics trajectories, lacks a straightforward method for evaluating hydrogen bonds when only heavy atoms are present. This project introduces an “implicit hydrogen bond (H-bond) interaction method” directly using heavy atom positions to detect H-bonds. This new feature for ProLIF will help many users (especially, beginner-level programming users) compare their experimental and computational structures without explicit hydrogens.</p>

<p>Yu-Yuan (Stuart) graduated from National Taiwan University (Taipei, Taiwan), holding a Bachelor of Science in Agricultural Chemistry, a Bachelor of Engineer in Chemical Engineering, and a Master of Science in Biomedical Electronics and Bioinformatics. He worked on both wet-lab (<a href="https://doi.org/10.1016/j.jtice.2024.105344">WPI fibril microcapsules</a>, <a href="https://www.linkedin.com/in/yuyuan871111/overlay/1635506597143/single-media-viewer?type=DOCUMENT&amp;profileId=ACoAACiNG10BL5O9KRp8TUNZI_sskb-wj5N80BM&amp;lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base%3BC9cMZG0TSRKfr%2F%2BybMQWPw%3D%3D">SEA-PHAGE</a>) and dry-lab (<a href="https://doi.org/10.1038/s41746-024-01022-x">FastEval Parkinsonism</a>, <a href="https://doi.org/10.1109/MNANO.2023.3249499">Quantum computing for drug discovery</a>, <a href="https://doi.org/10.1093/bfgp/elac053">MD simulations of SARS-CoV-2 omicron variants</a>, <a href="https://github.com/yuyuan871111/NHRI_group4">Automated WGS(WES) reporting system</a>) projects. <a href="https://www.qmul.ac.uk/sbbs/staff/yuyuanyang.html">Stuart</a> currently studies for a PhD in <a href="https://www.qmul.ac.uk/deri/ukri-aidd-doctoral-training-programme/">UKRI-AIDD doctoral training programme</a> in <a href="https://www.qmul.ac.uk/sbbs/staff/richardpickersgill.html">Richard W. Pickersgill</a>’s and <a href="https://afornililab.wordpress.com/">Arianna Fornili’s group</a> at Queen Mary University of London (London, UK) to explore protein conformations with a computer-vision-based deep learning model. He is pursuing a career as a computational research scientist in drug discovery. During the free time, Stuart enjoys playing volleyball and badminton and sometimes visiting new places and cities with his family and friends.</p>

<p>You can find Stuart on GitHub as @yuyuan871111 and on <a href="https://www.linkedin.com/in/yuyuan871111/">LinkedIn</a>. To keep up to date with his latest projects, check out his <a href="https://yuyuan871111.github.io/blogs/gsoc/">blog</a>.</p>

<p>— @BradyAJohnston @cbouy @fiona-naughton @jeremyleung521 @ljwoods2 @ltchong @orbeckst @talagayev @yuxuanzhuang @IAlibay @jennaswa (@MDAnalysis/gsoc-mentors and org admins)</p>]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[We are proud to announce that MDAnalysis — in collaboration with Molecular Nodes, ProLIF, and WESTPA — is hosting four Google Summer of Code (GSoC) contributors: @jpkrowe, @nilay-v3rma, @PardhavMaradani, and @yuyuan871111. MDAnalysis has been accepted as its own organization with GSoC for the sixth year in a row. We are grateful to Google for granting us the opportunity to get started on these four very exciting projects!]]></summary></entry><entry><title type="html">Announcement and Call for Abstracts for MDAnalysis UGM 2025</title><link href="https://www.mdanalysis.org/2025/04/13/ugm2025/" rel="alternate" type="text/html" title="Announcement and Call for Abstracts for MDAnalysis UGM 2025" /><published>2025-04-13T00:00:00+00:00</published><updated>2025-04-13T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2025/04/13/ugm2025</id><content type="html" xml:base="https://www.mdanalysis.org/2025/04/13/ugm2025/"><![CDATA[<p>We are pleased to announce the <a href="https://www.mdanalysis.org/pages/ugm2025/">2025 MDAnalysis UGM</a> (User Group Meeting), taking place on the 9-11th November, 2025, in Arizona, USA at <a href="https://www.asu.edu/">Arizona State University</a>. <a href="https://forms.gle/jfKsiWUDn4TMzX5Q6">Abstracts</a> are welcomed from all areas relevant to MDAnalysis’s work, from scientific applications (e.g., biomolecular simulations, soft matter and materials science, drug discovery and more) to the use and development of open source software and tools for data analysis of molecular simulation output. Additionally this UGM will have sessions focusing on ongoing work towards enabling simulation streaming being undertaken at ASU (see our previous <a href="https://www.mdanalysis.org/2024/11/03/ASU_streaming_workshop/">workshop</a> on this topic). When submitting your abstract, you may indicate whether you prefer to give a 15 minute talk, 5 minute lighting talk, or poster presentation.</p>

<p>MDAnalysis strives to be a diverse and welcoming community for all. A limited number of travel bursaries are available to enable those facing financial barriers to attend and present their work. If you would like to apply, please follow the prompts on the <a href="https://forms.gle/jfKsiWUDn4TMzX5Q6">abstract submission form</a>.</p>

<p>The deadline for submitting your abstract and/or bursary application is <strong>July 15th, 2025</strong>. Submissions will be reviewed by the end of July 2025; we will contact applicants shortly after.</p>

<p>Follow the <a href="https://www.mdanalysis.org/pages/ugm2025/">official event page</a> on our website for the most up-to-date information about the UGM. If you have any questions or special requests, please contact <a href="mailto:ugm@mdanalysis.org">ugm@mdanalysis.org</a>.</p>]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[We are pleased to announce the 2025 MDAnalysis UGM (User Group Meeting), taking place on the 9-11th November, 2025, in Arizona, USA at Arizona State University. Abstracts are welcomed from all areas relevant to MDAnalysis’s work, from scientific applications (e.g., biomolecular simulations, soft matter and materials science, drug discovery and more) to the use and development of open source software and tools for data analysis of molecular simulation output. Additionally this UGM will have sessions focusing on ongoing work towards enabling simulation streaming being undertaken at ASU (see our previous workshop on this topic). When submitting your abstract, you may indicate whether you prefer to give a 15 minute talk, 5 minute lighting talk, or poster presentation.]]></summary></entry><entry><title type="html">Release 2.9.0 of MDAnalysis</title><link href="https://www.mdanalysis.org/2025/03/11/release-2.9.0/" rel="alternate" type="text/html" title="Release 2.9.0 of MDAnalysis" /><published>2025-03-11T00:00:00+00:00</published><updated>2025-03-11T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2025/03/11/release-2.9.0</id><content type="html" xml:base="https://www.mdanalysis.org/2025/03/11/release-2.9.0/"><![CDATA[<p>We are happy to release version 2.9.0 of MDAnalysis!</p>

<p>This is a minor release of the MDAnalysis library, which means that it
contains enhancements, bug fixes, deprecations, and other
backwards-compatible changes.</p>

<h2 id="supported-environments">Supported environments</h2>

<p>This release supports NumPy 2.0+ and offers backwards compatibility
through to NumPy 1.23.2.</p>

<p>Supported Python versions: <strong>3.10, 3.11, 3.12, 3.13</strong>.</p>

<p>Supported Operating Systems:</p>
<ul>
  <li><strong>Linux</strong> (on <a href="https://en.wikipedia.org/wiki/X86-64">x86-64</a>)</li>
  <li><strong>Windows</strong> (on <a href="https://en.wikipedia.org/wiki/X86-64">x86-64</a>)</li>
  <li><strong>MacOS</strong> (on <a href="https://en.wikipedia.org/wiki/X86-64">x86-64</a> and <a href="https://en.wikipedia.org/wiki/Apple_M1">ARM64</a>)</li>
</ul>

<h2 id="upgrading-to-mdanalysis-version-290">Upgrading to MDAnalysis version 2.9.0</h2>

<p>To update with <code class="language-plaintext highlighter-rouge">mamba</code> (or <code class="language-plaintext highlighter-rouge">conda</code>)  from the <a href="https://anaconda.org/conda-forge/mdanalysis">conda-forge channel</a> run</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mamba update <span class="nt">-c</span> conda-forge mdanalysis
</code></pre></div></div>

<p>To update from <a href="https://pypi.org/project/MDAnalysis/">PyPi</a> with <code class="language-plaintext highlighter-rouge">pip</code> run</p>

<div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>python <span class="nt">-m</span> pip <span class="nb">install</span> <span class="nt">--upgrade</span> MDAnalysis
</code></pre></div></div>

<p>For more help with installation see the <a href="https://userguide.mdanalysis.org/stable/installation.html">installation instructions in the User Guide</a>. 
Make sure you are using a Python version compatible with MDAnalysis 
before upgrading (Python &gt;= 3.10).</p>

<h2 id="notable-changes">Notable changes</h2>

<p>For a full list of changes, bug fixes and deprecations see the <a href="https://github.com/MDAnalysis/mdanalysis/blob/release-2.9.0/package/CHANGELOG">CHANGELOG</a>.</p>

<h4 id="enhancements">Enhancements:</h4>

<ul>
  <li>Support for Gromacs v2024.4 and v2025 TPR files.</li>
  <li>A new “water” keyword for selecting water residues.</li>
  <li>
    <p>Support for <strong><a href="https://github.com/MDAnalysis/distopia">distopia</a> 0.4.0</strong> as an optional distance library
backend that now supports <a href="https://docs.mdanalysis.org/stable/documentation_pages/lib/distances.html#id2">many more distance
functions</a>
for <em>all box types</em> (including general triclinic unit cells).</p>

    <p>On supported <a href="https://en.wikipedia.org/wiki/X86-64">x86-64</a> platforms, install <em>distopia</em> with</p>
    <div class="language-bash highlighter-rouge"><div class="highlight"><pre class="highlight"><code>mamba <span class="nb">install</span> <span class="nt">-c</span> conda-forge distopia
</code></pre></div>    </div>

    <p>You can then <a href="https://docs.mdanalysis.org/stable/documentation_pages/lib/distances.html#use-of-the-distopia-library">enable <em>distopia</em> as a
backend</a>
to make use of the optimized <em>distopia</em> code for 
compute-intensive distance calculations, such as
<a href="https://docs.mdanalysis.org/stable/documentation_pages/lib/distances.html#MDAnalysis.lib.distances.distance_array"><code class="language-plaintext highlighter-rouge">distance_array()</code></a>:</p>

    <div class="language-python highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="n">protein</span> <span class="o">=</span> <span class="n">u</span><span class="p">.</span><span class="n">select_atoms</span><span class="p">(</span><span class="s">"protein and not name H*"</span><span class="p">)</span>
<span class="n">lipids</span> <span class="o">=</span> <span class="n">u</span><span class="p">.</span><span class="n">select_atoms</span><span class="p">(</span><span class="s">"resname POPC CHOL and not name H*"</span><span class="p">)</span>
<span class="n">d</span> <span class="o">=</span> <span class="n">MDAnalysis</span><span class="p">.</span><span class="n">lib</span><span class="p">.</span><span class="n">distances</span><span class="p">.</span><span class="n">distance_array</span><span class="p">(</span><span class="n">protein</span><span class="p">,</span> <span class="n">lipids</span><span class="p">,</span>
                                            <span class="n">box</span><span class="o">=</span><span class="n">u</span><span class="p">.</span><span class="n">dimensions</span><span class="p">,</span> 
                                            <span class="n">backend</span><span class="o">=</span><span class="s">"distopia"</span><span class="p">)</span>
</code></pre></div>    </div>

    <p>If you want to see if <em>distopia</em> is available as a backend in a running
program, check that the variable <code class="language-plaintext highlighter-rouge">MDAnalysis.lib.distances.HAS_DISTOPIA</code> is
<code class="language-plaintext highlighter-rouge">True</code>.</p>
  </li>
  <li>Parallel analysis support for <code class="language-plaintext highlighter-rouge">MDAnalysis.analysis.nucleicacids</code>, <code class="language-plaintext highlighter-rouge">MDAnalysis.analysis.contacts</code>, and <code class="language-plaintext highlighter-rouge">MDAnalysis.analysis.density</code>.</li>
  <li>XYZ writer can now write positions up to a user-supplied precision via the <code class="language-plaintext highlighter-rouge">precision</code> keyword argument.</li>
</ul>

<h4 id="changes">Changes:</h4>

<ul>
  <li><code class="language-plaintext highlighter-rouge">MDAnalysis.analysis.hole2</code>, <code class="language-plaintext highlighter-rouge">MDAnalysis.analysis.psa</code>, and
<code class="language-plaintext highlighter-rouge">MDAnalysis.analysis.waterdynamics</code>, are now only available via
optional dependencies (the mdahole2, pathsimanalysis, and
waterdynamics <a href="https://mdakits.mdanalysis.org/">MDAKits</a>). By default these will not be installed, you
will need to install them separately if you wish to use them from
within <code class="language-plaintext highlighter-rouge">MDAnalysis.analysis</code>. Please
note that <em>in v3.0</em> theses modules will be <em>removed completely from the
MDAnalysis core library</em> and you will need to use the MDAKits
directly.</li>
  <li><code class="language-plaintext highlighter-rouge">fasteners</code> dependency has been switched to <code class="language-plaintext highlighter-rouge">filelock</code>.</li>
  <li>Codebase is now formatted with black (version 24)</li>
</ul>

<h2 id="author-statistics">Author statistics</h2>

<p>This release was the work of 10 contributors, <strong>3</strong> of which are <strong>new contributors</strong>.</p>

<p>Our <strong>new contributors</strong> are:</p>

<ul>
  <li>@ChiahsinChu</li>
  <li>@tanishy7777</li>
  <li>@jauy123</li>
</ul>

<h2 id="acknowledgements">Acknowledgements</h2>

<p>MDAnalysis thanks <a href="https://www.numfocus.org">NumFOCUS</a> for its continued support as our fiscal sponsor and 
the <a href="https://chanzuckerberg.com/">Chan Zuckerberg Initiative</a> for supporting MDAnalysis under EOSS4 and EOSS5 awards.</p>

<p>— @IAlibay and @p-j-smith (<a href="/team/#roles">release managers</a>) on behalf of the <a href="/team">MDAnalysis Team</a></p>

<hr />]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[We are happy to release version 2.9.0 of MDAnalysis!]]></summary></entry><entry><title type="html">Google Summer of Code 2025</title><link href="https://www.mdanalysis.org/2025/02/28/gsoc2025/" rel="alternate" type="text/html" title="Google Summer of Code 2025" /><published>2025-02-28T00:00:00+00:00</published><updated>2025-02-28T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2025/02/28/gsoc2025</id><content type="html" xml:base="https://www.mdanalysis.org/2025/02/28/gsoc2025/"><![CDATA[<p>
<img src="https://developers.google.com/open-source/gsoc/resources/downloads/GSoC-Vertical.svg" title="Google Summer of Code 2025" alt="Google Summer of Code with
MDAnalysis 2025" style="float: right; height: 10em; " />
</p>

<p>MDAnalysis has been accepted as an <a href="https://summerofcode.withgoogle.com/programs/2025/organizations/mdanalysis">organization</a> for <a href="https://summerofcode.withgoogle.com/">Google Summer of
Code</a> (GSoC) 2025! 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 2025 with MDAnalysis.</p>

<p>The application window <strong>deadline</strong> is <strong>April 8, 2025 - 18:00 UTC</strong>.
As part of the application process you must familiarize
yourself with <a href="https://summerofcode.withgoogle.com/">Google Summer of Code 2025</a>, including eligibility requirements, timelines, and generally how the program works.</p>

<p>We are looking forward to all applications from <em>any new and beginner
open source contributors or students over 18 years old</em>; see a full list of the <a href="https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation">eligibility requirements</a> in the <a href="https://developers.google.com/open-source/gsoc/faq">GSoC FAQ</a>. 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).</p>

<p>Potential GSoC Contributors are expected to familiarize themselves with application
requirements and mentoring organizations <strong>as soon as possible</strong>. If you are interested in working with us, please read on to learn about <a href="#project-ideas">MDAnalysis project ideas</a> and <a href="#information-for-prospective-gsoc-contributors">MDAnalysis-specific requirements for putting together your application</a>.</p>

<h2 id="project-ideas">Project Ideas</h2>

<p>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 <a href="https://github.com/MDAnalysis/mdanalysis/discussions/categories/gsoc-discussions">GSoC with MDAnalysis discussion forum</a> to discuss it there.</p>

<p>We also have listed several <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas">possible projects</a> 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 <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas">ideas</a> page — we might add more ideas after the posting date of
this post.</p>

<p>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 <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-Proposal-Review">our decision criteria in choosing GSoC contributors</a>.</p>

<p>This year, MDAnalysis is joining forces with three other open source projects to offer even more far-reaching collaborative projects: <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#westpa">WESTPA</a>, <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#molecular-nodes">Molecular Nodes</a>, and <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#prolif">ProLIF</a> (an <a href="/pages/mdakits">MDAKit</a>).</p>

<table>
  <thead>
    <tr>
      <th>project</th>
      <th>name</th>
      <th>difficulty</th>
      <th>project size</th>
      <th>description</th>
      <th>skills</th>
      <th>mentors</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>1</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-1-integrating-mdanalysis-streaming-analysis-within-westpa-propagators">Integrating MDAnalysis streaming analysis within WESTPA propagators</a></td>
      <td>medium</td>
      <td>175 hours</td>
      <td>Integrate MDAnalysis with WESTPA to analyze streamed trajectory data</td>
      <td>Python (multiprocessing), Networking (TCP/IP), MD Engines</td>
      <td>@jeremyleung521, @ltchong, @fiona-naughton, @orbeckst</td>
    </tr>
    <tr>
      <td>2</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-2-dashboard-for-tracking-westpa-simulation-progress">Dashboard for tracking WESTPA simulation progress</a></td>
      <td>easy</td>
      <td>90 hours</td>
      <td>Create a graphical user interface to report MD trajectory progress</td>
      <td>Python (frontend UI, multiprocessing), Networking (TCP/IP)</td>
      <td>@jeremyleung521, @ltchong, @fiona-naughton, @talagayev</td>
    </tr>
    <tr>
      <td>3</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-3-lazy-trajectory-analysis-with-dask-and-a-lazy-timeseries-api">Lazy trajectory analysis with Dask and a Lazy Timeseries API</a></td>
      <td>medium</td>
      <td>175 hours</td>
      <td>Build out a lazy reader and timestep interface</td>
      <td>Dask or lazy computation paradigm, Object-oriented programming, Writing analysis code classes/scripts, Experience with a numpy-like-interface</td>
      <td>@ljwoods2, @orbeckst, @yuxuanzhuang</td>
    </tr>
    <tr>
      <td>4</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-4-better-interfacing-of-blender-and-mdanalysis">Better interfacing of Blender and MDAnalysis</a></td>
      <td>medium</td>
      <td>350 hours</td>
      <td>Improve how Blender and Molecular Nodes interface with MDAnalysis to import and animate MD trajectories</td>
      <td>Python, MDAnalysis, Blender (and programming via its Python API)</td>
      <td>@yuxuanzhuang, @bradyajohnston</td>
    </tr>
    <tr>
      <td>5</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-5-hbond-interactions-from-implicit-hydrogens">HBond interactions from implicit hydrogens</a></td>
      <td>medium</td>
      <td>175/350 hours</td>
      <td>Make interaction fingerprints analysis with ProLIF (an MDAKit) more accessible and faster to run</td>
      <td>Python, RDKit, SMARTS, compchem</td>
      <td>@cbouy, @talagayev</td>
    </tr>
    <tr>
      <td>6</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-6-continuous-ie-non-binary-interaction-fingerprints-ifps">Continuous (i.e., non-binary) interaction fingerprints (IFPs)</a></td>
      <td>hard</td>
      <td>350 hours</td>
      <td>Define thresholds for interactions and implement continuous encoding for interactions</td>
      <td>Python, RDKit, compchem</td>
      <td>@cbouy, @talagayev</td>
    </tr>
    <tr>
      <td>7</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-7-improving-prolifs-2d-interaction-visualizations">Improving ProLIF’s 2D interaction visualizations</a></td>
      <td>medium</td>
      <td>90/175 hours</td>
      <td>Improve ProLIF’s “LigNetwork” plot and add 2D visualizations to summarize information in IFPs</td>
      <td>Python, JavaScript</td>
      <td>@cbouy, @talagayev</td>
    </tr>
    <tr>
      <td>8</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-8-benchmarking-and-performance-optimization">Benchmarking and performance optimization</a></td>
      <td>easy/medium</td>
      <td>175/350 hours</td>
      <td>Write benchmarks for automated performance analysis and address performance bottlenecks</td>
      <td>Python/ASV, Cython</td>
      <td>@orbeckst, @ljwoods2</td>
    </tr>
    <tr>
      <td>9</td>
      <td><a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-9-integrating-openfolds-structural-prediction-confidence-metrics-into-the-topology-system">Integrating OpenFolds’ structural prediction confidence metrics into the topology system</a></td>
      <td>easy/medium</td>
      <td>90 hours</td>
      <td>Expose the predicted local distance difference test metric (pLDDT) via the MDAnalysis topology system</td>
      <td>OpenFold or structural prediction tools more generally, Python, Solving parsing problems</td>
      <td>@ljwoods2, @orbeckst</td>
    </tr>
  </tbody>
</table>

<h2 id="information-for-prospective-gsoc-contributors">Information for prospective GSoC Contributors</h2>

<p>You must meet our <a href="https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#our-expectations-from-gsoc-contributors">own requirements</a> 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 <a href="https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation">GSoC eligibility criteria</a>. <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-FAQ">Our GSoC FAQ</a> collects common questions from applicants.</p>

<p>In short:</p>
<ol>
  <li><a href="#code-of-conduct">Agree to be bound by our Code of Conduct</a> (and <a href="https://github.com/westpa/westpa/wiki/Code-of-Conduct">WESTPA’s Code of Conduct</a> if you are applying for a WESTPA collaboration project [i.e., <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-1-integrating-mdanalysis-streaming-analysis-within-westpa-propagators">Project 1</a>, <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-2-dashboard-for-tracking-westpa-simulation-progress">Project 2</a>]);</li>
  <li><a href="#familiarize-yourself-with-mdanalysis-and-relevant-partner-projects">Familiarize yourself with MDAnalysis and relevant partner projects</a>;</li>
  <li><a href="#submit-a-pre-proposal">Submit a short pre-proposal</a> —</li>
  <li><strong>If you have been invited to proceed with your application (based on your pre-proposal)</strong> <a href="#have-a-pull-request-merged-by-invitation">have a pull request merged</a> in MDAnalysis or a partner organization.</li>
</ol>

<h3 id="code-of-conduct">Code of Conduct</h3>

<p>The MDAnalysis community values diversity and is committed to providing a
productive, harassment-free environment to every member. Our <a href="/conduct">Code of Conduct</a>
explains the values that we as a community uphold. <em>Every community member (and every
GSoC Contributor) agrees to follow the <a href="/conduct">Code of Conduct</a></em>.</p>

<h3 id="familiarize-yourself-with-mdanalysis-and-relevant-partner-projects">Familiarize yourself with MDAnalysis and relevant partner projects</h3>

<p>As a start to get familiar with MDAnalysis and open source development you
should follow these steps:</p>
<ol>
  <li><a href="#watch-the-mdanalysis-trailer">Watch the MDAnalysis Trailer</a></li>
  <li><a href="#complete-the-quick-start-guide">Complete the Quick Start Guide</a></li>
  <li><em>If applicable to the <a href="#project-ideas">project idea</a> you are interested in</em>, <a href="#learn-more-about-westpa-molecular-nodes-and-prolif">learn more about WESTPA, Molecular Nodes, and/or ProLIF</a>.</li>
</ol>

<h4 id="watch-the-mdanalysis-trailer">Watch the MDAnalysis Trailer</h4>

<p>The <a href="https://www.youtube.com/watch?v=uMAfvwFkD3o">MDAnalysis Trailer</a> on YouTube
is a one minute introduction to MDAnalysis.</p>

<div class="js-video">
	<iframe src="https://www.youtube.com/embed/uMAfvwFkD3o" frameborder="0" allowfullscreen="" class="video"></iframe>
</div>

<p>There are also additional <a href="/pages/learning_MDAnalysis/#introductory">introductory videos</a> available to give you an idea of what problems MDAnalysis is solving.</p>

<h4 id="complete-the-quick-start-guide">Complete the Quick Start Guide</h4>

<p>Start by <a href="https://userguide.mdanalysis.org/stable/installation.html">installing</a> the MDAnalysis package. We have a <a href="https://userguide.mdanalysis.org/stable/examples/quickstart.html">Quick Start Guide</a> explaining the basics of MDAnalysis. You
should go through it at least once to understand how MDAnalysis is
used. Continue reading the <a href="https://userguide.mdanalysis.org/">User Guide</a> to learn more.</p>

<h4 id="learn-more-about-westpa-molecular-nodes-and-prolif">Learn More About WESTPA, Molecular Nodes and ProLIF</h4>

<p>As some of the <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas">project ideas</a> represent collaboration between MDAnalysis and other partner software projects, you should follow the recommended steps linked here to familiarize yourself (as relevant) with <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#westpa">WESTPA</a>, <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#molecular-nodes">Molecular Nodes</a> and/or <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#prolif">ProLIF</a>.</p>

<h3 id="submit-a-pre-proposal">Submit a pre-proposal</h3>

<p>We ask you to submit a short <em>pre-proposal</em> 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. <em>Please note that this decision is final, and applicants should only submit <strong>one</strong> pre-proposal.</em> 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.</p>

<p><strong>We require GSoC applicants to submit a pre-proposal</strong> that will determine who is then invited to <a href="#have-a-pull-request-merged-by-invitation">contribute a pull request for evaluation</a> (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.</p>

<p>Submit your pre-proposal via <a href="https://docs.google.com/forms/d/e/1FAIpQLSeOxd8b9MrHLtsQ6o8N7uq02P0CdyvyoWnQ1dhmJD_vW1Jh1w/viewform?usp=dialog">this submission form</a> <strong>as soon as possible, but no later than March 21, 2025</strong>. You should prepare the following information for your pre-proposal:</p>
<ul>
  <li>Email address</li>
  <li>GitHub handle</li>
  <li>Real name (optional)</li>
  <li>Basic information on your background (e.g., education, relevant experience with MDAnalysis and molecular dynamics or computational physics/chemistry/materials)</li>
  <li>Project title</li>
  <li>Project size (90h, 175h, 350h)</li>
  <li><strong>Problem:</strong> 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.</li>
  <li><strong>Approach:</strong> 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.</li>
  <li><strong>Objectives:</strong> 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.</li>
</ul>

<h3 id="have-a-pull-request-merged-by-invitation">Have a pull request merged (<em>by invitation</em>)</h3>

<p>Based on your <strong>pre-proposal</strong> we may invite you to contribute a pull request.</p>

<p>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 <strong>having a pull request (PR) merged <em>prior</em> to submitting their full GSoC application</strong> on the <a href="https://summerofcode.withgoogle.com/">GSoC website</a>. Submit the PR in one of the repositories under the <a href="https://github.com/MDAnalysis/">MDAnalysis org</a> or, for projects related to Molecular Nodes (i.e., <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-4-better-interfacing-of-blender-and-mdanalysis">Project 4</a>) or ProLIF (i.e., <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-5-hbond-interactions-from-implicit-hydrogens">Project 5</a>, <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-6-continuous-ie-non-binary-interaction-fingerprints-ifps">Project 6</a>, <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas#project-7-improving-prolifs-2d-interaction-visualizations">Project 7</a>), in the relevant repositories (MolecularNodes: <a href="https://github.com/BradyAJohnston/MolecularNodes">BradyAJohnston/MolecularNodes</a>, ProLIF: <a href="https://github.com/chemosim-lab/ProLIF">chemosim-lab/ProLIF</a>).</p>

<p>You must have <em>at least one commit</em> merged in one of the organizations to be eligible. Note that <strong>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!</strong></p>

<p>We have a list of <a href="https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3ADifficulty-easy">easy bugs</a> and
suggested <a href="https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3A%22GSOC+Starter%22">GSOC Starter issues</a> to work on in our issue tracker
on GitHub. <em>We only accept one <a href="https://github.com/MDAnalysis/mdanalysis/issues?q=is%3Aopen+is%3Aissue+label%3A%22GSOC+Starter%22">GSOC Starter issue</a> per
applicant</em> 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 <a href="https://github.com/MDAnalysis/mdanalysis/wiki/GSoC-2025-Project-Ideas">project ideas</a> include related issues that you might want to explore.</p>

<p>To start developing for MDAnalysis have a look at our guide on
<a href="https://userguide.mdanalysis.org/stable/contributing.html">contributing to MDAnalysis</a> and write to us on the <a href="https://github.com/MDAnalysis/mdanalysis/discussions/categories/gsoc-discussions">GSoC with MDAnalysis discussion forum</a> if you have more questions
about setting up a development environment or how to contribute.</p>

<h2 id="final-remarks">Final remarks</h2>

<p><strong>Submit your pre-proposal before March 21, 2025</strong>, but the earlier the better! We will then let you know via the email you provide in the <a href="https://docs.google.com/forms/d/e/1FAIpQLSeOxd8b9MrHLtsQ6o8N7uq02P0CdyvyoWnQ1dhmJD_vW1Jh1w/viewform?usp=dialog">pre-proposal submission form</a> 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, 2025.</p>

<p>Feel free to ask any questions on the <a href="https://github.com/MDAnalysis/mdanalysis/discussions/categories/gsoc-discussions">discussion forum</a>. We are also happy to chat on our <a href="https://discord.com/channels/807348386012987462/">MDAnalysis Discord server</a> in the <code class="language-plaintext highlighter-rouge">#gsoc</code> channel (join with the public <a href="/#participating">invitation link</a>). Please note that MDAnalysis as an organization highly values transparency and therefore we strive to <em>conduct all discussions in public forums</em> so please ask questions publicly and not via direct messages or emails.</p>

<p>We look forward to working with you in GSoC 2025!</p>

<p>— <a href="https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#available-mentors">MDAnalysis GSoC mentors and organization administrators</a> (GitHub <a href="https://github.com/orgs/MDAnalysis/teams/gsoc-mentors">@MDAnalysis/gsoc-mentors</a>, Discord <code class="language-plaintext highlighter-rouge">@gsoc-mentor</code>)</p>]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">Meet our New Core Developers!</title><link href="https://www.mdanalysis.org/2025/02/14/new_coredevs/" rel="alternate" type="text/html" title="Meet our New Core Developers!" /><published>2025-02-14T00:00:00+00:00</published><updated>2025-02-14T00:00:00+00:00</updated><id>https://www.mdanalysis.org/2025/02/14/new_coredevs</id><content type="html" xml:base="https://www.mdanalysis.org/2025/02/14/new_coredevs/"><![CDATA[<p>We are thrilled to announce that MDAnalysis has elected three new <a href="/about/#mdanalysis-core-developers">Core Developers</a> to the project: @BradyAJohnston, @marinegor, and @p-j-smith. We thank each of them for the many contributions they have already made to the MDAnalysis project, and look forward to having them help shape the future direction of the project. Keep reading to <a href="#introductions">learn more about Brady, Egor, and Paul</a>, as well as the <a href="#becoming-a-core-developer">process behind becoming a Core Developer</a> of MDAnalysis.</p>

<h2 id="introductions">Introductions</h2>
<h3 id="brady-johnston-bradyajohnston">Brady Johnston (@BradyAJohnston)</h3>
<p><img src="/public/images/bradyajohnston.png" title="Brady Johnston" alt="Brady Johnston" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>I originally did my PhD in structural biology at the University of Western Australia. Starting out doing crystallography, I became interested instead with ways to better visualise molecular data instead of collecting it. I created <a href="https://bradyajohnston.github.io/MolecularNodes">Molecular Nodes</a> (MN) for cinematic visualisation of molecular data inside of the 3D modelling and animation program <a href="https://blender.org">Blender</a>. Molecular Nodes relies heavily on MDAnalysis for import and handling of molecular dynamics (MD) datasets, with projects going forward also allowing Blender to become a tool for analysing MD trajectories. I have now left academia and do freelance scientific illustration and development full time. You can contact me on on <a href="https://bsky.app/profile/bradyajohnston.bsky.social">BlueSky</a>, <a href="https://github.com/bradyajohnston">GitHub</a>, Discord and <a href="https://www.linkedin.com/in/bradyajohnston/">LinkedIn</a> as @bradyajohnston, or see my <a href="https://bradyajohnston.github.io">website</a>. I’m always excited to chat about anything related to Blender and data visualisation.</p>

<h3 id="egor-marin-marinegor">Egor Marin (@marinegor)</h3>
<p><img src="/public/images/marinegor.png" title="Egor Marin" alt="Egor Marin" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>I started my career as a scientist from macromolecular crystallography, and during my PhD slowly moved towards structural bioinformatics and relevant machine learning methods.</p>

<p>I am currently employed at <a href="https://enpicom.com/about-us/">ENPICOM B.V.</a> as Machine Learning Scientist, and continue contributing to open-source as much as I can.</p>

<p>You can find me as <code class="language-plaintext highlighter-rouge">@marinegor</code> almost everywhere, and check out <a href="https://marinegor.dev">marinegor.dev</a> for some short-form tech posts about my research and open-source work.</p>

<h3 id="paul-smith-p-j-smith">Paul Smith (@p-j-smith)</h3>
<p><img src="/public/images/p-j-smith.png" title="Paul Smith" alt="Paul Smith" style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /></p>

<p>I did my PhD in computational biophysics at King’s College London, using molecular dynamics simulations to study the biophysics of lipid membranes. During my PhD, I began contributing to open-source scientific software, including MDAnalysis. I created <a href="https://github.com/p-j-smith/lipyphilic">LiPyphilic</a> - an open-source Python package for analysing simulations of lipid membranes, built on top of MDAnalysis.</p>

<p>I’m now a Research Software Engineer at <a href="https://www.ucl.ac.uk/advanced-research-computing/">University College London</a>, working on projects broadly related to medical imaging. I’m excited to join the Core Developer team, and always happy to chat about biophysics and open-source software. You can get in touch with me on <a href="https://www.linkedin.com/in/p-j-smith/">LinkedIn</a> or <a href="https://github.com/p-j-smith">GitHub</a>.</p>

<h2 id="becoming-a-core-developer">Becoming a Core Developer</h2>
<p>MDAnalysis is a dynamic, ever-changing <a href="/about/#community">community</a>, with many new contributors joining continuously. It is important to us that the leadership of MDAnalysis reflects the community that builds it. Therefore, the MDAnalysis Core Developer team regularly holds elections for new core developers, as described in our <a href="/about/#governance">governance section</a>. While this voting process is conducted in private, we are publishing and formalizing what we consider when voting, in the interests of transparency.</p>

<p>Firstly, potential Core Developers are identified based on their past contributions to MDAnalysis and potential to move the MDAnalysis project forward. Contributions we account for include both those that are technical in nature, and also less quantifiable ones which add value to the MDAnalysis organization. Examples include:</p>
<ul>
  <li>Fixing bugs</li>
  <li>Adding features</li>
  <li>Adding or fixing documentation</li>
  <li>Reviewing pull requests (PRs)</li>
  <li>Interacting with the community on <a href="https://github.com/MDAnalysis/mdanalysis">GitHub</a> or our <a href="https://discord.com/channels/807348386012987462/">Discord server</a></li>
  <li>Participating in discussions in PRs and issues</li>
  <li>Organizing workshops or events</li>
  <li>Mentoring either in an official capacity (e.g., <a href="https://summerofcode.withgoogle.com/">Google Summer of Code</a>) or unofficially (e.g., through reviewing PRs)</li>
  <li>Promoting a culture which reflects the core values of MDAnalysis, as detailed in our <a href="/pages/conduct">Code of Conduct</a> (e.g., promoting diversity and inclusion within our community)</li>
  <li>Involvement in ongoing community projects (e.g., applying for grants) and liaising with other organisations, such as our fiscal sponsor, <a href="https://numfocus.org/">NumFOCUS</a></li>
</ul>

<p>If a candidate has shown a history of participating in these activities, they are put forward for election. The Core Developer team reviews the candidate and votes on whether or not they wish to elect an individual, following <a href="/about/#decision-making-process-and-membership">our standard voting procedures</a>.</p>

<p>Finally, being an active Core Developer requires some amount of active participation in meetings, decisions, and other administrative business. As MDAnalysis does not have any guaranteed long-term funding, this work is usually unpaid. Therefore, the final decision to accept or decline the election is left to the developers themselves: do they have the time and willingness to keep contributing?</p>

<p>If you are interested in becoming a Core Developer, we highly encourage you to <a href="/#participating">participate</a> in some of the activities listed above, especially reviewing pull requests and mentoring other developers. Learn more about the many roles MDAnalysis community members take on to move the project forward on our <a href="/team">MDAnalysis team</a> page, and reach out to us on our <a href="https://github.com/MDAnalysis/mdanalysis/discussions">GitHub discussions forum</a> or <a href="https://discord.com/channels/807348386012987462/">Discord server</a> (join the server using the invitation link, <a href="https://discord.gg/fXTSfDJyxE">https://discord.gg/fXTSfDJyxE</a>. On our end, the MDAnalysis Core Developer team will, to the best of its abilities, aim to offer mentorship and other opportunities to people who express an interest in becoming a Core Developer.</p>

<p>Being a Core Developer is work, but it’s also a fantastic opportunity to work with and for a wonderful and welcoming community. As part of <a href="/about/#mission">our mission</a>, we welcome anyone who cares for this community and wants to help it grow.</p>

<p>— <a href="https://github.com/orgs/MDAnalysis/teams/coredevs">@MDAnalysis/coredevs</a></p>]]></content><author><name>The MDAnalysis Team</name><email>mdanalysis@numfocus.org</email></author><summary type="html"><![CDATA[We are thrilled to announce that MDAnalysis has elected three new Core Developers to the project: @BradyAJohnston, @marinegor, and @p-j-smith. We thank each of them for the many contributions they have already made to the MDAnalysis project, and look forward to having them help shape the future direction of the project. Keep reading to learn more about Brady, Egor, and Paul, as well as the process behind becoming a Core Developer of MDAnalysis.]]></summary></entry></feed>