[geeklog-devel] GSOC - Socnet
Randy.Kolenko at nextide.ca
Thu Mar 18 18:47:46 EDT 2010
Thanks for your interest in the Socnet project for GSoC.
To respond to your email in the best possible way, I will respond to each of your points in order:
1. Geeklog's current group management is fine for core Geeklog. As highlighted in the GSoC Geeklog wiki, there was already a good discussion on how to easily extend the current group structure that would easily allow the current core group code to exist with the minor data schema change.
2. You're correct in how you've explained the social networking capabilities. To boil it down, Socnet is based on giving end users group creation abilities and all administration that surrounds those groups as noted in the socnet wiki page. However the admins of GL should be able to administer those end user groups as well.
3. User's groups are totally managed by the end user and owned by the end user. They choose who they'd like to have as part of their social groups.
That means that there is most certainly the ability to have one "friend" as part of many socnet groups.
4. Notification of content changes is something that is certainly a must for social networking. However there is some debate still left to be had in terms of how those notifications happen. I would expect Socnet proposals to have something outlining how notifications could be handled.
Bullet item 4 above hints at having an API made available by the Socnet plugin that would help surface a permissions "widget" in any plugin that asks for it to be surfaced -- this is the beginnings of how content is secured and stored for social networks.
From: Ruturaj Dhekane [mailto:ruturajmd at gmail.com]
Sent: Thu 3/18/2010 5:19 PM
To: geeklog-devel at lists.geeklog.net
Subject: [geeklog-devel] GSOC - Socnet
I was looking at the Socnet Task, and would like post so that I understand
(here a user is referenced as a user is a entity, all other users are his
As few of the initial tasks suggest, there needs to be a big change in the
group management for geeklog.
A typical mechanism as seen in the other Social networking sites is,
A user creates groups (friends, family, students)
Permission to view a document is given to the groups. Can It be individual
members also? Probably yes, cause some friends might not be categorized into
any group by the user.
Following this, A friend needs to connect to the user, this is a request
accept mechanism. A user might choose not to have a accept, and all requests
are automatically accepted.
He should be able to move the friends in the groups and delete them
*Do we need to think of having a friend part of multiple groups?*
And finally notifying the friend that content has changed by the user.
I think here a lot of new ideas can be put in cause the present structure of
notification by other social networking sites is either spam-like email or
A idea would be to use a socnet specific page per user on which he gets all
he should be able to categorize the updates or stop receiving them.
One of the current trends is to allow social networking sites to work with
wide variety of mashups, so a api could be provided to allow users
to/develop quick mashup that use socnet.
The Ideas page was pretty self explainatory, but I just want to be sure, I
understand the problem and its requirements completely.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 4230 bytes
Desc: not available
Url : <http://eight.pairlist.net/pipermail/geeklog-devel/attachments/20100318/de9155c2/attachment.bin>
More information about the geeklog-devel