5,705
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: + + +
Platform Team/Package Management System/Getting started (view source)
Revision as of 08:11, 5 December 2011
, 08:11, 5 December 2011→Sweets introduction
::: "It is important to stimulate users into becoming doers—to modify existing activities, and to share the results of their experiments with other people, viz., a distribution method should handle different variants of the same project.";
::: "It is important to stimulate users into becoming doers—to modify existing activities, and to share the results of their experiments with other people, viz., a distribution method should handle different variants of the same project.";
::: so Sweets seems to be aimed at those about to graduate to the software sharing stage of Sugar learning. Do you think that this stage can be assumed for someone who has not launched or loaded Sugar before? (''Someone'', here, refers to a significant fraction of the population of beginning Sugar learners.) To this goal, significant stimulation efforts seem to be focused on providing malleable software at the Activity level, so learners can discover the gratification of creating new 'code' products. Sweets seems a bit advanced from that early stage. Clearly, a, or ''the'', goal is to lower the effort required for robust doer<->doer sharing. Seems like we need to advance by iteration with 'early adopters' and continue to eliminate all the 'hitches' and obstacles that discourage the vast majority of new users yet to become doers. --[[User:FGrose|FGrose]] 22:49, 3 December 2011 (EST)
::: so Sweets seems to be aimed at those about to graduate to the software sharing stage of Sugar learning. Do you think that this stage can be assumed for someone who has not launched or loaded Sugar before? (''Someone'', here, refers to a significant fraction of the population of beginning Sugar learners.) To this goal, significant stimulation efforts seem to be focused on providing malleable software at the Activity level, so learners can discover the gratification of creating new 'code' products. Sweets seems a bit advanced from that early stage. Clearly, a, or ''the'', goal is to lower the effort required for robust doer<->doer sharing. Seems like we need to advance by iteration with 'early adopters' and continue to eliminate all the 'hitches' and obstacles that discourage the vast majority of new users yet to become doers. --[[User:FGrose|FGrose]] 22:49, 3 December 2011 (EST)
:::: From one side, it is original intention to make Sweets useful for 'early doers', e.g., instead "./setup.py dist_xo && run Browse && go ASLO and login there && upload your .xo" it is only "sweets commit". From another side, Sweets is only low level technical tool, PMS, with strong idea exactly to
"It is important to stimulate users into becoming doers—to modify existing activities, and to share the results of their experiments with other people, viz., a distribution method should handle different variants of the same project.". And it is possible to create several frontends for different levels of 'early adopters' to make them doers. The one effort is might be undertaken within Peru pilot program, where it require new software/activity for having "offline ASLO" (and this application/activity might be also stimulate people become doers).
Could you [originally addressed to [[User:Inkyfingers|Inkyfingers]]] look at the documentation with the eye toward drafting an introductory posting and page for new non-technical users? If you could outline, or outright draft, an introduction, it would be a great service to us (and we need to exploit your 'newness' before it rapidly expires, if it hasn't already.) and much appreciated! --[[User:FGrose|FGrose]] 21:23, 2 December 2011 (EST)
Could you [originally addressed to [[User:Inkyfingers|Inkyfingers]]] look at the documentation with the eye toward drafting an introductory posting and page for new non-technical users? If you could outline, or outright draft, an introduction, it would be a great service to us (and we need to exploit your 'newness' before it rapidly expires, if it hasn't already.) and much appreciated! --[[User:FGrose|FGrose]] 21:23, 2 December 2011 (EST)