Subscribe to this blog and receive notifications of new posts by email.
Join 2,262 other subscribers
IRC Hours: Mon @ 1600 UTC & Thurs @ 1500 UTC
IRC Hours: Tues and Fri @ 2100 UTC
Backup: Scott Taylor
IRC Hours: Mon @ 1900 UTC & Thur @ 1600 UTC
Lead: Dave Martin
IRC Hours: Mon & Thur @ 2000 UTC
Lead: Sergey Biryukov
Lead: Lance Willett
Backup: Konstantin Obenland
IRC Hours: Tues & Thur @ 1700 UTC
Suggest agenda items for today’s developer chat.
Andrew Nacin, helloari, Tom Lynch, and 6 others are discussing. Toggle Comments
http://core.trac.wordpress.org/ticket/21532 jQuery 1.8
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/
Maybe https://core.trac.wordpress.org/ticket/18694 ?
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.
← In the better late than never category notes…
Suggest items for today’s developer chat September 5… →
License / GPLv2
Hosted WordPress.com |
WordPress.TV Videos |
WordCamp Events |
BuddyPress Social Layer |
bbPress Forums |
WP Jobs |