Agenda for today’s dev chat in the #core…

Agenda for today’s dev chat in the #core channel 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/. (November 5 2014 21:00 UTC):

  • BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./Merge Window@johnbillion would like to extend the merge window and tagging the beta to Friday
  • Hook Recursion#17817: @jbrinley is requesting some eyes on it (likely 4.2-early). Three main issues:
    1. Is there enough unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. coverage?
    2. Does it break plugins which interact with $wp_filter and $wp_actions directly (eg accessing the nested arrays)?
    3. Does it “fix” any existing behavior which could be seen as 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.?
  • Focus#29806: Patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. for editor focus v2 looks good. @markjaquith will be posting a merge request update on make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. @johnbillion will decide whether to merge on Thurs/Fri
  • Sessions UIUI User interfaceNeeds a ticketticket Created for both bug reports and feature development on the bug tracker., #30264 decision for merge will be Thurs/Fri
  • Shiny Updates#29820: Decision at WCSF was to go with shiny installs, leave shiny updates for a later release. Awaiting feedback from @pento/@nacin/@melchoyce about whether this still has a chance of getting done in time for merge
  • FS Credentials Modal#29820: Also affects #29395 (installing languages from general settings screen)
  • 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@boone is on fire
  • Twenty Fifteen – Some discussion around smaller issues with the new template functions and color schemes, nothing that can’t be iterated upon during beta
  • Bug Scrubs – Continuing weekly bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs on Friday this week, likely a mixture of a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and 4.1 tickets

#4-1, #agenda

Modernising our real-time communication

The WordPress project is testing out Slack as our main real-time communication platform, replacing IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. and ad hoc Skype chats.

chat.wordpress.org is our new information hub for 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/.. All 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/ users will be able to access WordPress Slack with immediate effect.

This change was announced by Matt during his State Of The WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. presentation 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. San Francisco this weekend, and was overwhelmingly positively received. In fact, it was so well received that this week’s dev chat (October 29 2014 20:00 UTC) will be hosted in the WordPress #core channel on Slack, rather than in the #wordpress-dev channel on IRC.

There will be volunteers hanging out in #wordpress-dev to inform users that the dev chat has moved to Slack. For those of you who don’t want to leave IRC just yet, you can connect to WordPress Slack using the IRC gateway.

The #core and #announcements channels on Slack have just surpassed 1,000 users, which is five times as many as we’ve ever had in the channels on IRC. Join us at chat.wordpress.org!

#irc, #slack

Agenda for October 22nd dev chat

Agenda for today’s dev chat in #wordpress-dev (October 22 2014 20:00 UTC)

  • Twenty Fifteen is coming along really well, main issue appears to be 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. scrolling behaviour.
  • 4.1 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for next week, so we have a busy week ahead. Also WCSF and the community summit.
  • Not much progress so far on the install/update UIUI User interface changes, how shall we progress?
  • IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. meeting schedules: @drewapicture
  • Editor focus: needs a decision on default behaviour, user testing, anything else?
  • User/Post Dropdown Performance: status update
  • 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./Term/Date Query Enhancements: lots of progress. Any other blockers?
  • User session UI, currently awaiting w.org geolocation 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. details.
  • Friday’s bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub coming LIVE from San Fran.
  • Any other business.

#4-1, #agenda

Agenda for October 15th dev chat

According to the 4.1 release schedule, we should be merging in our planned feature plugins today. Strictly the only feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. we have scheduled for 4.1 is the user session management UIUI User interface though, so I’m not too worried.

Today’s meeting we’ll cover:

  • Twenty Fifteen; what’s in, what’s left, what needs testing.
  • Weekly bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs starting Friday.
  • Status of the 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 install/update UI improvements.
  • Volunteers for some mobile media testing.
  • Updates from @helen @markjaquith @boonebgorges on their respective focuses.
  • Any other business.

#4-1, #agenda

Get your gloves on, weekly bug scrubs are back

In recent releases we’ve sporadically done weekly bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs on Fridays. They allow contributors a concentrated period of time to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets while other people are around at the same time, and they generally work well.

I’m starting up the weekly bug scrubs again for the 4.1 cycle. The aim is to gather in the #wordpress-dev IRC channel each Friday at 4PM GMT (October 17th 2014 16:00 UTC) and spend some time triaging a particular report or a particular subset of tickets. Sometimes it lasts 20 minutes, sometimes people are around for a few hours.

This Friday we’ll start with the 4.1 milestone report to trim it down a bit (it’s in good shape at the moment) and then move onto any other tickets which are candidates for inclusion in 4.1.

Never been to a bug scrub before? Join us!

#bug-scrub

Agenda for October 8th dev chat

Agenda for today’s dev chat (October 8 2014 20:00 UTC) in #wordpress-dev.

  • Updates from @helen and @markjaquith on post/user dropdown performance, and editor focus improvements, respectively. Anything needed from either party?
  • Updates from @boonebgorges on his query enhancements. Any pending blockers, feedback, testing, etc needed?
  • Updates from myself, @johnbillion, on the session management UIUI User interface feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins..
  • Let’s chat about improvements to the plugin and theme install/updates UIs. @nacin and @melchoyce
  • Status of ticketing and beginning to address mobile media management concerns. @rboren might not be around for the meeting. What’s ticketed? How can we progress this?
  • Other areas that people are focusing on and want help with.
  • 4.0.1.
  • Birthday wishes (if applicable).

#4-1, #agenda

Agenda for October 1st dev chat

We’ll be discussing 4.1 in today’s dev chat (October 1 2014 20:00 UTC). The release schedule can be found here.

