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!
Today’s dev chat was very brief. Since last week jjj pushed 2.3.1 which had a few minor fixes.
Notably it contained a fix for posting code and further refined the new back tick feature ( ` ). There is no need to use <code> or <pre> when posting lines/blocks of code, simply wrap the code in a ` (if you use GitHub or Markdown it is the same concept) and we take care of the rest.
Also in 2.3.1 the “visual tab” of the TinyMCE/fancy editor was turned off by default. The visual tab is great in theory but we’ve seen a slew of issues with it such as code being reformatted, mangled, etc. For users who really need it back (and don’t post code in their forums) they can either use this snippet or this plugin to bring back the visual mode.
Aside from the 2.3.1 release we are just moving forward with the 2.4 tickets.
MZAWeb also talked about looking into getting Alex Mill’s SyntaxHighlighter plugin working with bbPress now that we have the code posting sorted out.
Welcome to the bbPress development blog.
Just a quick update.
We didn’t have a formal dev chat on 8th or 16th. We’re still pressing forward with 2.4. Also there 2.3.2 was released which had a few updates.
The main thing right now is to keep working on 2.4. Also, if you haven’t already, test jmdodd’s hierarchal replies patch for #2036. For real, lot’s of testing on this. 🙂
Lastly, with the discovery of #2334 (http://bbpress.trac.wordpress.org/ticket/2334) there is certainly a possibility of a 2.3.3 release in the near future.
bbPress 2.5.10 is out, and is a security release for all previous 2.x versions.
bbPress versions 2.5.10 includes additional escaping on user display names in places where names & avatars are commonly displayed together.
These changes are internal to bbPress and do not affect any third-party themes or modifications to bbPress template parts. If you are using a third-party theme or template parts, you will inherit these fixes automatically.
Check the 2.5 milestone for a comprehensive changelog of fixes.
Take a moment to update your bbPress installations to 2.5.10. If you’re using WordPress’s built-in updater, it should only take a click or two.
These fixes have also been ported over to 2.6, which we continue to run here at bbPress.org and BuddyPress.org.
In accordance with our WP compatibility guidelines, we’ll be dropping official support for WordPress versions 3.6, 3.7, 3.8, and 3.9 in bbPress 2.6. For more details, see #2902
Edit: bbPress will require WordPress 4.7, see https://bbpress.org/blog/2016/12/bbpress-2-5-12-requires-wordpress-4-7/ (Dec 8th 2016)
Since we forgot to whip up a summary of last week’s meeting, I felt compelled to make this week’s thorough 🙂
Tickets worth noting
- #2036 – Hierarchal replies – jmdodd has put up a monster patch. This feature is ready to testing. Test, test, test. Break it if you can and report back. This is going to be one of the showcase features in 2.4. We are in the fortunate position to have this pretty far along early into the 2.4 release. It would be idea if we could get this tested and committed earlier in the 2.4 cycle thus giving those testing/running trunk and the bbPress Beta plugin time to do further testing.
- #2283 – Theme compat fixes and resets. bbPress has pretty darn good theme compat as it stands now, but low and behold there are themes out there that put this to the test daily. A good potion of the topics in the support forums are form users who simply activated bbPress and out of the gate the bbPress styes exploded. We’ll never get around this, but we can certainly improve where we can. If this happens on one of your installs please report it in this ticket. There is already a patch to clean up some issues introduced by the search feature as well as theme’s doing weird styling to <ul>s and <li>s.
- #459 – Making moderation forum specific – jmdodd is going to look at this when #2036 is solid. Another much requested feature. Would be nice to get into 2.4 if possible.
- #1799, #1649 – ‘bump’ functions and user counters. jjj’s got these covered I believe.
Currently there is a whole slew of tickets that already have patches, 14 at the moment. Hopefully in the next week or so these can but updated/committed as needed which will help thin out the 2.4 milestone.
Currently there is a bug when posting code in a topic or reply. If you are not an admin and try to post XML/HTML it will be stripped as those tags will not match the white list available for participants. We’re going to look at what can be done to escape text within <code> blocks before it’s processed by kses. Alex Mills’ SyntaxHighlighter should be a good place to start and we might be able to emulate much of the process based on what he does in his plugin.