-
Notifications
You must be signed in to change notification settings - Fork 47
Upload coredev blog post #423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 4 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
3702dc9
Upload coredev blog post
jennaswa f764913
add Paul's bio
orbeckst 5edb375
Use variable for discord invite link
jennaswa 0fe93e6
Fix text for Paul's photo ( copy/paste error :) )
jennaswa 4b08264
Update 2025-02-04-new_coredevs
marinegor e105a6f
add brady headshot (#31)
BradyAJohnston d670365
Add @marinegor 's headshot
jennaswa 8a1df5c
Link Egor's photo
jennaswa dd96a60
Add @p-j-smith 's headshot
jennaswa 3ffc095
Link Paul's photo
jennaswa 54cfdbe
Rename 2025-02-04-new_coredevs to 2025-02-14-new_coredevs
jennaswa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,58 @@ | ||
| --- | ||
| layout: post | ||
| title: Meet our New Core Developers! | ||
| --- | ||
|
|
||
| We are thrilled to announce that MDAnalysis has elected three new [Core Developers]({{ site.baseurl }}/pages/about/#mdanalysis-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](#introductions), as well as the [process behind becoming a Core Developer](#becoming-a-core-developer) of MDAnalysis. | ||
|
|
||
| ## Introductions | ||
| ### Brady Johnston (@BradyAJohnston) | ||
| <img | ||
| src="Picture Here" | ||
| title="Brady Johnston" alt="Brady Johnston" | ||
| style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /> | ||
|
|
||
| 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](https://bradyajohnston.github.io/MolecularNodes) (MN) for cinematic visualisation of molecular data inside of the 3D modelling and animation program [Blender](https://blender.org). 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](https://bsky.app/profile/bradyajohnston.bsky.social), [GitHub](https://github.com/bradyajohnston), Discord and [LinkedIn](https://www.linkedin.com/in/bradyajohnston/) as @bradyajohnston, or see my [website](https://bradyajohnston.github.io). I’m always excited to chat about anything related to Blender and data visualisation. | ||
|
|
||
| ### Egor Marin (@marinegor) | ||
| <img | ||
| src="Picture Here" | ||
| title="Egor Marin" alt="Egor Marin" | ||
| style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /> | ||
|
|
||
| Please write a short (1-2 paragraphs) bio here. Feel free to include your affiliation(s), ways you interface with MDAnalysis, and any other personal and/or professional interests. Please include any contact information you feel comfortable sharing publicly (e.g., GitHub/Discord handle, LinkedIn, website, etc.) | ||
|
|
||
| ### Paul Smith (@p-j-smith) | ||
| <img | ||
| src="Picture Here" | ||
| title="Paul Smith" alt="Paul Smith" | ||
| style="float: left; width: 110px; height: 110px; border-radius: 20px; border: 15px solid white" /> | ||
|
|
||
| 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](https://github.com/p-j-smith/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](https://www.ucl.ac.uk/advanced-research-computing/), 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](https://www.linkedin.com/in/p-j-smith/) or [GitHub](https://github.com/p-j-smith). | ||
|
|
||
| ## Becoming a Core Developer | ||
| MDAnalysis is a dynamic, ever-changing [community]({{ site.baseurl }}/pages/about/#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]({{ site.baseurl }}/pages/about/#governance/). 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]({{ site.github.repo }}) or our Discord server ({{ site.discord.url }}) | ||
| * Participating in discussions in PRs and issues | ||
| * Organizing workshops or events | ||
| * Mentoring either in an official capacity (e.g., [Google Summer of Code](https://summerofcode.withgoogle.com/)) or unofficially (e.g., through reviewing PRs) | ||
| * Promoting a culture which reflects the core values of MDAnalysis, as detailed in our [Code of Conduct]({{ site.baseurl }}/pages/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](https://numfocus.org/) | ||
|
|
||
| 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]({{ site.baseurl }}/pages/about/#decision-making-process-and-membership/). | ||
|
|
||
| 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]({{ site.baseurl }}/#participating) 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]({{ site.baseurl }}/pages/team/) page, and reach out to us on our [GitHub discussions forum]({{ site.mailinglists.discussions.url }}) or [Discord server]({{ site.discord.url }}) (join the server using the invitation link, [{{ site.discord.invite }}]({{ site.discord.invite }}). 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]({{ site.baseurl }}/about/#mission), we welcome anyone who cares for this community and wants to help it grow. | ||
|
|
||
| — [@MDAnalysis/coredevs](https://github.com/orgs/MDAnalysis/teams/coredevs) | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.