MozillaWiki

Community:SummerOfCode07: Difference between revisions

Page Discussion

Community:SummerOfCode07 (view source)

Revision as of 08:15, 7 October 2014

10,765 bytes added ,  7 October 2014
m
Protected "Community:SummerOfCode07" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))
(Add Mail filters project, which bienvenu has agreed to mentor)
m (Protected "Community:SummerOfCode07" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite)))
 
(25 intermediate revisions by 12 users not shown)
Line 1: Line 1:
<span style="color: red; font-weight: bold">Looking for this year's Summer of Code information? [[SummerOfCode|Step right this way.]]</span>
This page lists all the Google Summer of Code 2007 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 [[Community:SummerOfCode07:Brainstorming|the Brainstorming page]].
This page lists all the Google Summer of Code 2007 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 [[Community:SummerOfCode07:Brainstorming|the Brainstorming page]].


Line 5: Line 7:
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.
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 [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.
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==
==Firefox/Gecko==


{| border="1" cellpadding="3" width="100%" valign="top"
{| class="standard-table"
|- align="center"
|-
| style="background-color: #efefef;" | '''Title'''
!Title
| style="background-color: #efefef;" | '''Abstract - links to details/bugs/etc'''
!Abstract - links to details/bugs/etc
| style="background-color: #efefef;" | '''Reporter'''
!Reporter
| style="background-color: #efefef;" | '''Mentor(s)'''
!Mentor(s)
| style="background-color: #efefef;" | '''Comments'''
!Comments
|-
|-
| valign="top" | Implement link fingerprints
| valign="top" | Implement link fingerprints
Line 22: Line 24:
| valign="top" | Gerv
| valign="top" | Gerv
| valign="top" | This is similar to Heikki's proposal above and could be done as part of that larger activity, but I think it deserves separate mention as its scope is specified more precisely, and it might be faster to implement. - Jens<br><br>There is already an extension which does some of this; a proper patch for the trunk would be required, and then the writing up of the idea as an RFC - Gerv
| valign="top" | This is similar to Heikki's proposal above and could be done as part of that larger activity, but I think it deserves separate mention as its scope is specified more precisely, and it might be faster to implement. - Jens<br><br>There is already an extension which does some of this; a proper patch for the trunk would be required, and then the writing up of the idea as an RFC - Gerv
|-
| valign="top" | Firefox automation & Tinderbox integration
| valign="top" | Firefox 3 automated smoke-testing using Linux Desktop Testing Project; Tinderbox integration of LDTP results.
| valign="top" | [[User:NagappanAlagappan|Nagappan]]
| valign="top" | [[User:NagappanAlagappan|Nagappan]] and Emily Chen
| valign="top" | Once the system is integrated with Tinderbox, then we can extend it to use for Thunderbird automation testing too.
|-
| valign="top" | SMIL Animation
| valign="top" | Work on extending and polishing the [https://bugzilla.mozilla.org/show_bug.cgi?id=216462 existing patch] by [http://brian.sol1.net/svg/ Brian Birtles] which adds a SMIL animation to mozilla and hosts it in SVG.
| valign="top" | tor
| valign="top" |
| valign="top" |
|-
| valign="top" | SVG Fonts
| valign="top" | Add the ability to [http://www.w3.org/TR/SVG11/fonts.html define a font with SVG] to mozilla's SVG implementation.  Doing the "basic" style fonts that handle the "d" attribute, as used by SVG Tiny, should be fairly straightforward once [http://lists.freedesktop.org/archives/cairo/2007-February/009539.html cairo adds a user font API].
| valign="top" | tor
| valign="top" |
| valign="top" |
|-
| valign="top" | rich content microsummaries
| valign="top" | [https://bugzilla.mozilla.org/show_bug.cgi?id=341347 bug 341347]<br>[http://blog.mozilla.com/faaborg/2006/12/06/tufte-and-graphical-microsummaries/ Tufte and Graphical Live Titles]<br>[http://wiki.mozilla.org/GraphicalMicrosummaries Graphical Microsummaries]
| valign="top" | MykMelez
| valign="top" | MykMelez
| valign="top" | As Tufte notes, it can be very useful to pack a lot of information in a small space.  Microsummaries are targeted at that kind of information presentation.  But microsummaries can only display characters at the moment, which severely limits how much information they can display and how well they can display it.
In fact, the most dramatically informative microsummaries (like a graph of the day's activity for a stock, or a graphical depiction of the next five day's weather) are currently impossible to implement.  But if sites could provide rich content (i.e. HTML or image) microsummaries, then these would be possible.
|-
| valign="top" | microsummary builder
| valign="top" | [https://addons.mozilla.org/firefox/3741/ Microsummary Generator Builder extension]
| valign="top" | MykMelez
| valign="top" | MykMelez
| valign="top" | For sites that don't provide microsummaries, it's useful to be able to extract your own.  But building one from scratch requires knowledge of XSLT, XPath, and other technologies that even computer-savvy users and software engineers may lack.  And even for folks who do have that knowledge, it's much harder than it should be to extract a microsummary from a web page.
Tools could significant improve this situation, and [https://addons.mozilla.org/firefox/3741/ one such tool] is already available, but there's still a lot more that can be done in two directions: for regular users, we could have a tool that made extracting a microsummary super-simple.  In fact, it could start as simple as clicking an element on a web page and dragging it to the bookmarks toolbar.  We could then build on that basic functionality with additional simple mechanisms for massaging the information to be summarized.
For developers, we could have a tool that couples those simple mechanisms for average users with more sophisticated functions for inspecting and manipulating the microsummary generator.  For example, we might provide an editable "source" view of the generator.  And we might enable more complicated UI gestures for things like anchoring an XPath that retrieves some informatino to a non-root node (f.e. to the node that labels that information, whose relationship to the information is less likely to change over time than the relationship of that information node to the root node).
|-
| valign="top" | microsummary generator web service
| valign="top" | [http://userstyles.org/livetitle User Styles' Live Titles repository]
| valign="top" | MykMelez
| valign="top" | MykMelez
| valign="top" | userstyles.org has set up a repository for microsummary generators, which is a great first step in distributing the generators, but it would be much more useful if users didn't have to browse the repository and install a generator to use it on a site.
Imagine an extension (or an enhancement to an extension like [https://addons.mozilla.org/firefox/3639/ Microsummary Buddy] or [https://addons.mozilla.org/firefox/4248/ Microsummary Manager]) that automatically notifies users when a generator is available for a page they're browsing and shows them the microsummary it generates.  Then, if users decide they want to use the microrsummary, the extension installs the generator automatically and creates the microsummary-enabled bookmark for the user.  And all the user has to do is something simple like clicking on the "microsummary available" notification icon or dragging it to the bookmarks toolbar.
|-
| valign="top" | JPEG 2000
| valign="top" | [https://bugzilla.mozilla.org/show_bug.cgi?id=36351 Add JPEG 2000 support to Mozilla]
| valign="top" | schapel
| valign="top" | pavlov (maybe)
| valign="top" | This would be done as an extension, perhaps as described in [https://bugzilla.mozilla.org/show_bug.cgi?id=18574#c672 this Bugzilla comment]
|-
| valign="top" | SVG as an image format
| valign="top" | One of the possibilities that having a native SVG implementation in the browser provides is being able to use SVG in contexts where normally a raster image would be used, such as &lt;html:img&gt; and CSS properties that accept images.
Someone interested in taking this on as a SoC project would need to be pretty familiar with the Mozilla codebase, as this involves getting bits of code that weren't originally planned to work with one another to play nicely together.
| valign="top" | tor
| valign="top" |
| valign="top" |
|}
|}


==Thunderbird==
==Thunderbird==


{| border="1" cellpadding="3" width="100%" valign="top"
{| class="standard-table"
|- align="center"
|-
| style="background-color: #efefef;" | '''Title'''
!Title
| style="background-color: #efefef;" | '''Abstract - links to details/bugs/etc'''
!Abstract - links to details/bugs/etc
| style="background-color: #efefef;" | '''Reporter'''
!Reporter
| style="background-color: #efefef;" | '''Mentor(s)'''
!Mentor(s)
| style="background-color: #efefef;" | '''Comments'''
!Comments
|-
| valign="top" | Add tabbed messages support for Thunderbird
| valign="top" | Tabbed message reading is a highly demanded feature for Thunderbird and was on the planned feature list for version 2, but missed the bus and currently there is nobody working on it. Having to change the selected folder and/or message or opening a new window decreases productivity (increases waste of time). The new message pane should also be available for the tabbed view. See [https://bugzilla.mozilla.org/show_bug.cgi?id=297379 Bug 297379] and [https://bugzilla.mozilla.org/show_bug.cgi?id=218999 Bug 218999]
| valign="top" | Archaeopteryx
| valign="top" | mscott
| valign="top" | There had been experimental builds by Myk in the past, so there are already some concepts.
|-
|-
| valign="top" | Thunderbird: Vista Desktop Search Integration
| valign="top" | Thunderbird: Vista Desktop Search Integration
Line 39: Line 106:
| valign="top" | [[User:Bienvenu|Bienvenu]]
| valign="top" | [[User:Bienvenu|Bienvenu]]
| valign="top" | There is a lot of code in the Spotlight integration code that could be re-used for the Vista search integration.
| valign="top" | There is a lot of code in the Spotlight integration code that could be re-used for the Vista search integration.
|-
| valign="top" | Thunderbird and Firefox Integration Points
| valign="top" | Make using Thunderbird and Firefox together a better user experience.
| valign="top" | [[User:mscott|mscott]]
| valign="top" | [[User:mscott|mscott]]
| valign="top" | Add some integration hooks between Firefox and Thunderbird such as: adding a url to Thunderbird could autocomplete against Firefox bookmark and history urls. Filling out an address form in Firefox could extract the address data from your Thunderbird address book. I'm sure there are other ideas that could be explored here too.
|-
| valign="top" | RSS Feed Improvements
| valign="top" |
| valign="top" | [[User:mscott|mscott]]
| valign="top" | [[User:mscott|mscott]]
| valign="top" | Start with the work Ian did in Bug #255834. Convert Thunderbird's feed parsing implementation to use the feed parser in mozilla\toolkit. Consider moving the feed files to mailnews\extensions\newsblog so it can be shared with seamonkey. Once that's done, let's design some new user interface hooks for subscribing and managing RSS feeds because the current UI is very poor.
|-
|-
| valign="top" | Improve Thunderbird mail filters
| valign="top" | Improve Thunderbird mail filters
Line 44: Line 123:
| valign="top" | [[User:Jens.b|Jens.b]]
| valign="top" | [[User:Jens.b|Jens.b]]
| valign="top" | bienvenu
| valign="top" | bienvenu
| valign="top" |
|-
| valign="top" | Extend Bayesian feature set
| valign="top" | Upgrade Bayesian classes to support multi-state [[Bayesian]], and support auto-filtering.
| valign="top" | gandalf
| valign="top" |
| valign="top" |
| valign="top" |
|}
|}
Line 49: Line 134:
==Camino==
==Camino==


{| border="1" cellpadding="3" width="100%" valign="top"
{| class="standard-table"
|- align="center"
|-
| style="background-color: #efefef;" | '''Title'''
!Title
| style="background-color: #efefef;" | '''Abstract - links to details/bugs/etc'''
!Abstract - links to details/bugs/etc
| style="background-color: #efefef;" | '''Reporter'''
!Reporter
| style="background-color: #efefef;" | '''Mentor(s)'''
!Mentor(s)
| style="background-color: #efefef;" | '''Comments'''
!Comments
|-
|-
| valign="top" | Camino: Tabspose
| valign="top" | Camino: Tabspose
Line 62: Line 147:
| valign="top" | pinkerton
| valign="top" | pinkerton
| valign="top" | I've wanted to do this for years...
| valign="top" | I've wanted to do this for years...
|-
| valign="top" | Camino AppleScript Support
| valign="top" | Camino currently has very little AppleScript support.  One of the most useful commands for a browser, "do javascript", remains unimplemented.  Several other bugs separate Camino from parity with Safari's and OmniWeb's scripting support.  Filed bugs include {{bug|178917}}, {{bug|160106}}, {{bug|314061}}, {{bug|253486}}, and {{bug|156078}}.  Those bugs cover a lot of ground, including the ability to refer to tabs.
| valign="top" | Peter Jaros ([[User:Peeja|Peeja]], Bard College)
| valign="top" | [[User:Pinkerton|Mike Pinkerton]]
| valign="top" |
|}
|}


==Seamonkey==
==SeaMonkey==


{| border="1" cellpadding="3" width="100%" valign="top"
{| class="standard-table"
|- align="center"
| style="background-color: #efefef;" | '''Title'''
| style="background-color: #efefef;" | '''Abstract - links to details/bugs/etc'''
| style="background-color: #efefef;" | '''Reporter'''
| style="background-color: #efefef;" | '''Mentor(s)'''
| style="background-color: #efefef;" | '''Comments'''
|-
|-
| valign="top" | Make SeaMonkey Not Suck As A News Reader
!Title
!Abstract - links to details/bugs/etc
!Reporter
!Mentor(s)
!Comments
|-
| valign="top" | [[Make SeaMonkey Not Suck As A News Reader]]
| valign="top" | Basically, get some traction on some of the highlights of {{bug|176238}}/{{bug|12699}} , in particular: "clickable references" ({{bug|62033}}) and headers in general ({{bug|23114}}), a more usable subscribe dialog ({{bug|40260}}), reordering of the folder pane ({{bug|150274}}, maybe even hierarchical?). For bonus points, a correct implementation of the nntp/news protocols ({{bug|89939}}) would be really cool!
| valign="top" | Basically, get some traction on some of the highlights of {{bug|176238}}/{{bug|12699}} , in particular: "clickable references" ({{bug|62033}}) and headers in general ({{bug|23114}}), a more usable subscribe dialog ({{bug|40260}}), reordering of the folder pane ({{bug|150274}}, maybe even hierarchical?). For bonus points, a correct implementation of the nntp/news protocols ({{bug|89939}}) would be really cool!
| valign="top" | Mnyromyr
| valign="top" | Mnyromyr
Line 95: Line 186:
==Bugzilla==
==Bugzilla==


{| border="1" cellpadding="3" width="100%" valign="top"
{| class="standard-table"
|- align="center"
|-
| style="background-color: #efefef;" | '''Title'''
!Title
| style="background-color: #efefef;" | '''Abstract - links to details/bugs/etc'''
!Abstract - links to details/bugs/etc
| style="background-color: #efefef;" | '''Reporter'''
!Reporter
| style="background-color: #efefef;" | '''Mentor(s)'''
!Mentor(s)
| style="background-color: #efefef;" | '''Comments'''
!Comments
|-
|-
| valign="top" | Bugzilla: Plugin System
| valign="top" | Bugzilla: Plugin System
Line 116: Line 207:
| valign="top" | Gerv
| valign="top" | Gerv
| valign="top" | There may be some questions about importing data from the old systems. I think that New Charts are not in much use, since they aren't complete. The system would have to be able to import Old Charts, but the New Charts system could be entirely replaced by the system built in this project. (However, any left-over New Charts would have to be exported as CSV so that users wouldn't lose their data.)
| valign="top" | There may be some questions about importing data from the old systems. I think that New Charts are not in much use, since they aren't complete. The system would have to be able to import Old Charts, but the New Charts system could be entirely replaced by the system built in this project. (However, any left-over New Charts would have to be exported as CSV so that users wouldn't lose their data.)
|-
| valign="top" | Bugzilla: Duplicate Bug Detection
| valign="top" | Implement a system in Bugzilla that detects automatically that the user has likely entered a bug that is a duplicate of another bug, and display a list of bugs that this bug might be a duplicate of.
| valign="top" | [[User:MaxKanatAlexander|mkanat]]
| valign="top" | vladd
| valign="top" | [https://launchpad.net/malone Malone] can do this now, although  I'm not certain its code is actually open source. (Anyhow, GPL'ed code can't be included in Bugzilla, which uses the MPL.)
|}
==L10n==
{| class="standard-table"
|-
!Title
!Abstract - links to details/bugs/etc
!Reporter
!Mentor(s)
!Comments
|-
| valign="top" | Easing the way for localizers
| valign="top" |
* fixing .label/.accesskey combination in the whole codebase, so that automatic tools have a chance to catch them all.
* Step by step documentations for new localizers.
* A script to align Mozilla Translator files to en-US files.
| valign="top" | Abdulkadir Topal
| valign="top" | pike
| valign="top" |
|-
| valign="top" | Merge the two existing French spelling dictionaries
| valign="top" | There are currently [https://addons.mozilla.org/thunderbird/dictionaries/?lang=fr two French spelling dictionaries] for MySpell. The first was made available from a former ISpell dictionary, and it was later "enhanced" by another group wanting to support new spellings only (1990 reform), although those are not mandatory. As a result, we have two dictionaries, but none of practical use (the first is outdated, the other is underlining perfectly valid words).
A possible implementation of this project would be to take the new dictionary, re-add the hundreds of words that were removed from the old one, and enhance it in other ways (for example, HunSpell allows you to remove some words from the spelling suggestions without underlining them). It might looks like a trivial task, but it is not the case. There were structural changes in the affix dictionary file which can't be resolved by a simple diff.
| valign="top" | Benoit / [http://frenchmozilla.sourceforge.net/ The FrenchMozilla team]
| valign="top" |
| valign="top" |
|-
| valign="top" | Create a new French dictionary (HunSpell) from scratch
| valign="top" | No matter how good the French spelling dictionary may become, it can't be shipped with Firefox or Thunderbird because of licensing issues (It's GPL only, Mozilla products are tri-licensed)[http://frenchmozilla.sourceforge.net/blog/index.php/2006/02/02/21-correction-orthographique-et-logiciels-mozilla explanation in French].
This proposal is to build a new French dictionary from scratch, taking advantage of the new features in [http://sourceforge.net/docman/display_doc.php?docid=29374&group_id=143754 HunSpell]
Someone interested in taking this on as a SoC project would probably need to have a strong background in linguistics or a similar field.
| valign="top" | Benoit / [http://frenchmozilla.sourceforge.net/ The FrenchMozilla team]
| valign="top" |
| valign="top" |
|-
| valign="top" | L10n GUI Tool
| valign="top" | Create XulRunner based [[L10n:Tool]]
| valign="top" | gandalf
| valign="top" | gandalf
| valign="top" |
|}
|}
Gerv
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/52366...1022885"