[Portfolio] Sakai 3-ish discussion

[John Norman]

The groups may have different top-level priorities, but that doesn't  
mean there are not a vast number of shared interests i.e. if the plane  
is on fire and there is only one parachute, who gets the parachute?  
The groups may make different choices, but that doesn't mean they are  
not both interested in the prospect of a safe landing or putting out  
the fire.

I think OSP have developed some good practices around the needs  
statements that help developers a lot to see what is needed, I'd quite  
like to get "teaching and learning" group to follow a similar route,  
for example fleshing out David Goodrum's priority list to a similar  
level of detail. Many of the things David is calling for would be of  
value to portfolio folk - for example the concept mapping as a means  
of stimulating reflection.

For OSP needs, the main thing that I think Sakai 3 brings is a tag- 
centric view of content and therefore the ability to assemble and  
reassemble information in many ways and far more easily than in  
current Sakai. But that doesn't mean we know exactly how to do this  
best for OSP needs. Also Goal awareness and user activity tracking  
seem very relevant to both sets of requirements.

HTH
John

On 16 Mar 2009, at 16:05, Sean Keesler wrote:

> Here are some notes I took from the community conference call during  
> our discussion of the future development:
>
> Relevant notes from 2009-03-16 OSP Community Call
>
> Sean reviewed the changed to the vignettes page with the group and  
> suggested that a next step would be to come up with a strategy for  
> introducing this to the Sakai3 working group. Noah has been keeping  
> his finger on the pulse of Sakai 3, but others probably could also  
> participate. Sean asked if others would be willing and able to  
> participate in conversations with the UX and T&L group, and if so,  
> how do we best do that? Noah mentioned that there is a weekly UX  
> call that could be used, but that the main conversations for Sakai3  
> are small conversations over Skype and the Sakai 001 bridge with  
> Nathan and a small group of developers. This group is under a lot of  
> pressure to release a version of Sakai 3 for Cambridge/GeorgiaTech  
> and we are unlikely to have an impact on its direction.
>
> Perhaps a good strategy for interacting with the Sakai 3 WG would be  
> to do so in concert with the T&L group. We recognize that there is a  
> barrier between how we think. Lynn had mentioned last week that they  
> are primarily focused on course/project sites. It may be that the  
> readiness of the OSP are a barrier (in which case, we should talk  
> with them soon to ensure that this is not the case in the future).  
> Nancy mentioned that Matthiew Plourde attends the T&L calls and she  
> would ask him for a recommendation on how the T&L group is  
> interacting with the Sakai 3/UX group and report back next week.
>
>
>
> --
> Sean Keesler
> 130 Academy Street
> Manlius, NY 13104
> 315-663-7756
> _______________________________________________
> portfolio mailing list
> portfolio at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/portfolio
>
> TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"