By mixel on

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.