Skip to content
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

Add contact information to teams page #397

Open
jennaswa opened this issue Jul 30, 2024 · 6 comments
Open

Add contact information to teams page #397

jennaswa opened this issue Jul 30, 2024 · 6 comments
Assignees

Comments

@jennaswa
Copy link
Contributor

jennaswa commented Jul 30, 2024

During the Governance and Docs Meeting on July 29th, it was pointed out that we suggest reaching out to current team members listed, but do not provide contact information for doing so. We considered the following as potential options to resolve this:

  • Clarify that folks should email [email protected] and we will redirect to the appropriate team members internally
  • Add or link to github profiles when listing team member names

Are there preferences among @MDAnalysis/coredevs on moving forward one way or the other (or doing both or something else)?

@jennaswa jennaswa self-assigned this Jul 30, 2024
@orbeckst
Copy link
Member

I'd say "email [email protected]".

(There's no real harm in adding GitHub profiles but that's not really useful for contacting unless you add contact information to your profile.)

@tylerjereddy
Copy link
Member

+1 for the team email and avoiding a single person getting too much stuff (or at least that way we explicitly see if 38 people are trying to contact someone).

@lilyminium
Copy link
Member

+1 preference for the group email for the reasons above, also keeps things more open and consistent vs different people getting different communications.

@IAlibay
Copy link
Member

IAlibay commented Aug 9, 2024

I would do both - numfocus.org email for actual contact, github handles for everyone listed (allowing folks to be tagged in relevant conversations).

@orbeckst
Copy link
Member

orbeckst commented Aug 9, 2024

That's a good reason for adding GH handles, so "both" looks good to me.

@RMeli
Copy link
Member

RMeli commented Aug 18, 2024

+1 for both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants