...
- we were initially talking about minimizing UI changes for 2.5, but now we're entertaining this pop-up idea. Is that too much?
- not really. We'll just adopt a strategy of having the new bits off by default, but available for enabling through sakai.properties or tool options
- we should, however, try to halt the scope increase now. We're only two months from the next code freeze, and still trying to work on 2.4.x issues
- we haven't yet taken on the file-picker helper issues we had earlier planned to
- the basic problem: design issues oriented around user expectations for adding attachments to things, and consistency between two different ways of adding attachments (namely, attaching by linking and attaching by copying.)
- we need to give some design attention to this, but really need to move on it fairly soon, and set some deadlines for ourselves
- still mostly looking at design issues
Deadlines for 2.5.0
- Resources tool feature freeze: July 15
- 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
- we'll have a focused meeting about this next Tuesday at the same time (5 p.m. GMT)
- Specification freeze*: Aug 15
- final designs/specifications for what will be completed for 2.5
- Code freeze: Sept 15
- changes delivered in a working state (i.e. tested to a first order)
- 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
Dublin Core
- There was some comment that this had gone missing. Are we getting it back?
- The UI is already back, and there is some additional work underway, but in short: yes. Jim is doing this.
Should we have regular meetings?
- there is enough work going on, and enough separate threads that need coordination, that we should meet regularly for the next month at least.
- short, frequent meetings are easier to commit to, and probably healthier for the process