[sugar-sur] [Sugar-devel] [DESIGN] Re: [IAEP] Sugar Design Meeting/Reunión 21 September at 11 PM UTC IRC Sugar Meeting [DESIGN]

[Laura Vargas]

Thank you all that were present for the reactivation meeting for the Sugar
Labs Design Team.

Gracias a todos los que estuvieron presentes para la reactivación del
equipo de Diseño de Sugar Labs.

James, Tony

Thanks for your feedback.

After yesterday 's meeting am trying to understand the current process for
design ideas to become Sugar features.

I see many ideas from 2012 at
https://wiki.sugarlabs.org/go/Design_Team/Proposals and not design features
like "3G_Support" on the https://wiki.sugarlabs.org/go/Features

Let's say for example a teacher on field suggests we should make
downloading new activities easy and doable from the Sugar User Interface.
What should the teacher do with his/her idea?

Thanks for helping me understand.

Regards

Laura V



2017-09-22 0:04 GMT-05:00 Tony Anderson <tony_anderson en usa.net>:

> Laura
>
> The first example appears to be generally PC related and have nothing to
> do with Sugar specifically. I don't see any need to abandon Sugar.
> The Google translation of the second unfortunately seems like a rant and
> to have no specific proposal.
>
> What I think you need to convince us that there is a problem that needs to
> be solved is to identify the problems and what you would consider
> acceptable as
> a solution.
>
> Do you want to simplify the collaboration UI? Do you want to simplify the
> method to switch between Gnome and Sugar? Do you want to make backup of the
> Journal more meaningful? Do you want to modify the recent addition of
> projects to the Journal interface?
>
> So far I have seen nothing about Sugar that even suggests what you
> consider the problems with Sugar to be.
>
> Tony
>
>
> On 09/21/2017 03:40 PM, Laura Vargas wrote:
>
>
>
> 2017-09-21 10:09 GMT-05:00 Tony Anderson <tony en olenepal.org>:
>
>> Could you provide an example of a problem with the UI or UX that requires
>> improvement and could you propose a better way to handle it?
>>
>>
> I like to think this team will deal with several* UI an UX upgrading*
> *opportunities* for Sugar and Sugar-Web.
>
> UI and UX Sugar and Sugar-Web Design meetings are proposed as a continuous
> set of weekly meetings for open dialog,. drafting proposals and
> coordination events of volunteers.
>
> To integrate community is an important step to secure evolving design
> during the libre software appropriation cycle.
>
> I agree, we should identify specific requirements and/or successful design
> experiences:
>
> [Example 1] One of many good examples we shall review is the Obvious User
> Interface "OUI" Proposal By David Brown
> <https://3fc9298e-a-62cb3a1a-s-sites.googlegroups.com/site/djhbrown2/oui.pdf?attachauth=ANoY7cobW-oPdBQQLRXYoMaPM_BqO2hHLpawQ1KgyNMINUUtqLsy8iAzNfRcFC9lH791MpuFxmkaFU-hw44FN3w4zP918OZYu4YDPoLSs9X3YfcuBz-XMYQVNqCeYL1Y8Jff22E7vqqtCI3lDJBC_sxowmSju-uCQeSE8Y3PnuwaIprqfzrsEYsTgVf9pQNbFcv2jGzlqNmC&attredirects=0>.
> Although it lacks of mock-ups, he makes a clear description on how to
> upgrade the Sugar UI or/and the UX.
>
> On his implementation Suggestions David proposes: "Oui could be
> implemented as the skin of an existing operating system that already has
> automatic application search and installation mechanisms so that new tools
> can be added to the Library effortlessly by the user, without needing to
> recourse to a terminal shell".
>
> I think is logic and long time due.
>
> This is feature was part of the "System Design" of the Hexoquinasa - Sugar
> Network project back on 2011 and current version was first implemented by
> Aleksey Lim and Sebastian Silva latter on. By lighting or un-lighting the
> moon icon placed within each activity/context's space, a user with network
> connection would install/uninstall the Activity.
>
> Please find attached basic statistics of this feature's use since deployed
> 2014-2017 and a second chart for 2017 only.
>
> [Example 2] Another important review and suggested course of action was
> share today by Leonel Guillen in Spanish:
>
> "Completamente de acuerdo con vos, el problema que ha tenido sugar, es que
> no se ha visualizado como lo que es, una gama de oportunidades para la
> educación. y no un software para olpc. La mayoría de aplicativos que cuenta
> Sugar tienen un gran valor pero se ve limitada a la hora que lo asocias a
> un hardware, en cambio debería ya existir  el SUGAR EDUCATION, como
> distribución LINUX enfocada a que, no me importa tu "tarro", me interesa la
> educación. y así poder llegar a más regiones bajo el ideal de una
> distribución para la educación primaria."
> ​
> Here Leonel suggests us to visualize Sugar as a "Set of opportunities for
> Education". He specifically suggests us to deliver SUGAR EDUCATION as a
> GNULinux generic distribution.
>
> I expect beautiful minds to join the Design meetings.
>
> Best
>
> Laura
>
> SugarLabs has decided to participate in GCI which gives us potential
>> resources to tackle any of these problems which can be specifically
>> identified.
>>
>
> +1
>
>
>>
>> Tony
>>
>>
>> On 09/21/2017 10:20 AM, Laura Vargas wrote:
>>
>> Good day James,
>>
>> Thank you for the feedback and the instructions.
>>
>> 2017-09-19 21:04 GMT-05:00 James Cameron <quozl en laptop.org>:
>>
>>> For the proposed agenda [1];
>>>
>>> a.  Upgrading Sugar UI; could you please be more specific about what
>>> you want the design team to do?  This will encourage participation,
>>> although it looks like one of the design team may be challenged by the
>>> date you have chosen.
>>>
>>
>> Sugar Labs community has made several efforts to keep Sugar development
>> packages up to date. Unfortunately (for users) the design of the user
>> interface (UI) and the care for the user experience (UX) has not been
>> significantly improved over the years. For 5 years, the Sugar design
>> team has been dormant.
>>
>> This is the trend I plan to reverse.
>>
>> Sugar Labs needs an active Design Team taking care of Sugar UI and UX (affective
>> aspects of usage).
>>
>>
>> *My proposal is to reactivate the Sugar Design Team and lead it to an
>> upgraded Sugar User Interface and Sugar User Experience. *
>>
>> Our main focus needs to be maximizing Sugar and Sugar Web usability
>> (understanding usability as the degree to which Sugar can be used to
>> achieve quantified objectives with effectiveness, efficiency, and
>> satisfaction in a quantified context of use).
>>
>> Today's meeting will be a first exploration of who is interested in this
>> matter and how we can all work together.
>>
>> I'll try to call for a weekly Sugar Team design meeting.
>>
>>
>>> b.  Elimination of gender selection [2]; remove this agenda item, as
>>> it is not a design issue.  There is already reasonable consensus that
>>> this should be eliminated and left as a GSetting for any deployment
>>> that needs the feature, so could you please make a pull request for
>>> code review?  I never did like it myself, but Gonzalo and Walter had a
>>> customer require it.  That customer no longer uses Sugar.
>>>
>>
>> Where the Sugar User Experience starts is totally part of the Sugar User
>> Experience design.
>>
>> Design is not just about eliminating here and there,  we need to rethink
>> the whole experience from start to end so that children really benefit from
>> the Sugar and/or Sugar Web experience.
>>
>> That said for this case, I plan to follow your procedure instructions.
>>
>>
>>> c.  Modify main icons; remove this agenda item, as it is not a design
>>> issue.  As a patch already exists, please port it to master branch,
>>> prepare it as a pull request for review and merging.  Being able to
>>> change icon shape as well as colour would be a great improvement.
>>>
>>
>> How the Sugar UI looks like is also part of the Sugar Experience design.
>>
>> I'll keep this one also in the agenda just because we need to be open to
>> other proposals for the "by default" main icon (s) and/or the logic to
>> define the initial icon and define curse of action and responsible parties
>> to make the calls.
>>
>>
>>>
>>> Please also add a [DESIGN] tag to the subject, which is part of our
>>> mailing list policy for sugar-devel@ [3].  By omitting the tag, some
>>> design team members may have missed your meeting announcement, and
>>> this would be unfair to them.
>>>
>>> Thanks.
>>>
>>
>> I did.
>>
>> Again, thanks for your feedback.
>>
>>
>>>
>>>
>>>
>>> References:
>>>
>>> 1.  https://wiki.sugarlabs.org/go/Design_Team/Meetings
>>> 2.  https://github.com/sugarlabs/sugar/issues/770
>>> 3.  http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>> --
>>> James Cameron
>>> http://quozl.netrek.org/
>>>
>>
>>
>>
>> --
>> Laura V.
>> * I&D SomosAZUCAR.Org*
>>
>> “Solo la tecnología libre nos hará libres.”
>> ~ L. Victoria
>>
>> Happy Learning!
>> #LearningByDoing
>> #Projects4good
>> #IDesignATSugarLabs
>> #WeCanDoBetter
>>
>>
>> _______________________________________________
>> Sugar-devel mailing listSugar-devel en lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel en lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>
>
> --
> Laura V.
> * I&D SomosAZUCAR.Org*
>
> “Solo la tecnología libre nos hará libres.”
> ~ L. Victoria
>
> Happy Learning!
> #LearningByDoing
> #Projects4good
> #IDesignATSugarLabs
> #WeCanDoBette
>
>
> _______________________________________________
> Sugar-devel mailing listSugar-devel en lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel en lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>


-- 
Laura V.
* I&D SomosAZUCAR.Org*

“Solo la tecnología libre nos hará libres.”
~ L. Victoria

Happy Learning!
#LearningByDoing
#Projects4good
#IDesignATSugarLabs
#WeCanDoBetter
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <http://lists.sugarlabs.org/archive/sugar-sur/attachments/20170922/645281eb/attachment-0001.html>