SeaMonkey/StatusMeetings/2010-02-09

« last meeting | index | next meeting »

SeaMonkey Meeting Details

• Time: February 9, 2010, 13:00 UTC
• Location: #seamonkey IRC channel

Agenda

• Who's taking minutes?

Action Items

(who needs to do what that hasn't been recorded in a bug) We should assign people to the open items.

NEW

OPEN

• Get permission from Google to use their geolocation JSON service [KaiRo]. Contact at Google says: "We don't have a good estimate for when GLS will be opening up more broadly, but I will be sure to let you know when we take that step. Sorry that I can not be more specific at this time." - We can only wait right now.
  • KaiRo found out that the contact at Google changed. Also, discussing a possible open Geolocation service.

CLOSED

SeaMonkey 2.0 Feedback

Only unresolved items are tracked here - and we should find a way to deal with it for every item talked about in this section!

• Anything new?
• bug 539194 MailNews high CPU (bug 311774 regression).
  • Noted in relnotes for 2.0.3, anything else we can do to move this?

SeaMonkey 2.0.3

open blockers (1) blocker requests (0) fixed (112)

• Planned release for 16 February, based on Gecko 1.9.1.8.
• GetDefaultFeedReader and venkman slowdown pushed to 2.0.4, as well as some blocker requests.
• 23 security bugs in addition to 112 other fixes, again some good fixes for 2.0.x stabilization and smoothness.
• Builds are up on FTP and on the beta channel for testing.

SeaMonkey 2.0.4

open blockers (2) blocker requests (2) fixed (0)

Feature List, Planning

Bug statistics for last two (full) weeks: 44 new, 18 fixed, 20 triaged.

• Nearer to par, but still more new than resolved bugs. :(

Major wanted/needed features:

2.0.x

• bug 423281 Help updates.
  • bug 463903 (form autocomplete documentation).
  • FAQ to cover e.g. double-click / down arrow in form fields?
    • status/progress?
• bug 483282 Make sure normal SeaMonkey use doesn't pay a price for having venkman installed [Mnyromyr].
  • Needs at least a core patch landing for 1.9.1.9 bug 364864 nsICategoryManager::deleteCategoryEntry does not persist outside of component registration.
  • status/progress?
• bug 471346 Port GetDefaultFeedReader to SeaMonkey shell service. New patch needed [mcsmurf].
  • status/progress?

2.1

• bug 460953 kill-rdf port [sgautherie].
  • Postponed until mcsmurf (or sgautherie) can resume work on it.
  • status/progress?
• bug 436794 Enable Mac OS X system address book per default and add UI.
  • SM UI needed, unowned, helpwanted.
• bug 410613 OpenSearch. helpwanted.
  • We need to check if OpenSearch can support all our existing functionality, for example the INTEPRETS section in Sherlock search plugins. Mnyromyr will check on that, and on how extensible the Firefox code is.
• bug 449728 Drag tabs between windows.
  • unowned so far.
• bug 498596 Places bookmarks.
  • unowned so far.
• bug 480734 Satchel data editor ("Form Manager").
  • unowned so far.
• bug 477845 Build a standalone (Gecko 1.9.3) Composer.
  • kaze will look into that once KompoZer 0.8 is done.
  • bug 477840 Backport KompoZer to Composer (Depends on bug 477845).
  • kaze has done a ton of work there, we're trying to work out some organizational issues atm.
• bug 523274 Complete new default theme icon set.
  • A list of TODO icons is up in the bug
  • Still needs quite a bit of work.
  • bug 522023 is working on improving the browser globe in task icons, etc..
• bug 526210 Update the icon set for the SeaMonkey Modern Theme.
  • unowned so far.
• bug 521927 Make Search, Folder Location and Views widgets for MailNews customizable toolbars.
  • status/progress?

We also should take a look at the other items on wanted-seamonkey2.1+

• SeaMonkey 2.1 Planning: Gecko roadmap is still unclear, there are two proposals on Talk:Firefox/Roadmap now, and discussions in m.d.planning - also makes 1.9.3 vs. 1.9.2 for us somewhat unclear, but it seems that 1.9.3 might be in late summer or fall, which might fit our schedules well.
• We should go for smaller releases to ease upgrade paths for users. If we need to push back one or the other feature to the next smaller release, so be it, but we should stay closer to the Geckos Firefox is shipping as current.

Roundtable

Status Updates from developers - what are you working on, what's the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

KaiRo

• As usual, my blog has more detailed status about my work, and Mozilla Status Board Posts also tells about my next planned steps.

Standard8

• See Mozilla Status Board Posts.

Any other business?

• ?