[Building Sakai] Sakai 3 Capabilities

[nato]

Like many of you, I've been frustrated by my ability to put my head  
around the conversations and intersections around Sakai 3.

After a conversation with Clay, I decided to put together a stab at a  
wiki presentation of a Sakai 3 dashboard that might help us organize  
and better understand our work.

Accordingly, I've posted the bones of an example below, where I've  
begun a list of capabilities already under discussion for Sakai 3:
http://wiki.sakaiproject.org/display/MGT/Sakai+3+Capabilities

And I began to flesh out one example capability: Grading:
http://wiki.sakaiproject.org/display/MGT/Gradability

Still missing from Gradability are examples of actual (user)  
experiences and technologies used to deliver this capability.

There are at least a couple of limitations I see already to this  
format, but I'm open to suggestions and modifications:

1) Sakai 3 work is highly relational, yet it's handy to see material  
in context. I already found myself cutting and pasting material that  
might appear in more than one place.

2) The wiki format doesn't allow a preview of the "card" format, yet  
the card format allows chunks of info to surface at the top of the page.

--
Nate Angell
Client Evangelist
@xolotl = twitter
http://www.rsmart.com

_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"

[Clay Fenlason-3]

Reading through that list [1] again, there are a couple ways I can
take it, one of which makes me slightly nervous. The first way I think
is a better match for Nate's intent: an attempt to understand a broad
set of conversations about Sakai 3, and produce some sort of concept
map that might make sense of a lot of high-flown talk. The second, the
one that makes me nervous, is to read it as the beginning of a
capability definition of Sakai 3 that risks leapfrogging a design-led
effort.

I like how it's suggestive of other topics around which useful
'manifestos' (in the Norman model) might spring up. I dislike how it
suggests that these are gaps for which manifestos need to be
developed, and perhaps also how it might lend itself to designing by
functional area rather than working up from user goals and flows of
activity. In that sense it feels like a step back from the value of
the Google spreadsheet [2] which raises capabilities only in partial
response to clear expressions of user goals (abstracted from any
particular implementation).

I don't see that what Nate is putting forward necessarily positions it
as a product council activity or responsibility, but I'm also wary of
creating that impression.

~Clay

[1] http://confluence.sakaiproject.org//x/JgUAB
[2] https://spreadsheets.google.com/ccc?key=0AlfbHxo2qpHEdHRuSnowVGMwWE9HY1MtVjFpY1dtS0E&hl=en


On Wed, Oct 28, 2009 at 9:38 AM, Nate Angell <nate.angell@...> wrote:

> Like many of you, I've been frustrated by my ability to put my head
> around the conversations and intersections around Sakai 3.
>
> After a conversation with Clay, I decided to put together a stab at a
> wiki presentation of a Sakai 3 dashboard that might help us organize
> and better understand our work.
>
> Accordingly, I've posted the bones of an example below, where I've
> begun a list of capabilities already under discussion for Sakai 3:
> http://wiki.sakaiproject.org/display/MGT/Sakai+3+Capabilities
>
> And I began to flesh out one example capability: Grading:
> http://wiki.sakaiproject.org/display/MGT/Gradability
>
> Still missing from Gradability are examples of actual (user)
> experiences and technologies used to deliver this capability.
>
> There are at least a couple of limitations I see already to this
> format, but I'm open to suggestions and modifications:
>
> 1) Sakai 3 work is highly relational, yet it's handy to see material
> in context. I already found myself cutting and pasting material that
> might appear in more than one place.
>
> 2) The wiki format doesn't allow a preview of the "card" format, yet
> the card format allows chunks of info to surface at the top of the page.
>
> --
> Nate Angell
> Client Evangelist
> @xolotl = twitter
> http://www.rsmart.com
>
> _______________________________________________
> management mailing list
> management@...
> http://collab.sakaiproject.org/mailman/listinfo/management
>
> TO UNSUBSCRIBE: send email to management-unsubscribe@... with a subject of "unsubscribe"
>

_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"

[elicochran]

Nate,
Very helpful. I love the idea of having it all in one place.

At first I wanted to pull some of the items like "accessibility" and  
"rights and permissions" into their own list. They seem different than  
functionality that specifically supports teaching and learning.

But the more I think about it the more I like the one list to rule  
them all. It supports the idea that most of these concepts should be,  
like "Grading/Ranking/Rating/Reviewing/Evaluating", pervasive and  
omnipresent -- baked in everywhere -- in the same way that  
accessibility should be baked in everywhere and supported by the  
underlying architecture.

Thanks,
Eli

On Oct 28, 2009, at 2:38 AM, Nate Angell wrote:

> Like many of you, I've been frustrated by my ability to put my head
> around the conversations and intersections around Sakai 3.
>
> After a conversation with Clay, I decided to put together a stab at a
> wiki presentation of a Sakai 3 dashboard that might help us organize
> and better understand our work.
>
> Accordingly, I've posted the bones of an example below, where I've
> begun a list of capabilities already under discussion for Sakai 3:
> http://wiki.sakaiproject.org/display/MGT/Sakai+3+Capabilities
>
> And I began to flesh out one example capability: Grading:
> http://wiki.sakaiproject.org/display/MGT/Gradability
>
> Still missing from Gradability are examples of actual (user)
> experiences and technologies used to deliver this capability.
>
> There are at least a couple of limitations I see already to this
> format, but I'm open to suggestions and modifications:
>
> 1) Sakai 3 work is highly relational, yet it's handy to see material
> in context. I already found myself cutting and pasting material that
> might appear in more than one place.
>
> 2) The wiki format doesn't allow a preview of the "card" format, yet
> the card format allows chunks of info to surface at the top of the  
> page.
>
> --
> Nate Angell
> Client Evangelist
> @xolotl = twitter
> http://www.rsmart.com
>
> _______________________________________________
> management mailing list
> management@...
> http://collab.sakaiproject.org/mailman/listinfo/management
>
> TO UNSUBSCRIBE: send email to management-unsubscribe@...
>  with a subject of "unsubscribe"

. . . . . . . . . . .  .  .   .    .      .         .              .                     .

Eli Cochran
user interaction developer
ETS, UC Berkeley


_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"