Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Connection Info

  • Conference Code: 348
  • PIN: 72524
  • IP Address: 129.79.6.44
  • Telephone: 812-856-7060

Time

4:00pm GMT Corresponding times

Agenda

A. Updates on last week's action items:

  • IU's branch for the pop-up description: http://bugs.sakaiproject.org/jira/browse/SAK-10581
  • Following up on dijit drop-down widget (Harriet)
  • Status of Resources Viewer (Mike)
  • Maintenance branch status?
  • Decisions on proposed deadlines from last week:
    • Resources tool feature freeze: July 16
      • this will be for settling on the scope of any UI changes we'll consider for 2.5
      • probably no more than the pop-up idea IU is floating, but we'll give ourselves a week to think it over and get additional input
    • File-picker feature freeze: Aug 1
      • for settling the scope of any file picker (attachment helper) changes
      • need a little extra time to think through this one, as user expectations are a little murky
    • Specification freeze*: Aug 15
      • final designs/specifications for what will be completed for 2.5
      • this will be surfaced to the community as what they can expect to see in the release
    • Code freeze: Sept 15
      • changes delivered in a working state (i.e. tested to a first order)
      • this should involve a level of QA before the freeze, to make sure Resources isn't completely broken going into the release cycle
    • String freeze: Oct 1
      • we may not need this, but any message bundle work will be finalized by this point
    • Branch freeze: Oct 15
      • target for the release as a whole
    • Release: Nov 1

B. Review of filepicker situation:

  • defining implementation scope for 2.5
    • which contexts/tools?
    • new widget?
    • what are the resource commitments?

C. Dropbox improvements?

  • Could we look at SAK-7812 - Getting issue details... STATUS for 2.5 (Email notification sent when item is added to Drop Box)

Attendees

  • Jim Eng
  • Mike Osterman
  • Sean Keesler
  • Daphne Ogle
  • Clay Fenlason
  • Kathy Moore
  • Harriet Truscott

Minutes

Quick Updates:

  • Jira and branch for IU's UI proposal has been created, see link above
  • Harriet reviewed the outstanding widget bugs that gave Colin pause, and found that one applied to a widget we wouldn't use, while another seems fixed already
    • general consensus that we should move ahead with bringing this into trunk and the post-2.4 branch (but not the maintenance branch), even ahead of a 1.0 release for the widget
    • need to follow up with Colin about licensing question
    • Action item: Clay will follow up with Colin about licensing, and the licensing group as needed
  • Resources Viewer status
    • Mike has been working on some blocker issues about displaying the title and multiple RV tools; is past the hump on the former, and should be able to get Josh Ryan's help on the latter beginning next week
    • will then begin to appeal for more help on the resources list for closing other issues that have surfaced
  • Maintenance Branch
    • Two outstanding issues listed as "blockers" for maintenance branch work:
      • SAK-9526 - Getting issue details... STATUS is about the Dublin Core stuff, and Harriet's going to have a few people test it further to make sure the current work provides what people expect
      • SAK-10309 - Getting issue details... STATUS : Steve Lonn is working on this
    • at some point soon we'll need to shift away from maintenance branch work for the 2.5 stuff.
    • Action Item: we'll individually review outstanding JIRAs and promote to Blocker or critical status as appropriate
  • Proposed Deadlines
    • Deadlines listed above are adopted
  • Dropbox notifications considered
    • Need to make a determination for 2.5 fairly quickly here, since we've already agreed to a July 16 deadline
    • requirement might also be met by "Recent Activity" tool, though it's not clear whether that's in a working state
    • Since Resources already has notifications, the email notification route might be easiest
    • Action Item: Harriet will pursue some mock-ups and preliminary design work for what's really needed here. Enough for us to at least make some judgment about whether this (or how much) can be done for 2.5. By July 16!

Page for Drop Box notification - http://confluence.sakaiproject.org/confluence/x/obY

  • No labels