Ready to get started?Download WordPress

Make WordPress Core

Tagged: agenda Toggle Comment Threads | Keyboard Shortcuts

  • Andrew Nacin 12:14 pm on April 15, 2014 Permalink | Log in to leave a Comment
    Tags: , agenda   

    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)

  • Andrew Nacin 11:57 am on April 1, 2014 Permalink | Log in to leave a Comment
    Tags: , agenda   

    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
  • Andrew Nacin 5:08 pm on March 12, 2014 Permalink | Log in to leave a Comment
    Tags: agenda   

    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.

    • Robert Chapin 6:06 pm on March 12, 2014 Permalink | Log in to Reply

      It looks like I can join at least the first half of the meeting. There have been several iterations of the patch for #22692. It should be a comprehensive fix at this point. It will adjust quotes, smilies, and shortcodes so that their behaviors are normal in the presence of NBSP chars and entities. It also paves the way for refreshing patches in #26842, #8775, #20342, #23185, and many others. We could potentially clear out half of the wptexturize tickets if this gets the attention it deserves.

  • Andrew Nacin 8:15 am on February 12, 2014 Permalink | Log in to leave a Comment
    Tags: agenda   

    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.

    • Jen Mylo 8:21 am on February 12, 2014 Permalink | Log in to Reply

      If people want to write up their ideas for GSoC projects in advance, that would be great in terms of keeping things going. I’ll be submitting our GSoC application immediately following the dev chat, so if anyone has ideas but won’t be at the meeting, go ahead and post them at http://codex.wordpress.org/GSoC2014. Thanks!

    • Rami Yushuvaev 12:20 pm on February 12, 2014 Permalink | Log in to Reply

      How about a “Road Map” for upgrading the minimum requirements to PHP 5.4 and MySQL 5.5 (or any other version you choose). The purpose of the roadmap is to set a time frame, not choosing technology.

      The roadmap should be spread over a long period of time (let’s say 2 years from now), enough time for web hosts to make the proper adjustments. WordPress has three major version per year, this means WordPress 4.4 will require the new minimum requirements.

      The road map will not be a binding, meaning that if core developers will decide to upgrade the minimum requirements in wp4.6 or wp4.8 the road map can be changed. BUT, setting a time table is important, for plugin developers, web hosts, and core developers. It allows everyone the get ready for the upcoming change.

      • Bryan Petty 7:34 pm on February 12, 2014 Permalink | Log in to Reply

        It’s been mentioned many times that we should not become “a protest piece at the expense of our users”, and this is specifically mentioned in regards to setting hard deadlines for bumping minimum server requirements. We cater to our users, not dictate what they need by abandoning millions of users at arbitrary points, especially if they still account for more than 10% of WP installations.

        We still haven’t dropped PHP 5.2 support, and given the rate of use shown in the stats, that still isn’t happening for another couple years. Dropping 5.3 is probably more than 5 or 6 years down the road, and isn’t even worth thinking about right now.

        When the time comes, you can be assured there will be plenty of notice, but it won’t even be necessary for most since it will only apply to less than 10% of users.

    • Dominik Schilling (ocean90) 3:11 pm on February 12, 2014 Permalink | Log in to Reply

      State of #27078 (Autoprefixer), #26669 (wp-admin.css split) and #26799 (Backbone update).

    • Daniel Bachhuber 3:29 pm on February 12, 2014 Permalink | Log in to Reply

      I’d like to discuss #316 if it’s not too big of a conversation.

    • Tom Auger 4:47 pm on February 12, 2014 Permalink | Log in to Reply

      Let’s talk about all the great things that are happening with the Image Editor and Media Modal. I’m seeing the following tickets which are all tangential to each other: #24409 (which is awesome), #26672, #24567, #18947, #26870 (thank the gods), #21811 (which has turned into a much bigger deal than I thought) and #21810 (which seems to be a refresh of #19889).

      This all seems like “a thing”. @wonderboymusic, @gcorne and others seem to have things well in hand, but I’d like to see a little more sharing around all the great things that are going on, and where help / discussion / review is needed.

    • Aaron Jorbin 8:54 pm on February 12, 2014 Permalink | Log in to Reply

      I’d love to find out if anyone else has comments on #27023 and if people think grunt-patch is ready for me to tag it in npm and for us to add it.

    • Andrew Nacin 8:56 pm on February 12, 2014 Permalink | Log in to Reply


      • CSS/JS: Autoprefixer #27078, wp-admin.css #26669, Backbone update #26799
      • 3.9 status reports for teams/projects/tasks
      • Widgets Customizer merge: old style widgets + options API issue (details in the meeting)
      • Any other logjams or stuck situations we need to address
      • GSoC brainstorming

      We can hopefully get through all but the last point pretty quickly.

  • Andrew Nacin 3:26 am on February 5, 2014 Permalink | Log in to leave a Comment
    Tags: , agenda   

    Please suggest agenda items for the weekly developer meeting, Wednesday, February 5, 21:00 UTC.

    If there’s a task or ticket we need to work through, or need volunteers for, let’s get those spelled out now. Maybe we can even work through some of them pre-meeting.

    I’ll again be asking for a sentence or two (or more, if necessary of course) from each person/team working on a 3.9 task. You can also post those here if you’d like — please cross-reference any relevant tickets or discussions. Worked out great last week. For the state of things as of last week, see Mike’s weekly roundup.

    • Pippin Williamson 4:05 am on February 5, 2014 Permalink | Log in to Reply

      Not sure if there’s much discussion needed on them, but I’d love to see the remove/has_image_size() tickets shored up:


    • Jeremy Felt 4:19 am on February 5, 2014 Permalink | Log in to Reply

      I’d like to chat a bit about the direction of domain routing. I’ll be around pre-meeting as well.

      I opened #27003 last night with a patch that introduces `wp_get_network()` as a way to retrieve a network by it’s domain and path. This isn’t an absolutely necessary abstraction from `wpmu_current_site()`, but it does remove the functionality away from the `$current_site` global and focuses on retrieving just the requested information. In the process, `wpmu_current_site()` gets cleaned up quite a bit. It should be pretty straight forward to write unit tests that cover `wp_get_network()`.

      IMO, this is a first step toward cleaning up a bit of the load process. If we’re good with this direction, the next step will be to do the same thing for site discovery ($wpdb->blogs). I have more notes written up here on the multisite load process in general for anyone that wants an overview of how things are working.

    • Pippin Williamson 5:17 am on February 5, 2014 Permalink | Log in to Reply

      I’ll throw out another one. I’d LOVE to see further discussion on better custom comment types, per https://core.trac.wordpress.org/ticket/12668

    • Weston Ruter 8:14 am on February 5, 2014 Permalink | Log in to Reply

      There was a really good discussion today on #wordpress-dev regarding feedback for Widget Customizer. So I think we have a path forward for important issues to address. I’ve created a milestone on GitHub to track these issues: https://github.com/x-team/wp-widget-customizer/issues?milestone=4&state=open

    • Robert Chapin 11:27 am on February 5, 2014 Permalink | Log in to Reply

      3.9-early tickets, please

    • Manuel Schmalstieg 12:49 pm on February 5, 2014 Permalink | Log in to Reply

      For international users, improving the handling of accents/diacritics in file attachments would be a big win: https://core.trac.wordpress.org/ticket/22363 – the ticket has patches, and @markoheijnen has proposed it for 3.9 …

    • Tom Auger 7:59 pm on February 5, 2014 Permalink | Log in to Reply

      I’d like to discuss https://core.trac.wordpress.org/ticket/21811 and see if my patch / suggestions are salvageable, given the much bigger development effort around the entire Media Modal. The feature I was working on (prior to the whole Media Modal overhaul) was a very small, targeted, incremental enhancement that was kinda “shoehorned” in under that trac ticket, but really addresses something different and much smaller in scope.

    • Tom Auger 8:37 pm on February 5, 2014 Permalink | Log in to Reply

      Update: I see @gcorne has done some great work demonstrating how this could get integrated into Media Modal. I’ll continue this week and see if I can bring these things together. As for today’s meeting – we just got massively dumped on in Toronto, so I’ma head out of the office now and may not get back online in time to catch this week’s meeting.

  • Andrew Nacin 12:13 pm on January 29, 2014 Permalink | Log in to leave a Comment
    Tags: , agenda   

    Please propose agenda items for the development meeting today at 21:00 UTC. Let’s try to keep it to under an hour, like last week’s.

    Some to start us off:

    • Consider the Widgets Customizer plugin for 3.9 merge. If you haven’t looked at it yet, please spend some time today before the meeting. Obviously, we all like the idea, but we need to study the implementation and provide feedback. Please comment on that post if you haven’t already.
    • I’d like to propose an initiative for cleaning up a group of 556 tickets during the 3.9 cycle. (It has details, will explain in the meeting.)
    • Quick situation reports for various 3.9 tasks. If you’re working on something, please come armed with a sentence so we can do these rapid-fire — or post it in the comments thread. Some things are moving forward quickly, some aren’t. Where can we help? Here’s a list of what was proposed for 3.9 (see also the comments, which were updated after the last meeting). We need to take the “proposed” label off soon…
    • I’d like to get moving on the Trac component re-organization; I’ll see if there are any questions. We will need some help to move around tickets (ideally adding feedback to them along the way), so I’ll be looking for volunteers and talking about what is needed.

    Aren’t familiar with how these meetings work? They’re especially good for breaking logjams — whether that means talking through a major sticking point, finding volunteers to help with something. We also use them to plan out schedules and tasks, make sure everyone is on the same page, and do release post-mortems to see how things went. (As 3.8.1 was released on Thursday, could be good to discuss this and 3.8.2, for example.)

    The meeting takes place in IRC on chat.freenode.net in the #wordpress-dev channel. See you then!

    • William Bowles 12:27 pm on January 29, 2014 Permalink | Log in to Reply

      I like it! One of the problems with WP has always been the amount of time spent moving between the various components that make up the site. I’d like to see a lot of the backend stuff move to the Customize sidebar and the popout access to other widget tools seems to work perfectly.

    • Tom Auger 2:06 pm on January 29, 2014 Permalink | Log in to Reply

      I have moved forward with https://core.trac.wordpress.org/ticket/21811. Still trying the time to upload an actual patch, but could use some eyes on the last two plugin ZIPs that were uploaded to see whether there’s any buy-in on my proof-of-concept approach to modularizing the Image Editor.

    • Tom Lynch 2:43 pm on January 29, 2014 Permalink | Log in to Reply

      I’d suggest considering talk around some of the older parts of wp-admin that have static coded HTML tables that don’t have any hooks or filters, nor use the Settings API to actually make it possible for people to develop management plugins.

    • John Blackbourn 3:11 pm on January 29, 2014 Permalink | Log in to Reply

      We should have a think about how we can start to build this new “easy first bug” report on Trac.

    • Jen Mylo 3:28 pm on January 29, 2014 Permalink | Log in to Reply

      GSoC 2014. I’ll post about it on this blog before the meeting, but would like to take a few minutes during the chat to discuss areas of interest for projects and people who’d be interested in mentoring/co-mentoring so I can get the application started.

    • Andrew Ozz 4:16 pm on January 29, 2014 Permalink | Log in to Reply

      Decide on JavaScript actions and filters, https://core.trac.wordpress.org/ticket/21170. We need JS hooks in core, either our own implementation or standardize on jQuery( document ).trigger( 'event-name' ). I know @koop had more thoughts on this but he hasn’t been around for a while.

    • tomdryan 4:17 pm on January 29, 2014 Permalink | Log in to Reply

      I may not be able to make it today, but I would like to propose creating a new task force that can look at existing plugins that would be good candidates to get moved into core. Most of the core efforts appear to be in developing new functionality, which is critical, but there are existing plugins that also fix gaps in the core feature set. The goal would be to identify those plugins and approach the authors to see what there interest level is in contributing their code to core. This approach unitizes WP excellent plug in architecture and plug in community to move WP core forward more rapidly.

      I love to hear comments about this idea (post here). I’ll try to make it to today’s meeting, but if not, I love to talk about this subject in the near future.

    • Bryan Petty 6:07 pm on January 29, 2014 Permalink | Log in to Reply

      I have an upstream update to PHPMailer in #25560. There are a couple decisions that still need to be made: include the full library, or strip it down without docs, tests, and examples (both patches are there), and a quick review of the approach on back-compat. This does need to in early in the cycle though, so about now is a good time, and hence why I bring it up now.

  • Andrew Nacin 8:25 pm on December 18, 2013 Permalink
    Tags: agenda   

    Proposed agenda for today’s dev chat (~35 minutes from now):

    • Initial debrief for 3.8. Start to think about what we can learn from 3.8.
    • Status report of bugs/regressions for 3.8.1. Look at a tentative 3.8.1 timeline.
    • Initial 3.9 discussion. Discuss potential feature plugin candidates, timeline, and release leads.
  • Andrew Nacin 7:14 pm on November 1, 2013 Permalink
    Tags: , agenda   

    @matt will be running a WordPress 3.8 feature planning/decisions meeting on Monday, November 4, 21:00 UTC. Now that Daylight Saving Time has ended for both Europe and the U.S., note that the weekly Wednesday meeting is now moved from 20:00 UTC to 21:00 UTC (4 p.m. EST, 1 p.m. PST). (Americans, change your clocks on Sunday.)

    I’d strongly encourage everyone to study, test, and weigh in on the four 3.8 proposals before the meeting. I believe the goal of the meeting will be to establish what exactly gets merged into 3.8.

    API enhancements, bug fixes, etc. can/will continue as usual — it would be awesome if we had a surge not unlike 3.7. But for now, 3.7.1 is out, so stare at the download counter sip some tea, and relax this the weekend. :)

  • Andrew Nacin 5:29 pm on October 16, 2013 Permalink
    Tags: , agenda   

    Agenda for today’s meeting in #wordpress-dev at 20:00 UTC.

    • Go over the last few days of progress, as well as what we’ve been learning via statistics for background updates. (Spoiler: excellent.)
    • Need a commit or revert on #20316 (garbage collect transients). It has a patch — the queries need testing and review.
    • Need a decision on #24963 (IIS stuff).
    • Finalize the about page. It’s going to be text-heavy as there’s nothing to show off UI-wise. What about a single giant three-column image across the top? I mean, it can be a picture of a sunrise for all I care. Or some screenshot of the WordPress admin. Or some photos from the crowds at WordCamp San Francisco and WordCamp Europe. Anyone have any ideas?
    • WordPress 3.7 Release Candidate 1 (by tonight).
    • Branch WordPress 3.7 (after RC1).

    @dd32 and I are working on #10787 this afternoon as well.

  • Andrew Nacin 7:38 pm on September 25, 2013 Permalink
    Tags: , agenda   

    Meeting today: Road to WordPress 3.7 Beta 1 

    For the meeting today (starts in ~20 minutes), we need to work on getting to 3.7 Beta 1. I think if all goes well, we can release Beta 1 tonight or tomorrow morning. @dd32 has been doing some incredible work on automatic updates. If you haven’t read his post on them, please do!

    So, there are a few things we need to discuss and make decisions on:

    1. Search results ordered by relevance, #7394. Do we take a chance on this?

    2. Should we begin to require that users supply their current password in order to change their password? #20140.

    3. Should we consider a slightly more conservative different approach to transient garbage collection? We do not want updates to be blamed for breaking sites. #20316. What would this approach look like?

    4. How should individuals be notified via email when it comes to automatic background updates? #10787.

    5. How should individuals be notified their own dashboard that their site will be safe if there is a security release?

    Proposal for points 4 and 5: A green checkmark on about.php and update-core.php will let them know their install is OK and good to go for automatic background updates for security releases. (We can easily verify this without prompting the user.)

    If for some reason we attempt an automatic background update and it fails to complete, then we need to email get_site_option( 'admin_email' ). We need text for this email.

    If they don’t have a green checkmark, we should wait five days, after which we email them reminding them a security release is available. A timestamp five days from the point of release will be pushed via the API. Once that time is crossed, an email will be sent. (For a particularly critical situation, we could shorten the timeframe. For a non-security minor release, we might avoid having an email sent all together). We also need text for this email (which will be a fairly nice email).

    This does not accomplish all of #10787 (“Email administrators that an update is available for core, plugins, and themes”) but it seems to be a good security balance.


    My target is Beta 2 early next week, and Release Candidate 1 as early as next Friday. Here is our current progress on tickets:

    • There are no more enhancements or feature requests open on the 3.7 milestone.
    • There are under 20 tasks remaining for 3.7. Many of these are near completion. These need to be cleared by Beta 2.
    • There are 150 bugs open on the 3.7 milestone. We need to reduce this number to about 75 by Friday, and to zero by the end of next week. As in, these need to be cleared by RC1.

    We’ll likely branch 3.7 at the WordCamp Europe contributor day on October 7, which means anything that is punted out of 3.7 can still make it into 3.8 starting in just two short weeks from now. A reminder, this is a very short release cycle, and 3.8 is just a few months away and begins in earnest very soon. Here is what our philosophies document says about fast, agile release cycles with crisp deadlines:

    The more frequent and regular releases are, the less important it is for any particular feature to be in this release. If it doesn’t make it for this one, it’ll just be a few months before the next one. When releases become unpredictable or few and far between, there’s more pressure to try and squeeze in that one more thing because it’s going to be so long before the next one. Delay begets delay.

    If we’re not confident that three weeks is long enough for something to properly soak in trunk, let’s not be afraid to wait until 3.8.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc