bbPress.org

I write this in response to the growing posts and their ever-increasing angrier responses from moderators, to people who are simply asking for clarification of (mis-)information.

The problem we have, as a community, is that we have no communication nor project management involved with BBpress.

COMMUNICATION

A great example would be:

How many more ALPHA’s before BETA?

_ck_ rightly points out, and then gets angry at the poster, people are constantly asking the same questions. The bit _ck_ misses is that they are not pointless to a lot of people, or indeed one person, even if they are pointless to her. The point that hasn’t seen to be grasped by Sam/Moderators is that have an external facing Trac website that says one thing, when another is true, which is why people are asking the same questions over and over.

Instead of getting angry at people, why not change the date on Trac?? Even if you put it at 1st Jan 2010, it’s at least in the future and closer to being realistic than 1.0Beta 2 months ago.

I brought this up in October, and then again in December, and now again in February, but people who are new to this project or maybe not as involved ask _ck_ get their information from the website; but this info has been wrong for over 5 months. Which is why people are asking for clarification!

If you give people wrong/bad/out of date information, you have to accept that they will ask questions about it on the forum. It’s been the nature of humans throughout history, and we’re not going to change simply because it’s BBpress (sadly).

Given that the issue could be fixed by a BBpress person (not sure about user roles here so don’t want to presume that a forum mod could do it or if we need to wait for Sam); maybe we should stop being rude to people and fix it?

<u>A further example:</u>

It’s great that _ck_ knows that alpha 7 will break her plugins; but what about everyone else? Where is the blog post? Where is the forum post by Sam? Where is the sticky? Where is the announcement? Etc.

After much searching it turns out that 3 weeks ago _ck_ made a post about it, which has been off the front page of the forums section for the last 15 days. Brilliantly meaning that if you didn’t read the BBpress forums for a 5 day period at the start of February for any reason, then you won’t know about these massive changes. At the risk of appearing sarcastic, does anyone else think that maybe this should be the sort of thing we should Sticky/announce/keep on front page? Shouldn’t this sort of thing come from Sam?

But regardless it just re-emphasises the fact that communication about BBpress is close to non-existant.

TRAC

Devs and Moderators tell us to use Trac, and then are surprised that people are confused about the roadmap saying that Beta comes out 01/08/08 .

Either update Trac so that people don’t get confused, or inform people in some another way (which is a little redundant as that is what the Trac roadmap is for).

PROJECT MANAGEMENT

It somewhat goes hand in hand with the communication aspect, but as any developer knows, rushing head first into coding with no long term view quickly becomes fruitless.

As a community, and i’m in no way saying that Sam answers to us (really want to make that clear), we have no freaking idea what the heck is going on at any given time. We’re either given an ever changing answer by a moderator, or we’re told that Sam will tell us (like the voice behind the curtain), or we’re left with the (wrong) info on the website.

Every change comes out of no-where.

We have no idea what the short, medium and long terms goals are.

As much as this software is ‘free’, anyone planning to use it on a website at least wants to plan a little in advance.

It’s very difficult to want to help/take pride/give back to an open source project when we’re constantly told “it’s ready when it’s ready stop asking” – and in fact shows a total lack of project management and control.

Who runs the BBpress project?

Do they know/can they answer:

– how many scheduled man hours until alpha 7?

– are people assigned to work on it, or have they been moved elsewhere?

– what is the testing time on alpha 7?

– how long and we holding open bug acceptance for alpha 7?

– what is the due date for alpha 7?

– what is the likelihood of hitting that date?

– what are the dependant factors?

– what impact does alpha 7 have on existing installations?

– have the testers been informed of this?

– have the contributors been informed of this?

– what potential conflicts are there between current versions and alpha 7?

I’m not specifically looking for answers btw, as I said before Sam doesn’t answer to us, but I’m not sure I believe that ANYONE related with this project can answer those questions, and that is really really worrying.

IT IS FREE – THEREFORE IT IS OK.

Free is good, free we like.

Free means we accept bugs.

Free means we accept it’s not ideal.

Free means we know we wont get a 100% fit to what we need.

Free doesn’t mean we accept no communication.

Free doesn’t mean we accept what communication we get being wrong.

Free doesn’t mean we accept no management.

Free doesn’t mean we should get slapped down for asking perfectly legitimate and reasonable questions.

Free doesn’t mean we should accept instant yet wide sweeping changes.

Free doesn’t mean we should accept a total lack of respect.

AUTOMATTIC IS NOT A COMMERCIAL COMPANY

It is.

No, really… it is, so can we please stop saying that it’s not. Sam, while a loveable rogue to be sure (and he’s very cute in his picture), he is not fucking Ghandi – he does this for a wage.

Automattic is not building BBpress out of the goodness of their hearts to save all the wee orphans of the world, they’re a company making a profit and paying people’s wages.

