Community:SummerOfCode13:Brainstorming: Difference between revisions

Jump to navigation Jump to search

Community:SummerOfCode13:Brainstorming (view source)

Revision as of 15:20, 22 February 2013

3,260 bytes removed ,  22 February 2013
Undo revision 525704 by Gvwilson (talk) -- bogus HTMLization, perhaps by graphical editor
(adding IPython Notebook replay project)
(Undo revision 525704 by Gvwilson (talk) -- bogus HTMLization, perhaps by graphical editor)
Line 1: Line 1:
<p>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 &lt;a href="Community:SummerOfCode13"&gt;official list&lt;/a&gt;.)
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 [[Community:SummerOfCode13|official list]].)
</p><p><b>Are you a students looking to apply to SoC with Mozilla?</b> Your first stop should be the &lt;a href="Community:SummerOfCode13"&gt;official list of ideas&lt;/a&gt;. 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 <i>can</i>, 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.
</p>
<h2>How To Write A Good Project Proposal</h2>
<p>Before adding an proposal to this list, please consider the following:
</p>
<ul><li> <b>Be specific</b>. It's hard to understand the impact of, or the size of, vague proposals.
</li><li> <b>Consider size</b>. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
</li><li> <b>Do your research</b>. Support the idea with well-researched links.
</li><li> <b>Don't morph other people's ideas</b>. If you have a related idea, place it next to the existing one, or add a comment.
</li><li> <b>Insert only your own name into the Mentor column</b>, 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.
</li><li> <b>Check back regularly</b>. The administrators may have questions about your idea that you will need to answer.
</li><li> <b>Know when to give up</b>. 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.
</li></ul>
<h2>Suggestion List</h2>
<p>&lt;a href="SummerOfCode"&gt;Here are the ideas lists from previous years&lt;/a&gt;.
</p><p>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!
</p>
<h2> Mozilla Platform (Gecko) </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
<b>Are you a students looking to apply to SoC with Mozilla?</b> Your first stop should be the [[Community:SummerOfCode13|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 <i>can</i>, 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.
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Firefox </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
==How To Write A Good Project Proposal==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Firefox for Android </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
Before adding an proposal to this list, please consider the following:
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr>
</table>
<h2> Firefox OS / Boot2Gecko </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
<th> Title
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
</th>
* '''Do your research'''. Support the idea with well-researched links.
<th> Details
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
</th>
* '''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.
<th> Skills Needed
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
</th>
* '''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.
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Calendar </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
==Suggestion List==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Thunderbird </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
[[SummerOfCode|Here are the ideas lists from previous years]].
<th> Title
 
</th>
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!
<th> Details
 
</th>
== Mozilla Platform (Gecko) ==
<th> Skills Needed
 
</th>
{| class="standard-table" border="1" style="border-collapse: collapse"
<th> Reporter
|-
</th>
! Title  
<th> Mentor(s)
! Details
</th>
! Skills Needed
<th> Comments
! Reporter
</th></tr>
! Mentor(s)
<tr>
! Comments
<td> Tests
|}
</td>
 
<td> Write tests for Thunderbird features where they are missing. We also have some contributors writing patches that were rejected because the contributor was not up to speed to produce a test for the feature (much harder than just producing the feature/fix). If the student picks up (helps with) these patches/contributors and produces the patches, it would help us.
== Firefox ==
</td>
 
<td> Javascript required. Experience with mozmill or xpcshell test infrastructure an advantage.
{| class="standard-table" border="1" style="border-collapse: collapse"
</td>
|-
<td> aceman
! Title
</td>
! Details  
<td>&#160;?mconley?
! Skills Needed
</td></tr>
! Reporter
<tr>
! Mentor(s)
<td> Utilize capability attributes of nsIMsgIncomingServer and nsIMsgFolder
! Comments
</td>
|}
<td> Remove hard-coded checks through-out the comm-central codebase where a simple check of the server (nsIMsgIncomingServer) capability can be used.
 
<p>Example:
== Firefox for Android ==
</p>
 
<p><dl><dd> if (server.type == "nntp" || server.type == "rss") { enableSubscribe(); }
{| class="standard-table" border="1" style="border-collapse: collapse"
&lt;/dd&gt;</dl>
|-
</p>
! Title
<p>Change to:
! Details
</p>
! Skills Needed  
<p><dl><dd> if (server.canSubscribe) { enableSubscribe(); }
! Reporter
&lt;/dd&gt;</dl>
! Mentor(s)
</p>
! Comments
<p>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.
|-
|}
 
== Firefox OS / Boot2Gecko ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter  
! Mentor(s)
! Comments
|}
 
== Calendar ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)  
! Comments
|}
 
