Make WordPress Core

Updates from October, 2015 Toggle Comment Threads | Keyboard Shortcuts

  • Morgan Estes 1:45 am on October 13, 2015 Permalink |
    Tags: ,   

    Week in Core: Sept. 28 – Oct. 11, 2015 

    Welcome back to the latest issue of Week in Core, covering changes from Sept. 28 – Oct. 11, 2015, changesets [34659][35029]. Here are the highlights:

    See that ↑ right there? That’s an oEmbed. And it’s loaded from inside this site.

    Feature Plugins Merged

    The Responsive Images, oEmbed Provider, and the “baby” REST API feature plugins have been merged into core. Grab the latest version of trunk and test them out.

    WordPress logo with wordmark below

    Responsive images in your posts. Just upload and insert!

    Potent Notables

    These changes were big enough to merit their own blog posts:

    Deeper Reading

    Some commits pack in a lot of info, from detailed background to best practices in using hooks. Here are a few worth reading the entire commit message:

    (More …)

  • Ryan Boren 4:43 pm on September 2, 2015 Permalink |
    Tags: , maintainership   

    Component Page Updates for 4.4 

    Now that 4.4 is underway, let’s update the component pages to reflect 4.4 activity. The Customize, Editor, and Press This pages serve as good templates, though they all need 4.4 updates. The component pages are targeted at beta testers. They should describe the component, list milestones (roadmap), and explain what needs testing and how to test it. Good component pages assist triage. For details, see the previous round of component page updates.

    Also, if your component has a corresponding Slack chat, link to the component page from the chat’s channel topic. This assists using Slack in beta testing flows.

    Component maintainers, here are your component pages…

    (More …)

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

    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 6:14 pm on May 14, 2015 Permalink
    Tags: ,   

    Dev Chat Summary, May 13 

    Agenda, Slack log.

    Editor (#)
    @azaozz has been looking at the “WordPress integration” parts the last couple of days, a lot of things that can be improved there. It removes some of the oddities, like running the post content through wpautop() before outputting it in the textarea, but only when TinyMCE is expected to be loaded, etc. @iseulde is working on the mobile toolbar and is hopeful she can get a patch ready this week. By next week’s meeting they want to have the mobile toolbar working (except in iOS), as well as #31655, #30949, and maybe #31441 in.

    Admin UI (#)
    @helen has largely been working on prepping things (tickets, examples, links, etc.) for Thursday’s UI meeting. More about the meeting (including agenda) can be found here: https://make.wordpress.org/core/2015/05/11/weekly-core-ui-meetings-for-4-3/

    Network Admin UI (#)
    Recap of Multisite office hours: https://make.wordpress.org/core/2015/05/12/multisite-office-hours-recap-may-12-2015/
    Things they want to have done by next week:

    • Mockups for the Edit Site / Add New Site improvements by @hugobaeta.
    • Having more flows posted to Make Flow for the network admin, via @sofiarose @kraft, and @ubernaut.
    • Get some decent progress on `WP_Site` and `WP_Network` with @jjj.

    Partial Refresh (#)
    Weston hopes to add initial integration between Menu Customizer and Partial Refresh this weekend. Due to client projects he’ll have to work on Concurrency _concurrently_ with Partial Refresh so he doesn’t hold up Menu Customizer. By next week Partial Refresh should be abstracted enough for the Menu Customizer to work with.

    Menu Customizer (#)
    @voldemortensen, @celloexpressions
    Now that it’s object-oriented they’re ready to start ramping up work. They’ll be going through github issues and come up with the next milestone for possibly the end of the week. By next week they’re planning on getting lazy-loading of both all menu item controls and the add-menu-item panel done, as well as better error handling for duplicate menu names and the like.

    Better Passwords (#)
    By next week, Mark wants a HTML, CSS, JS working demo of the password setting UI, and tickets for that and all other items on their hitlist. If there’s time beyond that, they could knock off one of the easier ones like notifying users of their password/e-mail changes.

    Accessibility component update (#)
    There’s been a ton of work done on the List Table class and associated areas. Joe has a set of 10 tickets with patches that he’d like to see committed by next week: #32150, #32254, #32255, #32028, #32152, #32147, #32189, #31654, #32253, #32170.

    Build tools component update (#)
    QUnit update seems to have gone off without a hitch. There are 7 npm dependencies that need to be updated. 6 are ready to go. grunt-sass needs a bit more digging in. This week, @jorbin is going to update the build tools roadmap he wrote up after WCSF and then pester a lead (likely @helen) to give it a read so that it can finally be published.
    Not exactly build related, but test related: Bug scrub identified that we don’t have any tests for nav menus, especially around the classes we add. @johnbillion has agreed to write some tests there so that we can fix all the bugs around that.

    Favicons (#)
    Support for managing favicons seems like a rudimentary thing, and its absence in core does seem odd to some. We still need plugins to handle favicon and other media icons in the admin, there is currently no good way for users to do that. We’ve been talking about adding support for a favicon manager for a long time ( #16434 ), let’s make 4.3 the release that finally adds it. @johnbillion volunteered to lead the feature for 4.3, with help from @brandondove, @kraftbj, @sofiarose, and possibly @dh-shredder.

    Next chat will be on May 20, 2000 UTC

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

    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.


  • Ryan Boren 3:48 pm on January 22, 2015 Permalink
    Tags: , ,   

    Dev Chat Summary, January 21st 




    • @drewapicture is the 4.2 release lead.
    • @wonderboymusic will be feature lead for a lot of media/image stuff.
    • 4.1.1 will drop within a week.
    • All 4.1 guest committers are renewed for 4.2.
    • The tentative target release date for 4.2 is April 8th.
    • Wednesday meetings will continue as usual.
    • Weekly Friday bug scrubs start next week.
    • This Week in Core posts will resume.
    • The 4.2 feature plugins are, tentatively: Press This, Customizer Theme Switcher, and Shiny Updates. Customizer Menus is a possible long shot.
    • The general focus of 4.2 will be polishing existing UIs in terms of mobile and accessibility.


    • @nacin will post about guest commit renewal on make/core.
    • @drewapicture will post weekly bug scrub times on make/core.
    • @dh-shredder will start This Week in Core posts while permanent contributors are located.
    • @johnbillion will add a page to the core handbook on development processes for mobile.
    • @pento will post about contributing to Shiny Updates on make/core.
    • All feature plugins will post an update to make/core.
    • Component maintainers will make a list of the main issues affecting their components.
    • @johnbillion will post a call for component maintainers on make/core.

    Links Mentioned


    (More …)

  • Pascal Birchler 8:21 pm on October 29, 2014 Permalink
    Tags: ,   

    WordPress Core Weekly 

    Hi everyone!

    It’s this time of the week again: WordPress Core Weekly is here. This updates covers all commits since last week up to to today, October 29th.

    In case you missed it, the new default theme, Twenty Fifteen, is coming along very well, the feature plugins planned for 4.1 are being tested extensively and the Customizer JavaScript API is getting more and more complete.

    But there are many more things going on behind the scenes and Core has even passed revision [30,000]! Let’s have a look at this week:


    • Add labels to the Personal Options input fields on the user profile editing screen. [30027] #30101
    • Editor: Use <button> instead of <a> for the Visual/Text buttons, make them focusable. [30002] #27553
    • Customizer: Add the ability for a customizer control to render its controls via a JavaScript template. Switches the default color picker control to a JavaScript template. [30014] #29572


    • Twenty Fifteen: If the sidebar is taller than the viewport scroll it with the content, if it’s shorter keep it fixed. [30025] #29979
    • Introduce a new means of outputting a <title> tag in the theme head. Requires a theme to add support by calling add_theme_support( 'title-tag' ). [30074] #18548
    • Introduce some new template functions for navigation [30065] #29808
      • get_the_post_navigation() and the_post_navigation() for navigation to the next and previous post.
      • get_the_posts_navigation() and the_posts_navigation() for navigation to the next and previous page of posts.
      • get_the_pagination() and the_pagination() for paginated navigation between pages of posts.
      • Uses paginate_links(). This reduces the need for themes to define their own sets of navigation functions.


    • Deprecate admin_created_user_subject() [30005] #29915
    • Introduce an edit_form_before_permalink action which gets fired after the title field but before the permalink fields. [30028] #29691
    • In wp_link_pages(), only output link separators between actual pagination links. [30030] #24940
    • Rename _wp_password_hint() to _wp_get_password_hint() to bring it inline with core terminology. [30033] #21243
    • Don’t add sticky class in get_post_class() if ignore_sticky_posts query var is set. [30036] #18035
    • Don’t display Standard post format twice in the meta box if the theme unnecessarily mentions it in the add_theme_support() call. [30038] #16555
    • Add comment_reply_link_args filter for get_comment_reply_link() arguments. [30039] #10569
    • Allow slug param of get_terms() to accept an array. [30042] #23636
    • Introduce orderby=include support for get_terms(). [30052] #23261
    • Remove UNIQUE key from slug column of terms table. [30056] #22023
    • Add wp_json_encode(), a wrapper for json_encode() that ensures everything is converted to UTF-8. Change all core calls from json_encode() to wp_json_encode(). [30055] #28786
    • Introduce wp_is_trusted_network(). A first step to establish concepts around trusted and untrusted networks. [30071] #30145
    • Don’t hardcode height for videos – this was a workaround for MediaElement internals causing problems. Responsive videos now work properly and don’t cause extra whitespace. [30082] #30078
    • Introduce some actions and filters which aid plugins in revisioning post meta. [30091] #20564


    • Allow ORDER BY in WP_Comment_Query::query() to be disabled. [30004] #29902 DisableORDER BY by passing boolean false, an empty array, or the string none to the orderbyparameter. This mirrors the behavior of WP_Query.
    • Accept orderby=include in WP_User_Query. [30016] #30064 This lets the results of a user query be sorted manually by the value of the include param.
    • Fix count in WP_Comment_Query when using meta_query. [30026] #23369
    • Optimize site query when performing network database upgrades [30029] #30097
    • Improve WP_Tax_Query param sanitization for empty strings. [30031] #30117
    • Support multiple status values in WP_Comment_Query. [30084] #29612

    Thanks to @peterwilsoncc, @iamtakashi, @nacin, @mnelson4, @afercia, @psycleuk, @rianrietveld, @davidakennedy, @celloexpressions, @DrewAPicture, @jipmoors, @ipm-frommen, @mattwiebe, @avryl, @heshiming, @desaiuditd, @ankit-k-gupta, @captaintheme, @marcosf, @obenland, @tmtrademark, @briandichiara, @tareq1988, @jakub.tyrcha, @johneckman, @kosvrouvas, @ptahdunbar, @nacin, @pushplaybang, @joedolson, @aaroncampbell, @jfarthing84, @dlh, @danielbachhuber, @wpsmith, @hotchkissconsulting, @JustinSainton, @jwenerd, @wonderboymusic, @tollmanz, @chrisbliss18, @joostdevalk, @TobiasBg, @nofearinc, @karpstrucking, @ebinnion, @boonebgorges, @mattheu, @adamsilverstein, @momo360modena, @tareq1988 for their core contributions!

    Revisions covered: [29995] to [30093]. For the complete list of commits to trunk, check out the log on Trac.

    Interested in joining in? Write or test a patch for 4.1.

  • Pascal Birchler 4:28 pm on October 1, 2014 Permalink
    Tags: ,   

    Last Week in WordPress Core 

    Hi Everyone! It’s finally time for another update. This is the first Last Week in WordPress Core for WordPress 4.1! I know there hasn’t been one for ages, but after talking with @dh-shredder at WordCamp Europe I’m confident that we’re able to change that.

    Let’s have a look at the changes between September 23 and today:


    • If the current user does not have the delete_posts cap on the current post type, don’t list delete or trash as bulk actions for the relevant context of Post list table. [29757] #20175
    • TinyMCE: when pasting/inserting content before a view, add new paragraph above it and insert the content there.
    • TinyMCE: Use Tahoma for RTL in general and Arial for Hebrew in editor styles. [29773] #29553
    • Fix tapping on the menu in iOS and Android [29770] #29365
    • Don’t display an empty comment author IP link on Comments screen. [29774] #29766
    • In the form handler logic for edit-tags.php, don’t redirect until $_REQUEST['paged']has been checked. All switch cases (except edit) now use break instead of exit. [29782] #16162
    • Show the number of approved comments instead of all comments on the dashboard in the “At a glance” section. [29785] #26738

    Bundled Themes

    • Prevent the arrow in “Continue reading” links from wrapping to a second line. [29771] #27908
    • Twenty Fourteen: Include Latin Extended font subset for Lato. [29772] #29690


    • Add two properties to media.model.Attachments.propmap: include and exclude, which are aliases for post__in and post__not_in. This allows you to instantiate a library that includes and/or excludes specific attachments by passing a single ID or an array of IDs. [29759] #26587
    • Disable multi-file uploading in iOS 7.x Safari as it prevents uploading of videos. [29776] #29602
    • When the modal is open, don’t respond to arrow keys when <textarea> has focus. [29777] #29725
    • Add size to the UI for Gallery Settings in the media modal. Ensure that the TinyMCE view is refreshed when size changes. [29779] #18143


    • wp_extract_urls() needs to also grab URLs with query strings and hashes. [29756] #29314
    • In wp_ajax_replyto_comment(), if $_POST['comment_type'] is set, use it for the value of $comment_type, which the compact() call has assumed is set since [8720]. It never was. [29758] #29704
    • Ordering by RAND():
      The shortcode callbacks for gallery and playlist check for 'RAND' == $atts['order'], which isn’t a valid value for order. Remove those checks and update the docs.
      In WP_Query, if the value of orderby is rand, order is irrelevant and should be unset. [29760] #29629
    • Add safeguards for when ext/hash is not compiled with PHP. [29761] [29751] #29518
    • Improve and clarify inline commenting inside the check_comment() function. [29763] [29762] #29734
    • Create correct permalinks for child posts of hierarchical post types when default permalinks are used. [29765] #29615
    • Allow bookmarks to be ordered by link_description in get_bookmarks(). [29778] #29763
    • In paginate_links(), ensure that query string args are propagated to the resulting paginated links. [29780] #29636
    • The joys of wptexturize(): [29781] #29557
      • Revert parts of [28773] and [28727] and [29748].
      • Do not ignore unclosed HTML comments.
      • Do not break unregistered shortcodes, e.g. [hello attr=”value”], or when there is extra whitespace, e.g. [ hello ].
      • Do not break HTML in shortcode attributes, e.g. [hello attr=”<”].
    • Use SSL for all references to WordPress.org [29787] [29788] [29789] #27115
    • Change the default orderby value in wp_get_nav_menus() to 'name'. [29792] [29796] #29460

    Thanks to @hauvong, @dlh, @mvd7793, @nerrad, @pavelevap, @loushou, @avryl, @TobiasBg, @DustinHartzler, @dominik.schwind, @afercia, @ryelle, @richardmtl, @noplanman, @wonderboymusic, @obenland, @miqrogroove, @ixkaito, @benjmay, @mantismamita, @nikolov.tmw, @shooper, @shooper, @voldemortensen, @igmoweb, @curtjen, @simonwheatley for their core contributions!

    Revisions covered: [29756] to [29799]. For the complete list of commits to trunk, check out the log on Trac. Interested in joining in? Write or test a patch for 4.1. Also don’t miss the weekly meeting today 20:00 UTC

  • Samuel Sidler 8:13 pm on September 16, 2014 Permalink
    Tags: ,   

    Feature Plugin Chat on September 23 

    Last week we mentioned holding a feature plugin chat today, but that didn’t happen. Let’s have it next week on September 23 2014 20:00 UTC.

    We’ve done this before, but just to recap…

    If you have an idea for a new feature, this will be a great opportunity to bring it up and find others interested in helping out.

    Please leave one comment per feature idea with the following information:

    • A brief (one paragraph) overview of your feature plugin proposal.
    • Current plugin status (idea stage, planning stage, under development, existing feature plugin, prior work, etc).
    • A list of those involved or already interested in your feature plugin (including you!)
    • What you’d like help with (scoping, planning, wireframing, development, design, etc).

    This post and the accompanying chat are for posting ideas that you’d be interested in working on. It is not for posting every feature idea you have for WordPress.

    Current feature plugin leads: Please post an update for your plugin here, along with the information above.

    See you all at the chat!

    • Nikola Nikolov 10:08 pm on September 16, 2014 Permalink | Log in to Reply

      The meeting is going to be held in #wordpress-dev channel right? I’m adding the time & date to my calendar :)

    • Caspar 5:35 am on September 17, 2014 Permalink | Log in to Reply

      Added to calendar, thx!

    • Peter Luit 7:35 am on September 17, 2014 Permalink | Log in to Reply

      In general the installation of plugins will have to be done on a site-by-site base. It would be very nice to have the possibility to have pre-defined sets of plugins for certain applications. Now we can just ‘favorite’ a plugin at wordpress.org, in others words ‘you make one set’. Would it be a nice idea to be able to make more sets?

      It could be done in wordpress.org, but it would also be great to have one plugin-installer (as a plugin) in which you can choose one of your own pre-defined sets and then download them all…..

      I am sure the WordPress community would love such a feature.

      Kind Regards,

      Peter Luit
      The Netherlands

    • Siobhan 1:13 pm on September 17, 2014 Permalink | Log in to Reply

      Image Flow is a project focused on improving the the image editing experience in WordPress.

      Current status: UX and wireframes
      Already involved: siobhan, @mor10, @sonjanyc, @markoheijnen, @dh-shredder, @pablo-perea, @edwerd, @klosi, @teamadesign (also less active ppl in the chat room and lots of feedback from people on the UI blog – apologies if I’ve missed anyone).
      What we’d like help with: development (particularly JS), ui design, research, labelling, testing

      • Ryan Boren 12:59 pm on September 18, 2014 Permalink | Log in to Reply

        You know how desperately I want to improve media flow. I’ll be around for research and testing, particularly on mobile.

        Usability as a feature. A featured flow for each release. Each screen of that flow and every tap and click gets attention, on all devices and across all interfaces. 4.1: Starting on your blog’s home page, create and publish a captioned gallery of edited images.

      • Andy Mercer 1:24 pm on September 22, 2014 Permalink | Log in to Reply

        Given that we have Featured Images, would anyone else be interested in the concept of Featured Galleries? Being a metabox, like the Featured Img metabox, which would allowed a user to select multiple images, and be called in a theme template the same way?

    • Nick Halsey 5:08 am on September 18, 2014 Permalink | Log in to Reply

      I have a class during the meeting, so I won’t be there. But I’d like to officially introduce the Menu Customizer as a feature-plugin seeking contributors.

      Menu Customizer is my GSoC Project that I’d now like to build out as a feature-plugin with the help of anyone else who’s interested. The goal is to merge navigation menus into the Customizer. Ideally, this should be done in a feature-complete and backwards-compatible way that allows the mess that is nav-menus.php to go away entirely for users who have access to the Customizer. In addition to leveraging the live-previewing framework that the Customizer provides, this project seeks to improve the user experience of menus as well as fixing several significant technical issues with the current implementation (particularly, scaling). The project is similar to the Widget Customizer project that landed in 3.9 in many ways.

      Current plugin status: development. The plugin is mostly functional, implementing the entire menu-management experience in a Customizer panel and allowing menus to be live-previewed. However, significant work remains to make things scale even better, improve the add-menu-item experience, improve the handling of sub-menus, and make menu-addition and deletion work more smoothly. Many improvements to WordPress core have already come out of this project, including the panels API, and those will need to continue before the plugin is ready to be merged (in particular, for 4.1, #29572 and #28709).

      To date, I’m the only developer working on the project, per GSoC regulations. But the project is now officially open to contributions. I’m in the process of getting set up on plugins trac with @samuelsidler and will be scheduling weekly meetings soon. @ethitter and @obenland are also familiar with the project, as they were my GSoC mentors.

      We need help with the following: development, particularly some JS-heavy components, but also on the PHP side. UI/UX, workflow research, and user testing. Changing the relationships between pages/posts and menus is not in scope, but for the first iteration we’d like to offer a much-improved UI/UX that fixes many issues with the current workflow. This particular project requires significant dev work regardless, which is why formal UI/UX work is happening mid-development. If you’re interested in helping out in any way, please leave a comment here or say something at the meeting (I’ll read the logs), and we can try to schedule the weekly meetings at a time that works for everyone.

    • Aaron Jorbin 9:17 pm on September 22, 2014 Permalink | Log in to Reply

      WP Session manager is a UI around user sessions. We aim to provide users with controls on the user profile screen and user editing screen for managing logged-in sessions.

      Current Status: Under development at https://github.com/johnbillion/wp-session-manager

      Current Team: @johnbillion, @DrewAPicture, @nacin, @jorbin

      What we want help with: Development, design (our UI/UX is currently functional and inline with core, but can always be improved)

    • M. Gage Morgan 11:38 pm on September 23, 2014 Permalink | Log in to Reply

      I think we should bring the post formats UI back again, this time with the new steps added to the process (3.6 “Oscar”).

      Current Status: Needs extracted from the old core files, we’d need somebody to do that. Still in the technical “idea stage.”

      Current Team: Myself, as a student, plus anyone who would be willing to volunteer.

      What I Need Help With: Porting the old files to WP 4.0.(Plus plugin development, I’m new here.)

      • Samuel Sidler 11:40 pm on September 23, 2014 Permalink | Log in to Reply

        There was some interest in this previously, but I’m not sure there’s enough to get it off the ground. If you’re willing to work on it, feel free. Things will have to be quite a bit different for it to be incorporated into core, so keep that in mind. I’d recommend starting from scratch design-wise, going through the steps that the Image Flow team is doing.

    • M. Gage Morgan 12:34 am on September 24, 2014 Permalink | Log in to Reply

      I would think it’s more than possible to do, but it would likely not be ready by 4.1, rather 4.2 or 4.3. I’ll try to work when I can, but scheduling is complicated.

      • Samuel Sidler 12:36 am on September 24, 2014 Permalink | Log in to Reply

        Keep in mind that feature plugins aren’t targeted at specific releases. Inherently they’re flexible and can ship when they’re ready. It’s also possible that a feature plugin never gets into core. That’s fine too. Experimentation is good.

    • Daniel Bachhuber 10:20 pm on September 29, 2014 Permalink | Log in to Reply

      A pretty consistent problem I run into is shortcode UX. Specifically:

      1. Remembering what shortcodes are available to a given site.
      2. Remembering what attributes each shortcode supports.
      3. Preview disconnect (shortcode ain’t WSYWIG)

      It would be neat to have UX in WordPress for selecting from available shortcodes, filling out required vs. optional attributes, and TinyMCE preview framework for registering a display callback for a shortcode.

      I’d be interested in working on this. I’d be best supported with UX help. And I’m pretty curious as to why this problem hasn’t been solved yet (e.g. what big gotchas we’re going to run into).

  • Andrew Nacin 3:27 am on September 6, 2013 Permalink

    Team rep nomination/vote 

    As discussed in the weekly developer meeting, core contributors need to select a representative for the WordPress “team reps.”

    There should ideally be two reps: a primary and a secondary/backup.

    Primary duties are to post an update weekly on make/updates mentioning what we’re up to (you know, building core), and to meet monthly in IRC with the representatives from other teams (only one of the two reps need to attend). I would look through that blog to get an idea of expectations, and also the minutes from last month’s meeting.

    Sometimes other teams will be working on something that affects core (or core should know about it), at which point you are in a perfect position to make sure communication lines are open. Thus, anything that comes up in updates or meetings that other core developers need to know about or act on should be communicated back to the rest of the contributors. This would occur ostensibly during the weekly core dev IRC meeting, or potentially posting to make/core (this blog) for feedback as necessary.

    Qualities needed: knowledge of core and core development processes; dedication to following Trac, commit activity, IRC meetings, and make/core; strong communication skills; and an excess of patience.

    A rep will serve for three months. After three months, they should be in a position to help pick someone to succeed them, probably in the form of nominating a few people to the group. We should be able to keep this pretty chill; this isn’t meant to be something that requires a board of election supervisors.

    The current reps are me and Mike Schroder (@DH-Shredder). Mike and I would not mind continuing our duties, if only because we like to test our own patience/sanity. But we are also happy to step back if someone else wants to step up.

    So, to nominate yourself or someone else, please fill out this very simple survey by the end of day Friday (today).

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