Lets drop the humanitarian line when someone makes a good point and the moderators want to slap it down, eh? Or am I wrong, is BBpress ending world hunger as we speak? No? ok, maybe lets stop this one then. Just a thought.

HOW TO FIX THIS.

At the risk of opening up an old wound, I made a list at Christmas time (the oh so fun Facebook thread).

Either pause development on BBpress 1.0alpha7 for a week, or engage someone else to do it but:

<u>Fix the website. </u> Seriously, spend time going through each static page (there are 20 of them) removing all the bogus/wrong/out of date information. Some pages are fine, some are really really out of date. Given how much has changed with BBpress since WP2.5 came out, if you haven’t updated a page since that time then you know it’s wrong before reading.

<u>Blog more. </u> Not in a twitter “I am eating an apple” way, but you’ve made 5 posts in over 6 months (and 3 of them were within 3 days of each other). That development blog is our window into the BBpress development. It says “hey, this project ain’t dead”; instead all it does now is say “we released this bit of software on this date”. It’s not a blog, there’s no info other than release dates of software that don’t work anymore (for the most part).

<u>Extend / Plugin section. </u> This drastically needs an overhaul. There needs to be an option to filter out plugins that either don’t work or haven’t been updated to the latest release. Lets be honest, some of these plugins are 2 years old, and as soon as you click into them that’s the first stat you see.

<u>Download section. </u> Kinda/probably/should/maybe say that if you download the latest version it won’t work with a wordpress install form the last 9 months. Even though it’s from the same company. And it says it does work in the About page. And says it again on the Integration page. Yeah, we should probably write the truth somewhere or people will keep asking…

<u>Trac. </u> Lets update Trac. If someone has an understanding of the project to the level that they can answer the Project Manager 101 questions above, then why not put some of that info into Trac? I’m confident (though it’s just my opinion) that people are more motivated to fix bugs if we know there are X outstanding before the next alpha, rather than a huge list that has be fixed in an unknown amount of time.

<u>Development documentation. </u> A tough one this, and time consuming. I get that, I really do. But it makes helping out really difficult. As someone with rusty PHP coding skills (I‘ve been a BA far too long), I find Navigating bbpress to be a pain, and while I understand wordpress comparisons aren’t favourable, documentation makes wordpress editing 1000 times easier.

<u>Give us an overview. </u> Sounds very simple, and most PM’s have an overview list for each project anyway (usually on a power point to fob directors off), but it would make life easier. Many of us still don’t know what ‘features’ are standard with BBpress and which will only be available via plugin. Many of us don’t know what features are intended on being added, or what direction BBpress is going to go in. These aren’t bugs, we can’t add them to Trac, but many good points have been raised on these forums in the past – and I don’t think it’s right of us to assume you missed them or have ignore them, simply because there’s no communication.

Last bug not least…

Any chance we could have a reigning in chat with some Moderators? It’s great that they give up their time to reply here, and help the community, but (and I don’t know if it’s just someone having a bad day) the comments are getting way more aggressive/argumentative/absolutist.

It’s not that the standard answers aren’t wearing thin ofc, it’s just that we know the answer is going to be:

• It’s free.
• Sam’s too busy to pass on info.
• Blame Matt.
• It’s free.
• Stop asking. It’ll be ready when it’s ready.
• It’s free.
• Automattic are here to save us all and do not make any moey at all ever and everyone works for free I loves them – please ignore the $29 million they got which included the development of BBpress in the pitch.
• Go to trac.
• Don’t believe Trac.
• Sam’s too busy to keep you lot updated.
• Microsoft.
• It’s free.

That’s said a little tongue in cheek, and I hope it caused no offence, but while the moderators are clearly trying to do a great job (and we thank them), rarely do we get answers or constructive conversation when we talk about things like this. We’re shot down very quickly that we dared to have a different view point, and then given one of the standard answers that blame someone else or that it’s free.

WE WANT TO HELP.

Anyone who takes the time to hang around this forum sees we want to help. Anyone who takes the time to write on the forum wants to support BBpress.

If you’re the only developer on BBpress, or the person making almost all of the plugins, or the moderator who slams anyone who asks a question: please let us help.

We can’t just rock up, roll up our sleeves and stick our hand up a cow’s butt (an old farming joke – sorry). We need some direction, we need to be able to ask questions, we need information. Once we know what stage BBpress is at, we can help in taking it forward – with you.

But right now, all we can do is right posts like these every 2 months.

hey guys, just another idea:

what about integrate bbpress and wordpress that far (maybe with a plugin) that if registered and logged in users post a comment at a wordpress blog-post, this comment will appear in the profile of bbPress users under “user activity”.

And related to that:

