Calendar:Status Meetings:2006-04-06: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 41: Line 41:
## continue discussion regarding xpi (but not for xpfe) in the newsgroup, and keep it on next week's agenda for next week
## continue discussion regarding xpi (but not for xpfe) in the newsgroup, and keep it on next week's agenda for next week
# 1.0 brainstorming (cf [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/babba9eab651bbf2/937e8f6ab6bf6945#937e8f6ab6bf6945 newsgroup thread])
# 1.0 brainstorming (cf [http://groups.google.com/group/mozilla.dev.apps.calendar/browse_thread/thread/babba9eab651bbf2/937e8f6ab6bf6945#937e8f6ab6bf6945 newsgroup thread])
## lots done in nntp
# [http://www.joelonsoftware.com/uibook/chapters/fog0000000065.html Imaginary users] and product definition
# [http://www.joelonsoftware.com/uibook/chapters/fog0000000065.html Imaginary users] and product definition
## dmose: we've gotten to the point where we'll get more benefit from defining our audiences a bit more clearly than by doing more brainstorming immediately
## dmose: let's put together a meeting which includes mconnor and beltzner about this (action item - dmose: arrange meeting by tomorrow for sometime early next week and post details)
# Upcoming conferences / face-to-face meeting
# Upcoming conferences / face-to-face meeting
# Next meeting
# Next meeting

Revision as of 17:59, 6 April 2006

<< previous meeting | index | next meeting >>

Meeting Details

In Attendance

bienvenu, dmose, jminta, lilmatt (scribe), Mnyromyr, mschroeder, mvl, ssa, ssitter

Agenda

  1. Follow-up on action items from last week
    1. module owner state of the world / evolution possibilities (dmose)
      1. attempting to document the defacto state of the world more completely
        1. (ex: webdav = owner: mvl, peers: dmose)
      2. will put draft up in nntp this afternoon
      3. ssa: new provider module coming for connecting to Sun's calendar server (wcap)
    2. Info about Camino's review process (mvl)
      1. no response from emails. will follow up on #camino.
    3. ctalbert to take the lead on sorting out our QA picture (see nntp post)
      1. contacting davel@mozilla.com to find out more about the regression suite work davel has been doing for the moz project as a whole
      2. continue nntp discussion in the meantime
    4. mac build/release lossage (lilmatt)
      1. sorted out last week
    5. 1.0 features
      1. ssa started a good discussion in nntp
  2. Sunbird 0.3a2 status (mvl)
    1. some fixes applied
    2. some breakage (related to cairo being switched on on linux tbox)
      1. preed asked dmose whether we had wanted cairo for sb 0.3a2, replied "not particularly"
    3. bug 306157 remains - mvl not sure how to fix. others are r? or just need checking
    4. mvl away Easter weekend (~April 14). Prefer to release before then
    5. need to update version.txt and release notes url, and post release notes (sipaq)
  3. Calendaring extension future (cf newsgroup thread)
    1. main outcomes:
      1. drop calendar-xpi-in-tbird
      2. drop seamonkey support until it moves to toolkit
      3. drop xpfe support
      4. sunbird & lightning-in-tbird are our "tier 1" products
    2. still need to sort out our browser-calendar-story, whatever that is, whether it's "lightning", "calendar.xpi", "some other stub", or "nothing at all"
    3. ssa: can we get download numbers of lightning/sunbird? dmose: would be useful to track over time (action item - dmose: get numbers)
    4. continue discussion regarding xpi (but not for xpfe) in the newsgroup, and keep it on next week's agenda for next week
  4. 1.0 brainstorming (cf newsgroup thread)
    1. lots done in nntp
  5. Imaginary users and product definition
    1. dmose: we've gotten to the point where we'll get more benefit from defining our audiences a bit more clearly than by doing more brainstorming immediately
    2. dmose: let's put together a meeting which includes mconnor and beltzner about this (action item - dmose: arrange meeting by tomorrow for sometime early next week and post details)
  1. Upcoming conferences / face-to-face meeting
  2. Next meeting