Remove Website and About me sections from user profile



3 years ago
3 years ago


(Reporter: jwhitlock, Unassigned)




(Whiteboard: [specification][type:change])



3 years ago
What feature should be changed? Please provide the URL of the feature if possible.
Remove the Website and About Me sections from the user profiles, in display and editing.  Keep existing columns in the database, and continue anonymizing it, to allow a quick reversal in the near future.

What problems would this solve?
These fields are targets for spam on MDN.  Removing them would remove a spam vector and eliminate the need for developing spam moderation tools.

Who would use this?
These fields are rarely used by active MDN contributors. They are sometimes used by users who never contribute documentation updates.

What would users see?
The would no longer see the free-text About Me field in profiles or the profile editing screen. They would no longer see the URL-restricted Website field.

What would users do? What would happen as a result?
Users would continue to be able to enter websites for Twitter, Stack Overflow, LinkedIn, Mozillians, and Facebook.  Users could link their GitHub page to show that link on the site.  Users would add "About Me" and personal website links to other websites

Is there anything else we should know?
The proposal to remove these fields was discussed on the MDN mailing list:!topic/mozilla.mdn/uCU6q2jSs8k
Severity: normal → major
Keywords: in-triage


3 years ago
See Also: → bug 1271503

Comment 1

3 years ago
Commits pushed to master at
bug 1271499 - Remove About Me section from user profile display/edit and from the tests.
bug 1271499 - Remove Website URL field from user profile display/edit and from tests.
bug 1271499 - Replace missing ul.
bug 1271499 - Remove 'website_url' from user form.
bug 1271499 - Adjust 2 tests to remove bio/website_url.
Merge pull request #3867 from caktus/new-issue-1271499-remove-about-me

bug 1271499 - Remove about me, website from profile

Comment 2

3 years ago
About Me and Website removed in production:
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.