Author Archives: Andrew Nacin

Andrew Nacin 12:14 pm on April 15, 2014
Tags: ,   

Let’s have a meeting today

Let’s have a meeting today, Tuesday April 15, 2014, 18:00 UTC, to make sure we have everything in place for a release. (#wordpress-dev)

#3-9, #agenda

Andrew Nacin 6:00 pm on April 2, 2014  

Today’s meeting is at 20:00 UTC or exactly…

Today’s meeting is at 20:00 UTC, or exactly two hours from now. This is one hour earlier than last week, to coincide with the UK’s switch to Daylight Saving Time. Agenda here.

Andrew Nacin 11:57 am on April 1, 2014
Tags: ,   

Agenda for the April 2 meeting

Please suggest items for the April 2 developer meeting. So far:

  • The wpdialog TinyMCE 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 and the enqueuing of jQuery UIUI User interface Dialog ( #16284)
  • Transient/cache suspensions during 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. previews ( #27538)
  • Any other show-stoppers or critical issues
  • Timing of Release Candidaterelease 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). 1
  • April 16 is our target release date of 3.9

#3-9, #agenda

Andrew Nacin 5:24 am on March 27, 2014
Tags: , , ,   

TinyMCE 4.0 requires text/css for editor style files

As of TinyMCE 4.0, the visual editor iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. now has an HTML5 document type (<!DOCTYPE html>). In this scenario, CSSCSS Cascading Style Sheets. files must be served with the text/css content type. A server will serve a *.css file with the proper content type, but if you’re using a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher file for an editor style file, you need to be the one to do it. It’s as simple as leading with:

<?php
header( 'Content-Type: text/css; charset=UTF-8' );

So if you’re doing something particularly crazy with the editor and your styles aren’t loading in WordPress 3.9, you may just need a content type. Also, Chrome (and probably other browsers) throw a console warning when this happens.

(via #27288)

#3-9, #dev-notes, #editor, #tinymce

Andrew Nacin 5:08 pm on March 12, 2014
Tags:   

As a reminder the weekly meeting continues to…

As a reminder, the weekly meeting continues to be at 21:00 UTC.

Daylight Saving Time has started in the U.S., which means the meeting is at 5 p.m. Eastern time, 2 p.m. Pacific. We will revert to 20:00 UTC on April 2, after Europe enters Daylight Saving Time.

Our agenda for today will be to go over all 3.9 tasks and get an idea where we need the most resources, to ensure we are in a good position to close out the 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. period in less than three weeks.

#agenda

Andrew Nacin 6:00 pm on March 3, 2014  

Daily ticket triage meetings at 1900 UTC this week

To help realize the goal of a WordPress 3.9 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 by week’s end, let’s have daily ticketticket Created for both bug reports and feature development on the bug tracker. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions in 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. at 1900 UTC, or 2 p.m. U.S. Eastern time. (This is two hours before our usual weekly meeting.) If you’re able to join, see you in #wordpress-dev in one hour.

We have 99 enhancement tickets open. They either need to be closed or moved out of 3.9 by the end of the week. Just 20 per day will empty that report.

Of course, a number of us will be in IRC outside of these times as well, working on the same goal.

Andrew Nacin 11:29 pm on February 20, 2014  

Friday Trac Sprint

I mentioned this in the dev chat on Wednesday: Join us tomorrow (Friday, February 21) for a sprint through TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets that need a reply!

A few weeks ago I said one goal of mine for the 3.9 cycle was to make contributing easier and more accessible. That’s why so much work has gone into improving our tools in the last few months. One task is to empty one particular report of tickets: tickets that need a response. After that, I’d like to keep it empty.

As of this writing, there are 386 tickets on this report. (The report shows 441, as that includes another 55 opened by 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..) Help us empty this report!

To best coordinate a few dozen people all trying to comment on a few hundred tickets, please join us in #wordpress-dev in 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.. We’ll break these tickets into chunks, such as by age, component, or focus.

We’ll have people in IRC all day to help you out if you haven’t triaged tickets or given feedback before. There is a whole set of guidelines in the comments below. @SergeyBiryukov and @ocean90 will be around for morning in Europe, and I’ll be around starting at around 9 a.m. U.S. Eastern.

Andrew Nacin 8:15 am on February 12, 2014
Tags:   

Please suggest agenda items for the February 12…

Please suggest agenda items for the February 12 developer meeting.

Aside from usual 3.9 stuff, we’re going to be using part of this meeting for brainstorming for GSoC.

Here’s the agenda thread and meeting notes from last week, as a point of reference.

#agenda

Andrew Nacin 3:06 pm on February 6, 2014
Tags:   

Here’s a quick summary of yesterday’s meeting as…

Here’s a quick summary of yesterday’s meeting (IRC log), as a status report on WordPress 3.9:

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 will now be the week of March 3, a week later. The rest of the schedule is unchanged. I felt the extra week of alpha would be helpful given all of forward momentum right now, and others seemed to agree.

It was decided to green-light the widget customizer plugin for merge. If all goes well, it’ll be in 3.9 final. There’s still a lot to do: some UIUI User interface polishing, deeper code review, etc. — and surely it will get a lot of testing.

Quick hits raised in the meeting:

  • Settings review is in the ideas/sketch/wireframe stage. They have a meeting today. (@jenmylo, @melchoyce)
  • Lots of audio/video changes landed. Needs review on #27026 and UI feedback on #26631. (@wonderboymusic)
  • Work continues bringing the image editor into the media manager. #21811. (@gcorne, @tomauger)
  • TinyMCE/editor: modals are getting redesigned. #26952. (@melchoyce, @avryl) QUnit tests are being added. #27014. (@azaozz) @gcorne also sunk some time into MCE views, for gallery rendering.
  • THX 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 is being revived to take a crack at the theme install screen. If it works out, these patches could land in 3.9. (@matveb)
  • A Grunt 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. tool needs testing. #27023. (@jorbin)
  • Some refactoring of the 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 bootstrap will begin this week. #27003. (@jeremyfelt)
  • Volunteer(s) wanted: If anyone wants to work on expanding autocomplete in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., there is some work in that area to be done. @helen will help shepherd.

We have a few more weeks of alpha, so it’s a great time to help with writing or testing a patch for WordPress 3.9. We’ll be keeping the tempo quick. Expect lots of changes.

#3-9

Andrew Nacin 8:44 pm on February 5, 2014
Tags: ,   

Fine-grained Trac notifications

Some housekeeping items to share so I don’t need to cover it in the meeting today:

New notification preferences are live. On the notifications page, you’ll be able to subscribe to activity from all tickets in a particular milestone, component, or focus. You can also subscribe to only new tickets, in case you want to then selectively watch tickets as they come in.

New greeting on make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Look up. Or if you’re viewing this post directly, check out the homepage. Right now the “Get Involved” menu item leads you to there, but it’d been tough to know where to go from there. This serves to introduce new people and get them information quickly: what this blogblog (versus network, site) is, where to file a 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., how to start contributing; and provides some info about 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 our meetings.

New, simpler new ticketticket Created for both bug reports and feature development on the bug tracker. form: I simplified the new ticket form, cleaning up the warnings, text, and chrome (it had a lot of borders and fieldsets and such). It looks much less intimidating now.

New ticket reports and component pages. These went live late last week — here and here.

Create a new ticket This was also helpful because we shifted around where you can go to create a new ticket. You can now do it from search results, all ticket reports and the main reports screen, component pages, the icon in the navigation, and now from the make/core homepage. The new reports screen is a new entry point for TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. You’ll note it actually duplicates the content of Trac’s home page (new ticket button there too), which you’ll have trouble finding a direct link to anywhere.

Focuses/components: Component and focus triaging is pretty much done. (More than one thousand open tickets — 30% — have been modified in the last two weeks alone.) Still have some decisions to make about the Administration component, but I’m not worried.

And with that, I actually have no more changes planned for core trac. Except for ticket smashing. It’s now time to start clearing these two reports: Tickets without a response and Tickets that are ancient and inactive. Who is with me?!

Thanks also @ocean90 for replacing every last icon in Trac with a Dashicon. Love it.

#housekeeping, #trac