[wp-trac] [WordPress Trac] #16020: Upload custom avatar for user in Dashboard

[WordPress Trac]

#16020: Upload custom avatar for user in Dashboard
-------------------------------------+-------------------------------------
 Reporter:  computerwiz908           |       Owner:  whyisjake
     Type:  feature request          |      Status:  accepted
 Priority:  normal                   |   Milestone:  Future Release
Component:  Users                    |     Version:
 Severity:  minor                    |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  ui, administration,
  has-screenshots                    |  privacy
-------------------------------------+-------------------------------------

Comment (by matt):

 It's exciting to see this older ticket picking up so much steam.

 Implementing user uploads and customization of local avatars introduces a
 lot of actual and potential complexity, and may have unintended security
 consequences or surface area, as we found with our comment moderation
 changes recently. (BuddyPress is a good example of this!) There are also
 easy plugin ways to change how avatars work, so we likely aren't going to
 have a big impact on the world or WP's adoption by bringing this into
 core.

 From an every day usability point of view, we have some very important
 items on our roadmap!

 Let me use this opportunity to point to our progress on the 9 projects we
 set out to accomplish last year:
 https://make.wordpress.org/core/2019/12/06/update-9-projects-for-2019/

 And the scope for 5.5:
 https://make.wordpress.org/core/2020/05/13/wordpress-5-5-planning-roundup/

 An effort I would be very interested in supporting is creating a featured
 plugin, like a Gutenberg for privacy, that would be de-coupled from the
 core release schedule and iterate on providing the most control and
 flexibility for site administrators to customize the privacy options on
 their site relevant to their audience and priorities. The privacy working
 group could have a lot of autonomy for choosing what to prioritize within
 this plugin, and we could hopefully attract a wider array of global
 contributors and create more collaboration on a single plugin where right
 now we have developers making many separate plugins to solve some of the
 same issues.

 That discussion is out of scope for this ticket and we should continue the
 discussion on the relevant P2s and Slack meetings, but I just didn't want
 to lose the energy we have here given this particular issue isn't a good
 fit for 5.5.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/16020#comment:120>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform