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.
I’m not sure we have any updates for this at the moment and when they arrive they are better as posts on here that as part of the dev chat.
As the agenda for this week is already looking busy I have left this one off.
Get all current plugins and newly added plugins setup as components on the plugins trac. Currently the list appears to be very outdated when creating a new ticket
Is the point of Plugins Trac to allow users to submit tickets about bugs/features to the plugin developers? I’m just a little confused and want to make sure if users are creating bug tickets about my plugins I’m monitoring it
I don’t think this is a good topic for the dev chat.
Improvements to the infrastructure are under consideration and we do know that we need a good solution to this.
As Matt suggests there are problems with the components list as it is just too long to be useful for most bug reporters.
I don’t think we need to discuss this in the core development chat.
Could we please discuss why the Plugin Compatibility data are missing for version 2.9? It seems only the votes for 2.8.4, 2.8.5, and 2.8.6 were preserved after the latest stable. This is making the feature somewhat… broken.
Schedule update. Sprint status. Woo Menus update. Merge update. Given the timing, I’d prioritize this stuff in the order over the core plugins and other stuff, since those things don’t have a specific schedule.
The MU forums will be closed at some point in the near future. The mods should only be sending people over to the MU forums unless when the thread is about MU specific functionality.
We seem to be growing a large number of defines todo with configuring different bits of WP to be visible/invisible when running multisite – we should be able to do something better than this using filters rather than using a large number of defines and is_multisite() checks.
Andrew Nacin
5:50 pm on February 24, 2010 Permalink
I agree. Sidenote, one of the ideas of “default constants” also was to place all of these in the same place in large part for developer reference. I will probably do an audit in the coming weeks on those we don’t currently have in (ms-)?default-constants.php.
Andrew Nacin, and 7 others are discussing. 
Andreas Nurbo 8:52 am on February 19, 2010 Permalink
If this is the right chat then
Peter Westwood 10:29 pm on February 24, 2010 Permalink
I’m not sure we have any updates for this at the moment and when they arrive they are better as posts on here that as part of the dev chat.
As the agenda for this week is already looking busy I have left this one off.
Brad 6:30 pm on February 19, 2010 Permalink
Get all current plugins and newly added plugins setup as components on the plugins trac. Currently the list appears to be very outdated when creating a new ticket
Matt 9:53 pm on February 19, 2010 Permalink
The components list is useless, better to switch it to use tags.
Brad 10:21 pm on February 19, 2010 Permalink
Is the point of Plugins Trac to allow users to submit tickets about bugs/features to the plugin developers? I’m just a little confused and want to make sure if users are creating bug tickets about my plugins I’m monitoring it
Peter Westwood 10:14 pm on February 24, 2010 Permalink
I don’t think this is a good topic for the dev chat.
Improvements to the infrastructure are under consideration and we do know that we need a good solution to this.
As Matt suggests there are problems with the components list as it is just too long to be useful for most bug reporters.
I don’t think we need to discuss this in the core development chat.
miqrogroove 11:37 pm on February 19, 2010 Permalink
Could we please discuss why the Plugin Compatibility data are missing for version 2.9? It seems only the votes for 2.8.4, 2.8.5, and 2.8.6 were preserved after the latest stable. This is making the feature somewhat… broken.
Matt 11:57 pm on February 20, 2010 Permalink
That’s not really a discussion item, more a bug report. Maybe put it on Trac under the wordpress.org component.
miqrogroove 4:21 am on February 21, 2010 Permalink
Okay. I thought it might be a “feature”. Trac’d http://core.trac.wordpress.org/ticket/12317
Jane Wells 6:57 pm on February 20, 2010 Permalink
Schedule update. Sprint status. Woo Menus update. Merge update. Given the timing, I’d prioritize this stuff in the order over the core plugins and other stuff, since those things don’t have a specific schedule.
Ron 2:36 am on February 21, 2010 Permalink
Not sure the weekly meetup is appropriate for this, but could we talk to the mods in the wordpress.org forums: http://wordpress.org/support/topic/366835
The MU forums will be closed at some point in the near future. The mods should only be sending people over to the MU forums
unlesswhen the thread is about MU specific functionality.Peter Westwood 10:12 pm on February 24, 2010 Permalink
I think the best thing maybe to post to the wp-forums mailing list and let the mods know that way.
asif2bd 10:54 pm on February 23, 2010 Permalink
I am sorry but i was not following the development Schedule correctly. Sorry if its inappropiate, do we have a lineup for Official plugin?
Peter Westwood 8:15 am on February 24, 2010 Permalink
I’m not sure what you mean by “Official plugin” – could you explain a little more.
Peter Westwood 5:43 pm on February 24, 2010 Permalink
Multisite configuration implementation.
We seem to be growing a large number of defines todo with configuring different bits of WP to be visible/invisible when running multisite – we should be able to do something better than this using filters rather than using a large number of defines and is_multisite() checks.
Ref: http://core.trac.wordpress.org/ticket/12229
Andrew Nacin 5:50 pm on February 24, 2010 Permalink
I agree. Sidenote, one of the ideas of “default constants” also was to place all of these in the same place in large part for developer reference. I will probably do an audit in the coming weeks on those we don’t currently have in (ms-)?default-constants.php.
Agenda for Feb 25th 2010 dev chat « WordPress Development Updates 10:30 pm on February 24, 2010 Permalink
[...] Woo Menus update * Merge update * Schedule update * Multi-site configuration implementation. Peter (http://wpdevel.wordpress.com/2010/02/18/suggest-agenda-items-for-feb-25th-2010-d/comment-page-1/#com…) [...]