You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2025-02-14-new_coredevs.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,14 +48,14 @@ Firstly, potential Core Developers are identified based on their past contributi
48
48
* Participating in discussions in PRs and issues
49
49
* Organizing workshops or events
50
50
* Mentoring either in an official capacity (e.g., [Google Summer of Code](https://summerofcode.withgoogle.com/)) or unofficially (e.g., through reviewing PRs)
51
-
* Promoting a culture which reflects the core values of MDAnalysis, as detailed in our [Code of Conduct]({{ site.baseurl }}/conduct) (e.g., promoting diversity and inclusion within our community)
51
+
* 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)
52
52
* Involvement in ongoing community projects (e.g., applying for grants) and liaising with other organisations, such as our fiscal sponsor, [NumFOCUS](https://numfocus.org/)
53
53
54
54
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 }}/about/#decision-making-process-and-membership).
55
55
56
56
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?
57
57
58
-
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 }}/team) page, and reach out to us on our [GitHub discussions forum]({{ site.mailinglists.discussion.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.
58
+
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.discussion.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.
59
59
60
60
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.
0 commit comments