Connection Info
- Time: 5 p.m. BST, 12 p.m. EDT
- Conference Code: 348
- PIN: 72524
- IP Address: 129.79.6.44
- Telephone: 812-856-7060
Agenda
Updates on action items from last week:
- Clay following up with Colin about DOJO widget licensing, and the licensing group as needed.
- Harriet pursuing mock-ups and preliminary design work for what's really needed with dropbox notifications.
- We'll individually review outstanding JIRAs and promote to Blocker or critical status as appropriate
- Calling another filepicker meeting? Without getting into implementation or design questions during this call, talk about steps/timelines to drive this forward.
Attendees
- Harriet Truscott
- Jim Eng
- Mike Osterman
- Kathy Moore
- Clay Fenlason
Minutes
- Colin directed Clay to the DOJO toolkit licensing information, which seemed more permissive than necessary for Sakai's requirements. Followed up with the licensing group and announced our intent to move ahead with putting this work in trunk. We've done enough due diligence to move ahead with putting it in the post-2.4 branch. ( OPEN QUESTION: who is going to do this, and when?)
- Harriet still needs more time to do preliminary work on dropbox notifications.
- Group reviewed outstanding Resources JIRA issues. After some discussion, established the following as "Blocker" items that will be targeted for the maintenance branch:
Jira Legacy SAK-9526 SAK-9526 Jira Legacy SAK-9742 SAK-9742 Jira Legacy SAK-10309 SAK-10309 Jira Legacy SAK-10592 SAK-10592 Jira Legacy SAK-10779 SAK-10779
- An additional item for 2.5: new content types that will need to be recognized.
- We've slipped our self-imposed July 16 deadline to settle on 2.5 commitments with finality, but we can flex here a bit, over the course of the next week.
- Filepicker conversations indicate that there's clearly a lot to work through. Too much to contemplate for 2.5?
- Let's keep the discussion going - we may still find a few simple things that would help that would be worth knocking out for 2.5.
- It could be a really valuable effort to make the focus of 2.5 development be open bugs and issues. It could be a more powerful message, and more valuable to the community than any improvements under consideration.
- Sakai is often accused of looking ahead to the next cool change, and not cleaning up after itself well.
- We've established a coherent QA process focused on the Resources tool, and we can leverage it even further.
- Some consensus that emphasizing fixes in 2.5 would be a good goal
- We shouldn't, however, retreat at all from the ongoing design discussions and plans. Whether anything for 2.5 comes from that or not, it's worth pursuing.