Repository navigation
Provide email address for reaching PSF Board members #2453
Description
Activity
This would be changed in
/pages/page/1809/change/in the backend - but this would need input from the @python/psf-board-directors as to whether we should change verbiage on https://policies.python.org/python.org/code-of-conduct/Procedures-for-Reporting-Incidents/ to suggest reporting to the distribution list that goes to ALL sitting members, or if we should add individual emails for each, or bothHi ,
Thanks for the clarification. I understand this depends on guidance from the PSF Board regarding the preferred contact method.Once there’s a decision on whether to:
• reference a single distribution list for all sitting board members, or
• list individual board member emails, or
• include both,I’d be happy to help implement the agreed approach by updating the PSF Board page (or related documentation) accordingly.
Please let me know if I should wait for board input or if there’s any preparatory work you’d recommend in the meantime. Thanks!
https://www.python.org/psf/faq/#id3 contains the following information:
For general inquiries, please email psf@python.org. ...
Additional contact options will have to be discussed with the board first.
I have a suggestion:
I think we can add the email address for people who publicly list their email on the python.org domain, such as those exposed in the PSF reporting procedure or those with an email available on their respective wiki page (if available), displayed next to their name with an email emoji 📧.
Also, we can ask them to open an issue or send an email if they want to publicly show their contact information.2. (a better approach, in my opinion):
LinkPSF board members'andWG group members'and evenFellow Membersnames to theirwiki.python.orgpages if available.
For example, Marc-Andre Lemburg has a page with his contact info. This way, they have complete control over the info they want to share with others without putting more work on theInfrastructure WGedited due to:
This wiki is in the process of being archived due to lack of usage and the resources necessary to serve it — predominately to bots, crawlers, and LLM companies. Edits are discouraged.
Pages are preserved as they were at the time of archival. For current information, please visit python.org.
If a change to this archive is absolutely needed, requests can be made via the infrastructure@python.org mailing list.The wiki is being archived:
This wiki is in the process of being archived due to lack of usage and the resources necessary to serve it — predominately to bots, crawlers, and LLM companies. Edits are discouraged.
Pages are preserved as they were at the time of archival. For current information, please visit python.org.
If a change to this archive is absolutely needed, requests can be made via the infrastructure@python.org mailing list.Reacted by Ali TavallaieHi! I'm a student in the CodePath AI301 program and I'd like to work on this issue. I'll start by reproducing the problem locally this week. Any pointers on where to start in the codebase would be appreciated!
@Gezahegne Please read all the comments, this needs a decision from the board first.
Is your feature request related to a problem? Please describe.
I was trying to write an email to PSF board members.
I tried looking for information under https://www.python.org/psf/board/ but could not find a good contact info.
Describe the solution you'd like
Update the page https://www.python.org/psf/board/ with information how to reach the board members.
Describe alternatives you've considered
n/a
Additional context
Python community members should be able to easily reach the PSF Board members with concerns about the community.
I found my answer after asking in PSF Slack but not everyone has access to PSF slack. Not every members know the board members but it shouldn't exclude them from voicing concerns and sharing feedback with the elected PSF board members.