Hi bbPress contributors!

Can I bother you to contribute a few more minutes of your time to fill out the 2015 contributor survey? It helps everyone establish some baselines around the contributor experience so that we can gauge how things change over time.

This is being posted to all the Make teams, so if you subscribe to a bunch of p2s and keep seeing this post, know that you only need to fill the survey in once, not once per team.

The survey is anonymous (so you can be extra honest), all questions are optional (so you can skip any that you don’t want to answer), and we’ll post some aggregate results around the end of January. It took testers 5-10 minutes to complete on average (depends how much you have to say), so I bet you could crank it out right after you read this post.

There are two sections of the survey:

  • The first has questions about team involvement, recognition, and event involvement, and is pretty much what you’d expect from an annual survey (which teams did you contribute to, how happy are you as a contributor, etc).
  • The second section is about demographics so we can take a stab at assessing how diverse our contributor base is. All questions are optional, but the more information we have the better we can figure out what we need to improve. If there’s some information you’d rather not identify, that’s okay, but please do not provide false information or use the form to make jokes — just skip those questions.

The survey will be open until January 15, 2016. Whether you have 5 minutes now, or 10 over lunch (or whenever), please take the 2015 contributor survey. Thanks, and thanks again for making 2015 awesome!


Trac Updates

It can be cumbersome to navigate, intimidating to learn, and difficult to master. We know Trac isn’t always the most user friendly tool, but we love it anyways because it works really well for managing the type of project bbPress is and the workflow we use.

These issues are exacerbated when Trac is out of date, or has not been “gardened”, which usually refers to general pruning, tidying, and making sure there’s a place for everything and everything is in its place.

Over the past year we’ve focused on improving the software and the build tools, and (other than software updates to keep up with WordPress’s Trac) haven’t revisited our Components, Milestones, or Resolutions in a long while.

This afternoon I made some rearrangements I think will help us stay better organized and on-target, outlined below:

  • Added the “Under Consideration” milestone, for issues that the core team has reviewed but hasn’t decided on exactly where it belongs yet. This is good for keeping Awaiting Review empty, and getting feedback to ticket authors sooner.
  • Components are now namespaced by what exactly they are intended to be. This should help tickets get categorized sooner, and help the core team better assess what areas need what improvements.
  • Several components were renamed to more appropriately reflect our intentions for them.
  • Added the “regression” ticket type, to help draw attention to issues that should be tested more quickly and prioritized higher.
  • Add “idea” ticket type, to help promote brainstorming and planning on Trac vs. Slack or the Forums.

Like most things, all of these changes are open to criticism and scrutinization. If it turns out they hurt more than they help, we can try something else. These changes are inspired by years of interacting with Trac and witnessing repeated workflow hang-ups.

We aren’t exactly agile; sometimes members of the core team don’t intersect on issues for a few days, and tickets go unloved for weeks or months. I think we do great in the face of this, and hope our slightly modified arrangement feels like a natural progression of our growing team and project.

Some notes from today * 2.5 is overdue…

Some notes from today:

  • 2.5 is overdue. Going to concentrate on existing patches while @netweb works on importer tickets.
  • Everything else needing significant attention will get bumped to 2.6.
  • We want to get 2.5 out asap, before the holiday rush and break starts.

bbPress 2.3 is out Let’s take a few…

bbPress 2.3 is out! Let’s take a few days off and talk on Wednesday about 2.4.

Few things for 2.4:

  • Per-forum moderators
  • Storing user ID’s in the voices topic meta
  • Switching last_active meta to be post_modified_date, to speed up topics queries
  • Bump functions to avoid expensive recounting
  • Hierarchical replies
  • Better Akismet feedback and UI
  • Do we want to a slot in GSoC under the WordPress org?

bbPress 2.3 release is imminent Last chance to…

bbPress 2.3 release is imminent. Last chance to sneak anything in!

Updated bbPress org to latest trunk which includes…

Updated bbPress.org to latest trunk, which includes some tweaks to posting code, and some preliminary forum searching abilities (courtesy of jmdodd.)

I’ll be tweaking the site templates and CSS to make it fit the site more appropriately.

In lieu of a dev chat this week…

In lieu of a dev chat this week, I went through and prioritized our milestones in Trac.

  • Created 2.4 milestone.
  • Thinned out 2.3 milestone by moving some things to 2.4.
  • Cleaned up some Future Release tickets.
  • Fixed everything in 2.2.3 and a few 2.3 stragglers.

If you’d like to help out, assign yourself to a ticket, and get to patchin!

Picked through some initial 2.3 tickets today fixed…

Picked through some initial 2.3 tickets today, fixed some things that were annoying for a while, but not worthy of a 2.2.3 release.

Most importantly is the usage of extract() which is now forbidden from being used in bbPress core going forward. It’s confusing for developers and opens the door to undefined/unused variables.

There were 43 usages in all that were cleaned up, all through out the code base. None of this clean-up effected existing patches that I saw, and since 2.3 will introduce some new functionality, it was important to get these changes in early so future patches don’t go stale.

Copied branches plugin to trunk * bbPress 2.2+…

Copied /branches/plugin/ to /trunk/

  • bbPress 2.2+ development will happen in /trunk/ going forward.
  • /branches/plugin/ will be removed when checkout traffic shifts over to /trunk/.

Cleaned up a few query and converter issues…

Cleaned up a few query and converter issues over the US holiday.

bbPress 2.1 is about as ready as it’s going to get now. Last call!