Community:SummerOfCode10:Brainstorming
This page is for anyone to submit ideas for Google Summer of Code projects with Mozilla for 2010. 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.
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 | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Firefox
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|---|---|---|---|
| Built-in Grammar checking | This project would be divided into three parts :
- A syntax analyser, able o build a semantic tree from a sentence, proceeding by substitutions according to a given set of grammar rules. - Basic grammar rules and dictionnary for the English language (At this point, the system should be able to interpret all possible meanings simple well-formed sentence) - A correction system, built in two parts. First, completing the syntax analyser so that it can "guess" the closest correctly formed sentences when the provided one doesn't match with the rules, and second by verifying that all built trees, therefore structurally correct, don't contain concordance mistakes, etc. It would probably not be ready for everyday use by the end of the SoC (due to the complexity of natural languages making it a lot of work to transcribe them into substitution rules for tree building) but the language-independant part of the system should be operational. |
Arnaud VIÉ (Unas) | This could also be implemented into Thunderbird.
Plus, the syntax analyser could be used later as a basis in a translation tool too, when provided with a base of equivalence between words and sentence structures in two languages. |
Thunderbird
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Calendar
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|---|---|---|---|
| Improve import/export feature | This would basically consist of 3 parts:-
1.csv and ics import/export: Make sure that the import/export feature of calendar in .csv and .ics format works correctly, Presently either it transfers incomplete data during the export or doesn’t handle the errors(if any)efficiently during import and as a result import fails. 2.Improving the parser and error handling: Make the parser more error tolerant. It should display user understandable error messages when a corrupted file is imported or when a file with wrong extension is intended to be imported. 3.HTML import: Add a feature of importing events in the html format from user's computer as well as the remote URL. Part 1 and 2 would greatly improve import/export in different file formats and 3 would be a nice new feature. |
anirvana | ? | No confirmed mentor yet |
Camino
See the Camino Summer of Code 2010 page for project suggestions.
SeaMonkey
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
NSS (Network Security Services)
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|---|---|---|---|
| Implement PKCS #1 v2.1 RSA-PSS signature and RSA-OAEP encryption | RSA-PSS is more important. RSA-OAEP is optional.
See https://bugzilla.mozilla.org/show_bug.cgi?id=158750 and https://bugzilla.mozilla.org/show_bug.cgi?id=158747. |
Wan-Teh Chang | ||
| Implement TLS 1.1 and 1.2 | Start with TLS 1.1, and then go on to TLS 1.2 if there is time. | Wan-Teh Chang |
Bugzilla
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Mobile/Fennec
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Firefox Support (Sumo)
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Rhino
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Mozilla IT Infrastructure
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Labs: Weave
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|
Labs: Bespin
| Title | Abstract - links to details/bugs/etc | Reporter | Mentor(s) | Comments |
|---|