Deprecated - Social software and communities

From the view face-to-face talks I had with Drupal developers I noticed they are very interested in all the Social software and Community stuff (let me call it SoS). I'm also very interested but as a software-engineer I would like to get to genetic solutions on SoS to assure scalability and further expansion. I belief al lot of tools and best practice is known and I'm mostly interested in getting the whole to the level of api and generic functions. With a two year project we are actually working in this direction, but nothing would please me more if I could keep on calling it 'Drupal' and not a YADD (yet another Drupal derivation).

I'm looking in the last weeks how to get our work back Drupal and what exists there, but at the same time the conceptualization for SoS development is braking more features down, giving me quit a conflict of what to do. I simple won't like to create a YADD, I'm not in any position to call for developing the SoS as a 4.8 or 5.0 Drupal release. I'm hoping we could setup a cvs SoS-Drupal to play around and have discussions, I defiantly would like to do that. So I'm shouting out on this forum to find support. Please give your opinion.

In our work it became very clear how different some features are between SoS and the current Drupal CMS. You could summerise by saying CMS is controled from the top (administer) while SoS is buttom up. In other words users become manager over there own identity space and the software is making sure a good aggregation between the identities is manageable. There are all kinds of pro's and contra's in making a CMS more SoS. At the moment I'm trying to get a group up to discuss the features of SoS in a Drupal spirit. There will be all kind of other discussions about performance, maybe we should have a admin level to control what cost benefits get payed for what functionalities.

The following are additional improvements/enhancements to some OG contrib modules that I'll be working on. Evan Leeson of Catalyst Creative, Inc. has graciously offered to fund about half of the work, but CivicSpace Labs is looking for additional support to complete the spec. Please contact David Geilhufe if interested.

og_block_visibility: Allow blocks to be visible within multiple groups

Requirements:

1. Need to make an .install file which will create a table to store block/og relationships:
   
   og_block_visibility

   block_module (PK/FK -> block.module)	varchar(64)	The module to which this block belongs
   block_delta (PK/FK -> block.delta)	varchar(32)	Which of the module's blocks we're talking about
   og_nid (PK/FK -> node.nid)	int(10)	Organic group node ID

2. Need to modify UI for selecting groups to which visibility applies. Checkboxes are generally seen as more user-friendly, but will quickly clutter the screen, so I'm envisioning using a multiselect widget here.

Well, I submitted my application on time. But I was in the middle of finals and preparing for graduation so my application was not as fully thought out as I would have liked. Since no one has commented on my app in awhile I figured I would but forth my newer thoughts.

I orginally purposed a collaborative filtering approach that 'learned' what the user like based on what they read.

That is really hard to do. Furthermore, I was having a hard time coming up with a good solution to do that.

So, instead i would like to purpose a collaborative filtering approach called Slope One Predictors (http://www.daniel-lemire.com/fr/documents/publications/lemiremaclachlan_...)

It is updateable on the fly, effiecent and little information is required for the user. In other approaches, collaborative filtering alogrithms have the user fill out a survery to extract details about that user. Using this approach, only the simple votes are necessary. This paper outlines 3 related but different approaches which will allow Drupal admins to pick (presumally based on their users feedback). This is a simple approach which can later be agumented by a Information Filtering agents.

This algorithm is much easier to implement and the authors show that their alogrithm produces MAE scores similar to PEARSON algrithm even while being much simplier and much more efficient to query.

I am very interested in this project. I have already written my first module and I have a pretty decent grasp of Drupal API though it seems pretty extensive.

I have a Drupal 4.7 as my company's intranet site authenticated thru the corporate LDAP server. The same LDAP account is also use for our IMAP-based internal mail and this email address are registered in Drupal. Now, if someone lost his password, that means he will not be able to access both the drupal site and his IMAP email, and the sysadmin have to reset it for the user coz the user can't reset his own password since the link will be sent to his email which he can't access anyway.

I have several websites, most of which use drupal. I'm searching for someone who would like to be a web admin for a joke site that I have. I work on too many websites to be able to work as much as needs to be done on the site and I don't want it to become nothing. If you'd like to work for free and get credit, experience, and another website to add to your resume, give me an e-mail at ron[[at]]ronsnexus.com. Thanks

I have a community site where many users are now actively submitting various content to the site.

I would like to have all 'image' content appear in the 'user's blog' area. At present only 'blog' content appears there but in my case 'image' content can be the best method of posting user content and they are choosing this type more and more.

Consequence is that 'user's blog' looks like they may have stopped contributing and yet they may be the top contributor to the site. It is only by visiting the users tracker that all content shows up.