Community:SummerOfCode11:Brainstorming: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (→‎Mozilla Platform: fix markup error)
(Transfer ideas to main page.)
Line 29: Line 29:
!Mentor(s)
!Mentor(s)
!Comments
!Comments
|-
|Improve Cairo performance to match Skia
|There are a number of areas where [http://code.google.com/p/skia/ Skia] outperforms [http://www.cairographics.org/ Cairo]. Find them, and improve Cairo to match or exceed Skia's performance.
|jrmuizel
|jrmuizel
|
|-
|Improve border corner joins
|Our rendering of CSS border corners is very sloppy, particularly when the corner is rounded or when two styles intersect. You could code [https://bugzilla.mozilla.org/show_bug.cgi?id=382721 dotted and dashed rounded corners] and/or improve their [https://bugzilla.mozilla.org/show_bug.cgi?id=19963 interaction with other styles], or work on making other joins prettier.
|fantasai
|fantasai
|-
|Create a JPEG XR decoding library
|[http://en.wikipedia.org/wiki/JPEG_XR JPEG XR] gives us better compression and other useful features like HDR and alpha channels. The library should be as similar to libjpeg as possible. It would be a "from scratch", freely licensed version and will need a student that is very comfortable with image compression and as has ideally written decompressors from scratch before.
|jrmuizel
|jrmuizel
|
|-
|Implement HTML Speech proposal
|[http://www.w3.org/2005/Incubator/htmlspeech/charter HTML Speech XG] will have a proposal for integrating speech recognition and text-to-speech functionality to web pages. Google has proposed already one [http://www.w3.org/2005/Incubator/htmlspeech/2010/10/google-api-draft.html API], but it is expected that the proposal from XG won't look exactly like that. For implementation [http://mozillalabs.com/rainbow/ Rainbow] can be useful.
|smaug
|smaug
|davidb: Hey Olli, regarding tts, have you seen Google's [http://code.google.com/chrome/extensions/trunk/experimental.tts.html experimental impl]?
No, I hadn't seen that, but there is more reasonable
[http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2010Nov/att-0036/htmltts-draft.html proposal]
|-
|}
|}


Line 67: Line 40:
!Mentor(s)
!Mentor(s)
!Comments
!Comments
|-
|Unified Communications add-on
|Develop the base for an add-on that creates a unified messaging UI inside browser tabs, following the [http://wiki.kairo.at/wiki/RMD RMD concept]. This should work with feed display and twitter integration in the beginning, but extensible to be able to support other communications later.
|KaiRo
|KaiRo
|Not sure if this belongs in Firefox but there's no add-ons category.
|}
|}


Line 121: Line 88:
! Mentor(s)  
! Mentor(s)  
! Comments
! Comments
|-
| OCSP improvements
| Implement server-side OCSP stapling. (A patch for client-side OCSP stapling exists.) Implement client-side disk cache of OCSP responses.
| Wan-Teh Chang
| Wan-Teh Chang
| You must be an experienced C programmer and can work full time on the project.
|-
| New crypto algorithms for NSS softoken
| Add DSA with key sizes > 1024 bits (bug 475578); modes of operation for AES: GCM (bug 373108), CTR (bug 373106), CFB (bug 358219); and TLS 1.2 PRF to the NSS softoken.
| Wan-Teh Chang
| Wan-Teh Chang
| You must be an experienced C programmer and can work full time on the project.
|}
|}


Line 167: Line 122:
!Mentor(s)
!Mentor(s)
!Comments
!Comments
|-
|A real MediaWiki parser for Python
|There are no MediaWiki parsers for Python with extensible syntax or multiple output formats. We've felt this pain in SUMO, which uses MW syntax in its knowledge base, resulting in hacks upon hacks to support features like platform-sensitive content, inclusions, and templates. We propose to implement [[Community:SummerOfCode11:MediaWikiParser|a new MW parser]] that generates proper parse trees, allows for pluggable syntax, and does not drive callers out of their minds.
|ErikRose
|ErikRose
|
|-
|}
|}


Line 218: Line 166:
!Mentor(s)
!Mentor(s)
!Comments
!Comments
|-
|'''Tilt'''
|A WebGL-based 3D visualization of a Webpage. The developer will create a WebGL representation of a web-page that allows a user to rotate the page through axes to see the nesting of DOM nodes within the document. Floats and absolute positioned elements will be visible above and below the page based on their z-index. Tilt will be used as an additional visualization tool as part of a next-generation web page inspector.
| Rob Campbell
| Rob Campbell
| Candidate must be proficient in JavaScript, DOM programming and have a good grasp of 3D graphics preferably some WebGL or OpenGL experience.
|}
|}


Revision as of 16:58, 4 March 2011

This page is for anyone to submit ideas for Google Summer of Code projects with Mozilla for 2011. As it is open to all, it will inevitably contain suggestions of wildly variable quality.

Students: ideas approved by the SoC admins are here. You can also submit ideas from this page, but they are rather less likely to be accepted. (There's probably a reason they haven't been moved to that page.) You can also submit your own ideas - you don't have to put an idea on this page and get it made official in order to propose it.

How To Make Good Suggestions

Before adding an idea to this list, please consider the following:

  • Be specific. It's hard to understand the impact of, or the size of, vague proposals.
  • Consider size. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
  • Do your research. Support the idea with well-researched links.
  • Don't morph other people's ideas. If you have a related idea, place it next to the existing one, or add a comment.
  • Insert only your own name into the Mentor column, and then only if you are willing to take on the responsibility. If you think the SoC admins won't know you, leave contact details.
  • Check back regularly. The administrators may have questions about your idea that you will need to answer.
  • Know when to give up. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.

Suggestion List

Links to ideas lists from previous years.

Mozilla Platform

Title Details - with links as appropriate Reporter Mentor(s) Comments

Firefox

Title Details - with links as appropriate Reporter Mentor(s) Comments

Thunderbird

Title Details - with links as appropriate Reporter Mentor(s) Comments

Calendar

Title Details - with links as appropriate Reporter Mentor(s) Comments

Camino

See the Camino Summer of Code page for project suggestions.

SeaMonkey

Title Details - with links as appropriate Reporter Mentor(s) Comments

NSS (Network Security Services)

Title Details - with links as appropriate Reporter Mentor(s) Comments

Bugzilla

Title Details - with links as appropriate Reporter Mentor(s) Comments

Mobile/Fennec

Title Details - with links as appropriate Reporter Mentor(s) Comments

Firefox Support (Sumo)

Title Details - with links as appropriate Reporter Mentor(s) Comments

Rhino

Title Details - with links as appropriate Reporter Mentor(s) Comments

Mozilla IT Infrastructure

Title Details - with links as appropriate Reporter Mentor(s) Comments

Mozilla Services (Sync, Identity, etc)

Title Details - with links as appropriate Reporter Mentor(s) Comments

Developer Tools

Title Details - with links as appropriate Reporter Mentor(s) Comments

Drumbeat/Batucada

Any hacking projects connected to a Drumbeat project or Batucada.

Title Details - with links as appropriate Reporter Mentor(s) Comments
Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Community:SummerOfCode11:Brainstorming&oldid=288896"