Suggest agenda items for the September 18 19 developer chat.
20:00 UTC in #wordpress-dev in irc://chat.freenode.net
Suggest agenda items for the September 18 19 developer chat.
20:00 UTC in #wordpress-dev in irc://chat.freenode.net
The agenda I have for today is going through the projects-teams-tasks list and seeing where we are at.
Some goals:
Of course, propose any specific topics for discussion here.
I have read about 3 billion o-l-d Trac tickets in the past week to see what can be closed, duped, invalid’d, etc. Also, to see what was lingering and forgotten about, but could also be low-impact quick wins. I also scoured through bugs to see what was fixable, stuff that has been lingering for a while.
Here are some things I think at least warrant discussion (yea? nay? no way? cool?) that are NOT currently marked 3.5:
Meta / Tax without array of arrays (patched by batmoo)
https://core.trac.wordpress.org/ticket/17235
Middle and Little Endian Date Permastructs
https://core.trac.wordpress.org/ticket/13701
— this one is honestly a huge bug in rewrite, my patch may be insufficient, but it works and I think this issue
— deserves some love for our Int’l brothers and sisters.
Date Canonical Redirection
https://core.trac.wordpress.org/ticket/10935
oEmbed / embed_size_(w|h)
(Providers)
https://core.trac.wordpress.org/ticket/21704
https://core.trac.wordpress.org/ticket/15734
(Use transient for cache?)
https://core.trac.wordpress.org/ticket/17210
(removing options)
https://core.trac.wordpress.org/ticket/21719
Meta Query ordering / CAST
https://core.trac.wordpress.org/ticket/21621
https://core.trac.wordpress.org/ticket/15031
https://core.trac.wordpress.org/ticket/17065
Updating a term in one taxonomy affects the term in every taxonomy
https://core.trac.wordpress.org/ticket/5809
GlotPress Locales
https://core.trac.wordpress.org/ticket/13069
— Refresh the list in ms.php? Use GlotPress as an external? Do neither?
To add to these, I’ve also been looking through some old and new tickets, doing the same thing… three of these *are* 3.5.
Merge PHPMailer 5.2.2 (beta2 currently)
http://core.trac.wordpress.org/ticket/21074
– We’ve lost out on almost 2 months of beta testing, and it’s getting dangerously close to too late for any changes to make their way into PHPMailer 5.2.2 official if we do actually have problems that require changes.
Media Library Bulk Delete Error Handling Improvements
http://core.trac.wordpress.org/ticket/16165
– Also fixes #16164.
Avoid method redefinitions in docs by using unique method names for internal hooks
http://core.trac.wordpress.org/ticket/21564
Should I be adding “commit” keyword to these? They are all commit-ready.
I’m unable to attend Wednesdays. I need volunteers to test the patch I wrote for http://core.trac.wordpress.org/ticket/21858 That bug needs to be fixed as soon as possible.
Please suggest agenda items for today’s chat. We will be going over every 3.5 project and task today, to decide if our time and energy is best allocated across what remains on the table.
http://core.trac.wordpress.org/ticket/18302 ? Plz to haz? If someone can force PHPUnit onto my lappy at WCBaltimore, I’ll write the unit tests then.
Yeah I’m dieing to get this in. The latest discussion in that ticket actually relates to which JS files should be overwritable in the bundled themes, which I think could/should go into a separate ticket.
Starting here there was a good discussion last week in #wordpress-dev about Twenty Twelve not supporting all the post formats. As it turns out, neither does Twenty Eleven, but Twelve supports fewer than Eleven.
The discussion ended up being whether or not the admin interface should show all post formats regardless of which are supported by the current theme. I think we should discuss whether or not Twelve should support all the formats that Eleven does, and potentially the admin interface issue too.
#vers. #21796 nav bar menu dissapeared upon update can not replace tryed default themes and using swift v. 6.2.3 dissapeared from home and all pages
problen on 3.5 #vers. #21796 nav bar menu dissapeared upon update can not replace tryed default themes and using swift v. 6.2.3 dissapeared from home and all pages
Full list of projects: http://make.wordpress.org/core/wordpress-3-5-teams-and-tasks/
Things we need to discuss today:
Based on feedback above, adding:
#21796 is a standard bug we need to fix; no need for it to be part of the meeting.
Suggestion : improvement in “sealing” (étanchéité in french) of ” global” var $wp_rewrite between sites in multisite context – see http://core.trac.wordpress.org/ticket/21219 when switching to another blog. This purpose opens the general question of global vars in WP architecture.
I’ve mentioned it before but I’ll mention it again – accessibility of Custom Menu builder – #21289. It’s currently not possible for those using screen readers to successfully create their own custom menus with a hierarchy that features anything other than top level items. As it relies on drag and drop it can also be fraught for sighted keyboard users unless they are familiar with mouse keys functionality.
I know this is a big one, but is anyone looking at it? Surely it’s more key to maintaining your website then customizing your theme – something that is being looked at.
Suggest items for today’s developer chat.
September 5 is the “soft freeze”. I pictured this as a status check and a time for evaluation. At this point, we mercilessly cut things and quickly reassign contributors to things that need more attention.
That means a lot of things need to start landing this week.
i cant auto update to the latest nightly build
Seems like there are database tickets all over the place which deal a number of different things:
They don’t all fall under “database” in workflow and a lot haven’t been tagged 3.5. It would be great to organize an overall view of these issues, whether here or on Trac. Not to the extent of make.wordpress.org/db or anything, but perhaps a master list of: things that are very related to database but are currently in components Database / Taxonomy / Query.
I can help with this. It would good to see what is there, what’s gonna make 3.5, and what is punted and why.
@wonderboymusic, meet @pento. I think this will be the start of a great friendship. Let me know, I’m happy to help you both in this.
I just looked at all of the “bugs” in the Nacin filter – a lot of weird history in there! Here is a list of tickets that look to *me* like low-hanging fruit, bite-size, have patches (not all mine, many others), etc. Most of these have been hanging around for a while, and if they are NOT good candidates for inclusion: should maybe by closed, or the conversation restarted – but like I said, all have fixes / patches:
Meta and Tax Query without nested arrays
http://core.trac.wordpress.org/ticket/17235
Duplicate $$$ terms
http://core.trac.wordpress.org/ticket/17689
Allow a single taxonomy to be passed to get_terms() as an array.
http://core.trac.wordpress.org/ticket/17955
Slow SQL in get_adjacent_post()
http://core.trac.wordpress.org/ticket/18120
Searching with explicit post types unsets page post type
http://core.trac.wordpress.org/ticket/18513
Die fast in get_posts if in_search_post_types returns nothing
http://core.trac.wordpress.org/ticket/19198
Unneccessary term cache query for pages (set $post_type to page before update_post_caches)
http://core.trac.wordpress.org/ticket/20177
wp_list_pages fails with meta_value=0 criteria
http://core.trac.wordpress.org/ticket/20376
is_tax() with term parameter returns true for any taxonomy with that term
http://core.trac.wordpress.org/ticket/20590
Empty tax_query returns all posts
http://core.trac.wordpress.org/ticket/20604
Duplicate term insertion allowed after insertion with case differences
http://core.trac.wordpress.org/ticket/20850
error_log() not called in wp-db.php when error_log setting is empty
http://core.trac.wordpress.org/ticket/21103
$wp_query->found_posts is set to 0 with posts_per_page=-1
http://core.trac.wordpress.org/ticket/17066
Found posts not filled correctly
http://core.trac.wordpress.org/ticket/21147
get_all_category_ids() only used by a deprecated function
http://core.trac.wordpress.org/ticket/21200
get_cat_ID(): category “General” does not exist anymore by default
http://core.trac.wordpress.org/ticket/21201
reporting typo in dbDelta
http://core.trac.wordpress.org/ticket/21272
wp_set_post_categories fails if input array index starts with other than 0
http://core.trac.wordpress.org/ticket/5096
wp_get_object_terms should return arrays of integers for IDs and tt_IDs
http://core.trac.wordpress.org/ticket/17646
Garbage collect transients
http://core.trac.wordpress.org/ticket/20316
I would like to discuss: http://core.trac.wordpress.org/ticket/16416. Privacy vs. General vs. Reading Settings, “Site Visibility” versus “Search Engine Visibility,” and checkbox versus radios.
@bpetty wrote up a great page on triaging tickets. It would be great if others can contribute to it as well. http://make.wordpress.org/core/handbook/bug-gardening/
I’d like to discuss whether http://core.trac.wordpress.org/ticket/6821 is far enough along not to get cut.
also, I wrote a unit test for this: https://core.trac.wordpress.org/ticket/5809 – this would be killer to get in
Whether or not the new media UI/workflow is on course and/or whether any of the patches are ready to go into trunk
Improving the search query (also related to the DB stuff above), tickets http://core.trac.wordpress.org/ticket/7394 and http://core.trac.wordpress.org/ticket/21688.
This started as a quick “weekend” project to make the search return post titles first. Was thinking to add another query arg to only search titles, but that’s too limiting. The two patches above make searching for posts much much better without changing anything too drastically.
I’d love to see #17807 discussed. It’s been hanging around since 3.3 and I’ve tested it heavily. The refresh patch didn’t change anything appreciably, it was mostly coding-standards fixes.
It would also be great to see Viper007Bond’s date query improvements discussed: #18694.
Suggest agenda items for today’s developer chat.
http://core.trac.wordpress.org/ticketgraph?days=1011 — that’s starting at the first day I contributed. I’ve been talking to bpetty about things we can do to combat this. I’d like to revive some old ideas like people being responsible for specific components. Not default owners, but individuals and teams overseeing a component to allow for better triage of tickets. Also, we have not assigned new bug gardeners in a while, so we should see if that list should be updated with some new names.
I may miss the very start of the meeting, in which case @koopersmith will kick it off.
Good overview of outstanding UI/UX/design tickets for 3.5: http://make.wordpress.org/ui/2012/08/22/ticket-scrub-notes-for-8-21-patch-needed/
http://core.trac.wordpress.org/ticket/21289 – in my view another key accessibility issue that doesn’t seem to be getting any attention at the moment.
@GrahamArmfield I agree — this might get the right attention it needs if it is discussed during a #wordpress-ui meeting or bug scrub, http://make.wordpress.org/ui/.
I dont know if this is the right platform to say this. Is there any possibility for wordpress to introduces blocks feature and php input feature in upcoming version?
Hi there — not sure what you mean by either of these.
Can people from the outside suggest issues for dev chats?
Sure, though a few things to keep in mind:
Looking to see if anyone is interested on working on #18285 it’s a big’n but a good’n!
not sure if this is the right place to put this: small feature request: in the update page (/wp-admin/update-core.php) make note of which plugins are active and which are inactive. that way a user can update the inactive ones and be confident it will not break their site.
You’re welcome to propose this on http://core.trac.wordpress.org. I think it has been discussed before as well. I think part of the problem is that a change like this might have the opposite effect. That a user doesn’t update the inactive ones because they’re inactive.
Agenda for August 1 project meeting:
The agenda for today’s weekly project meeting:
Per our previous dev meeting, the 3.5 feature scope session will be taking place at 20:00 UTC on July 11 (tomorrow). (#wordpress-dev on irc.freenode.net — this is our regular place and time; see the sidebar.)
These meetings usually go long (1.5-2 hours), so this one will focus primarily on determining deadlines and planning out features. API/platform development (you know, the “Under the Hood” stuff) happens organically throughout the cycle anyway, so we may push those conversations to next week. (We’ve already been focusing on quite a few enhancements and bugs over the last few weeks thanks to near-daily bug scrubs, which I want to continue.)
Come armed with ideas and an open mind — see you tomorrow!
Excellent! I missed last week’s meeting somehow. I turned up at the usual time. Hopefully timezones aren’t messing with me.
Last week the meeting was on July 4th which meant that everyone in the US was going to be out partying, so we skipped it. We’re back to Wednesdays (today) @ 20:00 UTC
Unfortunately I have a previously-scheduled meeting then, but I’d love to work the adjacent post cleanup from 3.3 in. http://core.trac.wordpress.org/ticket/17807
Proposed agenda for our June 27 weekly project meeting:
While we won’t be finalizing our 3.5 plans this meeting, no time like the present to start following if you want to contribute this cycle. 20:00 UTC.
Looking forward to this one. Thanks for the early post, Nacin
I’m not going to make this weeks meeting but I think that we should focus now on the things that get missed too often like triaging trac and going through the 3.5-early tickets and the bug fix ones with patches on them to review, commit/feedback so that we can benefit from these contributions.
That gives us a clear focus for now while we discuss the 3.5 feature ideas.
Seems like we’re on the same page. You just said it better.
Quick agenda for today’s dev chat (starts in 30 minutes, at 20:00 UTC) —
Andrew Nacin 11:59 pm on September 18, 2012 Permalink | Log in to Reply
Embeds
Andrew Nacin 7:11 pm on September 19, 2012 Permalink | Log in to Reply
#20102 is in. Would like to have a short discussion on #18719.
John Blackbourn (johnbillion) 3:01 pm on September 26, 2012 Permalink | Log in to Reply
RE: #21632 – has anyone contact Imgur about their maxwidth/maxheight problem?
Robert Chapin (miqrogroove) 12:50 am on September 19, 2012 Permalink | Log in to Reply
I’m unable to attend Wednesdays. I need volunteers to test the patch I wrote for http://core.trac.wordpress.org/ticket/21858 That bug needs to be fixed as soon as possible.
Andrew Nacin 7:12 pm on September 19, 2012 Permalink | Log in to Reply
We’ll get this fixed; though, not something we need to discuss in a meeting as it is straightforward.
Robert Chapin (miqrogroove) 7:56 pm on September 19, 2012 Permalink | Log in to Reply
Cool.
Max Cutler 6:42 pm on September 19, 2012 Permalink | Log in to Reply
XML-RPC tickets that are ready for commit or need core feedback:
Marko Heijnen 8:02 pm on September 19, 2012 Permalink | Log in to Reply
Also some other related tickets: