Joe McGill 1:40 am on September 23, 2016
Tags: ,   

Media Weekly Update (Sept 22)

This post serves to jump-start discussion before our weekly check in, which takes place in #core-images on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Our next meeting is Friday, September 23 at 17:00 UTC and the agenda for these meetings include moving priority tasks forward, providing feedback on issues of interest, and reviewing media focused tickets on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

Summary from last week

Our last meeting was Friday, September 16 at 19:00 UTC. You can read the entire chat log in the #core-images channel on Slack.

Attendees: @joemcgill, @paaljoachim, @markoheijnen, @helen, @flixos90, @afercia

  • Unexpected change to media title behavior in WP 4.6.1 (#37989) – This is a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5., which has been partially fixed.
  • Sanitize accents in attachment filenames (#22363) – @mike and @markoheijnen were planning to work on #22363 in person this past week and will decide on next steps.
  • Better PDF thumbnails (#31050) – @markoheijnen tested out plugins that claim to handle this and found that all suffer from the same “corrupted image” issues that have blocked this ticketticket Created for both bug reports and feature development on the bug tracker.. The strategy is to see if we can detect which PDFs will fail and fall back to a default PDF icon when that is the case.
  • Media organization improvements:
    • Make media library searchable by filename (#22744) – This was fixed in [38625].
    • We had a lengthy discussion about the potential for adding a default taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. to attachments, including identifying some related tickets that would need to be addressed (e.g., #22938)
    • @paaljoachim shared the results of some research into how non-WP image applications handle media organization in the form of this Google doc.

Agenda for our next meeting

This week, we will continue discussion on our priority projects for the 4.7 release. If you have specific tickets that you want to have discussed, feel free to leave a comment on this post or reach out on Slack in the #core-images channel.

Priority Tickets:

  • #22363 – Accents in attachment filenames should be sanitized (@mike/@markoheijnen)
  • #32417 – CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Media WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. (@sheri)
  • #23594 (related: #22938) – Add default taxonomy support to the media library (@joemcgill)
  • #37840 – Improved full size image optimizations (@mike)
  • #31050 – Better PDF Upload Management (@markoheijnen)
  • #34635 – WordPress image’s title is not alt (@joemcgill)
  • WP-APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. – Private attachments assigned to public posts – GH1987

HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. Update: @johnbillion recently posted a call for an HTTPS Working Group on the make/core blogblog (versus network, site). Meetings will be on Fridays (time TBA).

#4-7, #media