Meet our New Core Developers!
14 Feb 2025We 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.
Introductions
Brady Johnston (@BradyAJohnston)
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 Molecular Nodes (MN) for cinematic visualisation of molecular data inside of the 3D modelling and animation program Blender. 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 BlueSky, GitHub, Discord and LinkedIn as @bradyajohnston, or see my website. I’m always excited to chat about anything related to Blender and data visualisation.
Egor Marin (@marinegor)
I started my career as a scientist from macromolecular crystallography, and during my PhD slowly moved towards structural bioinformatics and relevant machine learning methods.
I am currently employed at ENPICOM B.V. as Machine Learning Scientist, and continue contributing to open-source as much as I can.
You can find me as @marinegor almost everywhere, and check out marinegor.dev for some short-form tech posts about my research and open-source work.
Paul Smith (@p-j-smith)
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 LiPyphilic - an open-source Python package for analysing simulations of lipid membranes, built on top of MDAnalysis.
I’m now a Research Software Engineer at University College London, 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 LinkedIn or GitHub.
Becoming a Core Developer
MDAnalysis is a dynamic, ever-changing community, 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 governance section. While this voting process is conducted in private, we are publishing and formalizing what we consider when voting, in the interests of transparency.
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:
- Fixing bugs
- Adding features
- Adding or fixing documentation
- Reviewing pull requests (PRs)
- Interacting with the community on GitHub or our Discord server
- Participating in discussions in PRs and issues
- Organizing workshops or events
- Mentoring either in an official capacity (e.g., Google Summer of Code) or unofficially (e.g., through reviewing PRs)
- Promoting a culture which reflects the core values of MDAnalysis, as detailed in our Code of Conduct (e.g., promoting diversity and inclusion within our community)
- Involvement in ongoing community projects (e.g., applying for grants) and liaising with other organisations, such as our fiscal sponsor, NumFOCUS
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 our standard voting procedures.
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?
If you are interested in becoming a Core Developer, we highly encourage you to participate 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 MDAnalysis team page, and reach out to us on our GitHub discussions forum or Discord server (join the server using the invitation link, https://discord.gg/fXTSfDJyxE. 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.
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 our mission, we welcome anyone who cares for this community and wants to help it grow.
