Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 7 and Version 8 of SoCAndBountyIdeas


Ignore:
Timestamp:
Jul 10, 2007, 10:00:21 AM (17 years ago)
Author:
John Bailey
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SoCAndBountyIdeas

    v7 v8  
    11Periodically we see or come up with ideas that would make a good Google Summer of Code project.  Many of these get forgotten when we actually get around to listing ideas for the next summer.  Here is a space to store them.
    22
     3Some of these ideas may be insufficient for an entire Summer of Code project; in those cases it will probably be desirable to combine two or more ideas listed here into a single project.
    34
    45== ICQ TLC ==
    5 Our ICQ implementation in the oscar code is substandard in a variety of respects.  We do not have full support for ICQ status, ICQ privacy, or ICQ formatting to name just a few shortfalls.  Others include our buddy list management, message size restrictions and ICQ's chats.  Your goal is to compare what Pidgin does at a protocol level with what the official winicq client does, figure out where it differs, and to repair Pidgin's implementation, extending Pidgin's capabilities where possible.
     6Our ICQ implementation in the OSCAR code is substandard in a variety of respects.  We do not have full support for ICQ status, ICQ privacy, or ICQ formatting to name just a few shortfalls.  Others include our buddy list management, message size restrictions and ICQ's chats.  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.
     7
     8== Yahoo! TLC ==
     9Our Yahoo! implementation is currently a substandard in many ways.  For example, file transfers don't work between libpurple clients and the current versions of the official client.  We also don't support the newest protocol revision, which allows the MSN interoperability to function.  Your task is to compare what libpurple does at a protocol level with what the official Windows Yahoo! client does, figure out where it differs, and then repair libpurple's implementation.
    610
    711== Finch Improvements ==
    8 
    9 * A new window manager (or improvements to the existing ones). For
    10 example, a tiling window manager would be super awesome.
    11 
    12 * Improve the widget-packing in a container (GntBox), may be even have a
    13 grid like container.
    14 
    15 * Implement plugin-pref-ui using the request-api.
    16 
    17 * Have python (or some other) bindings for libgnt. This would allow
    18 creating functional/useful dbus clients with gnt ui.
    19 
    20 * Add some more items in the buddy-list menu. Copy the gstreamer,
    21 auto-reconnection etc. code from Pidgin to Finch
    22 
    23 * Have a spell checker, which would add some way of indicating spelling
    24 errors, suggesting possible corrections etc.
     12 * A new window manager (or improvements to the existing ones). For example, a tiling window manager would be super awesome.
     13 * Improve the widget-packing in a container (GntBox), may be even have a grid-like container.
     14 * Implement the Plugin Prefs UI using the Request API--this will likely require some extension of the Request API.
     15 * Have python (and/or some other) bindings for libgnt. This would allow creating functional/useful DBus clients or additional applications with a GNT-based UI.
     16 * Add some more items in the buddy list menu.
     17 * Have a spell checker, which would add some way of indicating spelling errors, suggesting possible corrections, etc.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!