This is the official blog for the core development team of the WordPress open source project. Follow our progress with weekly meeting agendas, project schedules, and the occasional code debate.
We need final testing and a green light on the two multisite tasks, #19235 and #19796.
3.5 status check.
Review 3.4.x tickets.
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.
@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?
If you’re going to suggest something to discuss, you should probably be there.
If you don’t regularly follow the dev chats, I would do this to get a hang for how they work, and propose the topic for a future chat (unless it is timely or time-sensitive).
Feel free to talk to any of us in IRC at any time. Not everything is worth talking about during a dev chat, but that doesn’t mean you can’t engage any of us. Individual bug reports, for example, are worthy of discussion but unless there is a major disagreement among core developers, or a big decision to make, we probably won’t put that on the agenda for a dev chat.
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.
TobiasBg 5:50 pm on August 22, 2012 Permalink
Ryan Boren 6:31 pm on August 22, 2012 Permalink
http://core.trac.wordpress.org/ticket/21532 jQuery 1.8
http://core.trac.wordpress.org/ticket/21309 WP_Post
Andrew Nacin 6:08 pm on August 22, 2012 Permalink
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.
Andrew Nacin 6:18 pm on August 22, 2012 Permalink
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/
Andrew Nacin 6:28 pm on August 22, 2012 Permalink
Ryan Boren 6:31 pm on August 22, 2012 Permalink
http://core.trac.wordpress.org/ticket/21459
camu 11:19 pm on August 22, 2012 Permalink
Maybe https://core.trac.wordpress.org/ticket/18694 ?
GrahamArmfield 7:25 am on August 23, 2012 Permalink
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.
Andrew Nacin 5:21 pm on August 31, 2012 Permalink
@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/.
ahmu83 2:05 am on August 24, 2012 Permalink
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?
Andrew Nacin 5:19 pm on August 31, 2012 Permalink
Hi there — not sure what you mean by either of these.
niklasbr 9:51 am on August 24, 2012 Permalink
Can people from the outside suggest issues for dev chats?
Andrew Nacin 5:17 pm on August 31, 2012 Permalink
Sure, though a few things to keep in mind:
Tom Lynch 9:39 pm on August 26, 2012 Permalink
Looking to see if anyone is interested on working on #18285 it’s a big’n but a good’n!
helloari 10:49 pm on August 26, 2012 Permalink
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.
Andrew Nacin 5:29 pm on August 31, 2012 Permalink
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.