-
Notifications
You must be signed in to change notification settings - Fork 1k
account recovery policy, FAQ, and tooling #3016
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
I believe this does need addressing before launch, so I'm keeping it in this milestone. |
I've made #3190 to add a note about account recovery to the FAQ, and we discussed this in today's core Warehouse developers meeting. What's our policy on helping users who ask for account recovery, and what's our policy on verifying their claim?: We do these investigations (claims to names) on a case-by-case basis. We generally ask a person to prove they have or had the domain in question, project page, etc. Sometimes we'll ask someone to make a commit to the repo and include a particular hash or keyword in the commit/commit message. Do Warehouse administrators want better tooling for account recovery? For the actual changing of a user's email address in Warehouse, no. But #3176 would be nice to check mail deliverability (that'd help us see if mail is bouncing), and I've filed #3231 to establish separate support queue for customer support. I'm calling this closed since my question is answered. |
* Fix prose style in user FAQ * Add CoC note for FAQs that suggest filing tickets * Add FAQ item on account recovery Ref. #3016. * Restructure contribution area of FAQ, add donation request * Reorganize FAQ Add subject headings, move items around to fit into categories, change question headings down a level from h2 to h3. * Style new FAQ structure
If a user says that they are having trouble recovering their password (because they don't have access to that email address anymore, or because they signed up before PyPI required an email address),
#pypa
not knowing where else to turn.)The text was updated successfully, but these errors were encountered: