Forums

Join
bbPress Support ForumsRequests and FeedbackWhat. The. Heck. Is. Going. On!

Info

Tags

What. The. Heck. Is. Going. On!

  1. >.<

  2. @Gautam*

    I just said that is was set and at that time there were no open tickets for 1.0.3 as far as I remember (and it was new then). Also, it is Gautam.

    Not really following you completely, but from what it sounds like, you just keep proving that nothing in TRAC is reliable. Deadlines aren't met, or even cared about really, tickets are ignored by those in power, (let alone shared with the public, and NO, 99% of users don't know about TRAC)... and overall, coordination is appalling, at best.

    If you choose to hold onto the wishful idea that TRAC and deadlines and work are all peachy keen and your work is worthwhile, then by all means, keep going... ignorance is bliss after all. Hell if I worked as hard as some of you guys, I would be spitting bullets about now...

    So since Kevin wants me to address specifics, here are my questions, to the entire bbpress community:

    1) When is 1.0.3 coming out. Seriously. What day? (when I check the "bbpress company blog" I seem to only see hacked up IRC chat logs from 5 months back... so much for "official sounding" posts, huh!)

    2) Who (names?) has editing rights to bbpress.org?

    3) Is bbpress definitely becoming a WP plugin?

    4) If bbpress becomes a WP plugin, will it also remain standalone?

    5) How will bbpress plugins be integrated into a proposed WP plugin?

    6) What exactly is backpress, and what is it's status?

    7) Who (names?) is in charge of updates/commits/releases for bbpress at this moment?

    8) How can plugin devs update their bbpress plugins and stay in touch with higher ups?

    That should be enough for now. Please, no condescending answers, since we are aiming for "maturity" in this thread from here on out. This is not just for me, but the community, remember. Even if I'm an immature idiot with false hope...

  3. 1) When is 1.0.3 coming out. Seriously. What day? (when I check the "bbpress company blog" I seem to only see hacked up IRC chat logs from 5 months back... so much for "official sounding" posts, huh!)

    I had sent a mail to Matt a few hours back, lets wait for sometime.

    2) Who (names?) has editing rights to bbpress.org?

    Chris (I am not sure), matt, mdawaffe.

    3) Is bbpress definitely becoming a WP plugin?

    There are 90% chances for this.

    4) If bbpress becomes a WP plugin, will it also remain standalone?
    5) How will bbpress plugins be integrated into a proposed WP plugin?

    As bbPress is not in the plugin phase, there is no roadmap for this (for the time being). Also check http://bbpress.org/forums/topic/bbpress-as-a-wordpress-plugin-thoughts

    6) What exactly is backpress, and what is it's status?

    Check http://backpress.org/ There were also some developments in it about 2 weeks back.

    7) Who (names?) is in charge of updates/commits/releases for bbpress at this moment?

    Matt, mdawaffe, filosofo (inactive), chrishajer. Don't know about anyone else.

    8) How can plugin devs update their bbpress plugins and stay in touch with higher ups?

    What do you mean by "higher ups"?

  4. Please stop feeding this troll (the op). I'm surprised everybody took his bait.

  5. @Gautam,

    Your response is appreciated. Maybe a mod can copy paste your answers into a sticky thread. Any email response from Matt yet?

    So mdawaffe is the only confirmed webmaster for bbpress.org, and he doesn't seem to pay attention to any feedback or bugs. I guess that has been confirmed at least... Chris, do you have access or not? This really ain't the biggest concern right now, but it would help the community to know who deals with this site, as Matt does not actively. For one thing, a bunch of plugin coders have repeatedly requested access to updating their old plugin files and better access to maintaining their plugin's "page" or information. This is whay I mean by "higher ups" - its great that 3-4 devs are having private IRC chats together and exchanging emails, but last time I checked, the point of an open source community is that everyone is communicating and sharing developments regularly and publicly. Hell, this forum itself barely has any staff or moderators to speak of. And even the forum regulars have no way to get in touch with "higher ups" even if they wanted to, so bbpress is 99% hearsay at this point. BIG PROBLEM.

    Also, if bbpress is 90% becoming a WP plugin, why hasn't this process been decided on or initiated yet? Will it be initiated after the 1.0.3 release?

    Coders and designers want and need to know these answers guys. I'm only speaking up for the silent majority and dozens of unanswered threads, this is not just my personal rant.

    @citizenkeith, thanks for providing another example of bored whiny bbpress trolls. If only we could get rid of users like you, we might have more progress around here.

  6. Any email response from Matt yet?

    He didn't reply to me, but you can also check here - http://bbpress.org/forums/topic/bbpress09-support-finishing-early#post-69893

    For one thing, a bunch of plugin coders have repeatedly requested access to updating their old plugin files and better access to maintaining their plugin's "page" or information.

    Any plugin author can update his/her plugin. That problem didn't arise.. where did you hear/read that from?

    the point of an open source community is that everyone is communicating and sharing developments regularly and publicly

    That is what Trac is about, anyone can see the developments, communicate and contribute.

    Also, if bbpress is 90% becoming a WP plugin, why hasn't this process been decided on or initiated yet? Will it be initiated after the 1.0.3 release?

    In an IRC meetup, Matt said that bbPress will start becoming a WP plugin near 1.2 or so. (and that IRC meetup is also posted on the blog)

    @citizenkeith, thanks for providing another example of bored whiny bbpress trolls. If only we could get rid of users like you, we might have more progress around here.

    citizenkeith is a valuable member to the community and has been here for long, so please.

  7. He didn't reply to me

    NO SURPRISE there huh.

    0.9 ... 1.0 ... 1.1

    How is anyone supposed to understand what is going on with all these releases. How can any reasonable and hard working member of the bbpress community still be in support of Matt?

    Matt's claims in IRC were now 6 months ago. You really believe them?

    And again I say that TRAC and IRC logs are NOT true "public" records. What is the point of the bbpress forum? Just to test out the software?

    AGAIN I PROPOSE:

    a) bug the living hell out of Matt until we get answers ... or
    b) fork bbPress July 2010

    Matt already hates/ignores/constantly-lies-to bbPress anyway, so its a no-loss set of options above. He has obviously reached the state of being a super rich, "content" guy who doesn't give a crap about anything anymore, which is great and congratulations to him, but screw his rudeness and immaturity and let's arrive at some new plans of action.

    I am not attacking citizenkeith or anyone else on a personal level. I'm attacking the users that keep trying to derail this thread and/or these important issues with petty condescending whining. These issues are critical and to employ playground politics is retarded and wastes everyone's time.

    Matt: if you read this, you only have one viable option at this point buddy, which is offer a sincere apology, update the blog, guide the devs to decide on a branch and future plans with WP plugin/standalone options, and INFORM the bbpress community of your decisions...

  8. b) fork bbPress July 2010

    There is absolutely nothing legally or physically preventing you from forking bbPress right now or in July. You literally don't need anyone's permission, so go right ahead.

  9. Don't ask what bbPress can do for you, ask what you can do for bbPress.

  10. For one thing, a bunch of plugin coders have repeatedly requested access to updating their old plugin files and better access to maintaining their plugin's "page" or information.

    Any plugin author can update his/her plugin. That problem didn't arise.. where did you hear/read that from?

    Probably he was referring to the weeks (months?) when Plugins section was not synchronized with SVN. I wrote about it here, Zaerl did here and I don't remember if any other plugin dev did it somewhere else.

    In an IRC meetup, Matt said that bbPress will start becoming a WP plugin near 1.2 or so.

    That milestone does not even exist! Anyhow it means they have to release 1.1 first, which unfortunately still has a load of open tickets...

    b) fork bbPress July 2010

    There is absolutely nothing legally or physically preventing you from forking bbPress right now or in July. You literally don't need anyone's permission, so go right ahead.

    If he could do that on his own, I think we would already heard about it. That kind of project definitely needs a team of more than just 1 dev!

  11. Beware. I'm a bit O.T. cause I will speak regarding my situation as a "plugin developer". Keep in mind that usually I don't write these kind of posts.

    I really don't like what's going on in this site. I mean: everybody are fighting each other regarding the near future of this software. It must be name 1.0.3, no it's 1.1, no it will be a plugin et cetera. It's just a number and nobody care about numbers. If Linux jumped from 0.12 to 0.95 then we can call the new version of bbPress 1.0.3, 1.1 or what we want.

    Now what is the real problem? The real problem is this site. After the releasing of the new template and the corresponding "Whoa!" thread everything stopped working. 404 pages, SVN broken, search broken, stupid HTML entities, trac substitution tag. Also the "Downloads This Week" statistics aren't updated, "Highest Rated Plugins" too and I can continue on.

    I really love this piece of code but we must provide a good experience for users now for the 1.0.2. We can't provide the new version if there isn't a solid base first. Few hints? Documentation or API documentation? I was forced to look at the code of the core in order to understand how to write my extensions.

    I am demotivated. I have built a lot of plugins but I don't want to hit the "submit" button cause why should I share my work if nobody can search for it in the plugin section or access it in several situations? As you can see I have stopped uploading big plugins after Editor and Visibility. Random Desc, Simple Registration, URL Preview and Post Permalink are like toys for me and I can share my toys with other people.

    Have a nice day and long live bbPress.

  12. I agree with Zaerl. Documentation has been bbPress biggest lack since I knew it. There is also a 3-months-old ticket regarding PHPdoc and coding standards which has never moved on...

    I deeply esteem your work, Zaerl: it's amazing what you were able to do with no documentation at all! And the fact that you consider your latest plugins as "toys" is... wow!

    Anyhow, we'd need more people with TRAC permissions to change the website (and to commit 1.0.3/1.1 patches too) and at the moment we just have a few...

    I'll be happy to contribute with my (very little) experience and my (big) free time, but we need to know who stakeholders are, first.

  13. @_ck_, okay. I'll fork if you fork. Seriously. You have the power to get 50 of us following after you, and I know at least 2 big coders who would probably follow. I'm a nobody, please remember.

    @mr_pelle, EXACTLY.

    @zaerl, sounds like you support a FORK too?

    SCREW TRAC. SCREW IRC LOGS.

    And screw trying to heal bbpress' relationship with Matt, it will never happen guys. WAKE UP. The man-child has too much pride to apologize and fix this mess. He will let it die on purpose, or suddenly delete this whole site and turn bbpress into a plugin of WP and remove all access to the old bbpress code and repositories if we let this crap continue.

    We need to mirror this entire domain's code and plugins onto another server before its too late.

    Even if we wanted to harass Matt into giving us answers, he still wouldn't do it. Seriously if bbpress is going to survive as a forum software, we need to FORK IT NOW.

  14. Hey don't involve me. I said you can do whatever you want.

    I don't want any of that responsibility or people whining at me.

  15. Check # 1-13

    http://ma.tt/2009/08/kill-your-community/

  16. Blaming matt/automattic or blaming eachother isn't going to take us and this project anywhere, people!

    Let's stop bitching at eachother and get this thing moving.

    To summarize :
    -Matt will be making bbpress into a wordpress plugin, afaics in this quarter, as WordPress skipps a release cycle to focus on the website and other projects
    -People are talking about forking bbpress 0.9 as an independant lightweight forum. Is this going to happen and who is going to do this.
    -I'll start a wordpress/backpress/bbpress fork probably at the end of next week, searching for extra devpower.

    That's the situation how it is, and there is little chance that it is going to change. Time to stop looking at the past and to start looking at the future.

  17. I don't understand why you people "looking for a lightweight forum" don't just use Vanilla.

    *Obviously* BBpress is about working with WordPress, so those complaining about it becoming a plugin really need to get over yourselves. BBpress wasn't made to cater whatever bizarre whim you wanted it to, it was made to provide a forum that functions with WordPress. A plugin works great for that.

    If you want something else, look elsewhere and stop blaming others for making a poor decision.

  18. *Obviously* bbPress is about working with WordPress, so those complaining about it becoming a plugin really need to get over yourselves. bbPress wasn't made to cater whatever bizarre whim you wanted it to, it was made to provide a forum that functions with WordPress. A plugin works great for that.

    You're totally wrong. Integrating with WordPress was an after-thought. At the beginning, it was made as a standalone software.

  19. @WimTibackx,

    Why are you seeking to fork WP and backpress?

    If we fork bbpress and make it standalone, that would solve half the world's problems. No point to think about backpress until the creators of backpress become more clear about their goals for it, etc... right?

  20. I might not have been very clear on that. Foremost I want to fork WordPress and turn it into a fast, modern and elegant cms. At the same time I want to fork WordPress and bbPress to run as plugins on that cms. I just used the backpress name in my post to avoid using WordPress two times.

    I'm personally not that interested in a standalone forum, but in a forum that integrates on my normal website easily and a normal website that is modern, fast and easily extendible. The current WP codebase might have the fast-part but it isn't modern and it isn't easily extendible (ok, it's better then phpBB for example but more object oriented code wouldn't do bad at all).

  21. *Obviously* BBpress is about working with WordPress

    ...it was made to provide a forum that functions with WordPress

    Don't you love it when people write totally 100% wrong statements and start them with "*Obviously*

    If we fork bbpress and make it standalone, that would solve half the world's problems.

    Comedy Gold

  22. pagal, I deleted your post. Your other topic has been closed. Further comments along the same lines will be deleted.

  23. pagal, I deleted that useless comment as well

  24. hahahaha......... chrishajer you drive me crazy
    I think this whole topic is useless.. why you are defending wtfmatt.. can I ask why you are not delete this topic? which is creating a bad impact for bbpresss...?

  25. Pagal, please direct your energy toward something constructive. And refrain from personal attacks.

  26. This thread stopped being helpful long ago, so I am closing it.

  27. This topic is closed