== Thunderbird ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Tests
| Write tests for Thunderbird features where they are missing. We also have some contributors writing patches that were rejected because the contributor was not up to speed to produce a test for the feature (much harder than just producing the feature/fix). If the student picks up (helps with) these patches/contributors and produces the patches, it would help us.
| Javascript required. Experience with mozmill or xpcshell test infrastructure an advantage.
| aceman
| ?mconley?
|-
| 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.
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.
The same can be done with folders, i.e. nsIMsgFolder.
</p><p>Starting point: &lt;a href="https://bugzilla.mozilla.org/show_bug.cgi?id=63369"&gt;bug 63369&lt;/a&gt;.
</p>
</td>
<td> C++, Javascript
</td>
<td> aceman
</td>
<td>&#160;?jcranmer?,&#160;?rkent?
</td></tr>
<tr>
<td> Rewrite our database code to be asynchronous when database if huge.
</td>
<td> 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: <span class="fck_mw_template"><span class="fck_mw_template">{{bug|588952}}</span></span>.
<p>Difficulty: Medium to hard depending on how far we go.
</p>
</td>
<td> C++ mainly
</td>
<td> atuljangra
</td>
<td>&#160;?anyone?
</td>
<td> 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).
</td></tr>
<tr>
<td> Implement backend connectors for Ensemble (or DOM Contacts?)
</td>
<td> Mconley's new address book work should be stable enough by the summer that it is possible to write new connectors. Ideas for implementation here include any system address book on any platform, as well as LDAP support (OpenLDAP via js-ctypes looks to be the best option here).
</td>
<td> JS, although some C/C++ for native may be necessary
</td>
<td> jcranmer
</td>
<td>&#160;?mconley?
</td></tr>
<tr>
<td> Implement a mailbox-to-maildir converter
</td>
<td> This is one of the last critical pieces blocking moving away from mbox-style mailboxes.
</td>
<td> C++ is probably the simpler solution, but OS.File and jsmime make it possible in JS.
</td>
<td> jcranmer
</td>
<td>&#160;?
</td></tr></table>
<h2> SeaMonkey </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
Starting point: [https://bugzilla.mozilla.org/show_bug.cgi?id=63369 bug 63369].
<th> Title
| C++, Javascript
</th>
| aceman
<th> Details
| ?jcranmer?, ?rkent?
</th>
|-
<th> Skills Needed
| Rewrite our database code to be asynchronous when database if huge.
</th>
| 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}}.
<th> Reporter
Difficulty: Medium to hard depending on how far we go.
</th>
| C++ mainly
<th> Mentor(s)
| atuljangra
</th>
| ?anyone?
<th> Comments
| 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).
</th></tr></table>
|-
<h2>NSS (Network Security Services)</h2>
| Implement backend connectors for Ensemble (or DOM Contacts?)
<table class="standard-table" border="1" style="border-collapse: collapse">
| Mconley's new address book work should be stable enough by the summer that it is possible to write new connectors. Ideas for implementation here include any system address book on any platform, as well as LDAP support (OpenLDAP via js-ctypes looks to be the best option here).
| JS, although some C/C++ for native may be necessary
| jcranmer
| ?mconley?
|-
| Implement a mailbox-to-maildir converter
| This is one of the last critical pieces blocking moving away from mbox-style mailboxes.
| C++ is probably the simpler solution, but OS.File and jsmime make it possible in JS.
| jcranmer
| ?
|}
 
== SeaMonkey ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title  
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}
 
==NSS (Network Security Services)==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}
 
== Bugzilla ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details  
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}
 
== Firefox Support (SUMO) ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed  
! Reporter
! Mentor(s)
! Comments
|}
 
== QA ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter  
! Mentor(s)
! Comments
|}
 
== Documentation ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)  
! Comments
|}
 
