Changes between Version 60 and Version 61 of SoCAndBountyIdeas

Timestamp:

Mar 27, 2010, 5:05:54 PM (14 years ago)

Author:

John Bailey

Comment:

Tweak, link to the 2010 info page, and remove the SMS project idea, as I think it's a poor project idea.

SoCAndBountyIdeas

@@ -5 +5 @@
 If you need clarification on anything listed below, or want to run a new idea by us to see if we think it would make a good project, or if you have any other questions please feel free to ask on our [http://pidgin.im/cgi-bin/mailman/listinfo/devel devel mailing list].
 
-[wiki:SummerOfCode2007 Information about some Summer of Code 2007 projects]
+== Information About Projects By Year ==
+[wiki:SummerOfCode2010 Information about some Summer of Code 2010 projects] -- '''''Read this if you intend to apply for 2010! '''''
+[[BR]][wiki:SummerOfCode2009 Information about some Summer of Code 2009 projects]
 [[BR]][wiki:SummerOfCode2008 Information about some Summer of Code 2008 projects]
-[[BR]][wiki:SummerOfCode2009 Information about some Summer of Code 2009 projects]
+[[BR]][wiki:SummerOfCode2007 Information about some Summer of Code 2007 projects]
 
 == Notes about the following ideas ==
@@ -42 +44 @@
 
 == Better chat log viewer ==
-Our current chat log viewer has only limited functionality.
-  * Displays a tree hierarchy of all logs (so you don't have to use the "View Log" dialog)
-  * A search box that does real-time pruning of the tree as you type partial buddy names
-  * Grouped by contact!  So if I have "markdoliner" on AIM and "mark.doliner@gmail.com" on XMPP, the logs show up in one window, with some differentiation for me to tell which IM account was used.
+Our current chat log viewer has only limited functionality.  A proposal for this project idea should include plans to implement the following:
+  * Enhance log viewing in Pidgin by creating a new log viewer that will have:
+    * A tree hierarchy of all logs (so you don't have to use the "View Log" dialog for each buddy)
+    * A search box for buddies that does real-time pruning of the tree as you type partial buddy names
+    * Grouped by contact (person), so if I have "markdoliner" on AIM and "mark.doliner@gmail.com" on XMPP combined into a contact/person, the logs show up as being for one person, with some differentiation for me to tell which IM account was used.
+  * Optionally propose an external log viewer.  This has been requested a few times and we have historically ignored these requests.
 
 == Emoticon cache ==
-Currently pidgin does nothing with received emoticons. It would save a lot of bandwidth if there is a cache with received emoticons. It could also be merged with local custom smileys so we have an unified way to manage this files.
-It can be done per session, per conversation, per account or permanent cache (just as buddy icons). I think it would be better to have a permanent cache so it would allow to just fetch the smileys once.
+Currently Pidgin does nothing with received emoticons.  It could save a lot of bandwidth if a cache od received emoticons existed.  It could also be merged with local custom smileys so we have a unified way to manage these files.  The cache can be done per session, per conversation, per account, or as a global permanent cache (just as buddy icons).  The preferred method is a permanent cache so emoticons could be fetched only once.
 
 == ICQ TLC ==
@@ -59 +62 @@
   * Message size restrictions are likely wrong (#4628)
   * There are many open tickets about encoding issues.
-Your goal is to compare what libpurple does at a protocol level with what the official Windows ICQ client does, figure out where it differs, and to repair libpurple's implementation, extending Pidgin's, Finch's, and libpurple's capabilities where possible or necessary.
+Your goal is to compare what libpurple does at a protocol level with what the ''official Windows ICQ client'' does, figure out where it differs, and to repair libpurple's implementation, extending Pidgin's, Finch's, and libpurple's capabilities where possible or necessary.
 
 == MySpaceIM TLC ==
-Our MySpaceIM implementation is currently substandard. The plugin was developed as part of Summer of Code 2007 by reverse-engineering the protocol spoken by the official client (making it the first publicly-available third party MySpaceIM implementation) , and although it is functional, further reverse-engineering of the protocol and bug-fixing of the libpurple implementation is needed to bring our client up to par with the official client. 
+Our MySpaceIM implementation is currently substandard. The plugin was developed as part of Summer of Code 2007 by reverse-engineering the protocol spoken by the official client (making it the first publicly-available third party MySpaceIM implementation), and although it is functional, further reverse-engineering of the protocol and bug-fixing of the libpurple implementation is needed to bring our client up to par with the official client. 
 
 A list of known bugs is available at MsimToDo. Areas to consider working on include, but are not limited to:
@@ -102 +105 @@
     * [wiki:rekkanoryo]: Plugins should become gobjects and prpl's should be implementations of a !PurpleProtocolIface (or similarly named interface) as a mandatory requirement of gobjectification.
 
+{{{
+#!comment
 == A Protocol Plugin Which Sends SMS Message via Your Cell Phone ==
 
 Possibly by using a pre-existing library such as Gammu, KMobileTools or libgsm. You could also send by email using teleflip.com
-
+}}}
 {{{
 #!comment
@@ -123 +128 @@
 
 == libpurple detachable sessions ==
-This is an often requested feature to which the response is often "run Finch in screen". Ideally, it would be possible for a user to run Pidgin and Finch simultaneously on a computer, with both programs sharing the same data and connections. This would allow users to leave Pidgin open, yet still access their IMs over SSH with Finch.
-This requires an implementation of some sort of libpurple server, and a method for the clients to connect to that server, and access and display the buddy list, conversations, and chats.
+This is an often-requested feature to which the response is often "run Finch in screen". Ideally, it would be possible for a user to run Pidgin and Finch simultaneously on a computer, with both programs sharing the same data and connections. This would allow users to leave Pidgin open, yet still access their IMs over SSH with Finch.
+
+This requires an implementation of some sort of libpurple daemon, and a method for the clients to connect to that server, and access and display the buddy list, conversations, and chats.  Existing ongoing conversations' history should be visible in Pidgin or Finch when they connect to this daemon.