BuddyPress

In the June 30, 2010 BP dev chat http://bpdevel.wordpress.com/2010/06/30/summary-of-june-30th-dev-chat/, it was decided that a small group would form to address some of the ongoing issues with the buddypress.org website. I’ll be leading the effort.

Anyone who is interested in playing a role in this process should join the group. In this thread, I’d like to work out how things will work. Here’s what I know so far:

- There have been numerous discussions on this site and elsewhere about the current state of buddypress.org. @r-a-y, @gigalinux, and @lph2005 have been working on a whiteboard that assembles some of these threads and organizes them by severity/priority. You can view the list here: http://123.writeboard.com/7555930eb348e12b5 (password is cake)
- @apeatling is working on getting me access to the buddypress.org environment. Once I have that access, I can act as the implementer of fixes. That said, I don’t want or need to be the only people fixing things. Many of the fixes on the list – especially feature requests – can and should be developed independently. If there’s something on the list that you’re particularly interested in coding, please start a thread in this group.

A few other thoughts:
* The purpose of this group is NOT to discuss the BuddyPress software more generally – ONLY its implementation as the software that runs this site, http://buddypress.org. If you want to discuss the BuddyPress software and its development, there are many places to do so: BuddyPress Trac, the BuddyPress Development Updates blog, the forums, #buddypress-dev and #buddypress on irc.freenode.net.
* The purpose of this group is not to complain. (May I suggest that you start your own blog ? ) The purpose is to find bugs and develop solutions for them, as well as to discuss/develop new features or UX/IA directions for buddypress.org.

Let’s get cracking!

I would hope that that ‘Feature Requests’ were at a minimum at least until essential fundamentals are addressed so the site simply performs.

@hnla I agree with you, but the line between ‘feature requests’ and ‘addressing essential fundamentals’ is not all that clear, eg displaying code correctly in the forums.

“Displaying code correctly in the forums” is similar to the moderate issue – “Missing various bbcode formatting filters in forum posts”.

Might need to clean up the writeboard as I haven’t really looked at it since May.

[EDIT]
Okay, I’ve sorted out the writeboard by adding new headings and moving a few items around. Take a look, comment and give some feedback!

@r-a-y

The new headings are much more clear.

Some of the work can be done faster than others – for example – the enhancements can be done quickly. Should the order on that page represent the priority and order of accomplishment? Should it represent a “to-do” page ?

A distinction then, or clarification Feature Requests are things that are nice but NOT fundamental to the usability of the board, fundamentals are those things that we all know are prerequisites for a usable tech forum (or any forum/board really) Don’t think I’ve ever experienced a tech forum where I couldn’t post code, it’s an essential. Being able to see all your posts or recent posts since last visit, allows you to easily keep current at the moment I lose track of posts. being able to search posts, being able to actually paginate to the next page of results when it says there are some.

I would have added Private Messaging PM system to that whiteboard list but remember it being mentioned by Andy? as to why it isn’t available at present. I think. It is a function that I think many of us would expect to be available.

I would have added Private Messaging PM system to that whiteboard list but remember it being mentioned by Andy? as to why it isn’t available at present. I think. It is a function that I think many of us would expect to be available.

I believe that the PM spamming was the reason for shutting it off.

PMs added to “enhancements” list. FYI, notice how “requested features” are listed at the bottom?

More link in Community need fixing. Sometimes clicking more show double/repeat posts.

http://img101.imageshack.us/img101/858/bpmore.png

This is currently listed as “Duplicate activity stream items” on the writeboard.

“I believe that the PM spamming was the reason for shutting it off.”
Improve anti-spam measures in BuddyPress.org – I’d like that PM back

How about…
-Better Site Search (luckily there’s still google to support this when needed)
-Sticky Posts at the top of the Support page
-A gold star next to Boone’s name for taking this on

Is @foxly still working on the SPAM issue? It seemed he was working on some BP.org anti spam measures…

@foxly At risk of taking this thread off tangent to it’s purpose but what on earth did the direction of the thread or the fact that a few ‘Noobs’ started ranting about spam have on your decision and announcement, it’s not a logical progression from talking in detail about plans to tackle this issue to … nothing!

You all have to put up with a ‘bunch of noobs’ as you put it, bear in mind that WP and BP both follow a deliberate marketing tactic of ‘Out of the Box’ and ease of installation aimed at these Noobs, so suffer them with good grace!