Meeting notes for 3/25/2010, added live:
* Feature status and schedule update – all. rboren: Menus have firmed up, no more changes to how things are stored, just UI changes. Still need accessible version. Need to get lighter header done johnonolan working on patch this weekend. Multiple post thumbnails not done, markjaquith has been slammed with work, will try to finish over weekend, if not, punt. Schedule: have missed the beta period beginning, need to get menus done first.
* Inline documentation of the twentyten theme – demetris. Referenced post at http://wpdevel.wordpress.com/2010/03/24/agenda-for-mar-25th-2010-dev-chat/ and second argument on function, which had no documentation. We need to document functions.php. http://core.trac.wordpress.org/ticket/12695 phpdoc in functions.php, and conversational elsewhere, maybe. jorbin will take a first pass tomorrow.
* Front end AJAX endpoint – best solution discussion (http://core.trac.wordpress.org/ticket/12400) – dd32. “wp-ajax.php will be removed for various reasons (#12400). The consensus was stronger for better education, not a new file.” code from rboren: admin_url(‘admin-ajax.php’, ‘http’) forces http.
* Menus – Ryan http://make.wordpress.org/core/files/2010/03/new-menus-wireframe.pdf Will be following the new wireframe. Need to finish before beta. Jane will do revised more detailed wireframe on Friday, pthdnbr will take lead on code.
*Code sprint at WCSF – Jane Monday and Tuesday after WCSF at Pier 38. Hacker Days/Code Sprint. Details to come.
* Information provided for update checks from multisite installs (http://core.trac.wordpress.org/ticket/12672) – denis de bernardy
* Making the agregate stats data public – denis de bernardy Privacy vs. utility.
jb510 7:04 pm on March 29, 2010 Permalink
Was an update to the schedule agreed upon? The schedule link at right still reads 3.0 Beta March 22 and Launch May 1st? I’m new here and maybe I’m not searching in the right places…
Matt Martz 1:23 pm on March 30, 2010 Permalink
I forgot to post this up here, but in addition to the code Ryan provided for the using admin-ajax.php when forcing admin ssl, there was also concern about password protecting wp-admin with .htaccess or similar. In that case the following code placed in a .htaccess will allow unrestricted access to admin-ajax.php:
Order allow,deny
Allow from all
Satisfy any