[geeklog-devel] GSOC - Socnet

Sat Mar 20 09:48:47 EDT 2010

Hi,

Other that revamping of the groups and access control, I believe that
notification of the activity is most important. For that I propose two
steps.

1. A user Profile page on which all activity streams are shown, from each of
his friends and himself/herself. This is a single point web based
notification area.

2. The second is to stream the notification. This can be designed according
to the Atom feed standards. The user might choose to make these feeds email
based, through which he will get email notification for them. As discussed
above, the format of notifications should be standardized across all
projects, even calendar and core notification support, because the services
can be scaled to mix with each other in the future (or even now).
This profile page must be very easy to manage and must not clutter up the
user space.
I think this Socnet is more of a community builder across GL, and must be
provided good backend support so that other services can build over it in
the  future.

Regarding the groups.

* However the admins of GL should be able to administer those end user
groups as well.*
I was wondering how an admin can keep a tab on the different groups a end
user is creating. It might become unmanageable.

Regards
Ruturaj

On Sat, Mar 20, 2010 at 6:39 PM, Randy Kolenko <Randy.Kolenko at nextide.ca>wrote:

> Hi Jakh,
>
> In regards to notifications, Geeklog doesn't have a centralized
> notification system other than COM_mail.  Other discussion threads on this
> list have already discussed why things like email throttling etc need to be
> established.  However that, I feel, is outside of the realm of what Socnet
> should provide.
>
> Socnet should have a basic notification system.  Whether that is through
> email or a combination of email and a notification "wall" for the user.
>
> In regards to meshing with other projects -- socnet will provide APIs for
> other plugins to use.  If the apis become stable and mature enough during
> the GSoC run for 2010, they could conceivably be used by, say, the calendar
> plugin revamp project to open up calendar content to social networking.
>  That, however, is probably not going to happen.
>
> -randy
>
>
>
>
> From: Jakh Daven [mailto:tuxcanfly at gmail.com]
> Sent: Saturday, March 20, 2010 8:29 AM
> To: Geeklog Development
> Subject: Re: [geeklog-devel] GSOC - Socnet
>
> Hi Randy,
> I am a would-be student participant and have lurking around this mailing
> list and the bug tracker for some time now.
>
> The socnet wiki page mentions that socnet will be meshed with other
> project. This mostly probably refers to core notification support project as
> socnet has many components that could use core notification apis.  My
> question is: What is the responsibility of socnet with regards to
> notifications? Will socnet have notification stubs that will use core
> notification apis after meshing? Or will socnet proceed independently and
> have a 'basic' notification system?
>
> Thanks,
> Jakh
>
> On Fri, Mar 19, 2010 at 4:17 AM, Randy Kolenko <Randy.Kolenko at nextide.ca>
> wrote:
> Hi Ruturaj,
>
> 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.
>
>
> -randy
>
> -----Original Message-----
> From:   Ruturaj Dhekane [mailto:ruturajmd at gmail.com]
> Sent:   Thu 3/18/2010 5:19 PM
> To:     geeklog-devel at lists.geeklog.net
> Cc:
> Subject:        [geeklog-devel] GSOC - Socnet
>
> Hi!
>
> I was looking at the Socnet Task, and would like post so that I understand
> it better.
> (here a user is referenced as a user is a entity, all other users are his
> friends)
>
> 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
> cluttered windows.
>
> A idea would be to use a socnet specific page per user on which he gets all
> the updates.
> 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.
>
> Regards
> Ruturaj
>
> --
> [Geekru2]
>
>
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>

-- 
[Geekru2]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20100320/a41a0a89/attachment.html>