Community:SummerOfCode08: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
You may wish to consider [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] before making your application. Then [http://code.google.com/soc/student_step1.html apply here] (you'll need a Google Account). | You may wish to consider [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] before making your application. Then [http://code.google.com/soc/student_step1.html apply here] (you'll need a Google Account). | ||
==Firefox | ==Mozilla Platform== | ||
{| class="standard-table" | |||
|- | |||
!Title | |||
!Abstract - links to details/bugs/etc | |||
!Reporter | |||
!Mentor(s) | |||
!Comments | |||
|- | |||
| valign="top" | NPAPI Test suite | |||
| valign="top" | {{bug|105959}} - Write a comprehensive testsuite plugin for the NPAPI implementation of the browser | |||
| valign="top" | bsmedberg | |||
| valign="top" | bsmedberg | |||
| | |||
|- | |||
| valign="top" | Package Dehydra for General Use | |||
| valign="top" | Create an automated build system for [[Dehydra_GCC]]: create a buildbot setup which builds and packages GCC and dehydra on Linux and mac. | |||
| valign="top | bsmedberg | |||
| valign="top | bsmedberg | |||
| | |||
|- | |||
| valign="top" | Convert Litmus tests to automated tests | |||
| valign="top" | We have many tests in Litmus that must be ran by a person. This won't catch bugs nearly as fast as if many of these were found at check-in time (or when a developer is hacking on a module). | |||
| valign="top" | [[User:comrade693|Shawn Wilsher]] | |||
| valign="top" | [[User:comrade693|Shawn Wilsher]] | |||
| valign="top" | | |||
|} | |||
==Firefox== | |||
{| class="standard-table" | {| class="standard-table" | ||
| Line 38: | Line 67: | ||
!Mentor(s) | !Mentor(s) | ||
!Comments | !Comments | ||
|- | |||
| valign="top" | Implement Full iTIP/iMIP support | |||
| valign="top" | Lightning uses the [http://tools.ietf.org/html/draft-ietf-calsify-2446bis-05 iTIP/iMIP protocol] to send and receive email invites. Currently, Lightning has the ability to send and receive event invitations. It can also send and reply to event updates. We are asking for help to implement deletion of appointments, rescheduling invitations, and delegating invitations to another person. We must also do this in a way that upholds the iTIP specification and still manages to interoperate with Outlook invitations from Outlook 2000, 2003, and 2007 (as well as Evolution, Apple iCal, and other calendar clients - these tend to be more standards based, though). Implementing this would improve Lightning's interoperability significantly. | |||
| valign="top" | [[Simon Paquet]] | |||
| valign="top" | [[Clint Talbert]] | |||
| valign="top" | | |||
|- | |||
| valign="top" | Enhance Sunbird's/Lightning's accessibility | |||
| valign="top" | Our accessibility is pretty basic right now (we've implemented keyboard shortcuts and accesskeys in most of the application) but to really make the application accessible, we still need to implement the nsIAccessible class for all our bindings, improve the overall keyboard navigation and make sure that our apps works well with screen readers. | |||
| valign="top" | [[Simon Paquet]] | |||
| valign="top" | [[Philipp Kewisch]] | |||
| valign="top" | | |||
|- | |||
| valign="top" | Implement natural language parsing for event creation | |||
| valign="top" | It would be totally cool and has been requested by our users for quite some time, if you could just drag and drop a text or an email to your calendar and our app would automatically parse the text/email for possible dates, times and locations and prefill the event details with this information. Bonus points if you make this localizable as well. | |||
| valign="top" | [[Simon Paquet]] | |||
| valign="top" | [[Philipp Kewisch]] | |||
| valign="top" | | |||
|} | |} | ||
| Line 60: | Line 107: | ||
!Mentor(s) | !Mentor(s) | ||
!Comments | !Comments | ||
|- | |||
|Anti-Discrimination Extension | |||
|Create an extension for SeaMonkey (possibly working in Firefox as well) that utilizes a local list (storage format TBD) to warn users about websites that discriminates against certain browsers by shutting them out, possibly even doing dynamic user agent spoofing to make the websites work in SeaMonkey despite that. | |||
This is a first part of the [[User:KaiRo:Dynamic_UA_Spoofing_Mechanism|dynamic UA spoofing mechanism]] proposed earlier, the project does not aim for this full mechanism, only for the basic client-side functionality. | |||
|Robert Kaiser | |||
|possibly Robert Kaiser | |||
| | |||
|- | |||
|Using the Places Backend | |||
|Make SeaMonkey's browsing history (and possibly bookmarks) build on the Mozilla platform's "places" backend. The target is to leave the user interface very similar to current SeaMonkey while building on a more modern, SQLite-based backend that allow extensions to add an interface for bookmark tagging and similar features of this new backend. This mostly involves porting front end code from Firefox and tweaking it so that it resembles the well-known SeaMonkey user interface, and can be done in separate steps for history and bookmarks. | |||
|Robert Kaiser | |||
| | |||
| | |||
|} | |} | ||
Revision as of 20:16, 11 March 2008
This page lists all the Google Summer of Code 2008 projects with confirmed mentors, and which have been approved by the SoC administrator. Please do not edit this page; new suggestions can be made on the Brainstorming page.
Potential students: you may choose from the list below, from the Brainstorming page, or submit your own proposal. Be wary when choosing from the Brainstorming page; there is often a good reason why the ideas haven't made it to this page.
If the idea has no mentor (or the person who has volunteered is unsuitable) then we would need to find a mentor; you will increase your chances of success if you find one for yourself and submit their name with your application. A mentor should generally be a respected Mozilla project contributor with expertise in the relevant field; projects involving integration with other code could be mentored by someone with expertise in the other codebase. However, lack of a mentor should not be a deterrent - please, still apply even if you don't have one.
You may wish to consider How Not To Apply For Summer Of Code before making your application. Then apply here (you'll need a Google Account).
Mozilla Platform
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|---|---|---|---|
| NPAPI Test suite | bug 105959 - Write a comprehensive testsuite plugin for the NPAPI implementation of the browser | bsmedberg | bsmedberg | |
| Package Dehydra for General Use | Create an automated build system for Dehydra_GCC: create a buildbot setup which builds and packages GCC and dehydra on Linux and mac. | bsmedberg | bsmedberg | |
| Convert Litmus tests to automated tests | We have many tests in Litmus that must be ran by a person. This won't catch bugs nearly as fast as if many of these were found at check-in time (or when a developer is hacking on a module). | Shawn Wilsher | Shawn Wilsher |
Firefox
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Thunderbird
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Calendar
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|---|---|---|---|
| Implement Full iTIP/iMIP support | Lightning uses the iTIP/iMIP protocol to send and receive email invites. Currently, Lightning has the ability to send and receive event invitations. It can also send and reply to event updates. We are asking for help to implement deletion of appointments, rescheduling invitations, and delegating invitations to another person. We must also do this in a way that upholds the iTIP specification and still manages to interoperate with Outlook invitations from Outlook 2000, 2003, and 2007 (as well as Evolution, Apple iCal, and other calendar clients - these tend to be more standards based, though). Implementing this would improve Lightning's interoperability significantly. | Simon Paquet | Clint Talbert | |
| Enhance Sunbird's/Lightning's accessibility | Our accessibility is pretty basic right now (we've implemented keyboard shortcuts and accesskeys in most of the application) but to really make the application accessible, we still need to implement the nsIAccessible class for all our bindings, improve the overall keyboard navigation and make sure that our apps works well with screen readers. | Simon Paquet | Philipp Kewisch | |
| Implement natural language parsing for event creation | It would be totally cool and has been requested by our users for quite some time, if you could just drag and drop a text or an email to your calendar and our app would automatically parse the text/email for possible dates, times and locations and prefill the event details with this information. Bonus points if you make this localizable as well. | Simon Paquet | Philipp Kewisch |
Camino
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
SeaMonkey
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|---|---|---|---|
| Anti-Discrimination Extension | Create an extension for SeaMonkey (possibly working in Firefox as well) that utilizes a local list (storage format TBD) to warn users about websites that discriminates against certain browsers by shutting them out, possibly even doing dynamic user agent spoofing to make the websites work in SeaMonkey despite that.
This is a first part of the dynamic UA spoofing mechanism proposed earlier, the project does not aim for this full mechanism, only for the basic client-side functionality. |
Robert Kaiser | possibly Robert Kaiser | |
| Using the Places Backend | Make SeaMonkey's browsing history (and possibly bookmarks) build on the Mozilla platform's "places" backend. The target is to leave the user interface very similar to current SeaMonkey while building on a more modern, SQLite-based backend that allow extensions to add an interface for bookmark tagging and similar features of this new backend. This mostly involves porting front end code from Firefox and tweaking it so that it resembles the well-known SeaMonkey user interface, and can be done in separate steps for history and bookmarks. | Robert Kaiser |
Bugzilla
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
L10n
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|