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

Laura Vargas laura en somosazucar.org
Jue Sep 21 10:20:27 EDT 2017

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
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!
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <http://lists.sugarlabs.org/archive/sugar-sur/attachments/20170921/b5a542e8/attachment.html>

Más información sobre la lista de distribución sugar-sur