Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Community:SummerOfCode09: Difference between revisions
m
Changed protection level for "Community:SummerOfCode09" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))
(Transferring more ideas across to the main page) |
m (Changed protection level for "Community:SummerOfCode09" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))) |
||
| (7 intermediate revisions by the same user 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 2009 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode09:Brainstorming|the Brainstorming page]]. | This page lists all the Google Summer of Code 2009 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode09:Brainstorming|the Brainstorming page]]. | ||
| Line 27: | Line 29: | ||
|Gerv | |Gerv | ||
|tridge has agreed to co-mentor, but we need a Mozilla person who thinks this is cool to mentor as well. | |tridge has agreed to co-mentor, but we need a Mozilla person who thinks this is cool to mentor as well. | ||
|- | |||
| nsIProcess2 | |||
| Replace the existing nsIProcess interface with a new interface that supports Unicode on all platforms, supports piping to/from processes and can handle asynchronous I/O via callbacks. The primary API should be a JS API, but will be implemented partly using XPCOM underneath. Also, this functionality should be available through Components.utils.import("resource://gre/process.js") or a similar JS module approach. ({{bug|484246}}) | |||
| James Boston | |||
| Mark Finkle | |||
| | |||
|} | |} | ||
| Line 68: | Line 76: | ||
!Mentor(s) | !Mentor(s) | ||
!Comments | !Comments | ||
|- | |||
|Automate Calendar Testing Using Mozmill | |||
|[http://quality.mozilla.org/documents-home/code-docs/mozmill-test-creation Mozmill] is a UI Automation tool for the Mozilla Platform. We should use it to automate many of the manual test cases used for calendar testing. It can also be used to automate many of the more interesting unit tests - for example, it could be used to unit test the "View" objects in the calendar code base. | |||
|Fallen | |||
|Ctalbert | |||
| | |||
|} | |} | ||
==Camino== | ==Camino== | ||
The Camino Project has [http://wiki.caminobrowser.org/Development:Good_Bugs_and_Projects their own Summer of Code 2009 page]. | |||
==SeaMonkey== | ==SeaMonkey== | ||
| Line 102: | Line 109: | ||
|Robert Kaiser | |Robert Kaiser | ||
|Crisp success/fail criteria still needs to be created. | |Crisp success/fail criteria still needs to be created. | ||
|- | |||
| Message Filter UI Overhaul | |||
| The current message filter UI is rather hard to work with and doesn't even provide the complexity the backend would allow. I propose to: | |||
* integrate the account hierarchy into the rule list | |||
* integrate the actual rules into the rule list, allowing "inline editing" (this may mean a bigger dialog window and twisties to collapse accounts/rules) | |||
* allow nested rules (and/or) | |||
* improve overall usability by allowing to copy rules, defining drag'n'drop and context menus, etc. | |||
| [[User:Mnyromyr|Karsten Düsterloh]] | |||
| [[User:Mnyromyr|Karsten Düsterloh]] | |||
| FilterListDialog.xul is almost identical in both SeaMonkey and Thunderbird, so it shouldn't be too hard to fix both or derive a TB version easily. | |||
|- | |||
| Folder Views | |||
| We provide the ability to create and use message views for pre-filtering which messages to show in the thread pane. We don't have a comparable feature yet in the folder pane... | |||
While this would basically mean to port 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; ... | |||
| [[User:Mnyromyr|Karsten Düsterloh]] | |||
| [[User:Mnyromyr|Karsten Düsterloh]] | |||
| | |||
|} | |} | ||
| Line 220: | Line 244: | ||
|Blog post [http://blog.mozilla.com/mrz/2008/05/26/geo-dns-or-getting-the-bits-closer-to-you/ #1] & [http://blog.mozilla.com/mrz/2008/06/11/geodns-one-week-later/ #2] for background and [https://wiki.mozilla.org/IT/GeoDNS here] for project notes. Would like to build on the existing GeoDNS platform and include per resource record weighting & better management/reporting tools. Would also like to build on this tool to become an open-source Global Load Server Load Balancing tool. | |Blog post [http://blog.mozilla.com/mrz/2008/05/26/geo-dns-or-getting-the-bits-closer-to-you/ #1] & [http://blog.mozilla.com/mrz/2008/06/11/geodns-one-week-later/ #2] for background and [https://wiki.mozilla.org/IT/GeoDNS here] for project notes. Would like to build on the existing GeoDNS platform and include per resource record weighting & better management/reporting tools. Would also like to build on this tool to become an open-source Global Load Server Load Balancing tool. | ||
|mrz | |mrz | ||
|mrz/IT | |mrz (Matthew Zeier)/IT | ||
|Trying to find out ways to get more community involvement with IT-related activities. We have a lot of community involved with Firefox but little with how IT runs Mozilla's services. I believe this will also help give more insight into IT and enable us to be more transparent and help replace some of the closed-source tools we use to deliver Mozilla products & services. | |Trying to find out ways to get more community involvement with IT-related activities. We have a lot of community involved with Firefox but little with how IT runs Mozilla's services. I believe this will also help give more insight into IT and enable us to be more transparent and help replace some of the closed-source tools we use to deliver Mozilla products & services. | ||
|} | |} | ||
== | ==Labs: Weave== | ||
{| class="standard-table" | {| class="standard-table" | ||
| Line 246: | Line 270: | ||
| valign="top" | | | valign="top" | | ||
|- | |- | ||
|} | |||
==Labs: Bespin== | |||
{| class="standard-table" | |||
|- | |||
!Title | |||
!Abstract - links to details/bugs/etc | |||
!Reporter | |||
!Mentor(s) | |||
!Comments | |||
|- | |||
|Thunderhead: Cross browser JavaScript UI toolkit | |||
|Work with us to implement a cross browser UI toolkit experiment, code named "Thunderhead" | |||
|Dion Almaer & Ben Galbraith | |||
|Almaer/Galbraith | |||
| | |||
|- | |||
|Bespin: Pluggable Syntax Highlighting | |||
|Build a syntax highlighter that groks emacs, vim, and Textmate highlighter files | |||
|Dion Almaer | |||
|Almaer/Galbraith | |||
| | |||
|- | |||
|Bespin: Offline editing | |||
|Create an offline Bespin editing experience | |||
|Dion Almaer | |||
|Almaer/Galbraith | |||
| | |||
|- | |||
|Bespin: Server Side JavaScript | |||
|Create a server side JavaScript Bespin server implementation | |||
|Kevin Dangoor | |||
|Almaer/Galbraith? | |||
| | |||
|- | |||
|Bespin: Heuristic analysis | |||
|Build server side rules analysis to check project code for errors and hints | |||
|Dion Almaer | |||
|Almaer/Galbraith | |||
| | |||
|} | |} | ||