Calendar:Status Meetings:2006-06-08

From MozillaWiki
Jump to: navigation, search

<< previous meeting | index | next meeting >>

Meeting Details

Telephone Info

  • Toll free numbers
  • Access Code
    • 3646989
  • Conference controls
    • *6 mute line
    • *7 unmute line
  • Each time you say something, please say your name first so people know who's talking

Attending

Proposed Agenda Items

  • Roadmap status update
    • How to get to 0.3?
    • How to continue with the task/feature matrix ?
  • How to address UI related enhancements needed to support the WCAP connector?
  • Pref re-org update
  • L10n move status update
  • Address a few questions pertaining to component reorganization
    • Security and printing component
    • nobody@mozilla.org as default assignee
    • default QA contacts -- should it be calendar@<component_name>.bugs?
      --ssitter 03:08, 9 June 2006 (PDT) at the moment component@product.bugs is used widely so I think we should use <component_name>@calendar.bugs
  • Shift this meeting to another day and time: Wednesday, 16:00 UTC or 16:30 UTC
  • Should we move themes to root of /calendar for sharing by Sb and Ln? Sanity check before posting to ng.

In Attendance

ctalbert, dmose, jminta, lilmatt, mickey, sipaq, ssa

Notes

Roadmap status update

  • lilmatt: want to move towards remove disclaimer+deprecate old roadmaps
  • ssa going to add timeline/milestone to roadmap

How to get to 0.3?

  • need to describe roadmap at proper level (above bug #s)
  • dmose: current stuff is good starting point while docs are finished
  • dmose: We should fill in details of the roadmap over time
  • lilmatt: We shouldn't try to stuff everything into 0.3
  • dmose: Let's focus on basics add new features as justification appears (This process works for FF)
  • as process documentss finish, dovetail them into the roadmap/plan
  • ssa: Let's target the roadmap for toronto. We can aim to get the process docs done before, and clear any other blockers before we arrive
  • all agreed: Roadmap construction will be a major focus at Toronto
    • sipaq: shoot for 95%, since some flexability is needed
  • Targeting 0.3 end of August-ish
    • jminta: spread QA over entire development period to help make target date
      • ctalbert: unit tests/QA stuff still being researched
      • dmose: We should try to supplament nightly testers with something structured too
      • ssa (action item): can push UI-tests, unit tests to Ulf, hope to get ng post soon
      • sipaq: We should also use community more (blogs, ng, etc)

How to continue with the task/feature matrix ?

  • This is a helpful doc for roadmap discussion
  • ssa (action item) Post to newsgroups asking for feedback

How to address UI related enhancements needed to support the WCAP connector?

  • Free-busy support is included
  • dmose: UI and provider is fairly independent, UI-ownership doc will give us people to turn to for help divorcing the two
    • free-busy derives from task list/roadmap
    • jminta: #ifdef build-flag
    • dmose: Can we get a complete list of features this will include?
      • mickey/dmose/daniel action item: IRC discussion on features
  • ssa: This is a lot of code. What's the best way of attacking/reviewing
    • dmose: Well, splitting into the raw-provider, prereq bugs (timezone bug), etc
    • dmose: We can land the code in tree, but leave it turned off. Only review before turning it on.
      • give daniel free reign within the wcap module until code is turned on
    • ssa (action item): Put notes in bugs blocking the landing

Pref reorg

  • lilmatt: waiting on one patch for review
  • dmose (action item): going to contact mvl to push the review

L10n move status update

lilmatt: All non-english locales moved yesterday (with great help from KaiRo/Pike) Remaining pieces:

    • 2 orphaned locales Welsh/Sorbian, no owner, haven't been updated
      • tag and delete? lilmatt (action item): push this forward
      • sipaq (action item - done): going to try to contact old owners
  • Lithuanian is only on branch
  • There are a couple other bugs needed to build self-standing langpacks
    • We need toolkit packaging code, patch awaiting review
  • wiki updated for building with other locales

Address a few questions pertaining to component reorganization

  • Security and printing component
    • Let's err on side of consistency and include them
  • nobody@mozilla.org as default assignee?
    • Yes
  • default QA contacts -- should it be calendar@<component_name>.bugs?
    • Yes
    • ctalbert: will post updated watchlist to newsgroups

Shift this meeting to another day and time: Wednesday, 16:00 UTC or 16:30 UTC

  • punt to next week with mvl

Should we move themes to root of /calendar for sharing by Sb and Ln? Sanity check before posting to ng.

  • lilmatt: This aims to prevent redundancy (ie duplicate toolbar style rules)
  • dmose: push to next week
Retrieved from "https://wiki.mozilla.org/index.php?title=Calendar:Status_Meetings:2006-06-08&oldid=28146"