WordPress.org

Make WordPress Core

Tagged: agenda Toggle Comment Threads | Keyboard Shortcuts

  • Helen Hou-Sandi 4:20 pm on May 21, 2015 Permalink |
    Tags: agenda, ,   

    UI Chat Agenda, May 21 

    Quick check ins on:

    Specific assignments for:

    • Screen-by-screen sweep
    • Trac gardening

    We’ll finish off with open floor / impromptu Trac scrub and see what, if anything, can get committed now.

     
  • Konstantin Obenland 3:52 pm on May 20, 2015 Permalink |
    Tags: , agenda   

    Dev Chat Agenda for May 20 

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

    Time/Date: May 20 2015 20:00 UTC:

    1. Feature Updates
      1. Editor – @azaozz / @iseulde
      2. Admin UI – @helen
      3. Multisite Admin UI – @jeremyfelt
      4. Partial Refresh – @westonruter
      5. Menu Customizer – @celloexpressions / @westonruter / @voldemortensen
      6. Passwords – @markjaquith
      7. Site Icon – @johnbillion
    2. Component Updates

    Feature Leads: Let’s review last weeks goals and set new ones for next week.

    Recommended reading:

     
  • Konstantin Obenland 10:25 pm on May 12, 2015 Permalink |
    Tags: , agenda   

    Devchat Agenda for May 13 

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

    Time/Date: May 13 2015 20:00 UTC:

    1. Feature Updates
      1. Editor – @azaozz / @iseulde
      2. Admin UI – @helen
      3. Multisite Admin UI – @jeremyfelt (if available)
      4. Partial Refresh – @westonruter
      5. Menu Customizer – @celloexpressions / @westonruter / @voldemortensen
      6. Passwords – @markjaquith
    2. Component Updates
      1. Accessibility – @joedolson
      2. Build tools – @jorbin
    3. Site Icon feature proposal – @obenland
    4. Open Floor – Looking for dev feedback on a ticket? Use this part of the meeting to let us know!

    Recommended reading:

     
    • Nick Halsey 3:09 pm on May 13, 2015 Permalink | Log in to Reply

      I can’t make the meeting, but regarding site icons, if that feature does happen it should really go in the Customizer. Specifically, the “Site Title & Tagline” section should be renamed to something like “Site Identity” and icons should be added there after the two existing options. Seeing as those options are all used in browser contexts (and usually, but not always in the theme for title & tagline). In the process all three options should be previewed in the browser as well as the Customizer preview, at least as well as we can (actually site title and tagline are currently previewed whenever a refresh is triggered, but many themes postMessage those, so we may want to find a way to do it directly with JS).

      Also, we should work out a way to implement the RSS feed links that can be specified for Windows 8.1 tiles alongside the various site icons that are used in that context so that all WordPress sites get automatic live tiles out of the box. See https://wordpress.org/plugins/custom-windows-pinned-tiles/. A filter to change the post type that it pulls would be nice too.

  • Helen Hou-Sandi 6:37 pm on May 11, 2015 Permalink |
    Tags: , agenda, ,   

    Weekly core UI meetings for 4.3 

    Remember weekly UI chats? It’s been a couple years since they wound down, but I’d like to get them started again for at least the 4.3 cycle, as we have some efforts that are not specific to a given feature or component team. UI chats are also a great way for newer contributors to get involved, as there are often a number of smaller patches that can be made and committed quickly. We’ll hold meetings each Thursday, starting this Thursday, May 14, 2015 13:00 UTC-4 in the #design channel in Slack. Updates will be posted here on Make/Core.

    For this week, let’s touch on these points:

    • Better responsive list tables.
    • Getting rid of media-new.php.
    • Screen-by-screen sweep for low-hanging fruit on small screens and touch devices (e.g. inconsistent spacing or font sizes at a given media query point).
    • The state of the CSS roadmap.
    • Coverage for other working groups (passwords, network admin, editor, customizer, anything else?).
    • Bug gardening team (see the UI focus on Trac).
    • Open floor (sound off below ahead of time if you wish – remember that this is about admin UI).
     
  • Konstantin Obenland 6:18 pm on May 6, 2015 Permalink |
    Tags: , agenda   

    Devchat Agenda for May 6 

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

    A lot of people will be on traveling to LoopConf or the VIP Developer Workshop so I anticipate a rather short meeting.

    Time/Date: May 6 2015 20:00 UTC:

    1. Feature Updates
      1. Editor – @azaozz / @iseulde
      2. Admin UI – @helen (if available)
      3. Multisite Admin UI – @jeremyfelt (if available)
      4. Customizer – @westonruter
      5. Passwords – @mark (if available)
    2. Component Updates
      1. Accessibility – @joedolson
    3. Open Floor – Looking for dev feedback on a ticket? Use this part of the meeting to let us know!

    Recommend reading:

     
    • Ryan Boren 6:58 am on May 7, 2015 Permalink | Log in to Reply

      We have five feature teams. How about a feature team list along the lines of the one on the Feature Plugins Tracking page? I want a place to point contributors looking to help with a feature, beta testers in particular.

      • Samuel Sidler 1:56 pm on May 8, 2015 Permalink | Log in to Reply

        How is that different from the components page? A good example is the customize subcomponent, which includes the latest posts for the component as well.

        • Ryan Boren 10:57 pm on May 8, 2015 Permalink | Log in to Reply

          I forget the components pages exist until I’m reminded of them. They don’t have chat times or channels. There is nothing that associates the components pages to features and feature teams in 4.3. The top-level components page is not tailored to 4.3. Finding any information I care about requires drilling down through each component, once I figure out which components map to which feature. This assumes a lot of knowledge.

          One page that gives me background on 4.3 and shows me how to follow and help. A start: https://make.wordpress.org/core/4-3/

  • Konstantin Obenland 7:45 pm on April 28, 2015 Permalink |
    Tags: , agenda,   

    WordPress 4.3 Kickoff 

    First I’d like to thank @drewapicture for his outstanding work in 4.2! I was particularly impressed with his ability to keep meetings on track and in time, I’ll work on making sure that won’t change going forward. :) A lot of the structure and artifacts he put in place have been proven quiet successful and I’d like to continue that, so you shouldn’t see too much change in that regard either.

    Release Date

    We’re aiming to release on Tuesday, August 18th. The 4.3 schedule is live and can be found here: https://make.wordpress.org/core/version-4-3-project-schedule/

    Deadlines are not arbitrary, and with your help I fully intend to get this version shipped comfortably on the 18th. Past releases have been quite good about releasing on time, let’s make that a signature trait of the WordPress project!

    Features

    WordPress 4.3 will be all about enabling users of touch and small-screen devices. @ryan has been testing flows on a myriad of different devices the past few releases and uncovered many things that desperately need attention.

    @joedolson has published a post over on make/accessibility about a11y priorities.

    If you see anything that sparks your interest feel free to leave a comment here and attend the kickoff meeting tomorrow, when we go through the list of things that were suggested. Specifically, Admin UI can will need a lot of hands. The meeting will also be a good time to suggest additional areas that you want to work on.

    Kickoff

    We’ll kick 4.3 off with a 2-hour meeting in #core at the usual time, April 29, 20:00 UTC.

     
    • sara cannon 7:55 pm on April 28, 2015 Permalink | Log in to Reply

      Excited for this release! I would love to help out with the Network Admin UI

    • Dave Navarro, Jr. 7:58 pm on April 28, 2015 Permalink | Log in to Reply

      Would like to see an update of the AUDIO shortcode as well to pull the title text from the audio file and display it.

      Really excited for the Shortcake stuff, hope it makes it.

    • Nick Halsey 9:51 pm on April 28, 2015 Permalink | Log in to Reply

      I have several ideas for continuing to work on themes in the Customizer building on 4.2. Would like to aim for adding theme install in 4.3, which would require a shiny install process, and shiny updates could work into that well too. I won’t be able to get started on that for a couple weeks, but should have a functional and tested proposal together well before the scheduled decision time.

      Along with the other mobile and touch improvements, I’d really like to see the much-needed Customizer UI design changes happen as well, hopefully we can pick back up with #31336 soon cc @folletto @designsimply.

      FYI, as is usually the case, I won’t be able to make most dev chats again this cycle.

    • aradams 10:07 pm on April 28, 2015 Permalink | Log in to Reply

      Hello All,

      I am not part of Make, just a WP user & designer. I have watched the unfurling of the New Editor saga over at WP.com and am concerned that there might be movement to implement that Editor to replace “Classic” editor for self-hosted WP. Could someone speak to that? I would be most grateful.

      • Konstantin Obenland 2:28 am on April 29, 2015 Permalink | Log in to Reply

        There are no plans that I’m aware of.

      • James Huff (MacManX) 5:27 am on April 29, 2015 Permalink | Log in to Reply

        You can use the new editor at WordPress.com for your self-hosted WordPress.org blog already if you have the Jetpack plugin installed and its Manage module active. Note that you’ll actually be using the new editor *on* WordPress.com, and can continue to use your WordPress.org blog’s Dashboard and “classic” editor as normal.

        Considering that WordPress.com and Jetpack are both products of Automattic Inc, and WordPress(.org) is not, I’m pretty sure there will be no deeper integration or replacement.

    • Pete Nelson 10:59 pm on April 28, 2015 Permalink | Log in to Reply

      Just a couple of patches waiting for that sweet, sweet commit: #31813 #31029

    • Stephen Edgar 11:49 pm on April 28, 2015 Permalink | Log in to Reply

      Admin UI – In #26311 I added a patch to make the “export admin screen” more responsive, I did this by replicating existing functionality from other admin screens, turns out these screens use tables, details of who, what and where tables are used in admin screens is also listed in that ticket.

    • mrjarbenne 3:50 am on April 29, 2015 Permalink | Log in to Reply

      It would be great to see this attended to: https://core.trac.wordpress.org/ticket/29606. Still can’t re-order gallery images on mobile (on iOS at least)

    • Max 7:37 am on April 29, 2015 Permalink | Log in to Reply

      I am not sure if that relates to Admin UI but #12706 is something which has been flowing around for a very long time without getting any closer to being fixed…

    • Ryan Boren 9:31 am on April 29, 2015 Permalink | Log in to Reply

      The touch bug I most want to see fixed is #29906. It is lingering desktop bias that fouls important toolbar flow.

    • leemon 12:45 pm on April 29, 2015 Permalink | Log in to Reply

      https://core.trac.wordpress.org/ticket/22938 – Presentation of hierarchical taxonomy in Media modal should be checkboxes rather than comma-separated tag list

    • Torsten Landsiedel 1:13 pm on April 29, 2015 Permalink | Log in to Reply

      It would be really great to fix https://core.trac.wordpress.org/ticket/28303 in 4.3. I know this is a problem just for a bunch of languages, but files being overwritten is always a big problem and people are complaining in our local forums.

    • Ryan Boren 7:47 pm on April 29, 2015 Permalink | Log in to Reply

      Perennial wish, retire media-new.php.

      https://make.wordpress.org/flow/2015/01/29/retiring-media-new-php/

      Seems like most of the work would be hooking the media addition ui from the grid view into the list view with some row insertion ajax. The list view would also need to become a full screen drop target like grid view.

    • pingram3541 8:07 pm on April 29, 2015 Permalink | Log in to Reply

      Would love to see the ability for nesting multiple shortcodes of the same name. Many themes and plugins could benefit, especially when building grids and nesting columns etc. The logic is fairly simple but there is no way to filter this currently.

      Another thing I’d love to see is the ability to define query “orderby” based on multiple meta_key, meta_values, currently you can pass an array to order by a single meta_value + any of the other orderby arguments but not 2 or more meta_keys.

    • Weston Ruter 9:59 pm on April 29, 2015 Permalink | Log in to Reply

      My proposals as I’ve also blogged:

      Customizer Partial Refresh
      This greatly improves performance of previewing changes in the Customizer for non-postMessage transport settings (JS-applied changes) by just refreshing the area of the page that has been changed. As such it eliminates some of the need to do postMessage in the first place, while also reducing the amount of duplicated logic that would have to be implemented in JS to mirror what is being done in PHP. This resurrects some code from the old Widget Customizer feature plugin developed for 3.9. Writeup and feature plugin are available.

      Customizer Transactions
      A low-level re-architecture of the Customizer plumbing that has a lot of side benefits and bugfixes, introducing some exciting possibilities for future feature plugins like scheduled settings, setting revisions, and drafted/pending settings. Partial Refresh is a dependency for this. Pull request available, but needs refresh. See proposal.

      Customizer Concurrency/Locking
      This is an important one for a client project I’m involved with, and so I’m having to prioritize it. I’m working on a client site that will have many users in the Customizer at a time, and given the way the Customizer is currently implemented (as with most areas of WP), there is no concurrency/locking support. So I’m working on adding locking at the control/setting level. See #31436.

    • RENAUT 11:31 pm on April 29, 2015 Permalink | Log in to Reply

      what about reviewing all the mails send by wordpress ?

  • Drew Jaynes 8:00 pm on April 15, 2015 Permalink |
    Tags: , agenda   

    Dev Chat Agenda, April 15, 2015 

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

    • RC1 was tagged just a little while ago, putting us back on trac for an April 22nd release.
    • We also entered hard string freeze today. All core and About string changes a frozen.
    • know!

    Time/Date: Wednesday 21:00 UTC 2015:

    Agenda

    1. Branching at RC1 – To do, or not to do it
    2. Since we just tagged RC1, Report 6 is pretty empty. What are any outstanding issues?
    3. Test test test!
    4. 4.2 Release 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 string finished
        • Hard string freeze
      • Release (0 tickets on Report 6)
        • About page finished
        • Remaining issues resolved
     
  • Drew Jaynes 3:26 pm on April 8, 2015 Permalink |
    Tags: , agenda   

    Dev Chat Agenda, April 8, 2015 

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

    • Beta 4 was tagged last week as scheduled and we’re heading toward tagging Release Candidate 1 this week.
    • The hard string freeze is targeted to coincide with tagging RC1 this week, so we need to wrap any remaining tickets with strings, including the About page ticket (#31929).

    Time/Date: Wednesday 21:00 UTC 2015:

    Agenda

    1. Task/Enhancements Review [List]
    2. RC1 Scrub – About 15 tickets remain on Report 6

    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.

    4.2 Release 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 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.

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