Meeting Summary Feb 25, 2010
Agenda:
- Sprint status
- Woo Menus update
- Merge update
- Schedule update
- Multi-site configuration implementation
Summary:
- Sprint Status. Lots of patches being committed. Can always use more patches and more testing. Do it by Monday or hold your peace until next cycle for enhancements and feature requests.
- Menus, janewells. Coming along nicely in trunk. The UI looks more like a plugin than core, so changes listed on wpdevel being worked on. Accessibility will be worked on after freeze. pthdnbr, filosofo and dremeda offered to tackle accessibility.Jane will make tickets for items in the wpdevel post.
- Merge update, wpmuguru and rboren. Patches, patches and more patches.
- Schedule update. On track for March 1 freeze.
- Non-agenda topic: hakre brought up test suite. Core devs agreed patches are top priority until freeze, and test suite can be looked at after freeze.
- Multi-site configuration implementation, westi. Suggested a code change from constant to filter, wpmuguru agreed along with others in chat. See chat transcript for specific code snippets. Westi pondering doing it for AUTOSAVE/TRASH intervals as well.
Shortest meeting ever.
sakib, and 1 other are discussing. 
Andrew Nacin 8:58 pm on February 25, 2010 Permalink
For as long as I can’t make the chats, I’m loving the live blog. Thanks Jane!
Regarding the patch sprint, we could use some trusted contributors to step up and review tickets and patches. I’ll continue to review as many patches and tickets as possible over the next few days.
Jane Wells 9:00 pm on February 25, 2010 Permalink
You know there’s a web client for the IRC channel, too, right?
Andrew Nacin 9:49 pm on February 25, 2010 Permalink
Yes, and it’s actually what I normally use (or Opera), but I’m usually mobile during the chat, and the only IRC client on a BlackBerry I can find never stays connected. :/
sakib 5:43 am on February 28, 2010 Permalink
off topic,
wordpress doing lots of things and working to bring different types of features. but, almost 2.5 yrs going on, wordpress didn’t focusing on the backup features. the only xml is enough? it can be full/yearly/monthly basis export features — bcoz, we know lots of limitations in export and size matters, what would happen if the file size is bigger and making problem to import 100 MB to another wp site?
please give some focus on “backup tools/features” and even it would be better if you introduce built-in database backup with options, email, server, schedule backup features and so on — just ensure it, if an user somehow missed to take the backup, server crash and still he saved all the lost files, contents and just because of wordpress.
i’m sorry to telling here, I guess Jane will response, before I knocked to official twitter, didn’t found any response.
Matt 6:30 pm on March 1, 2010 Permalink
Filters for XML exports would be welcome.
Andrew Nacin 6:38 pm on March 1, 2010 Permalink
http://core.trac.wordpress.org/ticket/10317 is a big part of that.
Matt 6:52 pm on March 1, 2010 Permalink
Can’t believe we missed that one again.
Andrew Nacin 6:58 pm on March 1, 2010 Permalink
Well, I’ve suggested to Ron that he check it in today if it still looks good after kicking the tires.