Community:SummerOfCode13:Brainstorming: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 75: Line 75:
{| class="standard-table" border="1" style="border-collapse: collapse"
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
|-
! Title  
! Title: Open Badges
! Details  
! Details: OBI is Mozilla's response to the growing badges in learning movement. The OBI allows learners to collect badges from a variety of badge issuers, and display them wherever they'd like. We need help building additional display widgets, developing an endorsement specification that allows for organizations and individuals to endorse a badge class or badge instance and further build out the functionalities of the badge management tool, ie the Backpack.  There's lots of work to be done, so we're pretty open to ideas you have.  Contact Chris for more information.
! Skills Needed  
! Skills Needed:  The OBI is written in Javascript, and runs on Node.js, so Javascript knowledge is a big plus.
! Reporter  
! Reporter  
! Mentor(s)  
! Mentor(s)
! Comments
! Comments
|-
|-

Revision as of 17:09, 1 April 2013

Mozilla community members - submit proposals here for 2013 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the official list.) The absolute last deadline for submitting ideas in time to help us get accepted by Google is March 29th.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the official list of ideas. This page is full of weird and whacky ideas, some of which are still on here for a reason - it could be that they are not properly defined, the wrong size, or don't have a mentor. That makes them less likely to get accepted. You can, of course, also submit your own ideas - you don't have to put an idea on this page and get it 'made official' in order to send in a proposal for it.

How To Write A Good Project Proposal

Before adding an proposal 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 who you are, 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

Here are the ideas lists from previous years.

Proposals can be in almost any part of the Mozilla project - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

Mozilla Platform (Gecko)

Title Details Skills Needed Reporter Mentor(s) Comments

Firefox

Title Details Skills Needed Reporter Mentor(s) Comments

Firefox for Android

Title Details Skills Needed Reporter Mentor(s) Comments

Firefox OS / Boot2Gecko

Title Details Skills Needed Reporter Mentor(s) Comments

Mozilla Open Badges

Title: Open Badges Details: OBI is Mozilla's response to the growing badges in learning movement. The OBI allows learners to collect badges from a variety of badge issuers, and display them wherever they'd like. We need help building additional display widgets, developing an endorsement specification that allows for organizations and individuals to endorse a badge class or badge instance and further build out the functionalities of the badge management tool, ie the Backpack. There's lots of work to be done, so we're pretty open to ideas you have. Contact Chris for more information. Skills Needed: The OBI is written in Javascript, and runs on Node.js, so Javascript knowledge is a big plus. Reporter Mentor(s) Comments

Calendar

Title Details Skills Needed Reporter Mentor(s) Comments

Thunderbird

Title Details Skills Needed Reporter Mentor(s) Comments
Utilize capability attributes of nsIMsgIncomingServer and nsIMsgFolder Remove hard-coded checks through-out the comm-central codebase where a simple check of the server (nsIMsgIncomingServer) capability can be used.

Example:

if (server.type == "nntp" || server.type == "rss") { enableSubscribe(); }

Change to:

if (server.canSubscribe) { enableSubscribe(); }

For this to work, the student has to see if the server types return the proper value for the capability (some may be unimplemented yet) and may have to add some new attributes where needed. Hard-coded checks are bad because they do not pick up new server types automatically even if they would have the capability. Extension authors have a hard time plugging into these hard-coded spots. Often they have to duplicate the whole function from TB to add their new server type to it. The same can be done with folders, i.e. nsIMsgFolder.

Starting point: bug 63369.

C++, Javascript aceman
Rewrite our database code to be asynchronous when database if huge. This would help us in improving the start-up time of Thunderbird. Main idea is splitting the database in chunks and then loading it, if the database is quite big. I guess related bug would be: bug 588952.

Difficulty: Medium to hard depending on how far we go.

