Subscribe to this blog and receive notifications of new posts by email.
Join 2,247 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 Feb 25th 2010 Developer Chat
Agenda for Feb 25th 2010 dev chat « WordPress Development Updates, Peter Westwood, Andrew Nacin, and 7 others are discussing. Toggle Comments
If this is the right chat then
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
The components list is useless, better to switch it to use tags.
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.
That’s not really a discussion item, more a bug report. Maybe put it on Trac under the wordpress.org component.
Okay. I thought it might be a “feature”. Trac’d http://core.trac.wordpress.org/ticket/12317
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.
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 unless when the thread is about MU specific functionality.
I think the best thing maybe to post to the wp-forums mailing list and let the mods know that way.
I am sorry but i was not following the development Schedule correctly. Sorry if its inappropiate, do we have a lineup for Official plugin?
I’m not sure what you mean by “Official plugin” – could you explain a little more.
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.
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.
[...] 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…) [...]
← Meeting Summary for February 18, 2010 Dev Chat
Plugins can now include videos in their readme.txt files →
License / GPLv2
Hosted WordPress.com |
WordPress.TV Videos |
WordCamp Events |
BuddyPress Social Layer |
bbPress Forums |
WP Jobs |