Update contact information for Team page

[jennaswa]

Per the discussion in #397, the main purpose of this PR is to:

• List mdanalysis@numfocus.org as a general contact email, and
• Link github profiles to listed team members

In addition, this would provide a good opportunity to update team members in preparation for our first upcoming R&R review, as decided in the Aug 20 business meeting. Namely:

• Could all @MDAnalysis/coredevs please briefly review what teams you are listed for and make any necessary updates?
• I (@jennaswa) am currently the only listed team member for "Community Engagement". However, in the way we have defined the Community Engagement role, I feel others are actually doing this work rather than me (e.g., @hmacdope, @orbeckst, @IAlibay, @RMeli, @yuxuanzhuang, @richardjgowers). Please add your names if you agree.
• Similarly, @IAlibay, as you are doing the majority of the metric tracking (and have tentatively volunteered to help with meetings during my leave), would you like to be listed for the Project Org & Mgmt role?
• @yuxuanzhuang - this seems the perfect opportunity to please add your name to roles you are currently taking on/interested in staying/getting involved with :)

Thanks!

[IAlibay]

Thanks @jennaswa !

I will opt out of including myself in community engagement, but will opt in for project organization.

Re: the build failure, I suspect the autogeneration from yaml might not like the links so much. @lilyminium would be best suited to weigh in on this.

[lilyminium]

Re: github failure -- yup, I hadn't included Markdown support in the teams pages. I've opened #403 to include this so that should fix it. However, the caveat is that the initial YAML still has to be valid, so all the team member links should be encapsulated in quotes to tell YAML it's a string and not a list. (i.e. "[Jenna Swarthout Goddard](https://github.com/jennaswa)" instead of just plain [Jenna Swarthout Goddard](https://github.com/jennaswa))

[lilyminium]

Added non-blocking comments for quotes. Otherwise LGTM -- thanks for this @jennaswa!

[orbeckst]

@MDAnalysis/coredevs please review and sign off or ask for changes. Should be a quick thing. Thanks.

[RMeli]

Retirement will be very well deserved!!!

[RMeli]

Sorry, it should have been a "request changes".

[orbeckst]

@RMeli I incorporated your change request.

[RMeli]

Thank you.

[orbeckst]

@MDAnalysis/coredevs could you please have a look at the PR with your team assignments? We'd like to merge the current state by the end of the week — it's been sitting here for a very long time and with new coredevs coming in, we need to have a proper public representation of responsibilities.

If you are ok with the content, a quick ✅ LGTM approval would be very much appreciated, otherwise we'll assume silent assent. If anything needs changing please do that by Friday 2025-01-25 or as a later update to the page.

Thank you!

[orbeckst]

@jennaswa given that you've been shepherding the PR through the ages, could you please be the one looking after getting it merged? Thank you!

[RMeli]

Still good from my side, thanks for doing this!

[jennaswa]

I've been wondering if we should remove the role terms listed below the teams table (originally Nov 14 2023-Nov 14 2024). Another option is to say the roles listed are valid through the current quarter of the year, since this table should theoretically be updated after each of our quarterly team reviews in the future.

[IAlibay]

Just adding myself on various roles I've had to take on by proxy of doing things like releases.

[p-j-smith]

Thanks for adding me @jennaswa! lgtm

[jennaswa]

Per Oliver's message from 01/22/25, I am going to merge this PR as there have been no further comments or requested changes. Should further discussion regarding the table take place (e.g., when evaluating our quarterly team reviews) and require changes, these changes will occur as a separate PR and update to the page. Thank you to all of those who helped push this update across the finish line!