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

From Camino Wiki
Jump to navigation Jump to search
(→‎Good First Bugs: stuff that belongs on contributor overview, but is here for now)
Line 8: Line 8:
  
 
==Good First Bugs==
 
==Good First Bugs==
 +
'''N.B.''' This list is largely out-of-date, but the query below it is still good.
  
 
* Drag-and-Drop Reorderable Tabs; {{bug|160720}} and {{bug|318260}} ([[User:delliott|delliott]] is doing this as part of the 2006 SoC)
 
* Drag-and-Drop Reorderable Tabs; {{bug|160720}} and {{bug|318260}} ([[User:delliott|delliott]] is doing this as part of the 2006 SoC)
Line 22: Line 23:
 
* Bookmarks Bar buttons should darken text on mousesdown; {{bug|300304}}
 
* Bookmarks Bar buttons should darken text on mousesdown; {{bug|300304}}
 
* Bookmark keywords with spaces gives "Invalid URL" error if entered in address bar (do input validation on keyword entry); {{bug|303628}}
 
* Bookmark keywords with spaces gives "Invalid URL" error if entered in address bar (do input validation on keyword entry); {{bug|303628}}
−
* keyword.enabled doesn't work in Camino (1.8branch and trunk); {{bug|336017}}
+
* <s>keyword.enabled doesn't work in Camino (1.8branch and trunk); {{bug|336017}}</s> - '''FIXED'''
 
*: <br>[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Camino&status_whiteboard_type=allwordssubstr&status_whiteboard=%5Bgood+first+bug%5D&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED good first bug query] (the query and the above list do not match yet)
 
*: <br>[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&product=Camino&status_whiteboard_type=allwordssubstr&status_whiteboard=%5Bgood+first+bug%5D&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED good first bug query] (the query and the above list do not match yet)
 +
 +
===Good First Bug vs. Triage Priority===
 +
 +
The "Good First Bugs" list is a list of "bugs" (problems or feature requests) that are good entry points for new Camino developers, not necessarily a list of the bugs that need to be fixed most urgently.  A bug's priority is determined (roughly) by the severity field, the priority field (used generally by developers to prioritize lists of bugs assigned to them), the target milestone, and the blocking flags.  For instance, bugs with a target milestone of Camino 1.1 are generally most important at the moment, and ones with higher severity (or a camino1.1+ or camino1.1? flag) are the most important of those.
 +
 +
* Bugs Targeted at Camino 1.1
 +
* ''Somewhere we should have an "Unofficial" Roadmap for Developers with bugs or categories of bugs for a release, like the Firefox PRD but more humane, to supplement the "target milestone" queries--a more-official version of Sam's Roadmap or Smokey's 1.1 list''
 +
* Stuff we'd like fixed: [[Development:Good Bugs and Projects]]
 +
 +
===Working on a bug===
 +
* When to take a bug, and how to do it (some of this is in the existing cbo dev pages)
 +
* Bugs with status '''NEW''' whose assignee is ''nobody@mozilla.org'', ''mikepinkerton@mac.com'', and  ''sfraser_bugs@smfr.org'' are fair game
 +
* Ask first before taking a bug with status '''NEW''' with any other assignee, or before taking a bug with status '''ASSI'''.
  
 
==Camino and Gecko-Mac Projects==
 
==Camino and Gecko-Mac Projects==

Revision as of 00:11, 3 August 2006

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.

For the latter set, we should also include Gecko-Mac platform bugs.

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

Bugs listed, especially in the “Good First Bugs” section, need to be audited by acutal devs for suitability ;-)

Good First Bugs

N.B. This list is largely out-of-date, but the query below it is still good.

  • Drag-and-Drop Reorderable Tabs; Bug 160720 and Bug 318260 (delliott is doing this as part of the 2006 SoC)
    Listed on MozillaWiki Summer of Code page
  • Software update notification (non-AUS); bug 185436
  • Private Browsing bug 251677
  • optional "Go" button for toolbar bug 181806 - WONTFIX?
  • Show/Hide Bookmarks toolbar button does not indicate state; Bug 235863
  • Ability to save session state; Bug 152147
  • Maximum width of location bar/search field is fixed at 2560 pixels; Bug 336947
  • Disable View Source menu command and toolbar button when viewing source; Bug 159337
  • Loading bookmarks with keywords doesn't allow popups (e.g., BugMeNot); Bug 319879
  • Tab context menu for tab with Bookmarks/History displayed includes "Reload Tab"; Bug 319922
  • Bookmarks Bar buttons should darken text on mousesdown; Bug 300304
  • Bookmark keywords with spaces gives "Invalid URL" error if entered in address bar (do input validation on keyword entry); Bug 303628
  • keyword.enabled doesn't work in Camino (1.8branch and trunk); Bug 336017 - FIXED

    good first bug query (the query and the above list do not match yet)

Good First Bug vs. Triage Priority

The "Good First Bugs" list is a list of "bugs" (problems or feature requests) that are good entry points for new Camino developers, not necessarily a list of the bugs that need to be fixed most urgently. A bug's priority is determined (roughly) by the severity field, the priority field (used generally by developers to prioritize lists of bugs assigned to them), the target milestone, and the blocking flags. For instance, bugs with a target milestone of Camino 1.1 are generally most important at the moment, and ones with higher severity (or a camino1.1+ or camino1.1? flag) are the most important of those.

  • Bugs Targeted at Camino 1.1
  • Somewhere we should have an "Unofficial" Roadmap for Developers with bugs or categories of bugs for a release, like the Firefox PRD but more humane, to supplement the "target milestone" queries--a more-official version of Sam's Roadmap or Smokey's 1.1 list
  • Stuff we'd like fixed: Development:Good Bugs and Projects

Working on a bug

  • When to take a bug, and how to do it (some of this is in the existing cbo dev pages)
  • Bugs with status NEW whose assignee is nobody@mozilla.org, mikepinkerton@mac.com, and sfraser_bugs@smfr.org are fair game
  • Ask first before taking a bug with status NEW with any other assignee, or before taking a bug with status ASSI.

Camino and Gecko-Mac Projects

Some of these projects were listed on the MozillaWiki 2006 Summer of Code page; see this blog entry.

  • Support a11y in the content area (bridge Apple's Carbon 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 :)
  • Fix issues with XUL in the content area in Camino (make XUL webapps completely functional; at least menus, selects, and context menus don't work right now); bug 306252, bug 306613
  • etc.

Other Camino bugs

Retrieved from "http://wiki.caminobrowser.org/index.php?title=Development:Good_Bugs_and_Projects&oldid=6072"