An OLPC Development Model

Walter Bender walter.bender at
Thu May 8 12:57:14 EDT 2008

I'd draw the distinction slightly differently. Presumably when one
first loads a new build, you'd also load an associated  activity
stream, e.g., the Peru feed. At any time, one might want to either
check for updates to existing activities -- they'll be decoupled from
the OS build cycle, presumably, but not something you need to do all
that frequently -- or, perhaps more common, one might want to find new
activities. I suppose that there need not be a difference between load
and update in the new build case. But isn't the real distinction one
of maintenance vs exploring?


On Thu, May 8, 2008 at 12:50 PM, C. Scott Ananian <cscott at> wrote:
> On Thu, May 8, 2008 at 12:22 PM, Eben Eliason <eben.eliason at> wrote
>  >  We could also discuss how updates work....perhaps there are two views
>  >  in the "get more activities" dialog, one of which only shows available
>  >  updates to already installed activities.
>  I like thinking of this as two views.  There is a lot of common code
>  and UI, but "show me updates to my existing activities" and "show me
>  brand new activities matching some search criteria" are pretty
>  different use cases.  In particular, I might suggest that "show me
>  updates to existing activities" be invoked when a new build is first
>  booted, and clarifying the difference between "show me brand new
>  activities" would be important to avoid confusing the user.
>   --scott
>  --
>                          ( )

More information about the Devel mailing list