Make WordPress Core

Tagged: agenda Toggle Comment Threads | Keyboard Shortcuts

  • Drew Jaynes 7:00 am on January 28, 2015 Permalink
    Tags: , agenda   

    Dev Chat Agenda, January 28, 2015 

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

    Time/Date: January 28 2015 21:00 UTC:

    • Kickoff Part II – Let’s talk a little bit about how we’re going to structure this release from week to week:
      • Monday Jumpstart posts
      • Bug scrubs
      • Ticket management
      • Mentoring
    • #5809 – Term splitting update (@boonebgorges)
    • Feature Plugins – Status updates from the three feature plugin leads:
      1. Customizer Theme Switcher – @celloexpressions
      2. Press This revamp – @michael-arestad
      3. Shiny Updates – @pento
    • WordPress Core Weekly@dh-shredder is looking for help with compiling the weekly activity roundup
    • Accessibility – Introduce the weekly hitlist and talk about accessibility priorities for 4.2
    • Mobilemake-flow tickets from @boren:
      • #29906 – Submenus can’t be dismissed on mobile.
      • #29989 – Hide Media Buttons on small screens
    • Open Floor – If you have something you’d like to bring to the table to discuss, leave a note in the comments
    • Weston Ruter 7:13 am on January 28, 2015 Permalink | Log in to Reply

      I’d love more thoughts and feedback for Customizer transactions: https://make.wordpress.org/core/2015/01/26/customizer-transactions-proposal/

      If not concerns, then more green lights and thumbs up.

    • Nick Halsey 7:54 am on January 28, 2015 Permalink | Log in to Reply

      I can’t make the meeting most weeks this semester due to class, but current status is that @sheri and @mikelking are both working on user testing and we’re fixing a few minor issues as they come up. I’m planning on tackling the remaining issues listed in my update post this weekend, and posting another update before our next meeting next Tuesday.

      I do read the logs, so I’d appreciate any general feedback that comes up during the meeting, as well as feedback submitted through other mediums.

      I’d also like to add to the agenda under Mobile to bring up #28784. Especially as we add more things to the Customizer, we really need to make it more usable on smaller devices. Shouldn’t take nearly as much effort as places like the media modal to make improvements here in 4.2, but we need eyes and patches there. The controls UI is already mobile-first, it’s really just a matter of making the controls/preview toggle more intuitive as a toggle here.

    • Paal Joachim Romdahl 1:16 pm on January 28, 2015 Permalink | Log in to Reply

      A few open questions that come to mind.

      What happened to beginning talks on revamping Settings?

      Further along a similar thread…..Any plans on discussions about which areas of priority in the WordPress backend need updating? (Of course this would be a huge discussion but one that is needed.)

    • Boone Gorges 2:03 pm on January 28, 2015 Permalink | Log in to Reply

      Splitting shared terms #5809. We’ve got some dev-facing documentation drafted, and will be soliciting feedback in the next few days.

    • Paul Bearne 2:11 pm on January 28, 2015 Permalink | Log in to Reply

      Can we look at workflow where unit tests for existing (working) code can get committed quickly so that we can encourage increasing the test coverage.

      I started to write tests for functions.php but have got discouraged as there is no clear way to get a pure unit test patch commented. I would thought that we should be able to these committed quickly.

      Here is couple tickets with mostly test patches but in both cases I found issues and this why I want to see this work done.


      We had a big project to get comments for actions / filters doing the same for Unit tests would be good

      • Boone Gorges 6:30 pm on January 28, 2015 Permalink | Log in to Reply

        Paul – Of note, we are no longer committing failing tests; see #30284. So, when creating a patch that contains tests, it’s wise to separate out those tests that are currently passing, since only *they* can be committed immediately (and be sure to note this point in your comment when posting the patch).

    • tohit 4:47 am on February 4, 2015 Permalink | Log in to Reply

      Hi Drew Jaynes,

      How can i join this meeting agendas ?
      Please help me to get participate in this.


  • John Blackbourn 5:04 pm on January 7, 2015 Permalink
    Tags: , , agenda   

    January 7th meeting agenda 

    The first meeting of the new year and our first post-4.1 meeting. January 07 2015 21:00 UTC. We’ll split this between items for 4.1 and 4.2.

    • 4.1 debrief
    • 4.1.1
    • Review 4.2 schedule
    • Feature plugins for 4.2 and beyond
    • AOB
  • Andrew Nacin 7:46 am on December 24, 2014 Permalink
    Tags: , agenda   

    Let’s cancel today’s weekly meeting, since the holidays are starting for some of us (and ending for some others).

    It can be open office hours* if anyone is around (I doubt I will be), but everyone (@johnbillion especially!) deserves a nice break for a great WordPress 4.1 release. It’s already been downloaded 2.5 million times, there’s been a lot of great feedback, and I also haven’t seen anything major reported. I just triaged about 40 recent tickets to be sure. Check out the 4.1.1 ticket report.

    Please check that report when you have time to see if there’s a ticket you should be giving feedback on. For example, I see stuff for @azaozz and @avryl (#30696), @helen (#30813), and @obenland (#30831). Again, nothing important, so enjoy any break you may be taking. Happy holidays!

    I suspect next week (New Year’s Eve) will be an informal meeting, as it’ll be only the afternoon for those in the U.S.

    * Keep in mind people are in the #core channel on Slack all the time, so it’s really 167 hours of office hours per week, plus one meeting.

  • John Blackbourn 4:15 pm on December 10, 2014 Permalink
    Tags: , agenda   

    Release candidate and today’s dev meeting agenda 

    4.1 was originally due for release today, but a few tickets in the 4.1 milestone have held things up a little. The release candidate will be tagged in time for today’s dev meeting at December 10 2014 21:00 UTC, and the target release date is now Monday, December 15th Tuesday December 16th.

    Here’s the agenda for today’s dev meeting:

    • Documentation from various make/core posts need to go into the plugin handbook and theme handbook.
    • The 4.1 page on the Codex is in progress.
    • Eyes on the support forums – the alpha/beta forum has seen almost no activity so we need eyes on the forums as a whole.
    • ‘About’ page design – @melchoyce, kelly, @helen #30435
    • Plugin developers – update your plugin’s readme files to indicate support for 4.1 once RC1 is released. You’ve tested all your plugins with the beta, yeah?
    • Looking for something to do? Tickets reported against trunk needs some continued triaging.
    • Status of plugin directory l10n and recommended plugins tab. @stephdau @tellyworth
    • Discuss status of l10ns for polyglots.
    • Discuss a status update meeting type thing on Sunday.
    • Discuss release plan. @nacin
    • Any other business.
    • Jeff Chandler 7:26 pm on December 10, 2014 Permalink | Log in to Reply

      One possible reason for the Alpha/Beta forums having low activity is that there hasn’t been much in the way of beta release communication on the WordPress.org development blog. There’s a small mention of a beta at the bottom of the 4.0.1 security update post but that’s from Late November. Hopefully, news of the RC1 release will be published on the official blog and that might get things going again on those forums.

      In that post, I’d also like to see specific items you want people to test.

    • Stephane Daury (stephdau) 8:39 pm on December 10, 2014 Permalink | Log in to Reply

      Plugin Directory l10n

      I’ve just uploaded a major milestone to #760-meta which bring the complete solution to life, as what I’d qualify as a sophisticated proof-of-concept (as in still needs a lot of work/testing but shows everything off):

      • code & readme translation processing
      • localized directories content translation display (wporg code already use gettext for its strings, that’s covered)
      • translation caching policy, as well cache expunging on interaction with translate.wordpress.org (imports, edits, etc)
      • api content translation display when passed a language param (arbitrary, not set-in-stone)

      See screenshots showing it in action here: https://cloudup.com/cmAHT9qu2Wx

    • Lance Willett 8:56 pm on December 10, 2014 Permalink | Log in to Reply

      For release plan, I’ll be on duty to prepare new versions of default themes for submission to Themes directory.

    • Michel - xiligroup dev 12:48 pm on December 11, 2014 Permalink | Log in to Reply

      Just a question of release : why when, testing feature on a temporary website, updating from admin from 4.1beta2 …734, we arrive directly to 4.2 alpha… and with no RC release…
      Please tell how to fin RC nighty build

    • conservativeread 1:06 pm on December 11, 2014 Permalink | Log in to Reply

      same issue here updating from admin from 4.1beta2 we arrive directly to 4.2 alpha

    • Xavier Borderie 2:03 pm on December 11, 2014 Permalink | Log in to Reply

      @michelwppi @conservativeread As discussed on Slack, “[the developers] branched 4.1 a bit earlier this time, that’s why you’re getting 4.2-alpha. The plugin gives you the nightly build from trunk, not the branch.”

    • Michel - xiligroup dev 4:18 pm on December 11, 2014 Permalink | Log in to Reply

      @[the developers]
      Branching is practical for developers… but not for ‘devoted’ testers… the update page in WP dashboard is unusable with / for RC versions… So need to use again FTP client even on localhost… and avoid again to go to 4.2 alpha… I am sure that developers can solve the UX issue 😉

      • Knut Sparhell 5:09 pm on December 11, 2014 Permalink | Log in to Reply

        I second this. I was really annoyed by experiencing the beta tester plugin took me to 4.2.alpha insted of 4.1-RC1. If you (leads) are going to branch out before last RC in the future please give us a beta tester with three options (point releases, beta/RC or trunk). Those who always want latest alphas select trunk, betaRC-testers select beta/RC. During the cycle we can change option from trun to btea/RC to avoid this, and still have alphas at the start of a cycle.

  • John Blackbourn 7:14 pm on November 26, 2014 Permalink
    Tags: , agenda   

    Agenda for today’s dev chat in #core Slack (November 26 2014 21:00 UTC).

    • Stephane Daury (stephdau) 7:25 pm on November 26, 2014 Permalink | Log in to Reply

      Under “Any other business”: progress on plugin directories (code/readme) internationalization:

      • Good progress, got both plugin code and readme processing (in practice), and GlotPress import (in theory for now).
      • Examples of POT file extracted from IRL readmes: https://cloudup.com/c4-PkWGb7mG
      • Currently: dealing with makepot.php expecting the plugin directory name to match the plugin slug (not so with tmp file), last hurdle before GP import.
    • Alex Shiels 9:04 pm on November 26, 2014 Permalink | Log in to Reply

      Unfortunately I can’t hang around, but I’d like to give #30337 a quick plug – it could use feedback.

  • John Blackbourn 7:00 pm on November 19, 2014 Permalink
    Tags: , agenda   

    Agenda for November 19th dev chat 

    Agenda for today’s dev chat in #core Slack (November 19 2014 21:00 UTC).

    Current status: A little over 100 tickets in 4.1 milestone

    • John Blackbourn 7:15 pm on November 19, 2014 Permalink | Log in to Reply

      • Stephane Daury (stephdau) 9:21 pm on November 19, 2014 Permalink | Log in to Reply

        As I’m going to have to take off before the chat ends, here’s where things are at:

        The system will work as follow:

        • monitors plugins.svn.wordpress.org
        • on commit, and based on a being-determinded trigger logic, we:

        * process the codebase using makepot.php
        * and/or extract translatable strings out of the parsed readme (paragraphs, list items, etc) using code I’m working on right now
        * either or both will give us a tmp pot file

        • we take the pot file and import it to glotpress, to approriate project (using existing import scripts for that)

        * code EG: https://translate.wordpress.org/projects/wp-plugins/wordpress-importer/dev
        * readme EG: https://translate.wordpress.org/projects/wp-plugins/wordpress-importer/dev-readme

        We’d now have community translation for both code and readme, for a dev and stable branch for each plugin.

        • ReadMe is kept in own GlotPress “project” because it’s used in far fewer contexts than the code’s, so we didn’t want to burden the code pot/po/mo files with the readme’s content.
        • We’ll be using https://translate.wordpress.org/projects/wp-plugins/ (might be renamed “plugins”). Was told it’ll scale.

        Next step is to use the data:

        • for plugin directory pages and API responses:

        * when accessed on localized site, or when passed a language (API), we’ll take the plugin slug
        * we query the glotpress db directly for all readme approved strings for plugin
        * we loop on them and regex replace them out of the readme content (bbpress topic_content)
        * cache the heck (long ttl) out of that (per readme section)
        * display

        That covers displaying on the sites (wp.org, fr.wp.org, etc), as well as in core, via the wp.org plugin API, since we’re already passing the local install’s laguage when querying it.

        I’ll leave the language packs part to @nacin to explain, it’s his baby :)

    • Kim Parsell 8:24 pm on November 19, 2014 Permalink | Log in to Reply

      I’d like to add #30405 to the discussion list. The Beta Tester plugin isn’t auto-updating my local installs (bleeding edge nightlies) as of today.

    • Boone Gorges 8:26 pm on November 19, 2014 Permalink | Log in to Reply

      Could I request that #30335 be moved up in the order a bit? I have to leave the meeting after the first hour and I want to make sure I’m there for the discussion.

  • Drew Jaynes 7:23 pm on November 5, 2014 Permalink
    Tags: , agenda   

    Agenda for today’s dev chat in the #core channel on slack (November 5 2014 21:00 UTC):

    • Beta/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 test 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 regression?
    • Focus #29806: Patch for editor focus v2 looks good. @markjaquith will be posting a merge request update on make/core. @johnbillion will decide whether to merge on Thurs/Fri
    • Sessions UINeeds a ticket, #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)
    • Taxonomy 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 bug scrubs on Friday this week, likely a mixture of a11y and 4.1 tickets
  • John Blackbourn 7:27 pm on October 22, 2014 Permalink
    Tags: , agenda   

    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 sidebar scrolling behaviour.
    • 4.1 Beta 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 UI changes, how shall we progress?
    • IRC meeting schedules: @drewapicture
    • Editor focus: needs a decision on default behaviour, user testing, anything else?
    • User/Post Dropdown Performance: status update
    • Meta/Term/Date Query Enhancements: lots of progress. Any other blockers?
    • User session UI, currently awaiting w.org geolocation API details.
    • Friday’s bug scrub coming LIVE from San Fran.
    • Any other business.
  • John Blackbourn 7:48 pm on October 15, 2014 Permalink
    Tags: , 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 plugin we have scheduled for 4.1 is the user session management UI 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 bug scrubs starting Friday.
    • Status of the plugin install/update UI improvements.
    • Volunteers for some mobile media testing.
    • Updates from @helen @markjaquith @boonebgorges on their respective focuses.
    • Any other business.
  • John Blackbourn 7:30 pm on October 8, 2014 Permalink
    Tags: , agenda   

    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 UI feature plugin.
    • 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).
    • Pascal Birchler 11:11 am on October 9, 2014 Permalink | Log in to Reply

      It feels like WordPress 4.1 is already coming along nicely. And you even put birthday wishes on the agenda. Cool! I’ll definitely attend the dev chat on my birthday :)

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
Skip to toolbar