Weekly Meeting Agenda for 21-Mar-2006
In attendance: Working team
Agenda
- review project plan
- roadmap
- intermediate deliverable for Winter '07
- project final deadline (1.0?)
Notes
Course Management Work Group
March 21, 2006 Meting Notes
Marc: Looks like we have a lot of good tasks in Jira to keep us going.
Ray: Hasn't had time to review the tasks for completeness
Lydia: What's CM-5?
Duffy: It's a GUI to browse the CM API
Ray: It's useful to have top to bottom technology stack from the start.
Duffy: We're on track to do DEV-1 through DEV-3 for end of March. DEV-5 seems out of reach in this timeframe.
Ray: Even if Stanford doesn't necessarily need CM for Fall 06, it's still worth talking with Casey about Stanford's needs.
Marc: What's the difference between the old providers and the new providers related to the CM API?
Ray and Josh: TBD. Integrators like Casey won't necessarily have to "write a provider". Instead, it's a matter of providing the enterprise data in a standard form, at which point Sakai will be able to refer to it. TBD is the amount of work needed to tweak institution-specific things like roles to Sakai-specific things.
Mark Marc: Is it in the realm of reality to expect cross listing by Fall 07
Josh: If it takes that long, we've failed
Mark Marc: Fall 06?
Duffy: It depends on exactly what Stanford needs. We need more details.
Daisy: I was involved with the Coursework cross listing. It uses a super course, with members as child courses. The membership of the super course is additive of all children. The name of the super course is arbitrary... whichever child course is more recognizable. The instructor would send a request to someone with administrative privileges to join up the courses which weren't officially cross-listed.
Duffy: It sounds like the linkages between courses are in the LMS. Cross listing for Stanford means that multiple courses can be linked inside the LMS.
Josh: The CM API allows only read only from the LMS
Ray: We can support what Daisy describes as long as we have a way for administrators to browse the CM data to set up manually-defined multiple-course sites.
Daisy: My knowledge is from 2 years ago
Mark Marc: It hasn't changed much. Having Daisy in the "Stanford cross listing" discussion with Casey would be useful.
Duffy: I'll set up the meeting. Casey, Ray, Josh, Duffy, and Daisy ToDo
Marc: So, I know this may be a chicken and egg question, but the reason I put "project project final deadline (1.0?)" on the agenda was to ask, "Do we know from our "higher ups" if there is an expected final deadline for the CM project?" That is, when do our current CM resources need to move onto other projects?
Ray: That's probably not a good question until we define exactly what we want to do
Daphne: UCB needs something by Fall 07
Josh: We need to build something before then.
Marc: Yeah, that's why we are talking about a mid-point deliverable of this cross-listing functionality built on the new CM API/service. It's just an example.
Ray: That's what we're doing here – trying to break it down for monthly deliverables.
Daphne: We need a roadmap
Josh: We have a roadmap in list form... if we need it in pictures, that's fine
Marc: OK, Duffy and I will work on a roadmap that we can review next week ToDo
(BTW, the original agenda item was "roadmap" -mARC)
Ray: We should talk about the two framework issues – Glenn still hasn't sent out the meeting notes from Davis, and we're in Contrib rather than entered as a top-level project. That makes everyone's life unnecessarily complicated. We're not just a drop-in application: we're involved in pretty central services. The new svn structure can protect the Sakai trunk and Sakai releases from new top-level projects just as well as putting them in contrib does.
Duffy: I will send an email request to Glenn to put us in the svn root. ToDo