WordPress.org

Make WordPress Core

Tagged: agenda Toggle Comment Threads | Keyboard Shortcuts

  • Drew Jaynes 6:05 pm on April 1, 2015 Permalink |
    Tags: , agenda   

    Dev Chat Agenda, April 1, 2015 

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

    • Beta 3 was tagged last week as scheduled and we’re heading toward tagging Beta 4 this week.
    • The soft string freeze is targeted to coincide with tagging Beta 4 this week, so we need to wrap any tickets with string changes (save for the About page).

    Time/Date: Wednesday 21:00 UTC 2015:

    DST reminder: The dev chat time has moved up an hour to 20:00 UTC following the European DST change.

    Agenda

    1. Congrats if you got ’em for @obenland and @wonderboymusic, release leads for WordPress 4.3 and 4.4!
    2. Task/Enhancements Review [List]
    3. String Ticket Scrub [List]
      One string:

      • #29958 – collapse menu keyboard accessibility
      • #31233 – Dismissable admin notices
      • #31769 – Prevent navigating away while plugins are updating via shiny updates
      • #31836 – Press This: Clean up text on tools.php

      Two or more strings:

      • (2) #31144 – Options general screen, accessibility improvements
      • (2) #31770 – Better feedback after bulk updating plugins via shiny updates
      • (3) #31722 – Shiny Updates: the aria-label should be updated to reflect the current status

      Various string changes:

      • #26600 – Search installed themes input has no submit button – New help text, one string split into two, new strings
      • #31832 – Add an Emoji section to the Help tab on post edit screen – New help text, replaced string
      • #27115 – HTTPS links to wordpress.org – Strings adjusted for links, may not need re-translating

    No Open Floor this week – Due to time constraints, we won’t be holding an open floor period during the regularly-scheduled dev chat this week. If you have a ticket on the 4.2 milestone you’d like to get dev feedback on, leave a note in the comments.

    Testing Stages Progress
    • Beta 1
      • Punt/convert all non-essential enhancements to tasks
    • Beta 2 (120 tickets on Report 6)
      • Get first run of FTP credentials modal in trunk
    • Beta 3 (90 tickets on Report 6)
      • Start finishing up tickets with string changes
      • Start About page
    • Beta 4 (50 tickets on Report 6)
      • Soft string freeze (all string changes completed save for the About page)
      • Start finishing up the About page
    • RC 1 (0 tickets on Report 6)
      • About page finished
      • Hard string freeze
     
  • Drew Jaynes 4:00 pm on March 25, 2015 Permalink |
    Tags: , agenda   

    Dev Chat Agenda, March 25, 2015 

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

    » Beta 2 was tagged last week as scheduled and we’re heading toward tagging Beta 3 this week.

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

    Reminder for those on Daylight Saving Time – If you’re already on Daylight Saving Time, the core dev chat will be an hour later for you until next week, though still 21:00 UTC. The above time link should give you the correct time and date for your local timezone.

    Agenda

    1. Decisions
      • Shiny Updates: Auto-activation behavior
      • wpLink modal: Behavior for working links lacking source text
      • Pursue or Punt: #26601 – Inappropriate content in headings on admin screens
      • About page highlights
      • Make/Core Posts – Ideas: Schema change, query class changes, TinyMCE views changes, twemoji front-end loader, update on HTML5 widgets revert, etc.
    2. Upcoming Milestones overview
      • Beta 3 (90 tickets on Report 6)
        • Start finishing up tickets with string changes
        • Start About page
      • Beta 4 (50 tickets on Report 6)
        • Soft string freeze (all string changes completed save for the About page)
        • Start finishing up the About page
      • RC 1 (0 tickets on Report 6)
        • About page finished
        • Hard string freeze
    3. Open Floor – Looking for dev feedback on a ticket? Use this part of the meeting to let us know!
     
    • Aaron Jorbin 5:03 pm on March 25, 2015 Permalink | Log in to Reply

      RE: Shiny Updates –

      24 hours ago I wouldn’t be advocating this, but there are a couple of really good reasons that we shouldn’t do auto-activates.

      1) Plugins that require after activation steps (such as connecting for jetpack or google analytics, updating permalinks for buddypress, etc) aren’t obvious. We need a way for plugins to provide a notice upon activation of next steps
      2) Since the menu isn’t updated, users still need to do a page refresh in order for the changes to actually go in affect and for them to utilize the features of many plugins.
      3) There are plugins such as maintenance mode ones that users will not want to be activated right away.

      I really like the idea of auto-activating since I think it helps to discourage users from having code that isn’t actually being used from being on the server and also saves the user a step, but in reality, they aren’t saved a step.

      We have at least two options for what to do instead.

      1) We remove shiny installs from the release. This is fairly easy to do as we just need to remove the js bindings on that page and remove the ajax actions. Since much of the infrastructure code is in place now, I think that it’s possible to continue development of shiny installs in a plugin. This would enable us to work on things such as:

      • Adding the ability for plugins to register “notifications” for users on what they need to do after installing.
      • Add the ability for plugins to “opt-out” of auto installs
      • Work on adding in menu items or at least a link to a plugins setting screen.

      2) Turn off auto-activation and instead do some UI changes when a user installs a plugin. I’m thinking a notice banner inside the plugin card giving the option to activate. This can either be a shiny (ajax) activation or a traditional activation. We also could change the “install” button to be “activate”.

      At this point, I recommend option 1. Shiny updates is still a solid MVP and a win for the users. It also sets us up for some bigger wins down the rode.

      • Eric Lewis 5:21 pm on March 25, 2015 Permalink | Log in to Reply

        I’m in favor of option 1 as well. It’s late in our release cycle to be making user-facing decisions that bear such heavy impact.

        Shiny Updates is a great improvement, let’s focus the rest of our effort there and follow-up on Shiny Installs later.

      • Gary Pendergast 10:47 pm on March 25, 2015 Permalink | Log in to Reply

        I’m strongly in favour of option 1. Providing an Activate option gives us one of two problems:

        • If it’s a Shiny Activate, it’ll have most of the same problems we’ve run into with auto-activate.
        • If it directs to the old activate screen, it’ll interfere with currently running Shiny Installs, and probably other things.

        I’m also in favour of seeing if we can turn this into a plugin. I think the Shiny Updates dev process has well and truly shown that the trunk dev model is totally broken.

      • Shailesh 9:14 pm on March 26, 2015 Permalink | Log in to Reply

        What if we convert Install button in Activate It after plugin is downloaded?
        If user click on activate button, page will open in new window something like target=”_blank”. So current other progress will not affected.

        Same for already activated plugins. We can put Deactivate It button and onclick we can deactivate it in new window.

      • Chuck Reynolds 2:31 am on March 27, 2015 Permalink | Log in to Reply

        agreed. glad the auto-activation was stopped.
        Something to consider going forward… a filter to disable the auto-activate after install.

  • Drew Jaynes 10:00 am on March 18, 2015 Permalink |
    Tags: , agenda   

    Dev Chat Agenda, March 18, 2015 

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

    » Beta 1 was tagged last week as scheduled and we’re heading toward tagging Beta 2 this week.

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

    Reminder for those on Daylight Saving Time – If you’re already on Daylight Saving Time, the core dev chat will be an hour later for you for the next few weeks, though still 21:00 UTC. The above time link should give you the correct time and date for your local timezone.

    Agenda

    1. Ticket Ownership
      • New Trac report, Tickets I Own, primarily for committers
      • Review milestoning best-practices in the testing stages
    2. Bug Scrub/Commit Sprint

    No Open Floor this week – Due to time constraints, we won’t be holding an open floor period during the regularly-scheduled dev chat this week. If you have a ticket on the 4.2 milestone you’d like to get dev feedback on, leave a note in the comments.

     
    • Justin Sternberg 1:04 pm on March 18, 2015 Permalink | Log in to Reply

      Would like to get a decision on https://core.trac.wordpress.org/ticket/31556. Thanks Drew.

    • Joe McGill 1:19 pm on March 18, 2015 Permalink | Log in to Reply

      I think https://core.trac.wordpress.org/ticket/30900 is ready to go in, just needs an owner.

      The second ticket where I’d like to get some feedback is https://core.trac.wordpress.org/ticket/31352 – making media icons retina friendly. Issue being whether it’s better to use SVGs for those icons or to modify the output of `wp_get_attachment_image_src()` to support multiple sources (e.g. icon1x.png, icon2x.png, etc.).

    • Paal Joachim Romdahl 5:58 pm on March 18, 2015 Permalink | Log in to Reply

      I believe there is a lack in people contributing to WordPress core.
      This is a topic that should be discussed.

      It would be informative to ask for feedback on how people experience contributing to WordPress.

      I see two different ways outside of slack we can handle this. Both would be helpful for the community.

      1.
      Creating a survery asking people if they have contributed to WordPress Core in some way.

      • How was your experience?
      • Do you have suggestions on how to improve the experience?
      • Anything else you would like to add?
      • How should we go about encouraging others to contribute?
      • Has your company considered donating employees time to contributing to improve WordPress? Yes/no
      • If so why or why not.
      • Etc…

      2.
      Holding a town hall meeting with the topic “Improving the contributing experience for WordPress Core”.

      Findings will then need to be strongly considered and changes implemented looking at the structure of how things are done in WordPress. All companies need to find ways to better themselves WordPress is also one of them. I am hoping that this can create a serious introspection with the result of adjusting what does not work with a new flow that does.

  • Drew Jaynes 8:59 pm on March 11, 2015 Permalink |
    Tags: , agenda   

    Dev Chat Agenda, March 11, 2015 

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

    » Beta 1 is scheduled to begin today.

    To hit Beta 1, we need to get the list of enhancements not tagged with 4.2-beta down to zero.

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

    Beta 1 Decisions

     
  • Drew Jaynes 12:09 pm on March 4, 2015 Permalink |
    Tags: , agenda   

    Dev Chat Agenda, March 4, 2015 

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

    » Beta 1 is one week away, along with the enhancements deadline.

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

    1. Feature Updates
      1. Customizer Theme Switcher – @ocean90 / @celloexpressions
      2. Press This – @michael-arestad / @stephdau / @azaozz
      3. Shiny Updates – @pento
      4. Emoji – @pento
    2. Component Updates
      1. Accessibility – @afercia
      2. Mobile – @ryan
    3. Release Schedule Recap
    4. Daylight Saving Time reminder
    5. Open Floor – Looking for dev feedback on a ticket? Use this part of the meeting to let us know!
     
  • Gary Pendergast 1:26 pm on February 25, 2015 Permalink |
    Tags: agenda, ,   

    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.
     
  • Drew Jaynes 12:00 pm on February 25, 2015 Permalink |
    Tags: , 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:

    1. 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
    2. Component Updates
      1. Accessibility – @afercia
      2. Mobile – @ryan
      3. Components – All the news that is news with @nacin
    3. Enhancements Deadline Reminder – Beta 1 is 2 1/2 weeks away. Need to start wrapping up enhancements.
    4. Open Floor – Looking for dev feedback on a ticket? Use this part of the meeting to let us know
     
  • Drew Jaynes 7:46 pm on February 18, 2015 Permalink |
    Tags: , 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:

    1. 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.
    2. Component Updates
      1. Accessibility – @afercia
      2. Mobile – @ryan
    3. 4.3 Release Lead – If you’re interested in leading a future release, it’s time to speak up.
    4. Open Floor – If you have something you’d like to discuss, leave a note in the comments
     
  • Drew Jaynes 10:15 am on February 11, 2015 Permalink |
    Tags: , 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:

    1. Housekeeping – Schedule updates, merge window status, maintenance release – @drewapicture
    2. Term Splitting@boonebgorges
    3. 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
    4. Component Updates
      1. Accessibility – @afercia
      2. Multisite – @jeremyfelt
    5. Open Floor – If you have something you’d like to discuss, leave a note in the 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 |
    Tags: , 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:

    1. Lead Promotions – Congrats @helen & @dd32!
    2. Feature Updates:
      1. Customizer Theme Switcher – @celloexpressions/@markjaquith
      2. Press This revamp – @michael-arestad
      3. Shiny Updates – @pento
      4. Customizer Transactions – @westonruter
    3. 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
    4. 4.2 Community Initiative – Details at the chat
    5. 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 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.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Skip to toolbar