Community:SummerOfCode12

Skills needed: some C++ for core Gecko, some JS and opportunity to use XUL to build the UI - probably as an add-on initially.

Language: C++.

Language: C++.

The implementation of this feature will mostly involve three languages: XUL, CSS and JS. Great CSS skills are important, and knowledge of XUL is a plus, or at least a good understanding of the different CSS layout models (specially the flexbox model)

tightly controlled, irreversible-without-password setting, but rather a feature that will make it harder to accidentally break or deteriorate the Firefox experience. Skills required: good JS skills and ability to work with large codebases

Skills Required: XUL, Javascript

Skills Required: Windows API, C/C++, Javascript, possibly XUL.

Level of difficulty: easy to medium Skills needed: JavaScript; Helpful: MongoDB & Information Visualization in the browser using JS and an infoviz toolkit like protovis or D3

Level of difficulty:easy to medium Skills Needed: Python, Some Django experience helpful.

Level of difficulty: medium to hard Skills Needed: Javascript, XUL/XBL, CSS

Level of difficulty: hard Skills required: JS, C++, XPCOM, XUL

Level of difficulty: medium Skills required, JS and/or C++

Level of difficulty: medium to hard, depending on how deep we go here. Skills required: C++.

Level of difficulty: medium to hard, depending on the provider API and how well it maps to our provider interface Skills required: JS

Level of difficulty: hard Skills required: JS or C++.

Level of difficulty: hard. Skills required: JS, HTML

Level of difficulty: medium?

Level of difficulty: medium (easy if initial groundworks is available)

enumerateWindows();
 Shell.enumWins[0].document.getElementById("tabmail").openTab(
  "chromeTab", {chromePage: "chrome://messenger/content/messengercompose/messengercompose.xul"});

Then try playing around with it, sending a message, etc. As you can see, the basic concept works, but there are currently issues with the UI. Your job will be to sort them out, make everything work properly, and ship your code as part of Thunderbird.

Easier way: Tools -> Error Console, then

top.opener.openTab("chromeTab", {chromePage: "chrome://messenger/content/messengercompose/messengercompose.xul"});

Level of difficulty: hard. Skills needed: will require writing XUL (menus will probably need to be moved out into an overlay), JavaScript (passing menu commands down to the child iframe) and CSS (to fix theming issues) and writing unit tests to ensure that things work as expected. Since Mac OS X has a global menu, getting it right might require more work. You will need access to a Mac for your proposal to be accepted..

Level of difficulty: hard Skills needed: JavaScript; HTML (no XUL)

• unread mail,
• pending events,
• unread RSS items,
• a couple icons to open websites in new tabs (for, say, google contacts or twitter),
• to-do list, etc.

Level of difficulty: hard Skills needed: JavaScript; HTML (no XUL)

The job of the shell service is to provide OS integration hooks. The full list of hooks is as follows:

• Check to see whether SeaMonkey is the default browser, mail, news and/or RSS client.
• Set SeaMonkey as the default browser, mail, news and/or RSS client.
• Set an image as the desktop wallpaper.
• Set the desktop background colour.

It may be possible to make some of these checks optional, however currently as a minimum it must be possible to set SeaMonkey as the default browser and it must be possible to set an image as the desktop wallpaper.

Skills needed: C++; some knowledge of GConf/GIO or Cocoa APIs as appropriate.

This should include full usual bookmark handling for those URLs, including sidebar support.

Relevant bugs:
Bug 14988 - Allow bookmarking of e-mail/Usenet messages
Bug 77186 - allow drag and drop bookmarking of mail / news messages
Bug 77195 - support news, imap, mailbox message urls from the browser
Bug 178003 - Restore access to Sidebar from Mail/News, Compose and Addressbook

Skills needed: JS, XUL; maybe C++.

While this would basically mean porting Thunderbird's bug 251296, the UI should be more in sync with the SeaMonkey look and feel, e.g. columns for unread count, size, etc; a drop down menu for switching views; allow custom folder views; ...

Skills needed: JS, XUL; maybe C++.

          [is                         ]
          [isn't                      ]
Score     [is lower than              ][\/]     [<value in range>]
          [is lower than or equal to  ]
          [is greater than            ]
          [is greater than or equal to]

and actions

[Increment score by]
[Decrement score by][\/]     [<value in range>]
[Set score to      ]

Each message would start with a score of 500 before filters get applied.

This feature will require MailNews Core C++ hacking.

Related:
Bug 151622 "filters that score messages"

Skills needed: CSS; some graphical ability.

Skills needed: SVG, DOM, moderate-to-good English writing skills.

Skills needed: HTML and CSS. Moderate-to-good English writing skills.

Skills needed: JavaScript, HTML, CSS, Python. Django framework familiarity a big plus.

Useful skills: some webdev and Python programming experience

Lots of users don't try a new IM client only because they don't want to spend time reconfiguring all their IM accounts. Being able to import accounts from other clients installed on the system would help Instantbird adoption. The student should focus on the dominant IM clients (Windows Live Messenger, AIM, ...) and on the other multi network IM clients (Digsby, Pidgin, Trillian, Miranda, ...). The student will need to study the way other IM clients store their profile data (reverse engineering may be required), think of an architecture to share as much code as possible between the various import modules, and implement import modules for some clients. Students should propose particular IM clients they plan to implement support for.

Skills needed: JavaScript XPCOM, XUL, maybe some reverse engineering.

A student working on this project will either extend the existing Error Console or create a new console from which it will be possible to see what data has been exchanged for each account. Example of desirable features: copying a log of whatever happened with an account from the beginning of the connection attempt; syntax highlighting of the exchanged data (requires some parsing of the data exchanged by protocols like XMPP, IRC, Twitter (JSON)); letting the user type and send a raw message to the server.

Skills needed: JavaScript, XUL/XBL, some basic understanding of XMPP, IRC and Twitter protocols.

This project intends to explore the possibilities for Voice and Video communication using the Mozilla platform. The student will need to experiment both with usage of the microphone and webcam and with codecs available in the system on the three supported OSes. Compatible implementations of the various IM protocols that support these features is out of the scope of this project, but the student will at least need to prove that s/he has seriously investigated using the various open source projects that have started some work on this. A (mostly) working proof of concept is expected. UI mockups for what a well-thought user interface for voice and video could be would be appreciated.

Skills needed: JavaScript, XUL, XPCOM, maybe C++.

Skills needed: C or C++ depending on the project, some JS, some familiarity with the project being ported, other technologies if the project uses it (for example, for a game that uses OpenGL, OpenGL would be needed)

support for the standalone runtime that runs the webapps, and support for the installation process that installs them to the OS. Skills needed: knowledge of Linux desktops, specially GTK APIs, is required, and good C++ and JS skills.

The ideal candidate will have some combination of experience with Python, JavaScript, and flow-based programming, and a demonstrated ability to get up to speed with the other fields by the start.