-
Notifications
You must be signed in to change notification settings - Fork 1k
Add option to display primary email on public profile #5944
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
Comments
This would be a great addition! :D |
@pgadige is this something you'd like to try working on? |
Thank you, @brainwane, for suggesting this one. I'm working on it. |
@pgadige How is it going? Do you have a branch somewhere that we can look at? |
@brainwane, I'm figuring out few JavaScript things (I'm a newbie to JS) for displaying the email address properly on the page. I managed to break the CSS of the page couple of times. I think I'll try to submit a PR by the EOD so the reviewers can show me what exactly I'm doing wrong. |
@pgadige Looking forward to that PR! |
I just emailed with @pgadige and she'll be working on sharing a work-in-progress pull request with us in the next few days. @pgadige: If you are working on this issue and have questions or get stuck, please feel free to speak up here, or in |
What's the problem this feature will solve?
Currently there's no way to publicly display an email address as a point of contact for a PyPI account. Instead, maintainer/author emails for a user's packages must be used instead.
Describe the solution you'd like
Similar to Github, on the "Account Settings" page, we should have an option such as:
This should default to "True" for all new and existing users.
Good First Issue: This issue is good for first time contributors. If you've already contributed to Warehouse, work on another issue without this label instead. If there is not a corresponding pull request for this issue, it is up for grabs. For directions for getting set up, see our Getting Started Guide. If you are working on this issue and have questions, feel free to ask them here,
#pypa-dev
on Freenode, or the pypa-dev mailing list.The text was updated successfully, but these errors were encountered: