WordPress.org

Tagged: agenda Toggle Comment Threads | Keyboard Shortcuts

• 

  Gary Pendergast 1:26 pm on February 25, 2015 Permalink | Log in to leave a Comment
  Tags: agenda, emoji ( 4 ), x1f4a9 ( 4 )   

  Emoji Chat Agenda, February 25, 2015 

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

  Time/Date: Immediately after the Dev Chat.

  1. Emoji Helper – On platforms that don’t have an emoji keyboard, should we provide one?
  2. Performance – When we’re falling back to Twemoji on large pages, we have to consider how it will perform. Are there faster ways of replacing the emoji characters with images?
  3. Open Floor – There’s still time to rant about the evils of emoji! Let us know how you really feel.
   

  Reply Cancel reply

  You must be logged in to post a comment.

• 

  Drew Jaynes 12:00 pm on February 25, 2015 Permalink | Log in to leave a Comment
  Tags: 4.2 ( 28 ), agenda   

  Dev Chat Agenda, February 25, 2015 

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

  Time/Date: February 25 2015 21:00 UTC:

  0. Feature Plugins – The Customizer Theme Switcher and Press This were merged into core on Tuesday. Please test and create new tickets for any issues you find
  1. Component Updates
     1. Accessibility – @afercia
     2. Mobile – @ryan
     3. Components – All the news that is news with @nacin
  2. Enhancements Deadline Reminder – Beta 1 is 2 1/2 weeks away. Need to start wrapping up enhancements.
  3. Open Floor – Looking for dev feedback on a ticket? Use this part of the meeting to let us know

  Ryan Boren is discussing. Toggle Comments

   
  • 

    Ryan Boren 3:34 pm on February 25, 2015 Permalink | Log in to Reply

    Mobile ticket status.

    https://make.wordpress.org/core/2015/02/18/mobile-flow-update/#comment-25331

• 

  Drew Jaynes 7:46 pm on February 18, 2015 Permalink | Log in to leave a Comment
  Tags: 4.2 ( 20 ), agenda   

  Dev Chat Agenda, February 18, 2015 

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

  Time/Date: February 18 2015 21:00 UTC:

  0. Feature Plugins:
     1. Consider the Customizer Theme Switcher plugin for merge [Proposal] [Plugin]
     2. Consider the Press This Revamp plugin for merge [Proposal] [Plugin]
     3. If you haven’t looked at either of the merge proposals yet, please spend some time today before the meeting. Please comment on those posts if you haven’t already.
  1. Component Updates
     1. Accessibility – @afercia
     2. Mobile – @ryan
  2. 4.3 Release Lead – If you’re interested in leading a future release, it’s time to speak up.
  3. Open Floor – If you have something you’d like to discuss, leave a note in the comments

  Ben Doherty (Oomph, Inc), Morgan Estes, Jonathan Brinley, and 2 others are discussing. Toggle Comments

   
  • 

    Robert Dall 7:53 pm on February 18, 2015 Permalink | Log in to Reply

    Bring me your tired, your slack, your feedback, bring me your EXIF/IPTC captions to the caption/post_excerpt.

    https://core.trac.wordpress.org/ticket/22768

  • 

    marcelomazza 8:35 pm on February 18, 2015 Permalink | Log in to Reply

    We need some feedback on:

    Hide Media Buttons on small screens – https://core.trac.wordpress.org/ticket/29989

  • 

    Jonathan Brinley 9:05 pm on February 18, 2015 Permalink | Log in to Reply

    As usual, I’d appreciate feedback on #17817.

  • 

    Morgan Estes 9:12 pm on February 18, 2015 Permalink | Log in to Reply

    I need some help moving #23367 forward so I can incorporate it into #31233.

  • 

    Ben Doherty (Oomph, Inc) 10:32 pm on February 18, 2015 Permalink | Log in to Reply

    I’d appreciate some feedback on #27282, also. Seems like a very old bug that I have a good (?) fix for.

• 

  Drew Jaynes 10:15 am on February 11, 2015 Permalink | Log in to leave a Comment
  Tags: 4.2 ( 15 ), agenda   

  Dev Chat Agenda, February 11, 2015 

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

  Time/Date: February 11 2015 21:00 UTC:

  0. Housekeeping – Schedule updates, merge window status, maintenance release – @drewapicture
  1. Term Splitting – @boonebgorges
  2. Feature Updates:
     1. Customizer Theme Switcher – @celloexpressions/@markjaquith
     2. Press This revamp – @michael-arestad
     3. Shiny Updates – @pento
     4. Emoji support – @pento
     5. Customizer Transactions – @westonruter
  3. Component Updates
     1. Accessibility – @afercia
     2. Multisite – @jeremyfelt
  4. Open Floor – If you have something you’d like to discuss, leave a note in the comments

  Jonathan Brinley, Paul Bearne, Paal Joachim Romdahl, and 1 other are discussing. Toggle Comments

   
  • 

    Weston Ruter 12:03 pm on February 11, 2015 Permalink | Log in to Reply

    In regards to Customizer transactions, my most recent thoughts are that I’ll hold off pushing for getting everything polished for 4.2. I don’t think I’ll have enough time to give it the attention it needs to make this release. Instead I’ll focus on some related pieces and general improvements that will make it smoother for merging in 4.3.

    • 

      Paal Joachim Romdahl 12:21 pm on February 11, 2015 Permalink | Log in to Reply

      Why is Press This and Emoji being worked on gradually becoming feature plugins planned for core? It seems a lot better if a priority list was created with what is most needed in WordPress, and work was done in that direction.

  • 

    Paul Bearne 2:52 pm on February 11, 2015 Permalink | Log in to Reply

    When will the “Needs Early Attention” patches form https://core.trac.wordpress.org/report/6 get merged?

  • 

    Jonathan Brinley 3:39 pm on February 11, 2015 Permalink | Log in to Reply

    #17817 needs some attention. Any committers able to review before it’s too late for 4.2?