WordPress users doesnt really have a profile page, so it would be nice if a user register and post a blog-comment, his name-link would open his bbpress profile page.

Hope you understand what i mean. I think it isnt that difficult. But too much difficult for me

greetings

Sumit

I may be totally blind but I am unable to see the enable XMLRPC and Pingbacks under settings. Am I missing something right in front of my face

Curious to know how many more ALPHA builds to expect before the builds move into BETA.

We are currently on build 6, I see a soon to be released ALPHA v7 is in the pipe.

Not trying to hold the bbPress team to a specific # of releases or anything, just curious if we have just a few more ALPHA’s or like a dozen more before BETA begins

For what it’s worth, I have been using ALPHA v6 since release without any problems.

I have wp and bbpress succesfully integrated. Now in my bbpress forum I’d like to display the wordpress pages. Basicly I want to replicate wp_list_pages() from wp. I know there’s a way to include wp in total inside bbpress. but that has a performance penalty and I’m also afraid it might cause bugs in the future.

So I’d prefer a simple query. What I have thus far:

global $bbdb;

$query = "SELECT wp_posts.*

FROM  wp_posts

WHERE wp_posts.post_status = 'publish'

AND wp_posts.post_type = 'page'

ORDER BY wp_posts.post_date DESC ";

$results=$bbdb->get_results($query);

foreach($results as $result) {

echo '<li><a href="' . $result->guid . '">' . $result->post_name . '</a></li>';

}

But I need a query which replicates wp_list_pages() closer. Where can I find that function in wordpress? Or how could I improve my query so that I get the subpages as well, for example?

I want to develop some plugins for bbpress, but cannot fid any documentation anywhere, is there anything that I can look at to get a list of filters/actions and what they do? bbpress looks great, but without any documentation for plugin developers its kinda hard to build for it…

Cheers.

I added a search box to header.php using this code:

<?php search_form( $q ); ?>

However, the search button shows up all the way on the right side of the page and below the input box. Does anyone have any suggestions?

Here is my (work-in-progress not live) forums site where you can see the problem.

http://www.watchandtrain.com/dogforums/

Thanks so much,

Jeff

Hello, I have several categories, with subforums. When a user clicks on the category they are taken to a page that shows the subforums for that category. I would also like to add a “Latest Discussions” listing that pulls recent posts from that category to this page. Any idea how how this can be done? Thanks.

Sorry for yet another WordPress integration topic. I’m mainly interested in integrating my WordPress header with BBpress, and I’ve read just about every page on the topic. I tried the deep integration suggestions by editing my bb-config.php to include:

if ( !defined( ‘ABSPATH’ ) ) {

include_once( ‘../wordpress/wp-blog-header.php’ );

}

I’ve also tried setting the path to wp-load.php instead with no luck. I keep getting an error saying that the file or directory does not exist. My WordPress and BBpress installs are in separate directories, but on the same level. Ex:

/home/wordpress

/home/bbpress

Is the path I have correct? Also, I went through every file in the template and changed:

<?php bb_get_header(); ?>

<?php bb_get_footer(); ?>

to

<?php get_header(); ?>

<?php get_footer(); ?>

Are there any other suggestions?

Edit: Sorry I forgot to mention that I’m using WordPress 2.7.1 with bbPress Alpha 1 and my website is http://www.rivenwow.net

I’m setting up a new web site, which is running WordPress 2.7. (Older versions aren’t an option because keeping them up-to-date with security releases is much harder.) The site’s going to need a forum, and I would like to use bbPress if I can.

Has anyone worked out the details in running WordPress 2.7 with the current stable release of bbPress 0.9.x? I know that seamless integration won’t be ready until 1.0 is ready, and if the developers say don’t use it yet, I won’t use it.

But if I do try to go with the current bbPress, what are the gotchas? Is there any integration possible at all, or do I have to wall them off as completely separate products with separate logins? If my client wants integration now, do I have no choice but go with something else like SMF?

There is one additional concern I have, though:

I had integrated bbPress 0.9 with a WordPress 2.5 site about a year ago, and loved how well they fit together — you guys really did an awesome job. Then 2.6 came out, and the incredible delay in bb’s WordPress integration seriously burned us. The web site got hacked twice due to 2.5.x security flaws that seem to be fixed in 2.7, and in the end we finally had to bite the bullet, delete the forum (it wasn’t getting that much use anyway), and upgrade WordPress. While the purist in me would love to work with bbPress again once 1.0 is available, I can’t shake this suspicion that when some future version of WordPress comes out, those of us who are using bbPress would get burned again because the developers are simply more interested in an ambitious future release that’s more than a year out. While 1.0 looks like an incredible release, a point upgrade to address compatibility would have been a really, really nice thing.

(Sorry if this sounds like a rant — I just would really like to trust this product again!)

Thanks,

Richard