SoC socialnetworking - Revision history

Dirk: added a note that his old project has been superseded by the SocNet project

2010-02-27T20:04:55Z

added a note that his old project has been superseded by the SocNet project

Dirk: clarified relation to OpenSocial; added XFN as an option

2009-02-14T22:11:09Z

clarified relation to OpenSocial; added XFN as an option

Dirk: Typos and such

2009-02-05T14:46:13Z

Typos and such

Blaine: /* Level of Difficulty */

2008-03-02T18:54:04Z

‎Level of Difficulty

Blaine: /* Level of Difficulty */

2008-03-02T18:53:50Z

‎Level of Difficulty

Blaine: /* Goals */

2008-03-02T18:52:12Z

‎Goals

Blaine at 18:51, 2 March 2008

2008-03-02T18:51:26Z

Blaine: /* Goals */

2008-03-02T18:50:27Z

‎Goals

Blaine: /* Ideas */

2008-03-02T18:42:32Z

‎Ideas

Blaine at 18:42, 2 March 2008

2008-03-02T18:42:09Z

← Older revision		Revision as of 20:04, 27 February 2010
Line 1:		Line 1:
−	~~<center>(Return to the main~~ idea page for the [[Google Summer of Code]])~~</center>~~	+	This idea page for the [[Google Summer of Code]] has been superseded by a new project idea: [[SoC_social_network_support\|Social Networking Support (SocNet)]]. This project outline is therefore only of historical interest and you can not apply for this project in future instances of the Google Summer of Code. Please see our [[Google Summer of Code\|ideas page]] for a current list of GSoC project ideas.
		+

	== Incentive ==		== Incentive ==

@@ Line 15: / Line 15: @@
 == Use Cases ==
 * Users features or blocks can be added so that I can easily monitor new updates to the site by my friends or watch list.
 * A user could create a private MediaGallery Album and then setup access to their friends list.
@@ Line 20: / Line 21: @@
 == Optional Ideas ==
-* Implement Google's [http://code.google.com/apis/opensocial/ OpenSocial API]
 * Support for [http://www.apml.org/ APML] (Attention Profile Markup Language)
 == Level of Difficulty ==

@@ Line 7: / Line 7: @@
 == Goals ==
-Geeklog has the idea or Groups which the site Admin can setup but users can not define their own groups or list of friends. Users would need to accept the inviation to join another members group but once joined they could view each others private content as determined by the content owner.
+Geeklog has the idea or Groups which the site Admin can setup but users can not define their own groups or list of friends. Users would need to accept the invitation to join another members group but once joined they could view each others private content as determined by the content owner.
 Sites like Facebook do this well and can be a model for what is needed. Users should be able to define multiple access control profiles so not all friends have to be give the same access to a users content.
@@ Line 27: / Line 27: @@
 ''medium''
-This project will require someone to spend time understanding how Geeklog maintains permissions and it's permission related functions. This could be implemented as a plugin but I suspect changes to the CORE SEC functions may be needed to extend the new permission checks.
+This project will require someone to spend time understanding how Geeklog maintains permissions and its permission related functions. This could be implemented as a plugin but I suspect changes to the core SEC_ functions may be needed to extend the new permission checks.
-As noted, new API's need to be created so other plugins can use the new features so this is not likely a plugin by itself but extensions to the core code.
+As noted, new APIs need to be created so other plugins can use the new features so this is not likely a plugin by itself but extensions to the core code.
 UI changes will be needed to integrate these new features so a user can manage their friends list and different access profiles.

@@ Line 31: / Line 31: @@
 As noted, new API's need to be created so other plugins can use the new features so this is not likely a plugin by itself but extensions to the core code.
-UI changes will be needed to integrate these new features so a user can manager their friends list and different access profiles.
+UI changes will be needed to integrate these new features so a user can manage their friends list and different access profiles.
 [[Category:Summer of Code]] [[Category:Development]]

@@ Line 27: / Line 27: @@
 ''medium''
-This project will require someone to spend time understanding how Geeklog maintains permissions and it's permission functions. This could be implemented as a plugin but I suspect changes to the CORE SEC functions may be needed to extend the new permission checks.
+This project will require someone to spend time understanding how Geeklog maintains permissions and it's permission related functions. This could be implemented as a plugin but I suspect changes to the CORE SEC functions may be needed to extend the new permission checks.
 UI changes will be needed to integrate these new features so a user can manager their friends list and different access profiles.

@@ Line 10: / Line 10: @@
 Sites like Facebook do this well and can be a model for what is needed. Users should be able to define multiple access control profiles so not all friends have to be give the same access to a users content.
 * Develop Trusted Members interface and control/access to trusted content
 * Add new GL API support for plugins to use new features

@@ Line 5: / Line 5: @@
 Geeklog does not have any current core features for individual members to develop their own trusted friends list so they for which they can share content with.
-== Ideas ==
+== Goals ==
 Geeklog has the idea or Groups which the site Admin can setup but users can not define their own groups or list of friends. Users would need to accept the inviation to join another members group but once joined they could view each others private content as determined by the content owner.