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

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.

Agenda for the April 2 meeting

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

  • The wpdialog TinyMCE plugin and the enqueuing of jQuery UI Dialog ( #16284)
  • Transient/cache suspensions during widget previews ( #27538)
  • Any other show-stoppers or critical issues
  • Timing of Release Candidate 1
  • April 16 is our target release date of 3.9

#3-9, #agenda

TinyMCE 4.0 requires text/css for editor style files

As of TinyMCE 4.0, the visual editor iframe now has an HTML5 document type (<!DOCTYPE html>). In this scenario, CSS 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 PHP 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

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 beta period in less than three weeks.

#agenda

Daily ticket triage meetings at 1900 UTC this week

To help realize the goal of a WordPress 3.9 Beta 1 by week’s end, let’s have daily ticket triage sessions in IRC 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.

Friday Trac Sprint

I mentioned this in the dev chat on Wednesday: Join us tomorrow (Friday, February 21) for a sprint through Trac 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 committer.) 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 IRC. 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.

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

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:

Beta 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 UI 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 plugin 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 patch tool needs testing. #27023. (@jorbin)
  • Some refactoring of the multisite bootstrap will begin this week. #27003. (@jeremyfelt)
  • Volunteer(s) wanted: If anyone wants to work on expanding autocomplete in core, 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

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/core. 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 blog is, where to file a bug, how to start contributing; and provides some info about IRC and our meetings.

New, simpler new ticket 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 Trac. 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