#weekly-updates thread for the week…

#weekly-updates thread for the week of March 10th. If you’ve been contributing to BuddyPress this last week, please leave an update here with what you worked on and how it’s going, and if/what help you need.

You should go read @boonebgorges‘ metadata changes post if you haven’t already, and rejoice in the news that the *.BuddyPress.org themes have been open sourced.

Fact of the day: eight years ago today marks the date when the Mars Reconnaissance Orbiter attained Martian orbit. It’s still out there today, doing wonderful Marsy things.

#2368, #3856, #4631, #4786, #5155, #5209, #5220, #5281, #5296, #5297, #5306, #5333, #5334, #5374, #5399, #5411, #5423, #5434, #5435, #5440, #5448, #5457

Proposed metadata function changes for BuddyPress 2.0

A few weeks ago, BP’s internal metadata functions, like bp_get_activity_meta() and groups_update_groupmeta(), were refactored to use WP’s core _metadata() functions. See #4551

During the refactoring, special care was taken to preserve the exact behavior of each function, including the oddities and quirks (and bugs) that they’ve accumulated over the years. Now that a functionally identical refactoring is complete, I’d like to address these oddities. 

If you’ve ever used one of the metadata functions from the activity, blogs, groups, or xprofile components, please read #5399 and review the proposed changes. A few of them are straightforward bugfixes that shouldn’t ruffle any feathers. Others are improvements that will break backward compatibility in some hypothetical edge cases, but in each instance I’m not aware of any actual edge case. If you have feedback – including pointers to existing plugins, themes, etc that would be broken by any of the proposed changes – please leave it here or on that ticket.

Thanks for participating.

#2-0, #metadata

#4551, #5399

Once upon a time, we…

Once upon a time, we had #agenda posts going up once a week before the dev chat. They kind of died out when we switched the frequency and time of the dev chats around, but now that we seem to be on a bit of a roll again, I’d like to suggest we try something similar.

The goal is to put individual updates in a more visible place (finding the IRC logs is kinda tricky) and, by moving a lot of the updates to this site, to free up more time in the dev chats to give everyone more time to talk to each other synchronously and ask questions. If a feature developer has other time commitments for a particular meeting, moving the updates to the bpdevel site will make sure that everyone has the opportunity to read an update from them. Let’s see how this works for a couple of weeks, and we can make changes as necessary.

I’ll publish a #weekly-updates post on this site every week, and for everyone who’s contributing to a ticket, please leave a comment on that week’s update post with a summary of you’ve done. As a prompt when writing these: tell everyone what you contributed to last week, and what you’re aiming to do this/next week.

#4551, #4680, #5128, #5220, #5328, #5357, #5398, #5399, #5400, #7899