Here’s the agenda:

  • Decision time for features being developed as a 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. See Ryan’s overview of what was discussed on Monday. Also need to discuss the menu customiser work by @celloexpressions.
  • Very brief update on Twenty Fifteen theme from @obenland.
  • Improved UIs for installing and updating plugins, themes, and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Who wants to help with design mockups, UXUX User experience, dev? Needs a ticketticket Created for both bug reports and feature development on the bug tracker. for each.
  • @Helen and @MarkJaquith both have focuses for 4.1. Do we have tickets for all of the various components? Who’s helping out?
  • Accessibility ticket priorities.
  • @rboren has been documenting various mobile media management issues. Who’d like to help address these? Probably needs a bunch of individual tickets.
  • Language switcher on the General Settings screen: #29395. Per-user setting has been proposed again: #29783. Who’s interested? cc: @SergeyBiryukov @ocean90
  • Query enhancements coming in from @boonebgorges. Unit testing and general dev help needed?
  • Keeping the 4.1 milestone under control. @wonderboymusic.

We won’t be touching on 4.0.1 this meeting unless something specific comes up (nacin will be on a flight). An RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). for 4.0.1 is expected by the end of the week.

Anything else you’d like to discuss? Leave a comment.

#4-1, #agenda

In yesterday’s Weekly Developer Chat various minor schema change…

In yesterday’s Weekly Developer Chat, various minor schema change tickets were discussed. We would want to address any changes in as efficient a fashion as possible, and have discussed using the pre_schema_upgrade() function rather than dbDelta(), so we can control the queries more precisely.

Below is a list of the tickets discussed yesterday, along with which tables they affect. Please add any questions, concerns, additional tickets, or +1’s for this work in the comments.

wp_comments

  • comment_author_email#21435 – “wp-includes/comment.php line85 causes slow query due to the non-indexed column” raised by @matsubobo (proposes adding an index to comment_author_email)
  • multiple-column indexes#15499 – “Add an index for get_lastpostmodified query” raised by @simonwheatley (proposes adding an index on post_type, post_status, post_date_gmt and another on post_type, post_status, post_modified_gmt)

wp_options

  • option_name#13310 – “Extend option_name to varchar(255)” raised by @scribu

wp_posts

  • post_name#10483 – Increase field length from 200 to 400. #21212 – Reduce index length to 191 for InnoDB.
  • guid#18315 – “Add an index to the GUID column in the posts table” raised by @alexkingorg
  • post_password – #881 – “Lengthen password field for protected posts” raised by @ScytheBlade1

wp_terms

  • slug#22023 – “Remove UNIQUE for slug in wp_terms” raised by @nacin (related). #16230 – Increase field length from 200 to 400. #21212 – Reduce index length to 191 for InnoDB

wp_term_taxonomy

  • modify existing index#5034 – “Impossible to have duplicate categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. slugs with different parents” raised by @snakefoot (proposes adding an index on term_id, taxonomy, parent)

#4-0, #database

SSL taskforce

We’re hoping to make many improvements relating to SSLSSL Secure Sockets Layer. Provides a secure means of sending data over the internet. Used for authenticated and private actions./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. support in 4.0. Several fixes have already gone in over the last couple of weeks, and several are in progress.

Below is an ad-hoc list of SSL related bugs and potential enhancements that I’ve experienced in one way or another. Please leave a comment with details of other SSL related issues you are aware of (whether they’re already in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. or not). I’m going to be tackling as many issues as possible for this release. We may or may not find some time to discuss some of this during tonight’s dev meeting.

Issues with 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. front end and an HTTPS backend

  • Customiser previews break, site is requested over http
  • ‘url’ and ‘return’ links in customiser have incorrect scheme
  • Media inserted into posts gets the incorrect scheme – #32479
  • GUIDs use the adminadmin (and super admin) scheme
  • Networknetwork (versus site, blog) admin, some mixed http/https issues – #14867, #27499
  • Idea: 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. to enable plugins to specify URLs / post IDs / paths which should be forced to https?
  • Idea: filter to enforce front end over http? (excluding urls from above filter)
  • Arguments in favour of a front-end ajax handler: x-domain and x-protocol issues with domain mapping – #12400

General issues with HTTPS on front end

  • Should we force https scheme on local content in post content, post excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox., comment text, etc?… – #28521
  • Should we force https scheme using canonical? – fixed – #27954
  • Should we force https scheme for enqueued local scripts/styles? – #28521

General issues with HTTPS backend

  • Mixed content in the editor – can we force https scheme for local content? What about CDNs etc? – #28521
  • XML-RPC does not enforce https – #28424
  • Theme thumbnails aren’t loaded over https – fixed

General HTTPS issues

  • No support for secure oEmbeds – #28507
  • wp_get_attachment_url() doesn’t respect scheme – #15928
  • HSTS – not something coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. should do – could be enabled with a filter but not enabled by default – #28520
  • “Update siteurl and home as well” on network admin loses https scheme – fixed by #32503
  • SSL terminating proxies aren’t supported by default – #31288, #29708, #6778, [28610], [30090]

Issues specifically with HTTPS everywhere

  • Not all cookies have secure flag set – #28427

Metadata API/UI Meeting 04/11

As discussed in the previous meetings, we’re pushing the time back one hour from 19:00 UTC to the new time at 18:00 UTC on Fridays. We’ll be in #wordpress-coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-plugins tomorrow, April 11th, 2014 as usual.

We will be talking about the progress on form and field registration and move into some new modeling oriented based on objects (post types) instead of forms as previously discussed.

See you all there!

#fields-api, #options-meta