Difference between revisions of "Development:Good Bugs and Projects"

From Camino Wiki
Jump to navigation Jump to search
(clean up the intro again, move the explanation of the bottom stuff down there to not confuse people)
(update for 2010)
Line 1: Line 1:
 
<div style="margin: 0; padding:0 .5em; border:1px solid pink; background:#FFE8E8;"><b>Welcome to the Camino Wiki Summer of Code page</b>.  Due to incessant spamming, we've locked down registration to be by request only.  If you would like an account in order to add ideas to this page, please contact any of these admins: [[User:Admin|ss]], <!--[[User:Froodian|froodian]],--> [[User:sardisson|sardisson]]<!--, [[User:Wevah|Wevah]]-->, or ping '''ss''' or '''ardissone''' on [irc://irc.mozilla.org/camino #camino on irc.mozilla.org].</div>
 
<div style="margin: 0; padding:0 .5em; border:1px solid pink; background:#FFE8E8;"><b>Welcome to the Camino Wiki Summer of Code page</b>.  Due to incessant spamming, we've locked down registration to be by request only.  If you would like an account in order to add ideas to this page, please contact any of these admins: [[User:Admin|ss]], <!--[[User:Froodian|froodian]],--> [[User:sardisson|sardisson]]<!--, [[User:Wevah|Wevah]]-->, or ping '''ss''' or '''ardissone''' on [irc://irc.mozilla.org/camino #camino on irc.mozilla.org].</div>
  
=Summer of Code 2009=
+
=Summer of Code 2010=
Camino intends to participate in the 2009 Google Summer of Code, again under the auspices of the Mozilla Foundation.
+
Camino intends to participate in the 2010 Google Summer of Code, again under the auspices of the Mozilla Foundation.
  
Below are two sections, one for all project ideas (either brief, or fleshed out) and a second for project ideas that have been examined by the Camino leads for suitability for the scope and timeframe of the Summer of Code.<!--  (Ideas from this second section will ultimately be listed on the [https://wiki.mozilla.org/Community:SummerOfCode09#Camino official Mozilla.org project ideas] page.-->
+
Below are two sections, one for all project ideas (either brief, or fleshed out) and a second for project ideas that have been examined by the Camino leads for suitability for the scope and timeframe of the Summer of Code.<!--  (Ideas from this second section will ultimately be listed on the [https://wiki.mozilla.org/Community:SummerOfCode10#Camino official Mozilla.org project ideas] page.-->
  
Past accepted proposals can be viewed [[Development:Summer_of_Code_2006:Proposal|here]], [[Development:Summer_of_Code_2007:Tabspose:Proposal|here]], and [[Development:Summer_of_Code_2007:AppleScript:Proposal|here]].  In addition to Google’s [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents advice for writing applications], be sure to avoid [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html these common pitfalls] found in past applications for Mozilla projects.
+
Past accepted proposals can be viewed [[Development:Summer_of_Code_2006:Proposal|here]], [[Development:Summer_of_Code_2007:Tabspose:Proposal|here]], [[Development:Summer_of_Code_2007:AppleScript:Proposal|here]], and [[Development:Summer_of_Code_2009|here]]/[http://summerofcamino.com/2009/05/01/some-background/ here]<!--/[http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2009/mozilla/t124022728617 here]-->.  In addition to Google’s [http://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents advice for writing applications], be sure to avoid [http://weblogs.mozillazine.org/gerv/archives/2006/05/how_not_to_apply_for_summer_of.html these common pitfalls] found in past applications for Mozilla projects.
  
==SoC 2009 Project Suggestions==
+
==SoC 2010 Project Suggestions==
 
''Project ideas listed in this section have been examined by Camino leads for suitability for the Summer of Code.  Please do not add or move ideas to this section unless you are a Camino lead.''
 
''Project ideas listed in this section have been examined by Camino leads for suitability for the Summer of Code.  Please do not add or move ideas to this section unless you are a Camino lead.''
 
* Location Bar enhancements
 
*: Expand the range of abilities of the location bar. The ability to autocomplete from bookmarks and history by both title and URL would be a top priority. Other enhancements include: adding a Go button; fixing inline autocomplete; and memorizing keyword searches.
 
*: Related bug(s): {{bug|166288}}, {{bug|162450}}, {{bug|340611}}, {{bug|432178}}, {{bug|181716}}, {{bug|188188}}, {{bug|188178}}, {{bug|461400}}, {{bug|181806}}
 
*: Mentor: Stuart Morgan or Mike Pinkerton
 
  
 
* User scripts (partial Greasemonkey support)
 
* User scripts (partial Greasemonkey support)
 
*: Add Greasemonkey-like support for site-specific, user-created JavaScript modification to be run automatically to Camino, with as much compatibility with existing Greasemonkey scripts as is feasible.
 
*: Add Greasemonkey-like support for site-specific, user-created JavaScript modification to be run automatically to Camino, with as much compatibility with existing Greasemonkey scripts as is feasible.
 
*: Related bug(s): {{bug|329309}}
 
*: Related bug(s): {{bug|329309}}
*: Mentor: Stuart Morgan or Mike Pinkerton
+
*: Mentor: TBA
  
 
* Inline PDF support
 
* Inline PDF support
 
*: Use PDFKit to implement a custom Camino view for embedded and standalone PDF files. Register with Gecko to support PDF content-types using this view. Also look into support for displaying Postscript and EPS content-types, of which PDFKit is also capable.
 
*: Use PDFKit to implement a custom Camino view for embedded and standalone PDF files. Register with Gecko to support PDF content-types using this view. Also look into support for displaying Postscript and EPS content-types, of which PDFKit is also capable.
 
*: Related bug(s): None
 
*: Related bug(s): None
*: Mentor: Stuart Morgan or Mike Pinkerton
+
*: Mentor: TBA
  
 
* Unit Testing
 
* Unit Testing
 
*: Add a unit testing framework to the Camino build system, and create unit test suites for significant portions of the Camino-specific code below the UI level (which would likely include refactoring some code for testability). This would include generation of code coverage information to measure progress.
 
*: Add a unit testing framework to the Camino build system, and create unit test suites for significant portions of the Camino-specific code below the UI level (which would likely include refactoring some code for testability). This would include generation of code coverage information to measure progress.
 
*: Related bug(s): {{bug|417879}}, {{bug|453202}}
 
*: Related bug(s): {{bug|417879}}, {{bug|453202}}
*: Mentor: Stuart Morgan
+
*: Mentor: TBA
  
==SoC 2009 Project Idea Scratchpad==
+
==SoC 2010 Project Idea Scratchpad==
 
'''Please list any Summer of Code project ideas here.'''
 
'''Please list any Summer of Code project ideas here.'''
  
Line 53: Line 48:
 
==Projects==
 
==Projects==
  
''Some of these projects were listed on the MozillaWiki [http://wiki.mozilla.org/Community:SummerOfCode06 2006 Summer of Code], [http://wiki.mozilla.org/Community:SummerOfCode07 2007 Summer of Code], or [http://wiki.mozilla.org/Community:SummerOfCode08 2008 Summer of Code] pages.''
+
''Some of these projects were listed on the MozillaWiki [http://wiki.mozilla.org/Community:SummerOfCode06 2006 Summer of Code], [http://wiki.mozilla.org/Community:SummerOfCode07 2007 Summer of Code], [http://wiki.mozilla.org/Community:SummerOfCode08 2008 Summer of Code], or [http://wiki.mozilla.org/Community:SummerOfCode09 2009 Summer of Code] pages.''
  
 
===Camino===
 
===Camino===
Line 65: Line 60:
  
 
* Rewrite autocomplete in Cocoa; {{bug|340611}}
 
* Rewrite autocomplete in Cocoa; {{bug|340611}}
 
* Move history off of Mork; {{bug|351351}}
 
 
* AppleScript support for reading page contents/page source; {{bug|374648}}, {{bug|394582}} ([[User:hendy|hendy]] has essentially implemented this)
 
  
 
* AppleScript support for making new tabs/windows (will require lots of [http://summerofcamino.com/comments/bookmarks_check_almost/#more wrapping BW]); {{bug|395711}}, {{bug|395712}}
 
* AppleScript support for making new tabs/windows (will require lots of [http://summerofcamino.com/comments/bookmarks_check_almost/#more wrapping BW]); {{bug|395711}}, {{bug|395712}}
Line 103: Line 94:
 
*: Listed on [http://wiki.mozilla.org/Community:SummerOfCode06 MozillaWiki Summer of Code page]
 
*: Listed on [http://wiki.mozilla.org/Community:SummerOfCode06 MozillaWiki Summer of Code page]
 
* <s><tt>.mar</tt>/AUS-based Software Update; {{bug|185436}}</s> ([[User:smorgan|smorgan]] did this using Sparkle)
 
* <s><tt>.mar</tt>/AUS-based Software Update; {{bug|185436}}</s> ([[User:smorgan|smorgan]] did this using Sparkle)
 +
* <s>AppleScript support for reading page contents/page source; {{bug|374648}}, {{bug|394582}}</s> ([[User:hendy|hendy]] has essentially implemented this)
 +
* <s>Move history off of Mork; {{bug|351351}}</s> ([[User:hendy|hendy]] has essentially implemented this)
  
 
===Larger/Summer Projects===
 
===Larger/Summer Projects===
 +
* <s>Location Bar enhancements - Expand the range of abilities of the location bar. The ability to autocomplete from bookmarks and history by both title and URL would be a top priority. Other enhancements include: adding a Go button; fixing inline autocomplete; and memorizing keyword searches.
 +
*: Related bug(s): {{bug|166288}}, {{bug|162450}}, {{bug|340611}}, {{bug|432178}}, {{bug|181716}}, {{bug|188188}}, {{bug|188178}}, {{bug|461400}}, {{bug|181806}}</s> ([[User:dan|dan]] did most of this project in Summer of Code 2010)
 +
 
* <s>Tab exposé; {{bug|312007}}</s> ([[User:jeff|jeff]] brought us this project and did it in Summer of Code 2007)
 
* <s>Tab exposé; {{bug|312007}}</s> ([[User:jeff|jeff]] brought us this project and did it in Summer of Code 2007)
  

Revision as of 16:52, 3 February 2010

Welcome to the Camino Wiki Summer of Code page. Due to incessant spamming, we've locked down registration to be by request only. If you would like an account in order to add ideas to this page, please contact any of these admins: ss, sardisson, or ping ss or ardissone on #camino on irc.mozilla.org.

Summer of Code 2010

Camino intends to participate in the 2010 Google Summer of Code, again under the auspices of the Mozilla Foundation.

Below are two sections, one for all project ideas (either brief, or fleshed out) and a second for project ideas that have been examined by the Camino leads for suitability for the scope and timeframe of the Summer of Code.

Past accepted proposals can be viewed here, here, here, and here/here. In addition to Google’s advice for writing applications, be sure to avoid these common pitfalls found in past applications for Mozilla projects.

SoC 2010 Project Suggestions

Project ideas listed in this section have been examined by Camino leads for suitability for the Summer of Code. Please do not add or move ideas to this section unless you are a Camino lead.

  • User scripts (partial Greasemonkey support)
    Add Greasemonkey-like support for site-specific, user-created JavaScript modification to be run automatically to Camino, with as much compatibility with existing Greasemonkey scripts as is feasible.
    Related bug(s): Bug 329309
    Mentor: TBA
  • Inline PDF support
    Use PDFKit to implement a custom Camino view for embedded and standalone PDF files. Register with Gecko to support PDF content-types using this view. Also look into support for displaying Postscript and EPS content-types, of which PDFKit is also capable.
    Related bug(s): None
    Mentor: TBA
  • Unit Testing
    Add a unit testing framework to the Camino build system, and create unit test suites for significant portions of the Camino-specific code below the UI level (which would likely include refactoring some code for testability). This would include generation of code coverage information to measure progress.
    Related bug(s): Bug 417879, Bug 453202
    Mentor: TBA

SoC 2010 Project Idea Scratchpad

Please list any Summer of Code project ideas here.

  • Tab Palette
    Create a floating palette of all open tabs, with the ability to quickly switch to those tabs. Add the ability to filter tabs based on their content; this would require implementing full-text search across all open tabs. Further enhancement may include implementing a search field in the Tab Overview view that uses the full-text search.
    Related bug(s): Bug 197720 Bug 185916
    Mentor:

Camino Bugs and Projects

This portion of the page lists some sample ideas accumulated by Camino developers over the years for people interested in contributing to Camino (note that not all of these ideas may be suitable for the Summer of Code; if you are considering using one of the ideas below for a Summer of Code application, please discuss it with us first).

Camino needs a list of “good first bugs” and bugs/areas of improvement that are suitable for a focused, longer-term project, e.g., Google's Summer of Code, so that interested new contributors without any pet peeves can be pointed towards a concrete list.

References: Sam's Roadmap, Camino Vote List (bugs with 5 or more votes), bugs marked helpwanted in Camino or relevant Core components

Good First Bugs

Projects

Some of these projects were listed on the MozillaWiki 2006 Summer of Code, 2007 Summer of Code, 2008 Summer of Code, or 2009 Summer of Code pages.

Camino

Bugs listed need to be audited for suitability for a summer-sized project and for "interest" before listing for the SoC; items in boldface have previously been given suitability blessings by a senior Camino developer.

  • User script support; Bug 329309 (at least partial support)
  • Unit Testing; Bug 417879 (just the tip of the iceberg)
  • Tab palette; Bug 197720, the probably not enough for a summer project unless coupled with cross-tab content search. Also, add a search field to Tabsposé once cross-tab content search is implemented.
  • View source in an external program; Bug 159336, including an old in-progress patch from torben
  • Offline support (requires lots of Gecko)
  • Site-specific prefs support (also requires some Gecko)

Gecko-Mac

  • Revive/finish the Cocoa-Gecko accessibility work (see below for the original work).

Other Camino bugs

Historical Examples

Below are historical examples of things we've thought would make good projects.

Small Projects

Larger/Summer Projects

  • Location Bar enhancements - Expand the range of abilities of the location bar. The ability to autocomplete from bookmarks and history by both title and URL would be a top priority. Other enhancements include: adding a Go button; fixing inline autocomplete; and memorizing keyword searches.
    Related bug(s): Bug 166288, Bug 162450, Bug 340611, Bug 432178, Bug 181716, Bug 188188, Bug 188178, Bug 461400, Bug 181806 (dan did most of this project in Summer of Code 2010)
  • Tab exposé; Bug 312007 (jeff brought us this project and did it in Summer of Code 2007)
  • Support a11y in the content area (bridge Apple's accessibility APIs to the Mozilla accessibility APIs); bug 157209
    a little birdie tells us this should be happening RSN it's public now; hwaara is working on this :)