Help out then. Report bugs, fix bugs, submit patches, program new features on the roadmap, write documentation, answer questions on the forums.
Sitting there twiddling your thumbs wondering when things are going to be done doesn’t help the project.
Buddy Press rocks.
One monetization idea for you guys — Akismet for message-spam…like that plague of MySpace message spam. I’ll hopefully have some better contributions for the BuddyPress pot-luck put together soon. 
Buddypress rocks but I ll be waiting for wordpress+buddypress combination anyway…
Had did Facebook start by the core of a few developers then other developers made plugins or widget … Just like wordpress only a few work on the core then others produce the plugins!
Therefore if you want any plugin made for you, get a developer to make you one.
Andy is absolutely right!!! Sometimes I forget how big, unique and special this project is. “Rome was not built in a day”
BP has evolved in the last months and what is planned for future releases is exciting. The more I learn about BuddyPress the more I LOVE it.
I will do the best I can to help out.
Buddypress is great, but how member/profile data is stored in the database is a mess.
Peterverkooijen: I’ll be reworking the schema in 1.2, interested to hear your ideas.
The one thing I’m wondering about, once 1.1 drops (looking forward to tomorrow, Andy!), is how my users (if the site I’m building takes off) will adjust to the overall way of thinking that Buddypress (and social apps in general these days) tend to bring to the fore.
What I mean is that the interaction model is more things-are-presented-to-me and less I-am-searching-for-things. The way my brain works, I tend to organize myself mentally in the latter way — I want to find a piece of information or a conversation or a comment or something, and am hungry for a clear way to get to it. A more static way of viewing the structure, I guess. I’m old.
But Buddypress and (to pick an example, Facebook) are more about the ‘flow’, I think. About jumping in and having ‘oooh shiny!’ moments, and moving more fluidly through the web of interactions.
They’re both perfectly good ways of organizing things, of course, and for the tasks at hand, Buddypress is great. I guess my worry is that it will be confusing for users when it comes to things like forums and the traditional architecture of them, but I’m hoping that with 1.1 it will all come together smoothly. I’m really excited about the future of the app and WP in general, and very hopeful that the site I’m working on (which I’ll pimp when it’s ready, of course) will gather a vibrant userbase. The community I’m targetting really needs it.
Edit: reading this which is, I guess hot-off-the-presses doco, I’m thinking running a traditional forum using bbpress alongside the group-attached forums might be an option, if it’s not too confusing. I’m guessing it’d be pretty easy to port the Buddypress styling over to the ‘sidecar’ forums to make it all look right… we’ll see!
About how member/profile data is stored in the database, Andy Peatling wrote:
I’ll be reworking the schema in 1.2, interested to hear your ideas.
I sent you a lengthy mail through the system, again describing the problem as I see it, but probably not enough solutions. I came across this in another thread:
I’m now using another 3rd party plugin for membership to the site (WP eMember). While it has its own table, it also creates a matching WP user for each of the members it creates.
I haven’t tested the various commercial membership plugins yet (Memberwing, Wishlist, …), but they must all have their own solutions for the problem. I’m curious what their database tables look like…
I’ll be reworking the schema in 1.2, interested to hear your ideas.
Could LDAP standards be a useful guideline?
As a side note… I find it humorous and ironic that in a thread that started with “this thing is taking forever” there’s a response above written just three short months ago saying “once 1.1 drops (looking forward to tomorrow, Andy!)”.
The 1.2 release of BP has gone all wrong 
My users aren’t Twitter users or technophiles of any description – BP is now too complicated for me to get my head round, and I’m supposed to be the one running the site based on it, so I can hardly expect my users to be able to understand.
The profile wire – why, why did you take it away? 1.1.x was fantastic, now I am beating my head against the keyboard trying to work out how to bring it back after I updated to 1.2 just so I could install a gallery plugin.
The wire (once I’d renamed it to ‘wall’ so my users would understand what it was) was about the only thing that my members really used for public exchange. I installed BP to replace an outdated site platform that I’d built from scratch years ago, thinking that it would take the hard work out of maintaining the site… oops, I was wrong
Rather than drag up a rather old thread , could you perhaps marshal your thoughts about the UI and general user experience in this thread:
https://buddypress.org/community/groups/miscellaneous/forum/topic/the-buddypress-ui-design-and-conceptual-approach-to-social-networking/
It’s a vague attempt at having a thread running to mirror the API developers thread but focused more on the presentaion tier or Frontend.
@bobs12 It was indeed regrettable that the wire was taken out, but using the @mention system basically works the same.
This works by using “ @name” in a activity update, this way the user that is mentioned gets notified and can react to it.
As Ray’s said, please use the thread he linked to or make a new one. If us moderators had our moderator powers back yet (which we don’t), this’d be closed.
+1 for moderator powers!
This thread is now officially closed. Do not write or read anything below this post or aliens will attack. Well, that’s the closet method I can think of to close this thread at this time.
