Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Community:SummerOfCode10: Difference between revisions
m
Changed protection level for "Community:SummerOfCode10" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))
m (Changed protection level for "Community:SummerOfCode10" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))) |
|||
| (5 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 2010 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode10:Brainstorming|the Brainstorming page]]. | This page lists all the Google Summer of Code 2010 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode10:Brainstorming|the Brainstorming page]]. | ||
| Line 10: | Line 12: | ||
* Read [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] and avoid doing the things listed there. | * Read [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html How Not To Apply For Summer Of Code] and avoid doing the things listed there. | ||
* Read our examples of good applications: [[SummerOfCode/SampleApplications/1|1]], [[SummerOfCode/SampleApplications/2|2]], [[SummerOfCode/SampleApplications/3|3]]. | * Read our examples of good applications: [[SummerOfCode/SampleApplications/1|1]], [[SummerOfCode/SampleApplications/2|2]], [[SummerOfCode/SampleApplications/3|3]]. | ||
* | * Apply [http://socghop.appspot.com/gsoc/student/apply/google/gsoc2010 here]. | ||
Questions of any sort? Send mail to [mailto:gerv@mozilla.org Gerv] and/or [mailto:chofmann@mozilla.org chofmann]. We will try and respond as soon as possible and get your questions directed to the right person. Please allow at least 48 hours for a reply. | Questions of any sort? Send mail to [mailto:gerv@mozilla.org Gerv] and/or [mailto:chofmann@mozilla.org chofmann]. We will try and respond as soon as possible and get your questions directed to the right person. Please allow at least 48 hours for a reply. | ||
| Line 40: | Line 42: | ||
|roc | |roc | ||
|jrmuizel | |jrmuizel | ||
| | |||
|- | |||
|Improved add-on packaging system | |||
|Main article: [http://xulforge.com/blog/2010/03/xpi-v2-making-ext-dev-easier/ XPI v2 – Making Extension Development Easier] | |||
The idea is to create a new packaging system for add-ons that makes it much easier to get started with add-on development. There are 3 parts to this idea: | |||
* Merge install.rdf and chrome.manifest into a single manifest file in JSON format. | |||
* Change the way chrome URLs map to actual files, in order to allow a more flexible add-on structure. | |||
* (optional?) Optimize the installation process for performance. | |||
The old system would need to continue to work with the new one. | |||
|jorgev (Add-ons team) | |||
|jorgev | |||
| | | | ||
|} | |} | ||
| Line 75: | Line 88: | ||
| David Bienvenu | | David Bienvenu | ||
| | | | ||
|- | |||
|Add Quicklook support for attachments | |||
|https://bugzilla.mozilla.org/show_bug.cgi?id=457546 | |||
|Libras2909 (irc: Libras2909 #nus) | |||
|bwinton | |||
|This would save MacOSX time skimming through attachments. Thus it would encourage more MacOSx users to move to Thunderbird. Moreover, there has been a lot of Quicklook plugin supports for displaying several different file types. [http://www.qlplugins.com/browse/]. Thus all we have to do is implementing a way to allow Finder to get the attachment from Thunderbird for display purpose. | |||
|} | |} | ||
| Line 235: | Line 254: | ||
|Joel Maher | |Joel Maher | ||
|The test would be most likely related to bookmarks, tabs, preferences, alerts, panning and zooming. This benefits Mozilla by giving a better testing coverage each day for the mobile browsers. Currently testing is done on lower level stuff, but not the front end. This would primarily be in xul and js code. | |The test would be most likely related to bookmarks, tabs, preferences, alerts, panning and zooming. This benefits Mozilla by giving a better testing coverage each day for the mobile browsers. Currently testing is done on lower level stuff, but not the front end. This would primarily be in xul and js code. | ||
|- | |||
|Automate Fennec Performance Tests | |||
|Fennec currently has two tests that test the performance of the mobile browser. New set of test will test other features like awesome bar, new tab load, setting preferences etc. | |||
|Aditya Rao | |||
|Joel Maher | |||
|This would be a great benefit to Mozilla as it would help set better goals for overall performance. This would primarily be in xul and js code. | |||
|} | |} | ||