[Sugar-devel] [IAEP] ASLO Suggestion

[Sean DALY]

hmmm thanks Martin for that

I guess I'm confused because for me, a "set of demo Activities" is not
at all the same thing as "baseline Activities included in every Sugar
deployment".

I mean, to demonstrate online collaboration, I could choose a fancier
or more advanced Activity than might be on a list of more basic ones
used in deployments already. As an example, Read Etext's ability to
bring in an eBook from the tens of thousands in the Gutenberg Project,
have it read by Speak, then share it, is an ultracool demo. But, is it
in Fructose?

GCompris has doubled our Activity offer and although the collaboration
/ view source / graphics are not where most other Activities are, I
would include one or two GCompris Activities in any "demo set", if
only to market Sugar to teachers already using GCompris in their
classrooms these past few years.

Activity Packs (Sets? Groups? Bundles? Hives?) seem to me a key part
of deployments, but I'm not sure where they fit in the diagram :-( and
I can't find a list of packs actually used in deployments, do we have
one somewhere?

thanks

Sean



On Thu, Jun 11, 2009 at 10:32 AM, Martin
Dengler<martin at martindengler.com> wrote:
> On Thu, Jun 11, 2009 at 09:51:24AM +0200, Sean DALY wrote:
>> ultimately, the question is: are there (or not) Activities common to
>> every, or nearly every instance of Sugar?
>
> This is "Fructose":
> http://wiki.sugarlabs.org/go/Taxonomy#Fructose:_The_set_of_demonstration_activities
>
> If you keep asking what to call them we'll keep telling you what
> they're called.
>
> Feel free to suggest alternates, but it's hard to effectively do so
> without an understanding of the status quo.  Please point out what's
> confusing as I'm sure plenty of people would like to make things as
> comprehensible as possible.  I recognise that the fact people keep
> asking could certainly be because it's not being well-explained.
>
> Please consider this diagram as well:
>
> http://wiki.sugarlabs.org/go/Taxonomy#The_SUGAR_stack:_block_diagram_view
>
>> Sean
>
> Martin
>