Notes/Agenda – 4.4 Dev Chat, August 26

Here’s the agenda for today’s Dev Chat in the #core channel on Slack.

Time/Date: Wednesday, August 12, 2015 16:00 UTC-4:

  1. New Committers were announced 
  2. Who wants to be the backup lead?
  3. Schedule is still being decided, looking at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US timetables
  4. Community Feedback

What’s going to be in 4.4?

There is still a lot to decide this week, but there are some things I know for sure we want to work on:

Twenty Sixteen

Announcement Post: https://make.wordpress.org/core/2015/08/25/introducing-twenty-sixteen/

Responsive Images

Update Post: https://make.wordpress.org/core/2015/08/25/responsive-image-support-update/

ImageFlow

This will be worked on in a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins, coupled with a healthy dose of user testing and intersecting with Boren’s Flow Patrol initiative. @sheri is going to help me with/teach me user testing, which will drive any new UXUX User experience/UIUI User interface media desktop/mobile/responsive initiatives.

CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. Performance

@westonruter and team have some GREAT initiatives:

  • Partial Refresh: https://core.trac.wordpress.org/ticket/27355
  • Transactions: https://core.trac.wordpress.org/ticket/30937
  • JS-driven widgets: https://core.trac.wordpress.org/ticket/33507

HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. 2.0 Exploration

@tollmanz has been giving great talks about HTTP/2. He and @ericlewis are going to deep-dive and see how WordPress can prepare itself/the community for taking advantage of 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./TLS/HTTP2 and identify changes that can be made in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and things like VVV to get us there.

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 and @melchoyce worked on this in 4.3 – we hope to pick this up again

Mutlisite, the Next Generation

@jeremyfelt is putting together a plan for WP_Site, WP_Network, WP_Network_Query, WP_Site_Query

The 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. Roadmap

A lot of people want Term MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., it has some pre-reqs. @boone will give us an update of where we are in the Taxonomy Roadmap, what we’ve done, what’s left, etc.

Things that landed in the past week

  • Images should default to not linking #31467 [33729]
  • WP_Embed::maybe_run_ajax_cache() now runs for pages [33642]
  • Term Splitting: Fix a reversal of parameters to wp_schedule_single_event() introduced in r33621. [33646]
  • Introduce post_name__in parameter for WP_Query. [33653]
  • Comments shouldn’t have more than one _wp_trash_meta_status entry. When deleting _wp_trash_meta_status, also delete _wp_trash_meta_time. [33654]
  • Show count next to “Approved”/fix dynamic counts when moderating comments: [33655][33656][33657][33662][33692]
  • Ensure that feeds are served with the proper Content-Type HTTP headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.. [33658]
  • Deprecate post_permalink() [33659]
  • Introduce is_post_type_viewable( $post_type_object )/Don’t show certain UI pieces when a post is not viewable on the front end [33666]
  • 'post_edit_category_parent_dropdown_args' filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. [33682]
  • new filters: default_hidden_columns and hidden_columns [33689]
  • Add new constant: MONTH_IN_SECONDS [33698]
  • Ensure that attachment_url_to_postid() matches cross-scheme when front-end and back-end schemes are different. [33705]
  • Add a query var, 'title', that allows you to query posts by post_title. [33706]
  • In wp_sanitize_redirect(), don’t eat @ characters. [33707]
  • In wp_insert_user(), add a filter: 'insert_user_meta' [33708]
  • wpdb::get_table_from_query() didn’t find table names with hyphens in them. [33718]
  • oEmbed: Remove blip.tv [33719], add ReverbNation [33745]
  • In WP_Query::parse_tax_query(), allow 'cat' and 'tag' querystrings to be formatted as arrays. [33724]
  • Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site: Add 'invite_user' action that fires immediately after a user is invited to join a site, but before the notification is sent. [33732]
  • Pass option name to option and transient filters with dynamic names. [33738]
  • Move a lot of classes into their own file, same with functions, load both in the original file: Widgets [33746] HTTP [33748] Users [33749] Comments [33750] Rewrite [33751] Roles [33752] Posts [33759] Tax [33760] Meta [33761]

#4-4, #agenda

New committers for 4.4!

It’s that time again… Please join me in welcoming Tammie Lister (@karmatosed) as a guest committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. for WordPress 4.4. There’s another committer to be announced, but we thought we’d wait until he’s back from vacation for a proper welcome.

You may recognize Tammie from her role as an adminadmin (and super admin) on the theme review team, and she’s also a theme developer extraordinaire at Automattic. Tammie will be heading up development of the new default theme, Twenty Sixteen.

The lead developers review and appoint new committers to serve each release cycle, often to work on a particular component or feature. This guest commit access comes up for review after each release and can be renewed. Ella Van Dorpe, Konstantin Obenland, and Weston Ruter, all new committers at the beginning of the 4.3 cycle, have been renewed for 4.4.

Over the last few cycles, both Aaron Jorbin and Jeremy Felt have been working through long-term plans, smashing through tickets, and improving the entire codebase, especially when it comes to tests and multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site. I’m happy to announce that both are now permanent committers. Please join me in congratulating everyone!

#4-4, #commit

Show Me Your WP REST API v2 Apps