== Mozilla IT and Infrastructure ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}
 
== Persona / BrowserID ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)  
! Comments
|}
 
== Sync / Services ==
 
{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}


<tr>
== Developer Tools ==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Bugzilla </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
{| class="standard-table" border="1" style="border-collapse: collapse"
<th> Title
|-
</th>
! Title
<th> Details
! Details
</th>
! Skills Needed
<th> Skills Needed
! Reporter
</th>
! Mentor(s)
<th> Reporter
! Comments
</th>
|}
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Firefox Support (SUMO) </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
== Add-on SDK ==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> QA </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
{| class="standard-table" border="1" style="border-collapse: collapse"
<th> Title
|-
</th>
! Title
<th> Details
! Details
</th>
! Skills Needed
<th> Skills Needed
! Reporter
</th>
! Mentor(s)
<th> Reporter
! Comments
</th>
|}
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Documentation </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
== Foundation ==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Mozilla IT and Infrastructure </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
{| class="standard-table" border="1" style="border-collapse: collapse"
<th> Title
|-
</th>
! Title
<th> Details
! Details
</th>
! Skills Needed
<th> Skills Needed
! Reporter
</th>
! Mentor(s)
<th> Reporter
! Comments
</th>
|}
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Persona / BrowserID </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
== Release Engineering ==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Sync / Services </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
{| class="standard-table" border="1" style="border-collapse: collapse"
<th> Title
|-
</th>
! Title
<th> Details
! Details
</th>
! Skills Needed
<th> Skills Needed
! Reporter
</th>
! Mentor(s)
<th> Reporter
! Comments
</th>
|}
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Developer Tools </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
== Instantbird ==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Add-on SDK </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
{| class="standard-table" border="1" style="border-collapse: collapse"
<th> Title
|-
</th>
! Title  
<th> Details
! Details  
</th>
! Skills Needed  
<th> Skills Needed
! Reporter  
</th>
! Mentor(s)  
<th> Reporter
! Comments
</th>
|}
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Foundation </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">
<tr>
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr>
<tr>
<td>Notebook Playback</td>
<td>
<p>The aim of this project is to add record-and-playback to the &lt;a href="http://ipython.org/ipython-doc/dev/interactive/htmlnotebook.html"&gt;IPython Notebook&lt;/a&gt;
using &lt;a href="http://popcornjs.org/"&gt;Popcorn.js&lt;/a&gt; (or its successor) so that people can create "screencasts" that are actually first-class content replayed
in the browser, rather than videos.  Based on &lt;a href="https://github.com/ipython/ipython/issues/2832"&gt;discussion with the IPyNB&lt;/a&gt; team and Bobby Richter,
we believe this can be done as a Javascript plugin to IPyNB v. 0.14 or higher by embedding timing metadata in the notebook's JSON file.  The project would
require substantial UI design and evaluation as well as Javascript hacking.  The result would immediately be used by &lt;a href="http://software-carpentry.org"&gt;Software
Carpentry&lt;/a&gt; and other projects for teaching, sharing code examples, etc.
</p>
</td>
<td>Javascript, UXD</td>
<td>gvwilson</td>
<td>gvwilson</td>
<td></td>
</tr>
</table>
<h2> Release Engineering </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
== Emscripten ==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Instantbird </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
{| class="standard-table" border="1" style="border-collapse: collapse"
<th> Title
|-
</th>
! Title
<th> Details
! Details
</th>
! Skills Needed
<th> Skills Needed
! Reporter
</th>
! Mentor(s)
<th> Reporter
! Comments
</th>
|}
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Emscripten </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
== Security Engineering ==
<th> Title
</th>
<th> Details
</th>
<th> Skills Needed
</th>
<th> Reporter
</th>
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
<h2> Security Engineering </h2>
<table class="standard-table" border="1" style="border-collapse: collapse">


<tr>
{| class="standard-table" border="1" style="border-collapse: collapse"
<th> Title
|-
</th>
! Title  
<th> Details
! Details  
</th>
! Skills Needed  
<th> Skills Needed
! Reporter  
</th>
! Mentor(s)  
<th> Reporter
! Comments
</th>
|}
<th> Mentor(s)
</th>
<th> Comments
</th></tr></table>
Gerv
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925

edits

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

Navigation menu