Like this:

Minutes of November 3rd dev chat:

BuddyPress1.2.7 release out towards the end of next week to fix a few important bugs that have been found in 1.2.6 (#2203, #2699 and #2685).

BuddyPress 1.3 roadmap items assigned to core devs, except basic profile privacy which is to be reviewed in a couple of weeks. A few new smallish features have been added, and we’ll post links to the relevant trac tickets as-and-when here.

Finally, we decided that dev chats will now happen every Wednesday at 19:00 UTC.

Like this:

Minutes

BuddyPress 1.2.6 release
Ticket 2587 is the only blocker. 1.2.6 is likely to be released by the end of this week.
A lot of key internal functions regarding the permalinks and active components have been changed, and we’d like any more feedback from tests of non-standard installations, such as deactivating components and turning things on and off.

Release cycles
Future releases will have an improved, more predictable release schedule, such as how the core WordPress team handles releases. BuddyPress’ core dev team and contributors will be considering this when 1.2.6 is shipped and work starts on 1.3, probably in the next couple of dev chats.

BuddyPress.org
Boone has been continuing to improve the website; check out the cool ‘topics I started’ page. More is on the way, and as always, volunteers are welcome to help improve the Codex: see this discussion for more details.

Like this:

Minutes

1.2.6
There are about 10 tickets, most of them fairly small, standing between us and 1.2.6. The thorniest issue is #2000, which concerns duplicate items in the activity stream. After some discussion, it sounds like this ticket might get punted. JJJ on 1.2.6 timing: “hopefully by next week”.

buddypress.org Ninjas
Boone reports progress on two fronts:
1) mercime has been working on an outline for a reorganization of the Codex. Dev and community feedback is requested. Check it out here: http://namoo.co.uk/groups/bpcodex-redesign/wiki/.
2) Boone now has access to the buddypress.org theme and plugins, and will be beginning the process of applying patches next week.

Roadmap
A poll will appearing soon on buddypress.org where community members can vote for what gets put on the roadmap.

Spam
All in attendance agreed that spam is a can of worms. Several ideas for combatting spam, both on bp.org and within BuddyPress itself, were floated, ranging from foxly’s discussion from a few months back, JJJ’s in-progress Honeypot, and Humanity. peterkirn and others are planning to start a group on buddypress.org to continue the conversation and offer up some suggestions.

Miscellaneous
Small strides are being made, both in plugin-land and in the core, toward the possibility of a longtime dream, multi-BP (or is it BPMU?)

Finally, the all-important issue of who’s in charge was thoroughly discussed. Thanks for a good meetup!

Like this:

Thanks to all who participated in this first BuddyPress dev chat; same time same place next week.

We looked at the outstanding tickets for BuddyPress 1.2. Andy’s done some awesome working getting large numbers of bugs fixed in the last few days, but there are plenty which people can help out on by checking tickets and confirm validity. Andy said his plan was to get most of the major tickets, and most of the important minor tickets, resolved before the 1.2 beta. Tickets #1086, #1222 and #1445 were mentioned; they deal with i18n issues so a request was made for anyone familiar with issues surrounding i18n to take a look.

We are going to contact active WordPress bug gardeners and share ideas on ticket workflow. Andy Peatling is going to add some custom reports to the BuddyPress trac to make ongoing ticket management easier.

We moved on to discussing “bug gardening”. This involves looking at tickets when they come in and checking that the issue has enough detail for a developer to investigate and commenting, tagging and assigning a milestone appropriately. As volume of tickets begins to increase, we need more people helping out.

Testing for 1.2 now needs to concentrate on regular WordPress installs (not WPMU). So far it appears to be stable, but we are interested also in usability on regular WordPress; if anyone finds installation quirks or oddities please open a defect ticket on trac. It was confirmed and re-iterated that BuddyPress 1.2 will be fully compatible with WordPress 2.9.1+ and WPMU.

People really loved the feature poll which was on the site back in the heady days of BuddyPress 1.0. We are going to create a new sub-forum where anyone can post any ideas or features into the hat that they’d like to see in future BuddyPress versions. A future dev chat will then go through the ideas, make a selection, then put those into a poll on the site for people to vote on. This will decide what happens to BuddyPress in 1.3 and beyond.

Andy shared his thoughts on the future of BuddyPress. He’d like to see the development of BuddyPress broken down into chunks, and find people that are really interested in specific features. For example, if you really love the activity stream functionality, you could focus specifically on that and stick to patching and improving just that area. The long term goal being to get teams on components, and have that transition into core commit teams. A thread is going up on the forums to explore this idea in more detail.

John James Jacoby, GIGALinux and junsuijin have formed a documentation team to improve the BuddyPress codex. Some discussion and comparisons were made with the jQuery API website, and php.net. People in the chat were also keen on the idea of screencasts, and that discussion is continuing in this thread.

To read the full chat log, visit the IRC chat log website (the meetup starts at 19:00 timestamp, and is one hour long).

Like this:

We’ve set the official dates and times for BuddyPress Development chats. Check the sidebar for changes, but we’ve decided to have them Wednesdays at 19:00UTC. (Click the 19:00 UTC link for the timezone conversion)