• 

  Drew Jaynes 5:15 pm on February 4, 2015 Permalink | Log in to leave a Comment
  Tags: 4.2 ( 13 ), agenda   

  Dev Chat Agenda, February 4, 2015 

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

  Time/Date: February 4 2015 21:00 UTC:

  0. Lead Promotions – Congrats @helen & @dd32!
  1. Feature Updates:
     1. Customizer Theme Switcher – @celloexpressions/@markjaquith
     2. Press This revamp – @michael-arestad
     3. Shiny Updates – @pento
     4. Customizer Transactions – @westonruter
  2. Weekly Hit-List Recaps:
     1. Accessibility
        • #30486 – (needs-patch) Missing label associations throughout network admin
        • #30914 – (commit) WP List Table: improve table footer tab sequence
        • #30619 – (follow-up) The wpView toolbar is not accessible by keyboard
        • #26553 – (follow-up) Remove title attributes: comment-template.php
     2. Mobile
        • #31185 – (fixed) The logo header on the log in screen is too large a tap target
        • #29906 – (needs-patch) Submenus can’t be dismissed on mobile
        • #29989 – (needs-patch) Hide Media Buttons on small screens
        • #31162 – (maybelater) Prevent device keyboard from displaying after selecting an image in TinyMCE
  3. 4.2 Community Initiative – Details at the chat
  4. Open Floor – If you have something you’d like to bring to the table to discuss, leave a note in the comments
     • Looking for something to work on in 4.2? Check the comments on the 4.2 open call

  Paal Joachim Romdahl is discussing. Toggle Comments

   
  • 

    Paal Joachim Romdahl 10:07 am on February 8, 2015 Permalink | Log in to Reply

    What happened to someone beginning to work on adding tags/taxonomies to the media library? I have a feeling someone began looking at it but have not heard a word about it for quite sometime.

• 

  Drew Jaynes 7:00 am on January 28, 2015 Permalink | Log in to leave a Comment
  Tags: 4.2 ( 11 ), 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
  • Mobile – make-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
    • #30937 – Customizer transactions (@westonruter) [proposal]
    • Fast-tracking unit tests – @pbearne would like to discuss fast-track committing test for existing code

  tohit, Scott Kingsley Clark, Boone Gorges, and 5 others are discussing. Toggle 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.

    • 

      Drew Jaynes (DrewAPicture) 7:22 am on January 28, 2015 Permalink | Log in to Reply

      Added.

  • 

    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.

    • 

      Scott Kingsley Clark 7:44 pm on January 28, 2015 Permalink | Log in to Reply

      +1

  • 

    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.

    https://core.trac.wordpress.org/ticket/28559
    https://core.trac.wordpress.org/ticket/29063

    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.

    Thanks
    Tohit

• 

  John Blackbourn 5:04 pm on January 7, 2015 Permalink | Log in to leave a Comment
  Tags: 4.1 ( 30 ), 4.2 ( 3 ), 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 | Log in to leave a Comment
  Tags: 4.1 ( 30 ), 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 | Log in to leave a Comment
  Tags: 4.1 ( 30 ), 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.

  Knut Sparhell, Michel - xiligroup dev, Xavier Borderie, and 5 others are discussing. Toggle Comments

   
  • 

    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.

    • 

      John Blackbourn 8:55 pm on December 10, 2014 Permalink | Log in to Reply

      Yeah we usually do separate posts for each beta but we got a bit caught up with 4.0.1 landing at the same time.

  • 

    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

    @john
    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 | Log in to leave a Comment
  Tags: 4.1 ( 30 ), agenda   

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

  • Splitting terms #30335 – move into feature plugin
  • Remaining tickets for 4.1 (>80) – bug scrub
  • RC and string freeze
  • Decision on focus/DFW behaviour and its default state #29806
  • ‘About’ screen text #30435
  • Any other business

  Alex Shiels and Stephane Daury (stephdau) are discussing. Toggle Comments

   
  • 

    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.