<br><div class="gmail_quote">2012/6/7 STEPHEN JACOBS <span dir="ltr"><<a href="mailto:itprofjacobs@gmail.com" target="_blank">itprofjacobs@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The documentation doesn't really address the context, purpose, goals or implementation of gamification beyond the fact that there should be hooks in the sugar network to support it.<br>
<br>
The seemingly arbitrary metaphor (sun, star, moon etc ) and the reference to points suggests that this is abstracted away from what the user actually does in the system as does the reference to points without a discussion of what they are for or how they work.<br>
<br>
Research shows that Gamification that is not thoughtfully designed and implemented may have a bump of interest in the short term but gets ignored, becomes an annoyance, or actually a disincentive to participation in the longer term.<br>
<br>
IMO, If the Sugar community wants this network to be gamified it needs more thinking and design work before that functionality is implemented.<br>
<br>
Sent from my iPhone<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div class="h5"><br>As we plan to start activating the network on a local "controlled" pilot we could certainly use some help defining the functionality of basic mechanisms for initial iteration. <br>
<br><br>On Jun 7, 2012, at 5:26 AM, Aleksey Lim <<a href="mailto:alsroot@sugarlabs.org">alsroot@sugarlabs.org</a>> wrote:<br>
<br>
> On Wed, Jun 06, 2012 at 12:04:36PM -0500, Sebastian Silva wrote:<br>
>> /* en español abajo */<br>
>> Hi,<br>
>> One proposal to evidence the value of "interactions" within the Sugar Network<br>
>> user interface is to count, for each context, and to show them in the interface<br>
>> as such:<br>
>><br>
>> 1 interaction = 1 "Sun" badge<br>
>><br>
>> This is to continue with the icons "Star" - "Moon" - "Sun".<br>
>><br>
>> To better understand this in reference to Sugar Network, with "interactions" we<br>
>> mean contributions of feedback or support resources users provide within the<br>
>> network.<br>
>><br>
>> Not every interaction has been implemented graphically yet but for reference<br>
>> here are the high level conceptual documentation:<br>
>> <a href="http://wiki.sugarlabs.org/go/Sugar_Network/Concept" target="_blank">http://wiki.sugarlabs.org/go/Sugar_Network/Concept</a><br>
>><br>
>> And the low level Objects Model that sustains it at this time:<br>
>> <a href="http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/Objects_model" target="_blank">http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/Objects_model</a><br>
>><br>
>> Feedback at this point is appreciated as we prepare to launch at scale.<br>
>><br>
>> Regards,<br>
>> Sebastian<br>
><br>
> In fact, regarding Sugar Network, my original post was rather about<br>
> popping up this subject (and it seems I missed the fast that it is<br>
> already was well discussed) and less about doing something particular.<br>
><br>
> But for Sugar Network in particular. I'm sure the core functionality<br>
> that SN is assumed to provide (content/social/support network to connect<br>
> offline and online people) is much more important than any [current]<br>
> trend. And before trying to implement such high level features like<br>
> gamification moments, SN should be mature enough to do its core<br>
> functionality on reliable basis.<br>
><br>
> The problem with gammification (as was already mentioned), it is just<br>
> one of possible ways and have its own props and contras. And it will be<br>
> more useful to design SN in the way that there is core functionality<br>
> and a bunch of high level solutions that implement one of education<br>
> metaphor.<br>
><br>
> In fact, there is already such model when there is a SN server and<br>
> it is possible to implement any client application. But I think it will<br>
> be more useful to have default client application that provides only<br>
> core functionality (i.e., pure technical possibility without forcing<br>
> particular model). As a useful addition, such default client application<br>
> might support applying a kind of skins on top of it to implement<br>
> particular education metaphor (I guess it will be useful during the<br>
> educational process to switch between several models).<br>
><br>
> --<br>
> Aleksey<br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="HOEnZb"></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> IAEP -- It's An Education Project (not a laptop project!)<br>
> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Laura V.<br>
I&D SomosAZUCAR.Org<br>
<br>
@Lima 9898-1111-7<br>
Skype acaire<br>
IRC kaametza<br>