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 1 and Version 2 of ProgressReport


Ignore:
Timestamp:
May 3, 2008, 3:55:52 AM (16 years ago)
Author:
Maiku
Comment:

Added some vv and MSNP15 information

Legend:

Unmodified
Added
Removed
Modified
  • ProgressReport

    v1 v2  
    55=== Past ===
    66
    7 Google SoC 2006 project on msnp13 support: the first start on future MSN protocols support, was apparently never merged so it was not complete enough.
     7Google SoC 2006 project on MSNP13 support: the first start on future MSN protocols support, was apparently never merged so it was not complete enough.
    88
    9 Google SoC 2007 project on msnp14 support: UpdateMsnSupport, continuing from last summer. Did not produce completely problem-free functionality, but a base for what is now in Pidgin trunk and can be enabled by modifying configure.ac. Remaining tickets for the "Activate MSNPV14" target in roadmap: [http://developer.pidgin.im/query?status=new&status=assigned&status=reopened&milestone=Activate+MSNPV14 tickets]
     9Google SoC 2007 project on MSNP14 support: UpdateMsnSupport, continuing from last summer. Did not produce completely problem-free functionality, but a base for what is now in Pidgin trunk and can be enabled by modifying configure.ac.
     10
     11A branch of Pidgin has also been created for MSNP15 support. Remaining tickets for MSNP14 and MSNP15 are assigned to the "Activate MSNPV14" target in roadmap: [http://developer.pidgin.im/query?status=new&status=assigned&status=reopened&milestone=Activate+MSNPV14 tickets]
    1012
    1113[http://code.google.com/p/msn-pecan/ msn-pecan]: An actively developed alternative MSN protocol plugin.
     
    1315=== Future ===
    1416
    15 Two choices, fixing and activating current msnp14 code or merging msn-pecan. According to the msn-pecan's web site, there have been some disputes between other Pidgin developers and the msn-pecan developer, so it's not clear that the merge will happen without someone's "social engineering" in-between.
     17Two choices, fixing and activating current MSNP14/15 code or merging msn-pecan. According to the msn-pecan's web site, there have been some disputes between other Pidgin developers and the msn-pecan developer, so it's not clear that the merge will happen without someone's "social engineering" in-between.
    1618
    1719== Voice & Video ==
     
    2527=== Future ===
    2628
    27 No current plans are known, maybe some of the currently active developers could write some information here?
     29As part of Google's Summer of Code 2008, a [wiki:GSoC2008/VoiceAndVideo voice and video project] has been accepted. The plans are to first implement and stabilize voice and video on XMPP (making adding GTalk trivial) and then continuing onto the other protocols.
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!