[markpea]

@21cdb “at the end the developers should identify what is most important … they have more knowledge and a better foresight as a common user like me.”

Yep. Agreed. And Activity stream control & manipulation — double plus good. But I wonder whether biting off bbpress at the same time would just be too much?

[markpea]

I think that in some ways the question ‘what is BuddyPress’ jumps the gun at this stage. The question might rather be phrased ‘what could BuddyPress become once we’ve rewritten the core and API’? My guess is that BuddyPress will grow organically in ways that we cannot possibly foresee at this juncture. That’s the one of the strengths of Open Source projects.

Is it too late to start this process? Nah mate! Look at some other Open Source projects – Gallery photo album is on it’s second rewrite. Elgg developers not only rewrote the core/API they made the 1.0 totally incompatible with previous beta versions thus leaving a whole bunch of implementors high and dry (which is why I’m moving to BP)! My question is more, who is going to lead this process — you, Mr Maz? — and what role will Automattic have?

One issue that might be addressed in the core is your philosophy with regard to access controls. One of the built-in features of Elgg 0.9 which I found superficially attractive was the ability to set an access control on any object — blog post, file upload (but not comment) — and to add arbitrary access controls at the user level. However, in practice this often didn’t work out very well. Members of a closed Community blog had to remember to apply ‘community only access’ to each post that they made, they would frequently forget and thus expose content unintentionally. But I do think that looking at this example, and also how Mahara handles it’s file and blog access can help inform the sorts of access features we would like to see exposed by the API.

What might BuddyPress become? With flexible group and access control features it could become a premier eportfolio solution for example. Just my 2 penneth ………

[markpea]

OK. I’m getting the same results as t’others (OzPoker, etc). I’m just getting a BP/WP-MU site going with WPMU 2.9.1 and BP 1.2. Auto-join-goups is the only plugin active (bar BuddyPress). Clicking on the ‘edit’ in Site Admin : Profile -> Groups Link just dumps me back to the blog admin. I have renamed auto-join-groups to bn-auto-join groups to no avail. I have a single group already created.

I grepped bn-auto-join-group.php and found ‘hard’ links on lines 23, 88, and 122. It doesn’t strike me that this is actually the issue here.

Thanks for any help offered.

Cheers

Mark

[markpea]

@Anointed

I take it that you are using Elgg 0.9 or at least a pre-1.0 version of Elgg. The granularity of Elgg’s ACL system is brilliant but in my experience of running an Elgg system for two years (https://els.earlham.edu) is that most users do not grasp the power of this system and/or forget to use it when posting to their blog for example. In addition, it seems like most if not all of the access control system has been jettisoned with versions 1.0 although I notice that 1.6 has brought something similar back. But my conclusion is that from the user’s perspective the granularity of access control that elgg provides is over the top — much more comprehensible to have all postings to a group blog be only accessible by the group for example than to have to set access for each individual post. Does this make sense?

Thus it seems to me that Jeff’s conclusion “Offering privacy control on BuddyPress’ core component objects is more than sufficient.” would actually address 99% of what I might need for a college social networking system. Also I want to say that this development is very exciting and definitely encouraging me to move over to BuddyPress. Well done Jeff!