CUNY Academic Commons

I will install it in a test environment and play with it, but I want to wait until it's been used by the community for a while before considering it on this site. It has the potential to permeate and thus screw up nearly every part of the site.

Would prefer to wait until after we upgrade to latest BP, as the Privacy plugin is not supported on legacy versions.

Still waiting on Jeff. Moving this to Features rather than Bugs

I talked to Jeff yesterday, and it sounds like he's shooting for a release within a week or so of the BP 1.2.6 release. Once it's out, I can start looking at it on some local installations. In any case, we'll have to upgrade to BP 1.2.6 first (it's not out yet)

Cool -- this will be big. At some point, we should talk about what kinds of privacy to enable.

Can we have a discussion about how this should work? There are a couple areas where I have questions.

- Levels of privacy. For a community like the Commons, I think that having two options makes sense: public, and visible only to logged-in members. This also has the advantage of being pretty easy to implement. Doing it on a "friends" basis is more complicated, and, I think, not in keeping with the goals of the Commons.

- Breadth of settings. Do we give a public/private setting for the profile as an entire unit? Or, on the other end of the spectrum, do we allow each profile field to be marked public vs private? The former is easier to implement. If we go with the latter, we should be careful not to overwhelm people with a sea of options. We could provide sensible defaults for each field (presumably phone and email would be private by default, college affiliation public), which might at least ease the tendency to have the privacy settings be overcomplex.

Happy to have this discussion here and also at our meeting on Friday.

-- Levels of privacy -- I very much like your ideas here. Yes -- public/visible only to community (ie., logged in users)

-- Breadth -- I'd love to see users have fine-grained control over the privacy of every item in their profiles, but I agree that we want to beware of an overwhelming panoply of options. Having sensible defaults is a great idea. We can also have a global checkbox that sets most items (excluding whichever ones we think that are mandatory public items -- name, college) to one privacy level or the other to allow for an easy, one-click switch.

I've got a first draft of this functionality written as a BuddyPress patch. There is a possibility that it will go into the next BP release. More soon.

Wow -- awesome.

Yes great. So this will be the central way to address the privacy concerns users have addressed.

Do we still want to change the language on the registration page to reflect the current privacy settings or do we just want to wait until this is in place and make the change once?

This has been added to BuddyPress and should be in the 1.6 release. http://buddypress.trac.wordpress.org/ticket/3695#comment:10

Excellent. Thanks, Boone!