WordPress 4.4 development hit the ground running last week, only a few hours after the launch of 4.3. We’re already close to 100 commits, and digging through the 385 responses on my “what’s on your wishlist” post. One feature that many of you want is the WP REST API (heard of it?). Lots of work has gone into it, and some people are already using a flavor of it in production – two that I know of:

  • Wired uses the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/ for communication between some of their internal systems
  • the New York Times for our Live Coverage platform (example – Republican Debate: Analysis and Highlights)

Both use version 1.*. I am working on an upgrade path for the NYT to version 2.

The point of this post is to solicit feedback from the general community:

  • What have you built using v2 of the REST API?
  • Are you running the project in production? If so, please post a link 🙂
  • Have you upgraded from v1 to v2? If so, how was it?
  • If you believe in the project, would like to see it in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and haven’t built anything with it: what’s stopping you?

Let’s take the excitement everyone has for the feature and start stress-testing it. Build something. Anything! And then report your findings back here.

#4-4, #rest-api

Introducing Twenty Sixteen

WordPress 4.4 will see a brand new default theme; that’s right, today is time to meet Twenty Sixteen! The process of selecting the Twenty Sixteen theme was a long one, taking several months. Lots of themes were considered, eventually settling on the one you see below. It’s a perfect fit!

00.twentysixteen

Twenty Sixteen features a new, never-released design that has some really unique touches on a traditional blogblog (versus network, site) layout. It adapts well to different devices and is a joy to use.

Twenty Sixteen is a modernised approach of an ever-popular layout — a horizontal masthead and an optional right sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. that works well with both blogs and websites. It has custom color options that allow you to make your own Twenty Sixteen. The theme was designed on a harmonious fluid grid with a mobile first approach. This means it looks great on any device.
– @iamtakashi

Let’s take a look at more!

We have the pleasure of welcoming back Takashi Irie as the designer of Twenty Sixteen. This year, the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team developing our new default theme will be myself and @iamtakashi — and you! We hope you can join us in getting Twenty Sixteen out to the world. Along with us, @iandstewart and @samuelsidler will be making sure the ship stays on course and giving us their wisdom as we charter the default theme seas.

How can you get involved?

There will be weekly meetings every Monday and Friday 16:00 UTC in #core-themes for half an hour. These weekly meetings will start once the theme has initially landed in core. If you are interested in contributing, subscribe to this blog (if you haven’t already), and leave your name in the comments. Once we’re ready, we will give everyone a pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” and we’ll let you know on this blog too.

Want to know more about default themes?

There are some great links where you can find out more about past default themes.

The road to releasing a new default theme is long, but we’re already well on our way! The next step is to commit the initial code to core. From there, we will begin testing and patching. We hope you join in the adventure of releasing Twenty Sixteen.

#4-4, #bundled-theme, #twenty-sixteen

WordPress 4.4: What’s on your wishlist?

4.4 has unofficially kicked off, now that 4.3 is out the door. As with any release, we want to garden TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., squash bugs, add new tools for dev, and wow our users.

I have spoken to many of my fellow core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org about their own wish lists. Now, it’s your turn:

  • What do you want to see happen in 4.4?
  • What are pain points for users?
  • What features can we add or iterate upon to empower our user base?

It can be anything: big or small.

As most of you know, I am leading WordPress 4.4

If we’ve never met, hello! You can learn a lot about me here:

 

#4-4, #wishlist

Release leads for WordPress 4.3 and 4.4

Since WordPress 3.5, we’ve had a rotating release leadRelease Lead The community member ultimately responsible for the Release.. Because of the ever-present demands of the current release’s development cycle, we’ve found it tough to make these appointments well in advance. We’ve always wanted to give leads opportunity to prepare, so they can hit the ground running. (Long term, we’d love for release development to overlap pretty significantly, aided primarily by feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins development, but also by branching.)

A release lead determines all important parameters for a release, like schedule, deadlines, which feature plugins are merged; and more generally, scope, goals, vision, and process. They take point when it comes to holding meetings, shepherding contributions, and writing announcement posts and updates. A release lead is a connector and facilitator, identifying bottlenecks and friction wherever they may be. They’re in frequent communication with the developers and pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. teams that are aiming to have something in a given release. The release lead follows what’s being committed, and sets the tone for prioritizing and gardening tickets. Given the constraint of time in hitting deadlines, help with prioritization and ensuring good communication lines are two of the most valuable things a lead can contribute.

Today, I’m excited to announce release leads for both WordPress 4.3 and 4.4.

Konstantin Obenland will lead WordPress 4.3, currently planned for August. Many of you may know @obenland (twitter) from his early work on default themes, but his contributions span across WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. More recently, he shipped the new WordPress.org theme directory. Obenland is a native of Germany and lives in southern California. He’s a code wrangler at Automattic, which donates all of his time to WordPress core and WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.

 

Scott Taylor will lead WordPress 4.4, due at the end of the year. A committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. since 3.7, @wonderboymusic (twitter) has been plowing through major changes to media and pretty much everything else he can get his hands on. Scott is a Tennessee native and lives in New York City. He’s a senior software engineer on the interactive news team at The New York Times.

 

You’ll hear from both of them in the coming days and weeks as they start to plan out their releases, including potential features, deputies, and strategies. Congratulations 🎉 and best of luck to both!

Not an April Fools’ joke.

#4-3, #4-4, #release-lead