C++ mainly atuljangra ?anyone? jcranmer - Mork database async opening needs to be completed, and we would probably also need nsIMsgDBHdr instances to become "dead" (cached copies of the database or newer changes).
Open ended project to solve several critical bugs My idea for this project is that we can have a student solve various bugs that are arising in Thunderbird which are makin users unhappy. For example Bug 516222, Bug 803921, Bug 618553 and many others. We can utilize this to solve such critical bugs. This would be some kind of open ended bug. Main area of concern would be Mailnews core. C/C++ mostly, Js for testing atuljangra ?anyone from Mailnews core? atuljangra- Do we need to prioritise the ideas?
Make OS X users happier Something from Bug 728438 to integrate Thunderbird better into OS X would be good. This includes interesting Bugs like the Quickloock integration Bug 457546, which was already a student project, but needs to be finished, integrated into Thunderbird and some tests. The same is true for Bug 465257 to support multi-touch gestures. It also includes Bugs to improve the addressbook behaviour for OS X users (write support, Bug 391057 and picture support, Bug 496789). You need to know about C++, JS and OS X APIs. ? ?

SeaMonkey

Title Details Skills Needed Reporter Mentor(s) Comments

NSS (Network Security Services)

Title Details Skills Needed Reporter Mentor(s) Comments

Bugzilla

Title Details Skills Needed Reporter Mentor(s) Comments

Firefox Support (SUMO)

Title Details Skills Needed Reporter Mentor(s) Comments

QA

Title Details Skills Needed Reporter Mentor(s) Comments

Automation & Tools

Title Details Skills Needed Reporter Mentor(s) Comments

Documentation

Title Details Skills Needed Reporter Mentor(s) Comments

Mozilla Developer Network

Title Details Skills Needed Reporter Mentor(s) Comments
Localization Dashboard Build a Localization Dashboard for the Mozilla Developer Network (MDN) to help contribuors view localization progress and find articles that need to be localized. The dashboard should be somewhat similar to the existing Revision Dashboard. Over the course of the summer, the student should build a minimum viable product and work with the MDN team to iterate on it, making as many improvements as time allows. HTML, CSS, JavaScript, Python John Karahalis (openjck) John Karahalis (openjck)

Mozilla IT and Infrastructure

Title Details Skills Needed Reporter Mentor(s) Comments

Persona / BrowserID

Title Details Skills Needed Reporter Mentor(s) Comments

Sync / Services

Title Details Skills Needed Reporter Mentor(s) Comments

Developer Tools

Title Details Skills Needed Reporter Mentor(s) Comments

Add-on SDK

Title Details Skills Needed Reporter Mentor(s) Comments

Foundation

Title Details Skills Needed Reporter Mentor(s) Comments

Release Engineering

Title Details Skills Needed Reporter Mentor(s) Comments

Instantbird

Title Details Skills Needed Reporter Mentor(s) Comments

Emscripten

Title Details Skills Needed Reporter Mentor(s) Comments

Rust

Title Details Skills Needed Reporter Mentor(s) Comments

Security Engineering

Title Details Skills Needed Reporter Mentor(s) Comments
Security Report It can be tricky for a developer to cover all their bases when it comes to security. Moreover, information about the security of a website can be difficult for advanced users to find without searching through multiple data sources in the browser (error console, cookie manager, certificate manager, etc.) This project is to build a firefox addon that reports all of this data in one place. Developers can then view the report for their websites or pre-production pages and quickly identify their security issues. Advanced users can quickly learn about a websites security before deciding whether or not they want to enter sensitive information on the page.

Here are some examples of what the security report could include:

  • information about network requests that have been blocked by the browser for security reasons (e.g. mixed content, CSP, CORS)
  • information about the cookies on the site (are they marked secure, do they have the httponly attribute?)
  • security related headers (does the site set STS, CSP, or X-Frame-Options headers?)
  • SSL information (is the websites ssl certficate about to expire?)
JavaScript, Add-on SDK, some platform knowledge. Mark Goodwin (mgoodwin), Tanvi Vyas (tanvi) Mark Goodwin (mgoodwin), Tanvi Vyas (tanvi)

Open(Art)

Title Details Skills Needed Reporter Mentor(s) Comments