Summer of Code/2013/Social Sugar project

< Summer of Code‎ | 2013
Revision as of 11:54, 21 June 2013 by Axitkhurana (talk | contribs) (→‎TODO: add meta-data to buddies done!)

This page tracks the progress of Akshit Khurana's GSoC project: "Social Sugar". More details about the project can be found on proposal page.

Work done

  • checked out previous work done: on webservices, journalx and sugar-network.
  • added social_ids to BuddyModel, still working on integration to access them in group view.
  • reading about GObject and Python GTK

Week ending Friday Jun 21st

  • read about GObject, gconf and some PyGTK.
  • am able to read social_ids from BuddyModel, access them in Group/Network views, send data through telepathy.

Adding social ids

What are social ids?

Social IDs identify a user on external platforms uniquely.

To create mini profiles in group view, we can add a social_ids dictionary to BaseBuddy model in addition to other properties like nick and color. social_ids is a mapping of `service key` : `uid`. E.g. {'/desktop/sugar/user/social/project_sharing_website': '19348r93jfioaf', '/desktop/sugar/user/social/another_service': 'adfjafp1asdf'}

social_ids can be stored in gconf. As multiple social_ids are added, we will have a gconf file that looks like this:

 <gconf>
   <entry name="project_sharing_website" mtime="1370907925" type="string">
       <stringvalue>19348r93jfioaf</stringvalue>
   </entry>
   <entry name="another_service" mtime="1370907925" type="string">
       <stringvalue>adfjafp1asdf</stringvalue>
   </entry>
 </gconf>

These social_ids will be obtained when a user adds his account to webservices module.

TODO

  • see how comments work and think which new methods we should need to get our "interactions" information

Code

socialsugar branch on my sugar fork on github.